open-vm-tools fails to find a working C compiler on Leap 15.5, but builds fine on SLES 15SP5?
Hi all, I prepared an update for open-vm-tools last week, checked the SR today and found something strange. My update as well as the older version in Virtualization:VMware are building fine for SLES15 SP5, but fail for Leap 15.5. It also fails for SLES15 SP4. The error is that configure does not find the C compiler (or rather it does not work).
[ 47s] + ./configure --host=x86_64-suse-linux-gnu --build=x86_64-suse-linux-gnu --program-prefix= --disable-dependency-tracking --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/lib --localstatedir=/var --sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info --disable-dependency-tracking --without-kernel-modules --without-root-privileges --with-x --disable-dependency-tracking --with-gtk3 --enable-xmlsec1 --with-udev-rules-dir=/usr/lib/udev/rules.d --enable-resolutionkms --enable-servicediscovery --with-fuse=3 --enable-salt-minion --disable-static --enable-containerinfo=yes [ 47s] configure: WARNING: unrecognized options: --enable-xmlsec1 [ 47s] checking build system type... x86_64-suse-linux-gnu [ 47s] checking host system type... x86_64-suse-linux-gnu [ 47s] checking for x86_64-suse-linux-gnu-gcc... no [ 47s] checking for gcc... gcc [ 48s] checking whether the C compiler works... no [ 48s] configure: error: in `/home/abuild/rpmbuild/BUILD/open-vm-tools-12.5.0/open-vm-tools': [ 48s] configure: error: C compiler cannot create executables [ 48s] See `config.log' for more details
I compared the packages related to gcc and they looked the same on both builds. (The xmlsec1 error seems unrelated) Is there some other OBS magic involved, that is different on 15.5 and SP5? Kind Regards, Johannes
Hi Johannes, Am 15.10.24 um 11:48 schrieb Johannes Kastl:
[ 48s] configure: error: in `/home/abuild/rpmbuild/BUILD/open-vm-tools-12.5.0/open-vm-tools': [ 48s] configure: error: C compiler cannot create executables [ 48s] See `config.log' for more details
You really should do that. Check config.log. It is a bit hard to dig through but it usually somewhere in the middle of the log file shows the error. Maybe some path is set differently or something like that.
I compared the packages related to gcc and they looked the same on both builds.
exact same versions? -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman
Hi Seife, On 15.10.24 16:31 Stefan Seyfried wrote:
Am 15.10.24 um 11:48 schrieb Johannes Kastl:
[ 48s] configure: error: in `/home/abuild/rpmbuild/BUILD/open-vm-tools-12.5.0/open-vm-tools': [ 48s] configure: error: C compiler cannot create executables [ 48s] See `config.log' for more details
You really should do that. Check config.log. It is a bit hard to dig through but it usually somewhere in the middle of the log file shows the error.
Will do so.
Maybe some path is set differently or something like that.
Yes, that is my guess. But appears to happen outside the package, if I did not overlook an %if statement...
I compared the packages related to gcc and they looked the same on both builds. exact same versions?
Hmmm, the one thing that I found is this: libgcc_s1-13.3.0+git8781-150000.1.12.1 vs. libgcc_s1-12.2.1+git416-150000.1.7.1 Leap 15.5 has the lower version. Adding a constraint for >= 13.3 says it is unresolvable on Leap 15.5:
unresolvable: nothing provides libgcc_s1 >= 13.3 (got version 7.5.0+r278197-4.30.1 provided by libgcc_s1-gcc7) (got version 8.2.1+r264010-150000.1.6.4 provided by libgcc_s1-gcc8) (got version 10.4.0+git2794-150000.1.9.1 provided by libgcc_s1-gcc10) (got version 12.2.1+git416-150000.1.7.1)
Kind Regards, Johannes
Moin, On Tue, 15 Oct 2024, 18:46:07 +0200, Johannes Kastl wrote:
Hi Seife,
On 15.10.24 16:31 Stefan Seyfried wrote:
Am 15.10.24 um 11:48 schrieb Johannes Kastl:
[ 48s] configure: error: in `/home/abuild/rpmbuild/BUILD/open-vm-tools-12.5.0/open-vm-tools': [ 48s] configure: error: C compiler cannot create executables [ 48s] See `config.log' for more details
You really should do that. Check config.log. It is a bit hard to dig through but it usually somewhere in the middle of the log file shows the error.
Will do so.
Maybe some path is set differently or something like that.
Yes, that is my guess. But appears to happen outside the package, if I did not overlook an %if statement...
I compared the packages related to gcc and they looked the same on both builds. exact same versions?
Hmmm, the one thing that I found is this:
libgcc_s1-13.3.0+git8781-150000.1.12.1 vs. libgcc_s1-12.2.1+git416-150000.1.7.1
Leap 15.5 has the lower version.
Adding a constraint for >= 13.3 says it is unresolvable on Leap 15.5:
Build against openSUSE:Leap:15.5:Update instead of plain openSUSE:Leap:15.5. If you need a newer compiler you must use the updated tools, even if this results in a higher rebuild frequency. But again, it's probably most interesting to find out why configure believes gcc cannot create executables!
unresolvable: nothing provides libgcc_s1 >= 13.3 (got version 7.5.0+r278197-4.30.1 provided by libgcc_s1-gcc7) (got version 8.2.1+r264010-150000.1.6.4 provided by libgcc_s1-gcc8) (got version 10.4.0+git2794-150000.1.9.1 provided by libgcc_s1-gcc10) (got version 12.2.1+git416-150000.1.7.1)
Kind Regards, Johannes
HTH, cheers. l8er manfred
On 15.10.24 16:31 Stefan Seyfried wrote:
Hi Johannes,
Am 15.10.24 um 11:48 schrieb Johannes Kastl:
[ 48s] configure: error: in `/home/abuild/rpmbuild/BUILD/open-vm-tools-12.5.0/open-vm-tools': [ 48s] configure: error: C compiler cannot create executables [ 48s] See `config.log' for more details
You really should do that. Check config.log. It is a bit hard to dig through but it usually somewhere in the middle of the log file shows the error.
Here it is:
configure:3343: checking for gcc configure:3359: found /usr/bin/gcc configure:3370: result: gcc configure:3599: checking for C compiler version configure:3608: gcc --version >&5 gcc (SUSE Linux) 7.5.0 Copyright (C) 2017 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
configure:3619: $? = 0 configure:3608: gcc -v >&5 Using built-in specs. Reading specs from /usr/lib64/gcc/x86_64-suse-linux/7/defaults.spec COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib64/gcc/x86_64-suse-linux/7/lto-wrapper OFFLOAD_TARGET_NAMES=hsa:nvptx-none Target: x86_64-suse-linux Configured with: ../configure --prefix=/usr --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64 --enable-languages=c,c++,objc,fortran,obj-c++,ada,go --enable-offload-targets=hsa,nvptx-none, --without-cuda-driver --enable-checking=release --disable-werror --with-gxx-include-dir=/usr/include/c++/7 --enable-ssp --disable-libssp --disable-libvtv --disable-libcc1 --disable-plugin --with-bugurl=https://bugs.opensuse.org/ --with-pkgversion='SUSE Linux' --with-slibdir =/lib64 --with-system-zlib --enable-libstdcxx-allocator=new --disable-libstdcxx-pch --enable-version-specific-runtime-libs --with-gcc-major-version-only --enable-linker-build-id --enable-linux-futex --enable-gnu-indirect-function --program-suffix=-7 --w ithout-system-libunwind --enable-multilib --with-arch-32=x86-64 --with-tune=generic --build=x86_64-suse-linux --host=x86_64-suse-linux Thread model: posix gcc version 7.5.0 (SUSE Linux) configure:3619: $? = 0 configure:3608: gcc -V >&5 gcc: error: unrecognized command line option '-V' gcc: fatal error: no input files compilation terminated. configure:3619: $? = 1 configure:3608: gcc -qversion >&5 gcc: error: unrecognized command line option '-qversion'; did you mean '--version'? gcc: fatal error: no input files compilation terminated. configure:3619: $? = 1 configure:3639: checking whether the C compiler works configure:3661: gcc -fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Wno-unused-local-typedefs -Wno-unused-but-set-variable -Wno-deprec ated-declarations -Wno-sizeof-pointer-memaccess -Wno-cpp -fPIE -pie -ltirpc -lgrpc -labsl_synchronization -labsl_log_internal_check_op -labsl_log_internal_nullguard -labsl_log_internal_message conftest.c >&5 /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: cannot find -labsl_synchronization: No such file or directory /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: cannot find -labsl_log_internal_check_op: No such file or directory /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: cannot find -labsl_log_internal_nullguard: No such file or directory /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: cannot find -labsl_log_internal_message: No such file or directory collect2: error: ld returned 1 exit status configure:3665: $? = 1 configure:3703: result: no configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "open-vm-tools" | #define PACKAGE_TARNAME "open-vm-tools" | #define PACKAGE_VERSION "12.5.0" | #define PACKAGE_STRING "open-vm-tools 12.5.0" | #define PACKAGE_BUGREPORT "open-vm-tools-devel@lists.sourceforge.net" | #define PACKAGE_URL "" | /* end confdefs.h. */ | | int | main () | { | | ; | return 0; | } configure:3708: error: in `/home/abuild/rpmbuild/BUILD/open-vm-tools-12.5.0/open-vm-tools': configure:3710: error: C compiler cannot create executables See `config.log' for more details
I am not a GCC expert, but my guess would be the "ld: cannot find..." errors. Not sure how to solve those? Kind Regards, Johannes Kind Regards, Johannes
On Okt 16 2024, Johannes Kastl wrote:
I am not a GCC expert, but my guess would be the "ld: cannot find..." errors. Not sure how to solve those?
It's verbatim in your spec file: export LDFLAGS="-pie -ltirpc -lgrpc -labsl_synchronization -labsl_log_internal_check_op -labsl_log_internal_nullguard -labsl_log_internal_message" -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."
Hi Andreas, On 16.10.24 10:52 Andreas Schwab wrote:
On Okt 16 2024, Johannes Kastl wrote:
I am not a GCC expert, but my guess would be the "ld: cannot find..." errors. Not sure how to solve those?
It's verbatim in your spec file:
export LDFLAGS="-pie -ltirpc -lgrpc -labsl_synchronization -labsl_log_internal_check_op -labsl_log_internal_nullguard -labsl_log_internal_message"
Why is this working on SLE15 SP5 and fails on Leap 15.5? Or is this caused by not building against Leap:Updates? I thought base packages should be consistent between SLE and Leap? Kind Regards, Johannes
On Wednesday 2024-10-16 17:22, Johannes Kastl wrote:
Hi Andreas, On 16.10.24 10:52 Andreas Schwab wrote:
On Okt 16 2024, Johannes Kastl wrote:
I am not a GCC expert, but my guess would be the "ld: cannot find..." errors. Not sure how to solve those?
It's verbatim in your spec file:
export LDFLAGS="-pie -ltirpc -lgrpc -labsl_synchronization -labsl_log_internal_check_op -labsl_log_internal_nullguard -labsl_log_internal_message"
Why is this working on SLE15 SP5 and fails on Leap 15.5?
configure:3661: gcc -fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Wno-unused-local-typedefs -Wno-unused-but-set-variable -Wno-deprecated-declarations -Wno-sizeof-pointer-memaccess -Wno-cpp -fPIE -pie -ltirpc -lgrpc -labsl_synchronization -labsl_log_internal_check_op -labsl_log_internal_nullguard -labsl_log_internal_message conftest.c >&5 /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: cannot find -labsl_synchronization: No such file or directory /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: cannot find -labsl_log_internal_check_op: No such file or directory
Seems pretty obvious that ABSL is not installed (BuildRequired) or that ABSL (if it is installed) is so old that it does not contain libabsl_log_internal_check_op.so yet.
On Okt 16 2024, Jan Engelhardt wrote:
On Wednesday 2024-10-16 17:22, Johannes Kastl wrote:
configure:3661: gcc -fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Wno-unused-local-typedefs -Wno-unused-but-set-variable -Wno-deprecated-declarations -Wno-sizeof-pointer-memaccess -Wno-cpp -fPIE -pie -ltirpc -lgrpc -labsl_synchronization -labsl_log_internal_check_op -labsl_log_internal_nullguard -labsl_log_internal_message conftest.c >&5 /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: cannot find -labsl_synchronization: No such file or directory /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: cannot find -labsl_log_internal_check_op: No such file or directory
Seems pretty obvious that ABSL is not installed (BuildRequired) or that ABSL (if it is installed) is so old that it does not contain libabsl_log_internal_check_op.so yet.
It's the first: $ osc buildinfo Virtualization:VMware open-vm-tools openSUSE_Leap_15.5 x86_64 | grep -c abseil 0 -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."
Hi Jan, On 16.10.24 17:44 Jan Engelhardt wrote:
Seems pretty obvious that ABSL is not installed (BuildRequired) or that ABSL (if it is installed) is so old that it does not contain libabsl_log_internal_check_op.so yet.
Thanks for your answer. I can of course add this dependency. My question remains: Why is this different between SLE15SP5 and Leap 15.5? Shouldn't the same packages pull in the same dependencies on both? And shouldn't "base" packages be the same in both? Should the project build against Leap:Updates? If so, why does SUSE:SLE-15-SP5:GA have those package updates while openSUSE:Leap:15.5 does not? Kind Regards, Johannes
On Wednesday 2024-10-16 18:13, Johannes Kastl wrote:
On 16.10.24 17:44 Jan Engelhardt wrote:
Seems pretty obvious that ABSL is not installed (BuildRequired) or that ABSL (if it is installed) is so old that it does not contain libabsl_log_internal_check_op.so yet.
Thanks for your answer. I can of course add this dependency.
My question remains: Why is this different between SLE15SP5 and Leap 15.5?
Usually: accidental inclusion through some other dependency. You can make a local build for Tumbleweed (`osc build`), then abort it midway, enter the chroot it had created (`osc chroot`) and then attempt to remove absl (rpm -qa 'libasbl*', rpm -e libabsl2024xyz), the latter of which will fail and tell how it came in.
On 16.10.24 18:29 Jan Engelhardt wrote:
On Wednesday 2024-10-16 18:13, Johannes Kastl wrote:
On 16.10.24 17:44 Jan Engelhardt wrote:
Seems pretty obvious that ABSL is not installed (BuildRequired) or that ABSL (if it is installed) is so old that it does not contain libabsl_log_internal_check_op.so yet.
Thanks for your answer. I can of course add this dependency.
My question remains: Why is this different between SLE15SP5 and Leap 15.5?
Usually: accidental inclusion through some other dependency. You can make a local build for Tumbleweed (`osc build`), then abort it midway, enter the chroot it had created (`osc chroot`) and then attempt to remove absl (rpm -qa 'libasbl*', rpm -e libabsl2024xyz), the latter of which will fail and tell how it came in.
Building against openSUSE:Leap-15.5, abseil-cpp-devel does not pull in libabsl2401_0_0. Building against openSUSE:Leap-15.5:Update, it does. And the build succeeds. On non-Update, the package does not even exist. So, even adding both abseil-cpp-devel and libabsl2401_0_0 to the packages does not solve this. Only building against openSUSE:Leap-15.6:Update. This really makes me wonder why adding Leap 15.5 from the project's repository section adds the non-Update project by default. I think adding Leap to a project as build target should use the Update project, not the non-Update one. Kind Regards, Johannes
On Wednesday 2024-10-16 18:58, Johannes Kastl wrote:
My question remains: Why is this different between SLE15SP5 and Leap 15.5?
Building against openSUSE:Leap-15.5, abseil-cpp-devel does not pull in libabsl2401_0_0.
like I said, it's really trivial. Start a local build for each, chroot into it, and examine! 15.5: abseil-cpp-devel is not even present in the buildroot (hence it can't pull in libabsl2401_0_0) grpc-devel-1.25.0 present grpc-devel pulled in by nothing else grpc-devel mentioned as BuildRequires protobuf-devel-3.9.2 present protobuf-devel pulled in by nothing else protobuf-devel explicitly listed in specfile 15.5_Update: abseil-cpp-devel pulled in by grpc-devel,protobuf-devel grpc-devel-1.60.0 present grpc-devel pulled in by nothing else grpc-devel mentioned as BuildRequires protobuf-devel-25.1 present protobuf-devel pulled in by nothing else protobuf-devel explicitly listed in specfile You should just remove these ungodly LDFLAGS lines. They make no sense. export LDFLAGS="-pie -ltirpc -lgrpc -labsl_synchronization -labsl_log_internal_check_op -labsl_log_internal_nullguard -labsl_log_internal (The errors that result from kililng off the LDFLAGS line is a class of errors that ought to be fixed elsewhere, likely in absl/grpc/open-vm-tools, not the specfile.)
On Wednesday 2024-10-16 22:14, Jan Engelhardt wrote:
My question remains: Why is this different between SLE15SP5 and Leap 15.5? [home/ojkastl_buildservice/Branch_Virtualization_VMware/open-vm-tools]
Building against openSUSE:Leap-15.5, abseil-cpp-devel does not pull in libabsl2401_0_0.
You should just remove these ungodly LDFLAGS lines. They make no sense.
export LDFLAGS="-pie -ltirpc -lgrpc -labsl_synchronization -labsl_log_internal_check_op -labsl_log_internal_nullguard -labsl_log_internal
(The errors that result from kililng off the LDFLAGS line is a class of errors that ought to be fixed elsewhere, likely in absl/grpc/open-vm-tools, not the specfile.)
Protobuf functions are used by open-vm-tools-12.5.0/open-vm-tools/services/plugins/containerInfo/containerInfo_grpc.cc The build recipe in open-vm-tools-12.5.0/open-vm-tools/services/plugins/containerInfo/Makefile.am has libcontainerInfo_la_LIBADD += -lprotobuf Pursuant to the use of protobuf, it *must* use: libcontainerInfo_la_LIBADD += ${PROTOBUF_LIBS} I could swear I touched open-vm-tools before because of such silly things. Oh right, https://github.com/vmware/open-vm-tools/pull/673 .
Hi Jan, thanks a lot for digging into this. Very interesting for someone unexperienced like me... On 16.10.24 22:42 Jan Engelhardt wrote:
On Wednesday 2024-10-16 22:14, Jan Engelhardt wrote:
You should just remove these ungodly LDFLAGS lines. They make no sense.
If it were my spec file, I would do so. I am mainly helping out by doing simple version updates...
export LDFLAGS="-pie -ltirpc -lgrpc -labsl_synchronization -labsl_log_internal_check_op -labsl_log_internal_nullguard -labsl_log_internal
Even so, I still think that it makes no sense to build against openSUSE:Leap-15.6 without updates, as SLE-15:SP5_GA seems to be getting those updates somehow? That sounds to me like a general problem... Kind Regards, Johannes
On Wed, 16 Oct 2024, 10:45:37 +0200, Johannes Kastl wrote:
On 15.10.24 16:31 Stefan Seyfried wrote:
Hi Johannes,
Am 15.10.24 um 11:48 schrieb Johannes Kastl:
[ 48s] configure: error: in `/home/abuild/rpmbuild/BUILD/open-vm-tools-12.5.0/open-vm-tools': [ 48s] configure: error: C compiler cannot create executables [ 48s] See `config.log' for more details
You really should do that. Check config.log. It is a bit hard to dig through but it usually somewhere in the middle of the log file shows the error.
Here it is:
configure:3343: checking for gcc configure:3359: found /usr/bin/gcc configure:3370: result: gcc configure:3599: checking for C compiler version configure:3608: gcc --version >&5 gcc (SUSE Linux) 7.5.0 Copyright (C) 2017 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
configure:3619: $? = 0 configure:3608: gcc -v >&5 Using built-in specs. Reading specs from /usr/lib64/gcc/x86_64-suse-linux/7/defaults.spec COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib64/gcc/x86_64-suse-linux/7/lto-wrapper OFFLOAD_TARGET_NAMES=hsa:nvptx-none Target: x86_64-suse-linux Configured with: ../configure --prefix=/usr --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64 --enable-languages=c,c++,objc,fortran,obj-c++,ada,go --enable-offload-targets=hsa,nvptx-none, --without-cuda-driver --enable-checking=release --disable-werror --with-gxx-include-dir=/usr/include/c++/7 --enable-ssp --disable-libssp --disable-libvtv --disable-libcc1 --disable-plugin --with-bugurl=https://bugs.opensuse.org/ --with-pkgversion='SUSE Linux' --with-slibdir =/lib64 --with-system-zlib --enable-libstdcxx-allocator=new --disable-libstdcxx-pch --enable-version-specific-runtime-libs --with-gcc-major-version-only --enable-linker-build-id --enable-linux-futex --enable-gnu-indirect-function --program-suffix=-7 --w ithout-system-libunwind --enable-multilib --with-arch-32=x86-64 --with-tune=generic --build=x86_64-suse-linux --host=x86_64-suse-linux Thread model: posix gcc version 7.5.0 (SUSE Linux) configure:3619: $? = 0 configure:3608: gcc -V >&5 gcc: error: unrecognized command line option '-V' gcc: fatal error: no input files compilation terminated. configure:3619: $? = 1 configure:3608: gcc -qversion >&5 gcc: error: unrecognized command line option '-qversion'; did you mean '--version'? gcc: fatal error: no input files compilation terminated. configure:3619: $? = 1 configure:3639: checking whether the C compiler works configure:3661: gcc -fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Wno-unused-local-typedefs -Wno-unused-but-set-variable -Wno-deprec ated-declarations -Wno-sizeof-pointer-memaccess -Wno-cpp -fPIE -pie -ltirpc -lgrpc -labsl_synchronization -labsl_log_internal_check_op -labsl_log_internal_nullguard -labsl_log_internal_message conftest.c >&5 /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: cannot find -labsl_synchronization: No such file or directory /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: cannot find -labsl_log_internal_check_op: No such file or directory /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: cannot find -labsl_log_internal_nullguard: No such file or directory /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: cannot find -labsl_log_internal_message: No such file or directory collect2: error: ld returned 1 exit status configure:3665: $? = 1 configure:3703: result: no configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "open-vm-tools" | #define PACKAGE_TARNAME "open-vm-tools" | #define PACKAGE_VERSION "12.5.0" | #define PACKAGE_STRING "open-vm-tools 12.5.0" | #define PACKAGE_BUGREPORT "open-vm-tools-devel@lists.sourceforge.net" | #define PACKAGE_URL "" | /* end confdefs.h. */ | | int | main () | { | | ; | return 0; | } configure:3708: error: in `/home/abuild/rpmbuild/BUILD/open-vm-tools-12.5.0/open-vm-tools': configure:3710: error: C compiler cannot create executables See `config.log' for more details
I am not a GCC expert, but my guess would be the "ld: cannot find..." errors. Not sure how to solve those?
$ rpm -qf /usr/lib64/libabsl_synchronization.so.2401.0.0 libabsl_lite_2401_0_0-20240116.2-3.1.x86_64 This is on Tumbleweed, so you should check if such a package exists for Leap 15.5. BUT, this is not a gcc specific thing as the package comes from abseil-cpp-20240116.2-3.1.src.rpm, which augments the C++ stdlib.
Kind Regards, Johannes
HTH, cheers. l8er manfred
participants (5)
-
Andreas Schwab -
Jan Engelhardt -
Johannes Kastl -
Manfred Hollstein -
Stefan Seyfried