See `config.log' for more details. * ERROR: dev-lisp/clisp-2.49-r101::gentoo failed (configure phase): * ./configure failed * * Call stack: * ebuild.sh, line 124: Called src_configure ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop-gnome-systemd_20171119-230025 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.2.0 * Available Python interpreters, in order of preference: [1] python3.4 [2] python3.6 (fallback) [3] python2.7 (fallback) Available Ruby profiles: [1] ruby22 (with Rubygems) * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.6.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpv dev-lisp/clisp [ebuild N ] dev-lisp/clisp-2.49-r101 USE="X berkdb dbus gdbm gtk pcre readline unicode zlib -fastcgi -hyperspec -pari -postgres (-svm) -threads"
Created attachment 505838 [details] emerge-info.txt
Created attachment 505840 [details] dev-lisp:clisp-2.49-r101:20171122-202425.log
Created attachment 505842 [details] emerge-history.txt
Created attachment 505844 [details] environment
Created attachment 505846 [details] etc.portage.tbz2
Created attachment 505848 [details] logs.tbz2
Created attachment 505850 [details] temp.tbz2
I see the same problem with gcc-6.4.0 and the stable clisp-2.49-r9.
(In reply to Javier from comment #8) > I see the same problem with gcc-6.4.0 and the stable clisp-2.49-r9. This bug happen because of transition to 17.0 profile. I believe that compiler version doesn't matter.
I'm seeing the a similar issue re-merging dev-lisp/clisp-2.49-r9, also during a complete re-merge after the profile transition. The configure log file contains the following messages: configure:4062: checking whether we are cross compiling configure:4070: gcc -o conftest -march=amdfam10 -O2 -pipe -fno-pie -Wa,--noexecstack -I/usr/include/db4.8 -Wl,-O1 -Wl,--as-needed c onftest.c >&5 /usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/../../../../x86_64-pc-linux-gnu/bin/ld: /var/tmp/portage/dev-lisp/clisp-2.49-r9/temp/cchsL83R .o: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC /usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/../../../../x86_64-pc-linux-gnu/bin/ld: final link failed: Nonrepresentable section on output collect2: error: ld returned 1 exit status configure:4074: $? = 1 configure:4081: ./conftest configure: line 4083: ./conftest: No such file or directory configure:4085: $? = 127 configure:4092: error: in `/var/tmp/portage/dev-lisp/clisp-2.49-r9/work/clisp-2.49/builddir': configure:4096: error: cannot run C compiled programs. If you meant to cross compile, use `--host'. See `config.log' for more details.
Just compiled clisp-2.49.60 without any problems.
@Denis Sokolovsky: Are you using a 17.0 profile, and have recompiled everything after? The problem appears to be caused by clisp insisting on "-fno-pie" in the conftest, while 17.0 has moved to PIE.
Sorry, misread the comment. Yes, I can confirm the issue exists with current stable 2.49-r9 on a 17.0 profile, but is fixed with clisp-2.49.60.
I can confirmed fixed with 2.49.60 as well.
(In reply to Aaron W. Swenson from comment #14) > I can confirmed fixed with 2.49.60 as well. Yes, but 2.49.60 does not build on x86 (bug #638942).
=dev-lisp/clisp-2.49-r101 removed from the tree, current clisp version is =dev-lisp/clisp-2.49.90
dev-lisp/clisp-2.49-r9 stil breaks sys-libs/readline-7.0_p3
By reopening you mean you can reproduce it in =dev-lisp/clisp-2.49.90? Last version builds fine here on amd64 with gcc-7.3.0 and glibc-2.26-r6.
dev-lisp/clisp-2.49-r9 does not compile on my amd64 machine with 6.4.0-r1 and 2.25-r10 (same error message as above)
*** Bug 648800 has been marked as a duplicate of this bug. ***
Still not building with dev-lisp/clisp-2.49.90 does not compile on my amd64 machine with 6.4.0-r1 and 2.25-r11
(In reply to Christoph Löhr from comment #21) > Still not building with dev-lisp/clisp-2.49.90 does not compile on my amd64 > machine with 6.4.0-r1 and 2.25-r11 Please provide a build.log and emerge --info if it still happens to you.
I run into this on a new amd64 installation with 2.49-r9 (stable version at that time), but was able to compile 2.49.90 after unmasking it.
(In reply to Florian Schmaus from comment #23) > I run into this on a new amd64 installation with 2.49-r9 (stable version at > that time), but was able to compile 2.49.90 after unmasking it. we need to stabilize a newer version then, in my case 2.49.92 works ok
Doesn't use cmake.
Filed bug #687220 for stabilization of newer version.
=dev-lisp/clisp-2.49.92 has been stabilized. Closing.
