bug#20358: MariaDB failed to link 'libgcc_s.so' with our ld-wrapper.

bug#20358: MariaDB failed to link 'libgcc_s.so' with our ld-wrapper.

[宋文武]

In my patch for mariadb, I have to set LDFLAGS to '-lgcc_s':
  https://lists.gnu.org/archive/html/guix-devel/2015-04/msg00321.html

without this, binaries are built linked with libstdc++.so, but
have a not found entry for libgcc_s.so, eg:
  $ ldd ./build/sql/gen_lex_hash
        linux-vdso.so.1 (0x00007ffcfbfea000)
        libpthread.so.0 => /gnu/store/wiqbxcvzj3r35hd55yxzz919b1dv1hnv-glibc-2.21/lib/libpthread.so.0 (0x00007ff62a182000)
        libstdc++.so.6 => /gnu/store/h132igxl2lkj3sbfcbknn2rd493j7d1l-gcc-4.8.4-lib/lib/gcc/x86_64-unknown-linux-gnu/4.8.4/../../../libstdc++.so.6 (0x00007ff629e80000)
        libm.so.6 => /gnu/store/wiqbxcvzj3r35hd55yxzz919b1dv1hnv-glibc-2.21/lib/libm.so.6 (0x00007ff629b7e000)
        libc.so.6 => /gnu/store/wiqbxcvzj3r35hd55yxzz919b1dv1hnv-glibc-2.21/lib/libc.so.6 (0x00007ff6297de000)
        /gnu/store/wiqbxcvzj3r35hd55yxzz919b1dv1hnv-glibc-2.21/lib/ld-linux-x86-64.so.2 (0x00007ff62a39f000)
        libgcc_s.so.1 => not found

The link script (sql/CMakeFiles/gen_lex_hash.dir/link.txt) contains:
--------------------------------------------------------------------
  /gnu/store/4sqgnc9bc1kmn058yp4xnj4vpydmfzpq-gcc-4.8.4/bin/c++    -fno-exceptions -fno-rtti -O3 -g -static-libgcc -fno-omit-frame-pointer -fno-strict-aliasing -Wno-uninitialized -DDBUG_OFF   CMakeFiles/gen_lex_hash.dir/gen_lex_hash.cc.o  -o gen_lex_hash  -lpthread
--------------------------------------------------------------------


And the build script (sql/CMakefils/gen_lex_hash.dir/flags.make):
-----------------------------------------------------------------
# CMAKE generated file: DO NOT EDIT!
# Generated by "Unix Makefiles" Generator, CMake Version 3.1

# compile CXX with /gnu/store/4sqgnc9bc1kmn058yp4xnj4vpydmfzpq-gcc-4.8.4/bin/c++
CXX_FLAGS =  -fno-exceptions -fno-rtti -O3 -g -static-libgcc -fno-omit-frame-pointer -fno-strict-aliasing -Wno-uninitialized -DDBUG_OFF -I/var/tmp/nix-build-mariadb-10.0.17.drv-0/build/include -I/var/tmp/nix-build-mariadb-10.0.17.drv-0/mariadb-10.0.17/include -I/var/tmp/nix-build-mariadb-10.0.17.drv-0/mariadb-10.0.17/sql -I/var/tmp/nix-build-mariadb-10.0.17.drv-0/mariadb-10.0.17/zlib -I/var/tmp/nix-build-mariadb-10.0.17.drv-0/mariadb-10.0.17/extra/yassl/include -I/var/tmp/nix-build-mariadb-10.0.17.drv-0/mariadb-10.0.17/extra/yassl/taocrypt/include -I/var/tmp/nix-build-mariadb-10.0.17.drv-0/build/sql    -DHAVE_YASSL -DYASSL_PREFIX -DHAVE_OPENSSL -DMULTI_THREADED

CXX_DEFINES = -DHAVE_CONFIG_H -DHAVE_EVENT_SCHEDULER -DHAVE_POOL_OF_THREADS -DMYSQL_SERVER
------------------------------------------------------------------

As Ludovic Courtès tell,  '-static-libgcc' may be the issue.

bug#20358: MariaDB failed to link 'libgcc_s.so' with our ld-wrapper.

[Andreas Enge]

Trying to build qt, I just had the same problem; it fails with the following
messages (building on only one core to actually see the error message):

[629/10115] CC obj/src/3rdparty/chromium/net/third_party/nss/ssl/libssl.sslver.o
FAILED: cd ../../../src/3rdparty/chromium/content/browser/service_worker; python ../../../tools/protoc_wrapper/protoc_wrapper.py --include "" --protobuf "../../../../../../src/core/Release/gen/protoc_out/content/browser/service_worker/service_worker_database.pb.h" --proto-in-dir . --proto-in-file "service_worker_database.proto" "--use-system-protobuf=0" -- ../../../../../../src/core/Release/protoc --cpp_out ../../../../../../src/core/Release/gen/protoc_out/content/browser/service_worker --python_out ../../../../../../src/core/Release/pyproto/content/browser/service_worker
../../../../../../src/core/Release/protoc: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: No such file or directory
ninja: build stopped: subcommand failed.
Makefile.gyp_run:712: recipe for target 'invoke_ninja' failed
make[4]: *** [invoke_ninja] Error 1
make[4]: Leaving directory '/tmp/nix-build-qt-5.4.1.drv-0/qt-everywhere-opensource-src-5.4.1/qtwebengine/src/core'
Makefile:63: recipe for target 'sub-gyp_run-pro-make_first' failed
make[3]: *** [sub-gyp_run-pro-make_first] Error 2
make[3]: Leaving directory '/tmp/nix-build-qt-5.4.1.drv-0/qt-everywhere-opensource-src-5.4.1/qtwebengine/src/core'
Makefile:48: recipe for target 'sub-core-make_first' failed
make[2]: *** [sub-core-make_first] Error 2
make[2]: Leaving directory '/tmp/nix-build-qt-5.4.1.drv-0/qt-everywhere-opensource-src-5.4.1/qtwebengine/src'
Makefile:44: recipe for target 'sub-src-make_first' failed
make[1]: *** [sub-src-make_first] Error 2
make[1]: Leaving directory '/tmp/nix-build-qt-5.4.1.drv-0/qt-everywhere-opensource-src-5.4.1/qtwebengine'
Makefile:745: recipe for target 'module-qtwebengine-make_first' failed
make: *** [module-qtwebengine-make_first] Error 2
phase `build' failed after 11389 seconds

Andreas

bug#20358: MariaDB failed to link 'libgcc_s.so' with our ld-wrapper.

[Ludovic Courtès]

Andreas Enge <andreas@enge.fr> skribis:

> Trying to build qt, I just had the same problem; it fails with the following
> messages (building on only one core to actually see the error message):
>
> [629/10115] CC obj/src/3rdparty/chromium/net/third_party/nss/ssl/libssl.sslver.o
> FAILED: cd ../../../src/3rdparty/chromium/content/browser/service_worker; python ../../../tools/protoc_wrapper/protoc_wrapper.py --include "" --protobuf "../../../../../../src/core/Release/gen/protoc_out/content/browser/service_worker/service_worker_database.pb.h" --proto-in-dir . --proto-in-file "service_worker_database.proto" "--use-system-protobuf=0" -- ../../../../../../src/core/Release/protoc --cpp_out ../../../../../../src/core/Release/gen/protoc_out/content/browser/service_worker --python_out ../../../../../../src/core/Release/pyproto/content/browser/service_worker
> ../../../../../../src/core/Release/protoc: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: No such file or directory
> ninja: build stopped: subcommand failed.

Could you send the command and output that builds this ‘protoc’ executable?

TIA,
Ludo’.

bug#20358: MariaDB failed to link 'libgcc_s.so' with our ld-wrapper.

[宋文武]

> As Ludovic Courtès tell,  '-static-libgcc' may be the issue.
Well, the proper solution is fix our 'libstdc++.so' (which has
a "not found" entry for libgcc_s.so) in the next 'core-updates'.

bug#20358: MariaDB failed to link 'libgcc_s.so' with our ld-wrapper.

[Ludovic Courtès]

宋文武 <iyzsong@gmail.com> skribis:

> Well, the proper solution is fix our 'libstdc++.so' (which has
> a "not found" entry for libgcc_s.so) in the next 'core-updates'.

Fixed with 21e583d.

Could you check whether that solves the MariaDB issue?  (You’ll have to
build most things locally, unless you wait for hydra.gnu.org to catch up.)

Andreas: ditto for the Qt 5 issue?

Thanks,
Ludo’.

bug#20358: MariaDB failed to link 'libgcc_s.so' with our ld-wrapper.

[Andreas Enge]

On Thu, Apr 23, 2015 at 09:08:10PM +0200, Ludovic Courtès wrote:
> Andreas: ditto for the Qt 5 issue?

With commit d074e2f, cmake, a dependency of qt, fails one of its tests:
99% tests passed, 1 tests failed out of 373
The following tests FAILED:
         72 - BundleUtilities (Failed)

Andreas

bug#20358: MariaDB failed to link 'libgcc_s.so' with our ld-wrapper.

[Ludovic Courtès]

Andreas Enge <andreas@enge.fr> skribis:

> On Thu, Apr 23, 2015 at 09:08:10PM +0200, Ludovic Courtès wrote:
>> Andreas: ditto for the Qt 5 issue?
>
> With commit d074e2f, cmake, a dependency of qt, fails one of its tests:
> 99% tests passed, 1 tests failed out of 373
> The following tests FAILED:
>          72 - BundleUtilities (Failed)

I see 宋文武 did some work on CMake in core-updates, so hopefully this
particular issue is gone now?

Ludo’.

bug#20358: MariaDB failed to link 'libgcc_s.so' with our ld-wrapper.

[Andreas Enge]

On Wed, Apr 29, 2015 at 06:37:07PM +0200, Ludovic Courtès wrote:
> I see 宋文武 did some work on CMake in core-updates, so hopefully this
> particular issue is gone now?

Yes, core-updates now builds satisfyingly on x86_64, and the other architec-
tures are catching up.

Andreas

bug#20358: MariaDB failed to link 'libgcc_s.so' with our ld-wrapper.

[Andreas Enge]

Now the problem occurs in gcc itself:
   http://hydra.gnu.org/build/402695/nixlog/2/tail-reload
validating RUNPATH of 23 binaries in "/gnu/store/nj9ps51n0pfdnn0qxq6cb32z5xy2g641-gcc-4.9.2-lib/lib"...
/gnu/store/nj9ps51n0pfdnn0qxq6cb32z5xy2g641-gcc-4.9.2-lib/lib/libvtv.so: error: depends on 'libgcc_s.so.1', which cannot be found in RUNPATH ("/gnu/store/hy2hi0zj5hrqkmkhpdxf04c9bcnlnsf9-glibc-2.21/lib")
phase `validate-runpath' failed after 0 seconds

Andreas

bug#20358: MariaDB failed to link 'libgcc_s.so' with our ld-wrapper.

[Ludovic Courtès]

Andreas Enge <andreas@enge.fr> skribis:

> Now the problem occurs in gcc itself:
>    http://hydra.gnu.org/build/402695/nixlog/2/tail-reload
> validating RUNPATH of 23 binaries in "/gnu/store/nj9ps51n0pfdnn0qxq6cb32z5xy2g641-gcc-4.9.2-lib/lib"...
> /gnu/store/nj9ps51n0pfdnn0qxq6cb32z5xy2g641-gcc-4.9.2-lib/lib/libvtv.so: error: depends on 'libgcc_s.so.1', which cannot be found in RUNPATH ("/gnu/store/hy2hi0zj5hrqkmkhpdxf04c9bcnlnsf9-glibc-2.21/lib")
> phase `validate-runpath' failed after 0 seconds

Fixed in 7e35b9d.

Ludo’.