LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Slack64 multilib: Xfe "configure error: libFOX-1.6 not found" (https://www.linuxquestions.org/questions/slackware-14/slack64-multilib-xfe-configure-error-libfox-1-6-not-found-755723/)

Compile this 09-16-2009 03:22 PM

Slack64 multilib: Xfe "configure error: libFOX-1.6 not found"
 
I installed the fox-toolkit SlackBuild and tried to run the Xfe SlackBuild and get this error, even though I've clearly installed fox-toolkit beforehand.
Apparently I can't build either of these in a 64-bit environment ("C compiler cannot build executables") so I followed the multilib install guide from Alien's wiki (installing the compatibility packages, switching profile, changing the script's ARCH variable to x86_64, etc) and I get this error no matter what I do.

The exact error:
Code:

checking for fxfindfox in -lFOX-1.6... no
configure: error: "libFOX-1.6 not found"

Anyone know what the problem is? While it's not imperative that I use Xfe, I'd like to at least know why this error is showing and the preventive measures.

EDIT: as it would appear, every package I try to build does this unless I use . /etc/profile.d/32dev.sh beforehand... Pretty sure that should not be the case. Maybe I'm doing something wrong...

Alien Bob 09-16-2009 03:54 PM

You usually get the error "C compiler cannot build executables" on Slackware64 if you have the ARCH value inside the SlackBuild set to anything else than "x86_64".

Eric

Compile this 09-16-2009 04:59 PM

I set the ARCH variable to x86_64, but didn't touch the rest of the script...
This, alone, actually fixed the problem!
I did not have to activate the separate 32dev.sh profile or change LIBDIRSUFFIX to "", which I'm assuming now is only necessary for certain packages, if at all?

Alien Bob 09-16-2009 05:21 PM

Quote:

Originally Posted by Compile this (Post 3685945)
I set the ARCH variable to x86_64, but didn't touch the rest of the script...
This, alone, actually fixed the problem!
I did not have to activate the separate 32dev.sh profile or change LIBDIRSUFFIX to "", which I'm assuming now is only necessary for certain packages, if at all?

The whole circus of source-ing "/etc/profile.d/32dev.sh" and changing LIBDIRSUFFIX is only needed when you want to build 32bit software on a multilib Slackware64. So far, I have only needed to do this for one package: wine.
At some point, you may run into a library dependency that is not covered by the converted Slackware "-compat32" packages, in which case you will be forced to build a 32bit library. But I guess that will be a rare occasion.

The normal way of compiling on a Slackware64 system would be to create 64bit binaries. Why would you want to build 32bit binaries on a 64bit Slackware? Only if you are forced to use them (because of the need for some closed-source 32bit program whose developers are neglecting their user base).

In all cases (building either 64bit or 32bit binaries) you will have to set ARCH="x86_64".

Eric

Compile this 09-16-2009 05:35 PM

Quote:

Originally Posted by Alien Bob (Post 3685977)
The whole circus of source-ing "/etc/profile.d/32dev.sh" and changing LIBDIRSUFFIX is only needed when you want to build 32bit software on a multilib Slackware64. So far, I have only needed to do this for one package: wine.

Just to experiment around, I decided to try and see if I had to do this with wine.
I just downloaded the SlackBuild and only changed ARCH="x86_64" and it's building in the background!
Now, if it'll work or not, I don't know (since wine takes one year to compile, and could at any point see some kind of error...), but I didn't have to do the two aforementioned steps to get this far. Is my system just weird? :p

Alien Bob 09-16-2009 05:59 PM

If you only changed ARCH to "x86_64" you're now compiling "wine64" which is entirely possible.
However - this particular binary version of wine will only be able to run 64bit Windows applications. I don't know if that was your goal.

If you want to build the version of wine that is able to run 32bit Windows applications, you will have to use the
Code:

. /etc/profile.d/32dev.sh
command before you start the SlackBuild ...

Eric

Compile this 09-16-2009 06:06 PM

Didn't know that.
Haha, I'm not that educated yet, but I'm learning!
Cleared some things up, though..
Thanks


All times are GMT -5. The time now is 08:15 PM.