Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Gentoo: Hardened

gcc 4.5.3 doesn't build on x86 hardened profile

 

 

Gentoo hardened RSS feed   Index | Next | Previous | View Threaded


jbahm at pcdesk

Feb 5, 2012, 7:28 PM

Post #1 of 12 (1481 views)
Permalink
gcc 4.5.3 doesn't build on x86 hardened profile

Howdy folks,
I recently tried to recompile some packages and I discovered that GCC
4.5.3, the current default version in the hardened profile will not
build on x86. Just for kicks, I downloaded a copy of the hardened stage3
and tried to build gcc on that, just to eliminate some possibilities. I
didn't change anything in it's default setup, except to set
MAKEOPTS="-j5". No joy, it doesn't build anyway. Any clues as to what I
have to do to make it build?
--
"All models are wrong, but some are useful." George E. P. Box
Joseph C. Lininger, <jbahm [at] pcdesk>


atoth at atoth

Feb 5, 2012, 10:33 PM

Post #2 of 12 (1439 views)
Permalink
Re: gcc 4.5.3 doesn't build on x86 hardened profile [In reply to]

Less and less people uses x86 nowdays. On my Pentium M and Athlon MP
system it builds OK.
Please let us know how the build dies.
--
dr Tóth Attila, Radiológus, 06-20-825-8057
Attila Toth MD, Radiologist, +36-20-825-8057

2012.Február 6.(H) 04:28 időpontban Joseph C. Lininger ezt írta:
> Howdy folks,
> I recently tried to recompile some packages and I discovered that GCC
> 4.5.3, the current default version in the hardened profile will not
> build on x86. Just for kicks, I downloaded a copy of the hardened stage3
> and tried to build gcc on that, just to eliminate some possibilities. I
> didn't change anything in it's default setup, except to set
> MAKEOPTS="-j5". No joy, it doesn't build anyway. Any clues as to what I
> have to do to make it build?
> --
> "All models are wrong, but some are useful." George E. P. Box
> Joseph C. Lininger, <jbahm [at] pcdesk>
>


jbahm at pcdesk

Feb 5, 2012, 10:42 PM

Post #3 of 12 (1440 views)
Permalink
Re: gcc 4.5.3 doesn't build on x86 hardened profile [In reply to]

You're right, less and less people do. But I still am required to offer
an x86 image for a custom build we use. I can post a build log or
something if necessary. Specifically what happens though is the build
gets well in, almost completes actually, then aborts. My x86_64 image
still builds ok. Like I said, it happens on the hardened stage3 from the
mirrors too. The standard gcc builds ok though. It's only if you're
using the hardened profile that it bombs out like this.
--
"All models are wrong, but some are useful." George E. P. Box
Joseph C. Lininger, <jbahm [at] pcdesk>


atoth at atoth

Feb 5, 2012, 10:54 PM

Post #4 of 12 (1441 views)
Permalink
Re: gcc 4.5.3 doesn't build on x86 hardened profile [In reply to]

I'll double-check it on my systems.
The relevant snippet of the build log would be nice.
--
dr Tóth Attila, Radiológus, 06-20-825-8057
Attila Toth MD, Radiologist, +36-20-825-8057

2012.Február 6.(H) 07:42 időpontban Joseph C. Lininger ezt írta:
> You're right, less and less people do. But I still am required to offer
> an x86 image for a custom build we use. I can post a build log or
> something if necessary. Specifically what happens though is the build
> gets well in, almost completes actually, then aborts. My x86_64 image
> still builds ok. Like I said, it happens on the hardened stage3 from the
> mirrors too. The standard gcc builds ok though. It's only if you're
> using the hardened profile that it bombs out like this.
> --
> "All models are wrong, but some are useful." George E. P. Box
> Joseph C. Lininger, <jbahm [at] pcdesk>
>


jbahm at pcdesk

Feb 5, 2012, 11:35 PM

Post #5 of 12 (1439 views)
Permalink
Re: gcc 4.5.3 doesn't build on x86 hardened profile [In reply to]

Sure. I'll generate it again (I cleaned the build dir) and send it on.
Give me a little bit.
--
"All models are wrong, but some are useful." George E. P. Box
Joseph C. Lininger, <jbahm [at] pcdesk>


jbahm at pcdesk

Feb 5, 2012, 11:59 PM

Post #6 of 12 (1445 views)
Permalink
Re: gcc 4.5.3 doesn't build on x86 hardened profile [In reply to]

As promised, here's the point in the build log where things fail.

/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build/./prev-gcc/xgcc
-B/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build/./prev-gcc/
-B/usr/i686-pc-linux-gnu/bin/ -B/usr/i686-pc-linux-gnu/bin/
-B/usr/i686-pc-linux-gnu/lib/ -isystem /usr/i686-pc-linux-gnu/include
-isystem /usr/i686-pc-linux-gnu/sys-include -DEFAULT_RELRO
-DEFAULT_BIND_NOW -DEFAULT_PIE_SSP -O2 -march=i686 -pipe -gtoggle
-DIN_GCC -W -Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes
-Wmissing-prototypes -Wmissing-format-attribute -pedantic -Wno-long-long
-Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition
-Wc++-compat -DHAVE_CONFIG_H -DGENERATOR_FILE -o build/genattrtab \
build/genattrtab.o build/rtl.o build/read-rtl.o build/ggc-none.o
build/vec.o build/min-insn-modes.o build/gensupport.o build/print-rtl.o
build/errors.o .././libiberty/libiberty.a
build/genattrtab
/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/config/i386/i386.md
\
insn-conditions.md > tmp-attrtab.c
/bin/sh
/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/../move-if-change
tmp-attrtab.c insn-attrtab.c
echo timestamp > s-attrtab
/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build/./prev-gcc/xgcc
-B/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build/./prev-gcc/
-B/usr/i686-pc-linux-gnu/bin/ -B/usr/i686-pc-linux-gnu/bin/
-B/usr/i686-pc-linux-gnu/lib/ -isystem /usr/i686-pc-linux-gnu/include
-isystem /usr/i686-pc-linux-gnu/sys-include -c -DEFAULT_RELRO
-DEFAULT_BIND_NOW -DEFAULT_PIE_SSP -O2 -march=i686 -pipe -gtoggle
-DIN_GCC -W -Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes
-Wmissing-prototypes -Wmissing-format-attribute -pedantic -Wno-long-long
-Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition
-Wc++-compat -DHAVE_CONFIG_H -I. -I.
-I/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc
-I/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/.
-I/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/../include
-I/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/../libcpp/include

-I/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/../libdecnumber
-I/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/../libdecnumber/bid
-I../libdecnumber insn-attrtab.c -o insn-attrtab.o
/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/config/i386/i386.md:
In function 'internal_dfa_insn_code':
/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/config/i386/i386.md:360:1:
internal compiler error: Bus error
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugs.gentoo.org/> for instructions.
make[3]: *** [insn-attrtab.o] Error 1
make[3]: Leaving directory
`/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build/gcc'
make[2]: *** [all-stage2-gcc] Error 2
make[2]: Leaving directory
`/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build'
make[1]: *** [stage2-bubble] Error 2
make[1]: Leaving directory
`/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build'
make: *** [bootstrap-lean] Error 2
emake failed
* ERROR: sys-devel/gcc-4.5.3-r1 failed (compile phase):
* emake failed with bootstrap-lean
*
* Call stack:
* ebuild.sh, line 85: Called src_compile
* environment, line 4015: Called toolchain_src_compile
* environment, line 4670: Called gcc_do_make
* environment, line 2348: Called die
* The specific snippet of code:
* emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}"
LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET} ||
die "emake failed with ${GCC_MAKE_TARGET}";
*
* If you need support, post the output of 'emerge --info
=sys-devel/gcc-4.5.3-r1',
* the complete build log and the output of 'emerge -pqv
=sys-devel/gcc-4.5.3-r1'.
*
* Please include
/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build/gcc-build-logs.tar.bz2 in
your bug report
*
* The complete build log is located at
'/var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/environment'.
* S: '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build'
--
"All models are wrong, but some are useful." George E. P. Box
Joseph C. Lininger, <jbahm [at] pcdesk>


puleglot at ya

Feb 6, 2012, 1:31 AM

Post #7 of 12 (1502 views)
Permalink
Re: gcc 4.5.3 doesn't build on x86 hardened profile [In reply to]

В Mon, 06 Feb 2012 00:59:55 -0700
"Joseph C. Lininger" <jbahm [at] pcdesk> пишет:

> As promised, here's the point in the build log where things fail.
>
> /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build/./prev-gcc/xgcc
> -B/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build/./prev-gcc/
> -B/usr/i686-pc-linux-gnu/bin/ -B/usr/i686-pc-linux-gnu/bin/
> -B/usr/i686-pc-linux-gnu/lib/ -isystem /usr/i686-pc-linux-gnu/include
> -isystem /usr/i686-pc-linux-gnu/sys-include -DEFAULT_RELRO
> -DEFAULT_BIND_NOW -DEFAULT_PIE_SSP -O2 -march=i686 -pipe -gtoggle
> -DIN_GCC -W -Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes
> -Wmissing-prototypes -Wmissing-format-attribute -pedantic -Wno-long-long
> -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition
> -Wc++-compat -DHAVE_CONFIG_H -DGENERATOR_FILE -o build/genattrtab \
> build/genattrtab.o build/rtl.o build/read-rtl.o build/ggc-none.o
> build/vec.o build/min-insn-modes.o build/gensupport.o build/print-rtl.o
> build/errors.o .././libiberty/libiberty.a
> build/genattrtab
> /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/config/i386/i386.md
> \
> insn-conditions.md > tmp-attrtab.c
> /bin/sh
> /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/../move-if-change
> tmp-attrtab.c insn-attrtab.c
> echo timestamp > s-attrtab
> /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build/./prev-gcc/xgcc
> -B/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build/./prev-gcc/
> -B/usr/i686-pc-linux-gnu/bin/ -B/usr/i686-pc-linux-gnu/bin/
> -B/usr/i686-pc-linux-gnu/lib/ -isystem /usr/i686-pc-linux-gnu/include
> -isystem /usr/i686-pc-linux-gnu/sys-include -c -DEFAULT_RELRO
> -DEFAULT_BIND_NOW -DEFAULT_PIE_SSP -O2 -march=i686 -pipe -gtoggle
> -DIN_GCC -W -Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes
> -Wmissing-prototypes -Wmissing-format-attribute -pedantic -Wno-long-long
> -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition
> -Wc++-compat -DHAVE_CONFIG_H -I. -I.
> -I/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc
> -I/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/.
> -I/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/../include
> -I/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/../libcpp/include
>
> -I/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/../libdecnumber
> -I/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/../libdecnumber/bid
> -I../libdecnumber insn-attrtab.c -o insn-attrtab.o
> /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/config/i386/i386.md:
> In function 'internal_dfa_insn_code':
> /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/config/i386/i386.md:360:1:
> internal compiler error: Bus error
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <http://bugs.gentoo.org/> for instructions.
> make[3]: *** [insn-attrtab.o] Error 1
> make[3]: Leaving directory
> `/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build/gcc'
> make[2]: *** [all-stage2-gcc] Error 2
> make[2]: Leaving directory
> `/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build'
> make[1]: *** [stage2-bubble] Error 2
> make[1]: Leaving directory
> `/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build'
> make: *** [bootstrap-lean] Error 2
> emake failed
> * ERROR: sys-devel/gcc-4.5.3-r1 failed (compile phase):
> * emake failed with bootstrap-lean
> *
> * Call stack:
> * ebuild.sh, line 85: Called src_compile
> * environment, line 4015: Called toolchain_src_compile
> * environment, line 4670: Called gcc_do_make
> * environment, line 2348: Called die
> * The specific snippet of code:
> * emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}"
> LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET} ||
> die "emake failed with ${GCC_MAKE_TARGET}";
> *
> * If you need support, post the output of 'emerge --info
> =sys-devel/gcc-4.5.3-r1',
> * the complete build log and the output of 'emerge -pqv
> =sys-devel/gcc-4.5.3-r1'.
> *
> * Please include
> /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build/gcc-build-logs.tar.bz2 in
> your bug report
> *
> * The complete build log is located at
> '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/build.log'.
> * The ebuild environment file is located at
> '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/temp/environment'.
> * S: '/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/build'

From the gcc ebuild change log:

30 Dec 2011; Magnus Granberg <zorry [at] gentoo> gcc-4.5.3-r2.ebuild:
Bump the piepatchset to 0.4.7 to fix 394821

--
With best regards,
Alexander Tsoy


jbahm at pcdesk

Feb 6, 2012, 3:13 AM

Post #8 of 12 (1449 views)
Permalink
Re: gcc 4.5.3 doesn't build on x86 hardened profile [In reply to]

I looked for that and couldn't find anything about it. Thank you. Any
idea when this might be in stable x86? Stable still uses 4.5.3-r1.
--
"All models are wrong, but some are useful." George E. P. Box
Joseph C. Lininger, <jbahm [at] pcdesk>


basile at opensource

Feb 6, 2012, 3:41 AM

Post #9 of 12 (1442 views)
Permalink
Re: gcc 4.5.3 doesn't build on x86 hardened profile [In reply to]

On 02/05/2012 10:28 PM, Joseph C. Lininger wrote:
> Howdy folks,
> I recently tried to recompile some packages and I discovered that GCC
> 4.5.3, the current default version in the hardened profile will not
> build on x86. Just for kicks, I downloaded a copy of the hardened stage3
> and tried to build gcc on that, just to eliminate some possibilities. I
> didn't change anything in it's default setup, except to set
> MAKEOPTS="-j5". No joy, it doesn't build anyway. Any clues as to what I
> have to do to make it build?

If you tried gcc-4.5.3-r1 and hit a bus error then try gcc-4.5.3-r2.

--
Anthony G. Basile, Ph. D.
Chair of Information Technology
D'Youville College
Buffalo, NY 14201
(716) 829-8197


basile at opensource

Feb 6, 2012, 3:44 AM

Post #10 of 12 (1437 views)
Permalink
Re: gcc 4.5.3 doesn't build on x86 hardened profile [In reply to]

On 02/06/2012 02:59 AM, Joseph C. Lininger wrote:
> As promised, here's the point in the build log where things fail.
>

> -I/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/../libdecnumber
> -I/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/../libdecnumber/bid
> -I../libdecnumber insn-attrtab.c -o insn-attrtab.o
> /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/config/i386/i386.md:
> In function 'internal_dfa_insn_code':
> /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/config/i386/i386.md:360:1:
> internal compiler error: Bus error
> Please submit a full bug report,

https://bugs.gentoo.org/show_bug.cgi?id=396059

Two things to note here:

1) internal compiler error: Bus error
2) Please submit a full bug report,

The second isn't chastisement, gentoo's bugzilla is a wealth of knowledge.

--
Anthony G. Basile, Ph. D.
Chair of Information Technology
D'Youville College
Buffalo, NY 14201
(716) 829-8197


basile at opensource

Feb 6, 2012, 3:46 AM

Post #11 of 12 (1451 views)
Permalink
Re: gcc 4.5.3 doesn't build on x86 hardened profile [In reply to]

On 02/06/2012 06:13 AM, Joseph C. Lininger wrote:
> I looked for that and couldn't find anything about it. Thank you. Any
> idea when this might be in stable x86? Stable still uses 4.5.3-r1.

*shrug* toolchain and hardened teams are not always in sync. Just mark
it stable on your system.

--
Anthony G. Basile, Ph. D.
Chair of Information Technology
D'Youville College
Buffalo, NY 14201
(716) 829-8197


klondike at gentoo

Feb 6, 2012, 4:54 AM

Post #12 of 12 (1442 views)
Permalink
Re: gcc 4.5.3 doesn't build on x86 hardened profile [In reply to]

El 06/02/12 08:59, Joseph C. Lininger escribió:
> /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/config/i386/i386.md:
> In function 'internal_dfa_insn_code':
> /var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/gcc/config/i386/i386.md:360:1:
> internal compiler error: Bus error
Hi, this function compilation is usually a memory hog and can give some
issues. So...
* Check dmesg for any clues, maybe the program tried to use too many
memory and hit a limit.
* Reduce -j to 1 to reduce concurrent memory usage.
* If you still need -j 5 make sure you add enough swap space and have a
PAE kernel.
Attachments: signature.asc (0.26 KB)

Gentoo hardened RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.