[SOLVED] multilib enable produces SBopkg failures "gcc is unable to produce executables"
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.
multilib enable produces SBopkg failures "gcc is unable to produce executables"
Since upgrading my quite fresh Slackware 14.2 64 to multilib, following the Quick and Dirty instructions to the letter (I think), I cannot compile anything with gcc.
I get:
Code:
gcc is unable to create an executable file.
With everything in sbopkg.
I have gcc and glibc versions 5.5.0 & 2.23 multilib.
The build/config.log says this:-
86 configure:3526: gcc -V >&5
87 gcc: error: unrecognized command line option '-V'
88 gcc: fatal error: no input files
89 compilation terminated.
90 configure:3537: $? = 1
91 configure:3526: gcc -qversion >&5
92 gcc: error: unrecognized command line option '-qversion'
93 gcc: fatal error: no input files
94 compilation terminated.
95 configure:3537: $? = 1
96 configure:3557: checking whether the C compiler works
97 configure:3579: gcc -O2 -fPIC conftest.c >&5
98 gcc: error trying to exec 'as': execvp: No such file or directory
99 configure:3583: $? = 1
100 configure:3621: result: no
101 configure: failed program was:
102 | /* confdefs.h */
103 | #define PACKAGE_NAME "atomicparsley"
104 | #define PACKAGE_TARNAME "atomicparsley"
105 | #define PACKAGE_VERSION "0.9.6"
106 | #define PACKAGE_STRING "atomicparsley 0.9.6"
107 | #define PACKAGE_BUGREPORT "http://bitbucket.org/wez/atomicparsley/issues/new/"
108 | #define PACKAGE_URL ""
109 | #define PACKAGE "atomicparsley"
110 | #define VERSION "0.9.6"
111 | /* end confdefs.h. */
112 |
113 | int
114 | main ()
115 | {
116 |
117 | ;
118 | return 0;
119 | }
120 configure:3626: error: in `/tmp/SBo/wez-atomicparsley-da2f6e4fc120':
121 configure:3628: error: C compiler cannot create executables
122 See `config.log' for more details
Looks like something's up with gcc. Try these two commands
Code:
which as
ldd /usr/bin/gcc |grep found
If either give suspicious outputs, reinstall gcc and try again.
EDIT: With Compat32, there's a bunch of gcc and glibc packages which have 64 bit packages with 32bit compatibility libs. Did you install those? If not, install what you need from them with upgradepkg --reinstall --install-new
Last edited by business_kid; 02-24-2020 at 04:15 AM.
Looks like something's up with gcc. Try these two commands
Code:
which as
ldd /usr/bin/gcc |grep found
If either give suspicious outputs, reinstall gcc and try again.
EDIT: With Compat32, there's a bunch of gcc and glibc packages which have 64 bit packages with 32bit compatibility libs. Did you install those? If not, install what you need from them with upgradepkg --reinstall --install-new
Those two commands tell me "as" is not in my path and there is no 'found' for /usr/bin/gcc.
But I did it again anyway, and those two commands gave the same thing.
A slackpkg file-search for "as" showed some weird things at the bottom of the list, offering several packages to upgrade to a lower version, so they come back again on the next search.
But binutils was there and when I upgraded it to whichever version it was no longer on the list and has provided the necessary as binary and everything is working again.
Thanks for your help.
Last edited by Pipeline79; 02-24-2020 at 05:52 AM.
Those two commands tell me "as" is not in my path and there is no 'found' for /usr/bin/gcc.
The 'found' is part of 'not found' so that's a good thing. /usr/bin/as should be part of the binutils package so install that if it's not there, or reinstall it. It should be in the d/ directory on the dvd.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
