[opensuse-buildservice] [Arch] gcc is broken
Good evening, I am having a problem building a package with gcc on OBS Arch image. The package is just a `./configure; make; make install` one, although it doesn't work because within the Arch chroot something is broken. The important part of the failed configuration log is the following: configure:2941: checking whether the C++ compiler works configure:2963: g++ -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now conftest.cpp >&5 /usr/bin/ld: /usr/lib/libc.so.6: version `GLIBC_2.27' not found (required by /usr/bin/ld) collect2: error: ld returned 1 exit status I am not sure which fixtures has the Arch chroot, but I believe this should not happen. By using the official chroot tool provided by Arch this issue does not arise. If needed I can attach the *config.log* generated by `./configure`. -- Giovanni Santini My blog: http://giovannisantini.tk My code: https://git{hub,lab}.com/ItachiSan My GPG: 2FADEBF5 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Samstag, 12. Mai 2018, 20:37:51 CEST wrote Giovanni Santini:
Good evening, I am having a problem building a package with gcc on OBS Arch image. The package is just a `./configure; make; make install` one, although it doesn't work because within the Arch chroot something is broken. The important part of the failed configuration log is the following:
configure:2941: checking whether the C++ compiler works configure:2963: g++ -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now conftest.cpp >&5 /usr/bin/ld: /usr/lib/libc.so.6: version `GLIBC_2.27' not found (required by /usr/bin/ld) collect2: error: ld returned 1 exit status
I am not sure which fixtures has the Arch chroot, but I believe this should not happen. By using the official chroot tool provided by Arch this issue does not arise. If needed I can attach the *config.log* generated by `./configure`.
I can not reproduce it here with a most basic setup. It might have been a temporary problem, since Arch is rolling release or you have some packages breaking it in your project. -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Il 14/05/2018 09:02, Adrian Schröter ha scritto:
... I can not reproduce it here with a most basic setup.
It might have been a temporary problem, since Arch is rolling release or you have some packages breaking it in your project.
Hey, I suppose it was a temporary chroot problem; recreating the chroot did the trick. -- Giovanni Santini My blog: http://giovannisantini.tk My code: https://git{hub,lab}.com/ItachiSan My GPG: 2FADEBF5 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (2)
-
Adrian Schröter -
Giovanni Santini