[SOLVED] can no longer compile

aikempshall · 02-11-2021, 04:22 AM

I've messed up two of my three VirtualBox guests. All three are running current with the 5.10.14 kernel. They all appear to be OK but on two of them I can't compile anything.

if I try to compile say xdg-dbus-proxy.SlackBuild it fails with

Quote:

checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/home/packages/tmp/SBo/xdg-dbus-proxy-0.1.2':
configure: error: C compiler cannot create executables

The config log contains a bit more information

Quote:

configure:2465: checking whether the C compiler works
configure:2487: gcc -O2 -fPIC conftest.c >&5
configure:2491: $? = 0
configure:2529: result: no
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "xdg-dbus-proxy"
| #define PACKAGE_TARNAME "xdg-dbus-proxy"
| #define PACKAGE_VERSION "0.1.2"
| #define PACKAGE_STRING "xdg-dbus-proxy 0.1.2"
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE_URL ""
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }

Tried this at the command line

Code:

gcc /usr/src/linux-5.10.14/tools/build/feature/test-hello.c -o /tmp/hello

It runs silently returning 0 result code, but doesn't produce any output or create the file /tmp/hello

On the one working machine it creates the output file and generates this output

Quote:

hi

One would have thought that with one working machine and two failing that the problem would be easy to spot. It must be environmental, but what everything appears to be the same.

Thom1b · 02-11-2021, 04:47 AM

Hi,

When glibc-solibs was renamed, I made a mistake. Instead of upgrading glibc-solibs with aaa_glibc-solibs-2.32-x86_64-2 package, I upgraded glibc package, then I can't compile. After fixing that, it works again.
Did you upgrade carefully your packages when glibc-solibs was renamed?

Code:

upgradepkg aaa_elflibs%aaa_libraries-15.0-x86_64-1.txz
upgradepkg glibc-solibs%aaa_glibc-solibs-2.32-x86_64-2.txz

aikempshall · 02-11-2021, 06:29 AM

I've compared the packages on all three machines and they all appear to be the same - names at least. I've got multilib installed wondering whether that's getting in the way somehow. In the area of interest I've got these installed

Quote:

-rw-r--r-- 1 root root 2132 Feb 11 11:29 aaa_base-14.2-x86_64-6
-rw-r--r-- 1 root root 15123 Feb 11 11:29 aaa_glibc-solibs-2.32_multilib-x86_64-2alien
-rw-r--r-- 1 root root 3319 Feb 11 11:30 aaa_libraries-15.0-x86_64-1
-rw-r--r-- 1 root root 14409 Feb 11 11:30 aaa_terminfo-6.2_20201219-x86_64-3
-rw-r--r-- 1 root root 51223 Feb 11 11:30 gcc-10.2.0_multilib-x86_64-3alien
-rw-r--r-- 1 root root 1262 Feb 11 11:30 gcc-brig-10.2.0_multilib-x86_64-3alien
-rw-r--r-- 1 root root 45811 Feb 11 11:30 gcc-g++-10.2.0_multilib-x86_64-3alien
-rw-r--r-- 1 root root 55113 Feb 11 11:30 gcc-gdc-10.2.0_multilib-x86_64-3alien
-rw-r--r-- 1 root root 2526 Feb 11 11:30 gcc-gfortran-10.2.0_multilib-x86_64-3alien
-rw-r--r-- 1 root root 267336 Feb 11 11:30 gcc-gnat-10.2.0_multilib-x86_64-3alien
-rw-r--r-- 1 root root 21668 Feb 11 11:30 gcc-go-10.2.0_multilib-x86_64-3alien
-rw-r--r-- 1 root root 769 Feb 11 11:30 gccmakedep-1.0.3-noarch-3
-rw-r--r-- 1 root root 2341 Feb 11 11:30 gcc-objc-10.2.0_multilib-x86_64-3alien
-rw-r--r-- 1 root root 33487 Feb 11 11:30 glibc-2.32_multilib-x86_64-2alien
-rw-r--r-- 1 root root 519239 Feb 11 11:31 glibc-i18n-2.32_multilib-x86_64-2alien
-rw-r--r-- 1 root root 1236 Feb 11 11:31 glibc-profile-2.32_multilib-x86_64-2alien
-rw-r--r-- 1 root root 71542 Feb 11 11:31 glibc-zoneinfo-2021a-noarch-1

I've got an untainted machine which I can use to see if I get the same problem.

aikempshall · 02-11-2021, 11:56 AM

Tried piecemeal replacement of the aaa, glibc and gcc series. Also uninstalled the various alienbob packages and reinstalled the equivalent from slackware64. Still couldn't get gcc to work.

As I'd spent several hours on this decided to do a reinstall. The system was already up to date before i did the reinstall, so I just deleted all incoming .new config files. Didn't have to make a new initrd.gz or grub2 config file.

Rebooted the system. Everything working including gcc.

It was only one machine effected. I'll mark this as solved with cause unknown, but it was probably due to something I'd done,

zhl · 02-11-2021, 03:20 PM

Just got the similar error on built 3proxy from sbo,

Code:

make[4]: gcc: Permission denied.

Someone figured out it maybe a bug for gnulib, https://stackoverflow.com/a/61505892.
And this bug is special for make 4.3 version, https://savannah.gnu.org/bugs/?57962.
Downgrade make to 4.2, everything works again.

Ps. For current32.

marav · 02-11-2021, 06:14 PM

Quote:

Originally Posted by zhl

Just got the similar error on built 3proxy from sbo,

Code:

make[4]: gcc: Permission denied.

Someone figured out it maybe a bug for gnulib, https://stackoverflow.com/a/61505892.
And this bug is special for make 4.3 version, https://savannah.gnu.org/bugs/?57962.
Downgrade make to 4.2, everything works again.

Ps. For current32.

Maybe this ?

Code:

You have a directory named gcc somewhere in one of the directories in your PATH, 
before the one that contains the gcc binary.

This is a bug in a module in the GNU gnulib library, that GNU make uses to locate content on the PATH. 
See https://savannah.gnu.org/bugs/?57962

https://stackoverflow.com/questions/...ied-arch-linux

zhl · 02-11-2021, 06:46 PM

Cannot confirm, if change "CC = gcc" to "CC = /usr/bin/gcc" in Makefile.Linux, building will go smoothly. However the "gcc" directory located in /usr/libexec which cannot be excluded from PATH.

marav · 02-11-2021, 07:00 PM

Quote:

Originally Posted by zhl

Cannot confirm, if change "CC = gcc" to "CC = /usr/bin/gcc" in Makefile.Linux, building will go smoothly. However the "gcc" directory located in /usr/libexec which cannot be excluded from PATH.

I don't have any /usr/libexec in my PATH ( both user & root )
And I also don't have any problem to compile

marav · 02-11-2021, 07:29 PM

I've tested, with a fresh install slackware64-14.2

no /usr/libexec in the PATH
you've probably added it, so you can safely remove it from your PATH, as long as you don't personally need it

zhl · 02-11-2021, 07:58 PM

OK, removing /usr/libexec located in ~/.bashrc.
I don't know when it was added to PATH, this slackware was installed 10 years ago, and upgraded from 14.0 to current some years later.