Build failure for 8.90.004 Generic x64 - broken toolchain?

shiznix · September 10, 2018 at 10:08 AM

Following Compile [LibreELEC.wiki] instructions, LibreELE-8.90.004 fails to build:

Code

PROJECT=Generic ARCH=x86_64 make image

Code

...
  LINK    tests/qemu-iotests/socket_scm_helper
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: error: cannot find -lgcrypt
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: error: cannot find -lgpg-error
/usr/lib/gcc/x86_64-pc-linux-gnu/7.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: error: cannot find -lgpg-error
collect2: error: ld returned 1 exit status
make[1]: *** [/home/rick/LibreELEC.tv/build.LibreELEC-Generic.x86_64-9.0-devel/qemu-2.12.0/rules.mak:121: tests/qemu-iotests/socket_scm_helper] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory '/home/rick/LibreELEC.tv/build.LibreELEC-Generic.x86_64-9.0-devel/qemu-2.12.0/.x86_64-pc-linux-gnu'
make: *** [Makefile:12: image] Error 2

In trying to debug I couldn't help but notice LE's build process constantly jumps in and out of it's toolchain randomly.

For example, sometimes it uses the system's GCC (7.3.0) and sometimes it uses the toolchain's GCC (8.2.0).

Sometimes it builds with the toolchain GCC, then within the same package build uses the system LD (?!).

Any ideas or do the build scripts need a re-write?

Note that I don't even want to build the image, just update the kernel enough to support laptop's mouse on current hardware but have been pointed down this dead-end road

shiznix · September 10, 2018 at 11:49 AM

Success finally!

Although libgcrypt is a package that is installed into the LE image, it's not part of the toolchain and qemu was erroneously enabling libgcrypt support because it detected it as being present on the host system doing the build.

Editing packages/tools/qemu/package.mk to '--disable-gcrypt' allows qemu to build.

Also, it helps a great deal to use 'V=1' on the build command line when debugging build failures like this:

Code

PROJECT=Generic ARCH=x86_64 make V=1 image

**CvH** · September 10, 2018 at 9:07 PM Official Post

shiznix pls have a look here

qemu: disable gcrypt by CvH · Pull Request #2965 · LibreELEC/LibreELEC.tv · GitHub

shiznix · September 10, 2018 at 10:13 PM

Thanks CvH.

The next failure is packages/sysutils/open-vm-tools:

Code

libtool: link: /home/rick/LibreELEC.tv/build.LibreELEC-Generic.x86_64-9.0-devel/toolchain/bin/x86_64-libreelec-linux-gnu-gcc -shared  -fPIC -DPIC  .libs/libvmtools_la-i18n.o .libs/libvmtools_la-monotonicTimer.o .libs/libvmtools_la-signalSource.o .libs/libvmtools_la-vmtools.o .libs/libvmtools_la-vmtoolsConfig.o .libs/libvmtools_la-vmtoolsLog.o .libs/libvmtools_la-vmxLogger.o .libs/libvmtools_la-guestSDKLog.o .libs/libvmtools_la-stub-log.o  -Wl,--whole-archive ../lib/lock/.libs/libLock.a ../lib/backdoor/.libs/libBackdoor.a ../lib/asyncsocket/.libs/libAsyncSocket.a ../lib/sslDirect/.libs/libSslDirect.a ../lib/pollGtk/.libs/libPollGtk.a ../lib/poll/.libs/libPoll.a ../lib/dataMap/.libs/libDataMap.a ../lib/hashMap/.libs/libHashMap.a ../lib/dict/.libs/libDict.a ../lib/dynxdr/.libs/libDynxdr.a ../lib/err/.libs/libErr.a ../lib/file/.libs/libFile.a ../lib/glibUtils/.libs/libGlibUtils.a ../lib/guestApp/.libs/libGuestApp.a ../lib/guestRpc/.libs/libGuestRpc.a ../lib/message/.libs/libMessage.a ../lib/netUtil/.libs/libNetUtil.a ../lib/nicInfo/.libs/libNicInfo.a ../lib/panic/.libs/libPanic.a ../lib/procMgr/.libs/libProcMgr.a ../lib/rpcChannel/.libs/libRpcChannel.a ../lib/rpcIn/.libs/libRpcIn.a ../lib/rpcOut/.libs/libRpcOut.a ../lib/rpcVmx/.libs/libRpcVmx.a ../lib/string/.libs/libString.a ../lib/syncDriver/.libs/libSyncDriver.a ../lib/system/.libs/libSystem.a ../lib/stubs/.libs/libStubsCS.a ../lib/unicode/.libs/libUnicode.a ../lib/user/.libs/libUser.a ../lib/vmCheck/.libs/libVmCheck.a ../lib/vmSignal/.libs/libVmSignal.a ../lib/wiper/.libs/libWiper.a ../lib/misc/.libs/libMisc.a ../lib/slashProc/.libs/libSlashProc.a -Wl,--no-whole-archive  -Wl,-rpath -Wl,/home/rick/LibreELEC.tv/build.LibreELEC-Generic.x86_64-9.0-devel/toolchain/x86_64-libreelec-linux-gnu/sysroot/usr/lib -Wl,-rpath -Wl,/home/rick/LibreELEC.tv/build.LibreELEC-Generic.x86_64-9.0-devel/toolchain/x86_64-libreelec-linux-gnu/sysroot/usr/lib -L/usr/lib -ltirpc -ldl -lrt -lcrypt -L/home/rick/LibreELEC.tv/build.LibreELEC-Generic.x86_64-9.0-devel/toolchain/x86_64-libreelec-linux-gnu/sysroot/usr/lib /home/rick/LibreELEC.tv/build.LibreELEC-Generic.x86_64-9.0-devel/toolchain/x86_64-libreelec-linux-gnu/sysroot/usr/lib/libglib-2.0.so /home/rick/LibreELEC.tv/build.LibreELEC-Generic.x86_64-9.0-devel/toolchain/x86_64-libreelec-linux-gnu/sysroot/usr/lib/libdnet.a /home/rick/LibreELEC.tv/build.LibreELEC-Generic.x86_64-9.0-devel/toolchain/x86_64-libreelec-linux-gnu/sysroot/usr/lib/libtirpc.a -lpthread  -march=x86-64 -m64 -Os -mmmx -msse -msse2 -mfpmath=sse -Wl,-z -Wl,defs -Wl,-lc -march=x86-64 -m64 -Wl,--as-needed -fuse-ld=gold   -Wl,-soname -Wl,libvmtools.so.0 -o .libs/libvmtools.so.0.0.0
.libs/libvmtools_la-signalSource.o:signalSource.c:function VMTools_NewSignalSource: error: undefined reference to 'fcntl64'
.libs/libvmtools_la-signalSource.o:signalSource.c:function VMTools_NewSignalSource: error: undefined reference to 'fcntl64'
../lib/asyncsocket/.libs/libAsyncSocket.a(asyncsocket.o):asyncsocket.c:function AsyncTCPSocketAttachToSSLSock: error: undefined reference to 'fcntl64'
../lib/asyncsocket/.libs/libAsyncSocket.a(asyncsocket.o):asyncsocket.c:function AsyncTCPSocketAttachToSSLSock: error: undefined reference to 'fcntl64'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:573: libvmtools.la] Error 1
make[2]: Leaving directory '/home/rick/LibreELEC.tv/build.LibreELEC-Generic.x86_64-9.0-devel/open-vm-tools-stable-10.3.0/.x86_64-libreelec-linux-gnu/libvmtools'
make[1]: *** [Makefile:543: all-recursive] Error 1
make[1]: Leaving directory '/home/rick/LibreELEC.tv/build.LibreELEC-Generic.x86_64-9.0-devel/open-vm-tools-stable-10.3.0/.x86_64-libreelec-linux-gnu'
make: *** [Makefile:12: image] Error 2

Display More

Any ideas?

**CvH** · September 10, 2018 at 11:20 PM Official Post

what OS do you use to build LE ?

shiznix · September 10, 2018 at 11:32 PM

Gentoo Linux

Is LE not distro agnostic?

I thought that was the whole idea behind building it's own toolchain?

EDIT: Disabling the use of 'Gold' linker in 'distributions/LibreELEC/options' allows sysutils/open-vm-tools to build

I'm unable to disable 'Gold' for the entire image build as some packages fail to build without it enabled.

Not really sure why but I'm suspecting it has a lot to do with my host system using the standard GNU BFD linker and LE defaulting to use GOLD.

As the build process seemingly steps out of it's toolchain randomly, I'm guessing the build doesn't like switching back and forth to use different linkers.

Using standard BFD linker because it's the default for Gentoo but also because of 10238 – Gold linker does not resolve symbols using indirect dependencies