25141 – SegFault/"Internal compiler error" while ebuild compile in different states (no hardware problem)

Bug 25141 - SegFault/"Internal compiler error" while ebuild compile in different states (no hardware problem)

Summary: SegFault/"Internal compiler error" while ebuild compile in different states (...

Status:	RESOLVED WORKSFORME

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Unclassified (show other bugs)
Hardware:	x86 Linux

Importance:	High critical (vote)
Assignee:	Martin Schlemmer (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2003-07-23 14:56 UTC by Ludwig Ruderstaller
Modified:	2011-10-30 22:19 UTC (History)
CC List:	2 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Ludwig Ruderstaller 2003-07-23 14:56:44 UTC

no matter which ebuild i compile (kde at the moment, but happends also in other
ebuilds) i get randomly seg faults or "Internal compiler error" (but never on
the same place).
Its defently not a hardware problem. (i double checked it) 

if i go to /var/tmp/portage/<packagename>/work/<packagename>/ and do a simple
'make -j2' it compiles without problems. I also tryd different CFLAGS (with -O2
-march=i686 same problem) after compile is finished i can do touch ../.compiled
&& ebuild qmerge and it installs without problems.


If you need further information, let me know.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.




CPU is a 2.6 P4 with Hyper Threading enabled.
Kernel 2.4.21 with smp support.

Portage 2.0.48-r5 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1)
=================================================================
System uname: 2.4.21 i686 Intel(R) Pentium(R) 4 CPU 2.60GHz
GENTOO_MIRRORS="http://gentoo.oregonstate.edu/ http://www.ibiblio.org/pub/Linux/
distributions/gentoo"
CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share
/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/config"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
PORTDIR="/usr/portage"
DISTDIR="/mnt/distfiles"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR_OVERLAY=""
USE="x86 oss 3dnow apm avi crypt cups encode foomaticdb gif jpeg gnome libg++ li
bwww mad mikmod mmx mpeg ncurses nls pdflib png quicktime sdl slang spell svga t
ruetype xml2 xmms xv zlib gdbm berkdb readline arts java X gpm tcpd pam ssl perl
 python esd imlib oggvorbis gtk qt kde motif opengl xinerama"
COMPILER="gcc3"
CHOST="i686-pc-linux-gnu"
CFLAGS="-march=i686 -O2"
CXXFLAGS="-march=i686 -O2"
ACCEPT_KEYWORDS="x86"
MAKEOPTS="-j3"
AUTOCLEAN="yes"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
FEATURES="sandbox ccache"

Comment 1 Martin Holzer (RETIRED) gentoo-dev

2003-07-24 12:37:56 UTC

is you system overclocked ?
is your memory timing too agressive ?

use memtest86 and check your memory

Comment 2 Ludwig Ruderstaller 2003-07-25 01:18:58 UTC

hi, as i said not a hardware problem. but to answer you question: 
the system is not overclocked. memtest86 has it tested for 12hours without an single error

Comment 3 Martin Schlemmer (RETIRED) gentoo-dev

2003-08-07 08:08:57 UTC

Try with:

  # FEATURES="-sandbox -usersandbox" emerge .....

Comment 4 Caleb Tennis (RETIRED) gentoo-dev

2003-10-23 13:27:37 UTC

Closing due to inactivity.