SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello Everyone,
I tried to compile the following programs on slackware 64 current.
1).Hard Info 0.5.1
report.o:/tmp/SBo/hardinfo-0.5.1/report.c:195: more undefined references to `strend' follow
collect2: error: ld returned 1 exit status
Makefile:24: recipe for target 'all' failed
make: *** [all] Error 1
I tried to compile the following programs on slackware 64 current.
1).Hard Info 0.5.1
report.o:/tmp/SBo/hardinfo-0.5.1/report.c:195: more undefined references to `strend' follow
collect2: error: ld returned 1 exit status
Makefile:24: recipe for target 'all' failed
make: *** [all] Error 1
you cutted the log before the error: try posting more line of the log.
eventually post it all on pastebin and then post the link to it here.
FYI, this builds fine here on a slackware64-current full clean install.
Hello Everyone,
I tried to compile the following programs on slackware 64 current.
1).Hard Info 0.5.1
report.o:/tmp/SBo/hardinfo-0.5.1/report.c:195: more undefined references to `strend' follow
collect2: error: ld returned 1 exit status
Makefile:24: recipe for target 'all' failed
make: *** [all] Error 1
Debian adds -std=gnu89 to the Makefile.in file, like this:
maybe it's me, but here on slackware64-current the SlackBuild for this built fine without the need to specify -std=gnu89.
EDIT: ops, sorry for the noise, I missed that David already patched it for this in our repository http://cgit.ponce.cc/slackbuilds/commit/?h=libewf
please use this to build your stuff before reporting issues in this thread.
please post the link to the full output from running the SlackBuild (this applies also to dolphin-emu).
consider also that, reading some of your previous topics, you have some custom stuff installed in /usr/local that in this particular case happens to be an optional dependency of doplhin-emu (I am talking about wxGTK) and that is also included in dolphin-emu's sources themself as an external library: SBo supports building against the dependencies we have in our repository on a clean slackware full installation, we would go crazy trying to support any setup out there that we have not tested ourself for 5000+ scripts.
that applies also on this humble, unofficial, attempt to let SBo things build on current, I'm sorry.
no need to say it but if someone else don't agree with this policy and wants to support also non-standard setups is free to do it.
the only suggestion I can give you is to try building this also on a full clean installation and report eventual errors that happen there.
EDIT: I tested it myself and the version on SBo doesn't build on current.
I tried to patch the SlackBuild to build from a git snapshot (official sources are there now, google code subversion is not updated anymore) and it seems to work; you can find it in a dedicated branch http://cgit.ponce.cc/slackbuilds/commit/?h=dolphin-emu
if the maintainer has a better fix for it to build on current he's welcome! (this applies always)
I did not do the libewf paste bin because you said it's fixed.
And about my previous posts i dont think that should matter because
this a pure 64 slackware build with just SBo compile with slackware
current DEC 16 2015.
BTW: I checked directories in /usr/local and they are empty.
Last edited by GreenFireFly; 12-19-2015 at 10:01 AM.
About hardinfo, it needs -fgnu89-inline. I tried to fix it through CFLAGS="$SLKCFLAGS -fgnu89-inline" and also through CC="gcc -fgnu89-inline", but neither solution works, because the configure script is old and inflexible. It should be possible to fix the configure script, but there are at least 160 more SlackBuilds that need fixes at the moment; I'll get back to hardinfo eventually, after I've done all the "easiest" fixes.
Edit: _gin has the answer, thanks!!
Fedora threw hardinfo out of their repo in the middle of last year because it's dead upstream... quitters
(I think -fgnu89-inline might be better than -std=gnu89, but I'm willing to listen to advice on that.)
Last edited by 55020; 12-19-2015 at 10:20 AM.
Reason: Thanks _gin, I should have read the whole thread :)
above I said that I have prepared a patch for the SlackBuild that you can find on SBo.
if you find problems in applying the diff linked, I have now prepared a folder with the already patched SlackBuild files for you to download: download and build from that script using the sources linked in the .info file.
Quote:
I did not do the libewf paste bin because you said it's fixed.
it should have been already fixed if you had used the unsupported repository for current.
let me get this thing clear: the scripts that you can find on the official SBo repository are for Slackware stable so, in many cases, they won't build on current as they are provided.
if you need a repository that already has script patched to build on current, please use this (if you want to see the single patched scripts, there's a list available here) and, as I said before, report issues on this thread only if you have already tried the scripts from there and they won't build on current.
that said, don't expect that *everything* will be patched to work on current as we don't do the job of the scripts maintainers and it's a best-effort thing.
maybe I should start a new topic with a first message in which I clarify these points...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.