I have a little situation... I installed the compat32 stuff and now I have to upgrade ghc and stuff and when I try compiling ghc it says this:

checking for path to top of build tree... /tmp/SBo/ghc-7.8.4
Build platform inferred as: x86_64-unknown-linux
Host platform inferred as: x86_64-unknown-linux
Target platform inferred as: x86_64-unknown-linux
GHC build : x86_64-unknown-linux
GHC host : x86_64-unknown-linux
GHC target : x86_64-unknown-linux
checking for perl... /usr/bin/perl
checking for a BSD-compatible install... /bin/ginstall -c
checking whether ln -s works... yes
checking for gsed... sed
checking for gcc... /usr/bin/gcc
checking for ld... /usr/bin/ld
checking for gcc... /usr/bin/gcc
checking whether the C compiler works... no
configure: error: in `/tmp/SBo/ghc-7.8.4':
configure: error: C compiler cannot create executables
See `config.log' for more details

What can I do? It says unknown linux... dont know why... Can anyone tell me what to do? Thanks.

Cheers
(=
Dumdadum

Your issue is not the "x86_64-unknown-linux" - in fact that is pretty common when compiling software. Your real issue can be found in that file "config.log" which was created by the configure command. You will find it in the same directory as "configure".
Open "config.log" in a text editor, find the string "cannot create" and the actual issue will be found in the lines directly above.

You did read http://slackbuilds.org/faq/#multilib , yes?

1 members found this post helpful.

Will read right now yes...

I checked the config.log file, and yes alot of info, I dont think I'm smart enough to know what it all means, all I know is that the C compiler doesnt work, or thats what it says in the stuff I posted in the first post...

Thanx, I'll check all that and come back if any questions.

Cheers,
(=
Dumdadum

Ok mainly it says multilib is unsupported...
Or else well I'll check the ghc.Slackbuild script and check the 3 lines...

Really, if I cannot compile any 64bit softwares after I go multilib, thats going to be an issue...

I'll check if it compiles with the 3 lines of the configure part.

Thanks,
Cheers,
(=
Dumdadum

Yup says cannot create executables... And theres also a line that says the C compiler doesnt work...
Ahhh well... I guess the word "unofficial" for the multilib part means you guys are working as hard as you can to make it official. I'll just wait. I'm patient...

Still, why is it that I cannot compile 64bit packages on my multilib... its not a 32 bit package... I dont get it...

Cheers,
(=
Dumdadum

qversion or something like that... I noticed we went from 4.8.5 to 4.8.7 with qt...is there a link to that?


Cheers, I'm looking to make it work...
Dumdadum

Lets say I was to compile ANY package with SBo's scripts, are you telling me its now impossible to compile after you go multilib? Thats odd... Theres really nothing I can do? I dont understand...

Anyways thats for everything. Waiting if any response...

Cheers,
Dumdadum

Well I found a little thing called multilibpkg, dont know who thought of this, but he's a real genius...

Hope this helps a futur Slacker, cuz I dont slack, if you know what I mean.

Cheers (=
Dumdadum

What Alienbob refers to is point 18 in that FAQ. If a package doesn't compile on a multilib system in most cases you just need to add the LDFlag as explained in that specific point.

If you are not able to find the actual issue in that "config.log" file, I suggest you post the contents of that file on a pastebin and I will point it out to you.

The SlackBuilds.org admins are not willing to add multilib support out of the box to the scripts they host. In most cases (but not always) adding the LDFLAGS line will be enough. The "not always" means that the admins would have to test every submission twice: on a stock Slackware64 computer and then once more on a multilib computer. That is just too much work and therefore multilib is "unsupported".

1 members found this post helpful.