Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Hi: I looked in google and searched in LQ, but the combination ARJ - 64 bits - Linux seems to have bad luck. Although the ARJ official page offers no newer then ARJ32. Perhaps if I try to get some other software compatible with the ARJ archive format?
Distribution: pclos2016, Slack14.1 Deb Jessie, + 50+ other Linux OS, for test only.
Would you point to one in particular (tarball) ?
Well, you will get one, if you do like mentioned in your other arj thread,
post # 4.
Comment the line BuildRequires : autoconf
in arj.spec : # BuildRequires : autoconf
( You have no autoconf rpm in your "rpm data base" )
... and automatic patching will happen by $ rpmbuild -bb arj.spec
The build result is in ~rpm*/RPMS/x86_64/
.. and the patched arj in ~rpm*/BUILD/arj-*
Also : # src2pkg arj-3.10.22.tar.gz
.. will automatically include any patches in the same directory.
I.e. src2pkg is the recommended method, if you don't want to use a Slackbuild script.
Here you see the tarball and the .debian.tar (the patch) in the same directory. However,
semoi@darkstar:~/src/test1$ src2pkg arj-3.10.22.tar.gz
Found source archive: arj-3.10.22.tar.gz
Deleting old build files - Done
Creating working directories:
Unpacking source archive - Done
Correcting source permissions - Done
Checking for patches - None found
Skipping configuration: Nothing to be done
Continuing - We found at least one makefile
Compiling sources - Using: 'make'
ERROR! Compiling source code has failed.
This usually happens because of missing libraries, or
badly written Makefiles or configure scripts.
Sorry! No Dependency or Requirements information found.
But you can read 'Checking for patches - None found' in the code block! It's only a matter of making src2pkg know the patch pathname!