| Summary: | dev-lisp/clisp-2.49-r9: configure: gcc: error: unrecognized command line option '-no-pie' | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Lee Starnes <lee> |
| Component: | Current packages | Assignee: | Common Lisp Bugs <common-lisp> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | felix.leif, kripton, stefan.gast |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=618170 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | build.log | ||
|
Description
Lee Starnes
2017-10-25 04:34:53 UTC
Created attachment 500008 [details]
build.log
I see the same behaviour in my (non-hardened) Gentoo running as a VirtualBox guest From the config.log: configure:3901: $? = 1 configure:3921: checking whether the C compiler works configure:3943: gcc -O3 -march=native -pipe -no-pie -Wa,--noexecstack - I/usr/include/postgresql-9.6 -I/usr/include/db4.8 -Wl,-O1 -Wl,--as-needed conftest.c >&5 gcc: error: unrecognized command line option '-no-pie' configure:3947: $? = 1 configure:3985: result: no The "-no-pie" option should probably be "-fno-pie"? (In reply to Pär Karlsson from comment #3) > From the config.log: > > configure:3901: $? = 1 > configure:3921: checking whether the C compiler works > configure:3943: gcc -O3 -march=native -pipe -no-pie -Wa,--noexecstack - > I/usr/include/postgresql-9.6 -I/usr/include/db4.8 -Wl,-O1 -Wl,--as-needed > conftest.c >&5 > gcc: error: unrecognized command line option '-no-pie' > configure:3947: $? = 1 > configure:3985: result: no > > The "-no-pie" option should probably be "-fno-pie"? Which in turns comes from: src_configure() { # Bug 618170. If anyone has a better idea... append-flags -no-pie In the clisp-2.49-r9.ebuild Same here on a stable, non-hardened amd64: === >>> Emerging (1 of 1) dev-lisp/clisp-2.49-r9::gentoo * clisp-2.49.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking clisp-2.49.tar.bz2 to /var/tmp/portage/dev-lisp/clisp-2.49-r9/work >>> Source unpacked in /var/tmp/portage/dev-lisp/clisp-2.49-r9/work >>> Preparing source in /var/tmp/portage/dev-lisp/clisp-2.49-r9/work/clisp-2.49 ... * Applying clisp-2.49-bits_ipctypes_to_sys_ipc.patch ... [ ok ] * Applying clisp-2.49-get_hostname.patch ... [ ok ] * Applying clisp-2.49-tinfo.patch ... [ ok ] >>> Source prepared. >>> Configuring source in /var/tmp/portage/dev-lisp/clisp-2.49-r9/work/clisp-2.49 ... * enabling module wildcard * enabling module rawsock * enabling module bindings/glibc * enabling module clx/new-clx * enabling module berkeley-db * enabling module dbus * enabling module fastcgi * enabling module gdbm * enabling module gtk2 * enabling module pcre * enabling module zlib * ./configure --prefix=/usr --libdir=/usr/lib64 --with-readline --with-unicode --with-ffcall --without-dynamic-modules --with-threads=POSIX_THREADS --with-module=wildcard --with-module=rawsock --with-module=bindings/glibc --with-module=clx/new-clx --with-module=berkeley-db --with-module=dbus --with-module=fastcgi --with-module=gdbm --with-module=gtk2 --with-module=pcre --with-module=zlib --hyperspec=http://www.lispworks.com/reference/HyperSpec/ builddir executing /var/tmp/portage/dev-lisp/clisp-2.49-r9/work/clisp-2.49/builddir/configure --prefix=/usr --libdir=/usr/lib64 --with-readline --with-unicode --with-ffcall --without-dynamic-modules --with-threads=POSIX_THREADS --with-module=wildcard --with-module=rawsock --with-module=bindings/glibc --with-module=clx/new-clx --with-module=berkeley-db --with-module=dbus --with-module=fastcgi --with-module=gdbm --with-module=gtk2 --with-module=pcre --with-module=zlib --hyperspec=http://www.lispworks.com/reference/HyperSpec/ builddir configure: creating cache config.cache checking for a BSD-compatible install... /usr/lib/portage/python2.7/ebuild-helpers/xattr/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes configure: ** check for host type checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking for style of include used by make... GNU checking for gcc... gcc checking whether the C compiler works... no configure: error: in `/var/tmp/portage/dev-lisp/clisp-2.49-r9/work/clisp-2.49/builddir': configure: error: C compiler cannot create executables The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3372a5ecbeaa719f733cccf67caf8f96b61f3d2c commit 3372a5ecbeaa719f733cccf67caf8f96b61f3d2c Author: Andreas K. Huettel <dilfridge@gentoo.org> AuthorDate: 2017-10-25 13:53:06 +0000 Commit: Andreas K. Huettel <dilfridge@gentoo.org> CommitDate: 2017-10-25 13:53:06 +0000 dev-lisp/clisp: Use correct gcc option, bug 635386 Shame on me for only testing with gcc-6. Let's see what explodes next. Closes: https://bugs.gentoo.org/635386 Package-Manager: Portage-2.3.12, Repoman-2.3.3 dev-lisp/clisp/clisp-2.49-r101.ebuild | 2 +- dev-lisp/clisp/clisp-2.49-r9.ebuild | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) gcc-7 requires -no-pie; -fno-pie does not work |
