Summary: | sys-apps/memtest86-4.3.3-r1: x86_64-pc-linux-gnu-gcc: error: unrecognized option ‘-nopie’ | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Juergen Rose <rose> |
Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alexander, atoth, blueness, bruce, jason.mours |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
memtest86-4.3.3-build-nopie.patch.patch
memtest86-4.3.3-r1.ebuild.patch |
Description
Juergen Rose
2013-10-11 06:30:45 UTC
I believe, the option is called -fno-pie. The option -nopie may be some deprecated form, that stopped working with gcc 4.7 (I'm using sys-devel/gcc-4.7.3-r1). My apologies. Let's see if we can fix this without a revision bump, after all, those affected will not be able to merge this. How about test-flags-CC from flag-o-matic.eclass? See the usage example in lilo ebuilds. Created attachment 361112 [details, diff]
memtest86-4.3.3-build-nopie.patch.patch
Patch for "files/memtest86-4.3.3-build-nopie.patch"
Created attachment 361114 [details, diff]
memtest86-4.3.3-r1.ebuild.patch
Patch for ebuild. I've performed compile test only.
(In reply to Sven from comment #1) > I believe, the option is called -fno-pie. The option -nopie may be some > deprecated form, that stopped working with gcc 4.7 (I'm using > sys-devel/gcc-4.7.3-r1). I don't get this. We add -nopie to gentoo's gcc: yellow ~ # echo "int main() { return 0 ; }" > test.c yellow ~ # gcc -nopie -o test test.c yellow ~ # ./test yellow ~ # gcc -v Using built-in specs. COLLECT_GCC=/usr/x86_64-pc-linux-gnu/gcc-bin/4.7.3/gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/4.7.3/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /var/tmp/portage/sys-devel/gcc-4.7.3-r1/work/gcc-4.7.3/configure --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.7.3 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.3 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.3/man --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.3/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/include/g++-v4 --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --disable-altivec --disable-fixed-point --without-cloog --without-ppl --disable-lto --enable-nls --without-included-gettext --with-system-zlib --enable-obsolete --disable-werror --enable-secureplt --enable-multilib --with-multilib-list=m32,m64 --enable-libmudflap --disable-libssp --enable-esp --enable-libgomp --with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/4.7.3/python --enable-checking=release --disable-libgcj --enable-libstdcxx-time --enable-languages=c,c++,fortran --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-targets=all --with-bugurl=http://bugs.gentoo.org/ --with-pkgversion='Gentoo Hardened 4.7.3-r1 p1.3, pie-0.5.5' Thread model: posix gcc version 4.7.3 (Gentoo Hardened 4.7.3-r1 p1.3, pie-0.5.5) With 4.8.1: $ echo "int main() { return 0 ; }" > test.c $ gcc -nopie -o test test.c $ gcc -v Using built-in specs. COLLECT_GCC=/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.1/gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/4.8.1/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /var/tmp/portage/sys-devel/gcc-4.8.1-r1/work/gcc-4.8.1/configure --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.8.1 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.1/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.1 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.1/man --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.8.1/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.8.1/include/g++-v4 --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --disable-altivec --disable-fixed-point --with-cloog --disable-isl-version-check --enable-lto --enable-nls --without-included-gettext --with-system-zlib --enable-obsolete --disable-werror --enable-secureplt --enable-multilib --with-multilib-list=m32,m64 --enable-libmudflap --disable-libssp --enable-libgomp --with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/4.8.1/python --enable-checking=release --enable-libstdcxx-time --enable-objc-gc --enable-languages=c,c++,java,objc,obj-c++,fortran --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-targets=all --with-bugurl=http://bugs.gentoo.org/ --with-pkgversion='Gentoo 4.8.1-r1 p1.2, pie-0.5.7' Thread model: posix gcc version 4.8.1 (Gentoo 4.8.1-r1 p1.2, pie-0.5.7) And, with 4.7.3-r1: $ . /etc/profile $ gcc -nopie -o test test.c gcc: error: unrecognized option ‘-nopie’ $ gcc -v Using built-in specs. COLLECT_GCC=/usr/x86_64-pc-linux-gnu/gcc-bin/4.7.3/gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/4.7.3/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /var/tmp/portage/sys-devel/gcc-4.7.3-r1/work/gcc-4.7.3/configure --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/4.7.3 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.3 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.3/man --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.7.3/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/include/g++-v4 --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --disable-altivec --disable-fixed-point --with-cloog --with-ppl --with-cloog-include=/usr/include/cloog-ppl --disable-ppl-version-check --enable-lto --enable-nls --without-included-gettext --with-system-zlib --enable-obsolete --disable-werror --enable-secureplt --enable-multilib --with-multilib-list=m32,m64 --enable-libmudflap --disable-libssp --enable-libgomp --with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/4.7.3/python --enable-checking=release --enable-libstdcxx-time --enable-objc-gc --enable-languages=c,c++,java,objc,obj-c++,fortran --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-targets=all --with-bugurl=http://bugs.gentoo.org/ --with-pkgversion='Gentoo 4.7.3-r1 p1.3, pie-0.5.5' Thread model: posix gcc version 4.7.3 (Gentoo 4.7.3-r1 p1.3, pie-0.5.5) (In reply to Anthony Basile from comment #6) > gcc version 4.7.3 (Gentoo Hardened 4.7.3-r1 p1.3, pie-0.5.5) I notice your profile is hardened. That's why -nopie works for you. I've just confirmed memtest86 builds just fine on a hardened profile box. (In reply to Alexander Tsoy from comment #5) > Created attachment 361114 [details, diff] [details, diff] > memtest86-4.3.3-r1.ebuild.patch > > Patch for ebuild. I've performed compile test only. I tried this patch, but it still fails: ... x86_64-pc-linux-gnu-gcc -Wall -march=i486 -m32 -O1 -fomit-frame-pointer -fno-builtin -ffreestanding -fPIC -fno-stack-protector -nopie -c -o init.o init.c x86_64-pc-linux-gnu-gcc: error: unrecognized option ‘-nopie’ x86_64-pc-linux-gnu-gcc: error: unrecognized option ‘-nopie’ x86_64-pc-linux-gnu-gcc: error: unrecognized option ‘-nopie’ make: *** [reloc.o] Error 1 root@leopard:/usr/local/portage/sys-apps/memtest86(35)# emerge -pvD memtest86 These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] sys-apps/memtest86-4.3.3-r1::x-portage [4.0s::gentoo] USE="-serial" 0 kB root@leopard:/usr/local/portage/sys-apps/memtest86(37)# diff memtest86-4.3.3-r1.ebuild memtest86-4.3.3-r1.ebuild_saved 7c7 < inherit flag-o-matic mount-boot eutils toolchain-funcs --- > inherit mount-boot eutils toolchain-funcs 46,50d45 < < src_compile() { < HARDENED_CFLAGS=$(test-flags-CC -nopie) < emake CC="$(tc-getCC) ${HARDENED_CFLAGS}" < } I.e.: the patch from Commnet 4 is not included in this modified ebuild. Is this intentionally? (In reply to Anthony Basile from comment #6) > (In reply to Sven from comment #1) > > I believe, the option is called -fno-pie. The option -nopie may be some > > deprecated form, that stopped working with gcc 4.7 (I'm using > > sys-devel/gcc-4.7.3-r1). > > I don't get this. We add -nopie to gentoo's gcc: But what if gcc is compiled with USE=nopie? From toolchan.eclass: want_pie() { ! use hardened && [[ -n ${PIE_VER} ]] && use nopie && return 1 ... } do_gcc_PIE_patches() { want_pie || return 0 ... } (In reply to Roc Vallès from comment #8) > I notice your profile is hardened. That's why -nopie works for you. I've > just confirmed memtest86 builds just fine on a hardened profile box. Do you have USE=nopie enabled on non-hardened box? (In reply to Juergen Rose from comment #9) > (In reply to Alexander Tsoy from comment #5) > > Created attachment 361114 [details, diff] [details, diff] [details, diff] > > memtest86-4.3.3-r1.ebuild.patch > > > > Patch for ebuild. I've performed compile test only. > > I tried this patch, but it still fails: > ... > x86_64-pc-linux-gnu-gcc -Wall -march=i486 -m32 -O1 -fomit-frame-pointer > -fno-builtin -ffreestanding -fPIC -fno-stack-protector -nopie -c -o > init.o init.c > x86_64-pc-linux-gnu-gcc: error: unrecognized option ‘-nopie’ > x86_64-pc-linux-gnu-gcc: error: unrecognized option ‘-nopie’ > x86_64-pc-linux-gnu-gcc: error: unrecognized option ‘-nopie’ > make: *** [reloc.o] Error 1 > > root@leopard:/usr/local/portage/sys-apps/memtest86(35)# emerge -pvD memtest86 > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > [ebuild U ] sys-apps/memtest86-4.3.3-r1::x-portage [4.0s::gentoo] > USE="-serial" 0 kB > > > root@leopard:/usr/local/portage/sys-apps/memtest86(37)# diff > memtest86-4.3.3-r1.ebuild memtest86-4.3.3-r1.ebuild_saved > 7c7 > < inherit flag-o-matic mount-boot eutils toolchain-funcs > --- > > inherit mount-boot eutils toolchain-funcs > 46,50d45 > < > < src_compile() { > < HARDENED_CFLAGS=$(test-flags-CC -nopie) > < emake CC="$(tc-getCC) ${HARDENED_CFLAGS}" > < } > > > I.e.: the patch from Commnet 4 is not included in this modified ebuild. Is > this intentionally? I guess you forgot to patch the "files/memtest86-4.3.3-build-nopie.patch" file. (In reply to Alexander Tsoy from comment #10) > Do you have USE=nopie enabled on non-hardened box? No. It's not part of the default USEs in the standard profile, either. (In reply to Roc Vallès from comment #12) > (In reply to Alexander Tsoy from comment #10) > > Do you have USE=nopie enabled on non-hardened box? > > No. It's not part of the default USEs in the standard profile, either. Also check for nopie here, please. Just in case, :) $ cat /var/db/pkg/sys-devel/gcc-4.7.3-r1/USE abi_x86_64 amd64 cxx elibc_glibc hardened kernel_linux mudflap multilib nls nptl openmp userland_GNU (In reply to Alexander Tsoy from comment #13) > (In reply to Roc Vallès from comment #12) > > (In reply to Alexander Tsoy from comment #10) > > > Do you have USE=nopie enabled on non-hardened box? > > > > No. It's not part of the default USEs in the standard profile, either. > > Also check for nopie here, please. Just in case, :) > > $ cat /var/db/pkg/sys-devel/gcc-4.7.3-r1/USE > abi_x86_64 amd64 cxx elibc_glibc hardened kernel_linux mudflap multilib nls > nptl openmp userland_GNU Nope :) $ cat /var/db/pkg/sys-devel/gcc-4.7.3-r1/USE abi_x86_64 amd64 cxx elibc_glibc fortran gcj graphite kernel_linux lto mudflap multilib nls nptl objc objc++ objc-gc openmp userland_GNU $ cat /var/db/pkg/sys-devel/gcc-4.8.1-r1/USE abi_x86_64 amd64 cxx elibc_glibc fortran gcj graphite kernel_linux lto mudflap multilib nls nptl objc objc++ objc-gc openmp userland_GNU (In reply to Juergen Rose from comment #9) > (In reply to Alexander Tsoy from comment #5) > > Created attachment 361114 [details, diff] [details, diff] [details, diff] > > memtest86-4.3.3-r1.ebuild.patch > > > > Patch for ebuild. I've performed compile test only. > > I tried this patch, but it still fails: > ... > x86_64-pc-linux-gnu-gcc -Wall -march=i486 -m32 -O1 -fomit-frame-pointer > -fno-builtin -ffreestanding -fPIC -fno-stack-protector -nopie -c -o > init.o init.c > x86_64-pc-linux-gnu-gcc: error: unrecognized option ‘-nopie’ > x86_64-pc-linux-gnu-gcc: error: unrecognized option ‘-nopie’ > x86_64-pc-linux-gnu-gcc: error: unrecognized option ‘-nopie’ > make: *** [reloc.o] Error 1 > > root@leopard:/usr/local/portage/sys-apps/memtest86(35)# emerge -pvD memtest86 > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > [ebuild U ] sys-apps/memtest86-4.3.3-r1::x-portage [4.0s::gentoo] > USE="-serial" 0 kB > > > root@leopard:/usr/local/portage/sys-apps/memtest86(37)# diff > memtest86-4.3.3-r1.ebuild memtest86-4.3.3-r1.ebuild_saved > 7c7 > < inherit flag-o-matic mount-boot eutils toolchain-funcs > --- > > inherit mount-boot eutils toolchain-funcs > 46,50d45 > < > < src_compile() { > < HARDENED_CFLAGS=$(test-flags-CC -nopie) > < emake CC="$(tc-getCC) ${HARDENED_CFLAGS}" > < } > > > I.e.: the patch from Commnet 4 is not included in this modified ebuild. Is > this intentionally? If I still add the patch from Comment 4, emerge can do a little more: ... x86_64-pc-linux-gnu-gcc -Wall -march=i486 -m32 -O1 -fomit-frame-pointer -fno-builtin -ffreestanding -fPIC -fno-stack-protector -nopie -c -o init.o init.c x86_64-pc-linux-gnu-gcc -Wall -march=i486 -m32 -O1 -fomit-frame-pointer -fno-builtin -ffreestanding -fPIC -fno-stack-protector -nopie -c -o lib.o lib.c x86_64-pc-linux-gnu-gcc -Wall -march=i486 -m32 -O1 -fomit-frame-pointer -fno-builtin -ffreestanding -fPIC -fno-stack-protector -nopie -c -o patn.o patn.c x86_64-pc-linux-gnu-gcc: error: unrecognized option ‘-nopie’ x86_64-pc-linux-gnu-gcc: error: unrecognized option ‘-nopie’ make: *** [reloc.o] Error 1 (In reply to Alexander Tsoy from comment #11) > (In reply to Juergen Rose from comment #9) > > (In reply to Alexander Tsoy from comment #5) > > > Created attachment 361114 [details, diff] [details, diff] [details, diff] [details, diff] > > > memtest86-4.3.3-r1.ebuild.patch > > > > > > Patch for ebuild. I've performed compile test only. > > > > I tried this patch, but it still fails: > > ... > > x86_64-pc-linux-gnu-gcc -Wall -march=i486 -m32 -O1 -fomit-frame-pointer > > -fno-builtin -ffreestanding -fPIC -fno-stack-protector -nopie -c -o > > init.o init.c > > x86_64-pc-linux-gnu-gcc: error: unrecognized option ‘-nopie’ > > x86_64-pc-linux-gnu-gcc: error: unrecognized option ‘-nopie’ > > x86_64-pc-linux-gnu-gcc: error: unrecognized option ‘-nopie’ > > make: *** [reloc.o] Error 1 > > > > root@leopard:/usr/local/portage/sys-apps/memtest86(35)# emerge -pvD memtest86 > > > > These are the packages that would be merged, in order: > > > > Calculating dependencies... done! > > [ebuild U ] sys-apps/memtest86-4.3.3-r1::x-portage [4.0s::gentoo] > > USE="-serial" 0 kB > > > > > > root@leopard:/usr/local/portage/sys-apps/memtest86(37)# diff > > memtest86-4.3.3-r1.ebuild memtest86-4.3.3-r1.ebuild_saved > > 7c7 > > < inherit flag-o-matic mount-boot eutils toolchain-funcs > > --- > > > inherit mount-boot eutils toolchain-funcs > > 46,50d45 > > < > > < src_compile() { > > < HARDENED_CFLAGS=$(test-flags-CC -nopie) > > < emake CC="$(tc-getCC) ${HARDENED_CFLAGS}" > > < } > > > > > > I.e.: the patch from Commnet 4 is not included in this modified ebuild. Is > > this intentionally? > > I guess you forgot to patch the "files/memtest86-4.3.3-build-nopie.patch" > file. Yes, I added memtest86-4.3.3-build-nopie.patch.patch to the files directory and added a epatch "${FILESDIR}"/memtest86-4.3.3-build-nopie.patch.patch to the ebuild. After patching files/memtest86-4.3.3-build-nopie.patch I was now able to emerge memtest86-4.3.3-r1.(In reply to Alexander Tsoy from comment #11) > (In reply to Juergen Rose from comment #9) > > (In reply to Alexander Tsoy from comment #5) > > > Created attachment 361114 [details, diff] [details, diff] [details, diff] [details, diff] > > > memtest86-4.3.3-r1.ebuild.patch > > > > > > Patch for ebuild. I've performed compile test only. > > > > I tried this patch, but it still fails: > > ... > > x86_64-pc-linux-gnu-gcc -Wall -march=i486 -m32 -O1 -fomit-frame-pointer > > -fno-builtin -ffreestanding -fPIC -fno-stack-protector -nopie -c -o > > init.o init.c > > x86_64-pc-linux-gnu-gcc: error: unrecognized option ‘-nopie’ > > x86_64-pc-linux-gnu-gcc: error: unrecognized option ‘-nopie’ > > x86_64-pc-linux-gnu-gcc: error: unrecognized option ‘-nopie’ > > make: *** [reloc.o] Error 1 > > > > root@leopard:/usr/local/portage/sys-apps/memtest86(35)# emerge -pvD memtest86 > > > > These are the packages that would be merged, in order: > > > > Calculating dependencies... done! > > [ebuild U ] sys-apps/memtest86-4.3.3-r1::x-portage [4.0s::gentoo] > > USE="-serial" 0 kB > > > > > > root@leopard:/usr/local/portage/sys-apps/memtest86(37)# diff > > memtest86-4.3.3-r1.ebuild memtest86-4.3.3-r1.ebuild_saved > > 7c7 > > < inherit flag-o-matic mount-boot eutils toolchain-funcs > > --- > > > inherit mount-boot eutils toolchain-funcs > > 46,50d45 > > < > > < src_compile() { > > < HARDENED_CFLAGS=$(test-flags-CC -nopie) > > < emake CC="$(tc-getCC) ${HARDENED_CFLAGS}" > > < } > > > > > > I.e.: the patch from Commnet 4 is not included in this modified ebuild. Is > > this intentionally? > > I guess you forgot to patch the "files/memtest86-4.3.3-build-nopie.patch" > file. Yes, I added memtest86-4.3.3-build-nopie.patch.patch to the files directory and added a epatch "${FILESDIR}"/memtest86-4.3.3-build-nopie.patch.patch to the ebuild. After patching files/memtest86-4.3.3-build-nopie.patch I was now able to emerge memtest86-4.3.3-r1. There are currently two patches in the files directory: 1. memtest86-4.3.3-build-nopie.patch - which is good for hardened 2. memtest86-4.3.3-build.patch - which is good for non-hardened memtest86-4.3.3.ebuild applies the non-hardened patch, while memtest86-4.3.3-r1.ebuild applies the hardened version. Current code in src_prepare for hardened in memtest86-4.3.3-r1.ebuild: epatch "${FILESDIR}"/${P}-build-nopie.patch #66630 + #206726 Current code in src_prepare for non-hardened in memtest86-4.3.3.ebuild: epatch "${FILESDIR}"/${P}-build.patch #66630 My suggestion: if use hardened ; then epatch "${FILESDIR}"/${P}-build-nopie.patch #66630 + #206726 else epatch "${FILESDIR}"/${P}-build.patch #66630 fi It will be fine for everyone thereafter. (In reply to Attila Tóth from comment #16) > My suggestion: > if use hardened ; then > epatch "${FILESDIR}"/${P}-build-nopie.patch #66630 + #206726 > else > epatch "${FILESDIR}"/${P}-build.patch #66630 > fi > > It will be fine for everyone thereafter. Not a good solution as it requires to mantain two patches. IMHO my solution with test-flags-CC is better. (In reply to Alexander Tsoy from comment #17) > (In reply to Attila Tóth from comment #16) > > My suggestion: > > if use hardened ; then > > epatch "${FILESDIR}"/${P}-build-nopie.patch #66630 + #206726 > > else > > epatch "${FILESDIR}"/${P}-build.patch #66630 > > fi > > > > It will be fine for everyone thereafter. > > Not a good solution as it requires to mantain two patches. IMHO my solution > with test-flags-CC is better. I have just took a look at your suggestion and I agree, that it's better than maintaining two patches. (In reply to Alexander Tsoy from comment #17) > Not a good solution as it requires to mantain two patches. IMHO my solution > with test-flags-CC is better. The difference between the specific patch and the test-flags-CC approach is that for the latter nopie gets appended to every compilation... (In reply to Attila Tóth from comment #19) > (In reply to Alexander Tsoy from comment #17) > > Not a good solution as it requires to mantain two patches. IMHO my solution > > with test-flags-CC is better. > > The difference between the specific patch and the test-flags-CC approach is > that for the latter nopie gets appended to every compilation... Just use -fno-pie instead of -nopie and that should work on both hardened and vanilla compilers. (In reply to Anthony Basile from comment #20) > (In reply to Attila Tóth from comment #19) > > (In reply to Alexander Tsoy from comment #17) > > > Not a good solution as it requires to mantain two patches. IMHO my solution > > > with test-flags-CC is better. > > > > The difference between the specific patch and the test-flags-CC approach is > > that for the latter nopie gets appended to every compilation... > > Just use -fno-pie instead of -nopie and that should work on both hardened > and vanilla compilers. I just made this change, can people please do a compile and run test for me. Compiled ok. Qemu doesn't want to run it and I don't want to reboot now, so that'll have to wait. (In reply to Anthony Basile from comment #21) > I just made this change, can people please do a compile and run test for me. I modified the existing nopie-patch myself a few days ago to use -fno-pie as suggested in comment #1 and was wondering about the long discussion. So with -fno-pie it compiles and works fine on my x86 and amd64-systems. |