View previous topic :: View next topic |
Author |
Message |
pjp Administrator
Joined: 16 Apr 2002 Posts: 20067
|
Posted: Sat Aug 03, 2002 4:50 pm Post subject: |
|
|
In your first post, you mention the errors aren't exactly the same. Can you post a new error message.... maybe having 2 to compare will turn something up. _________________ Quis separabit? Quo animo? |
|
Back to top |
|
|
Jammen Guest
|
Posted: Sat Aug 03, 2002 6:38 pm Post subject: |
|
|
Well, the error not only appears on xfree.... if I put emerge -u system, the error also appears in glibc: Segmention fault, *** [math/subdir_lib] Error 2, *** [All] Error 2, etc..
This type of error.
I'm deseperate, I really need help |
|
Back to top |
|
|
pjp Administrator
Joined: 16 Apr 2002 Posts: 20067
|
Posted: Sat Aug 03, 2002 8:48 pm Post subject: |
|
|
Anonymous wrote: | Maybe u have somehow corrupted xfree tarballs, remove them, they are in /usr/portage/distfiles ( i think), and run emerge xfree again. | Did you ever try this? You may also need to remove the glibc file from this directory. _________________ Quis separabit? Quo animo? |
|
Back to top |
|
|
Jammen Guest
|
Posted: Sat Aug 03, 2002 9:43 pm Post subject: |
|
|
I reinstall the system 10 times and appears the same error!!!
I'm furious!!! |
|
Back to top |
|
|
klieber Bodhisattva
Joined: 17 Apr 2002 Posts: 3657 Location: San Francisco, CA
|
Posted: Sat Aug 03, 2002 11:38 pm Post subject: |
|
|
I'm not sure exactly what your problem is, but here's a few things you can try:
- Change your optimization settings from -O3 down to -O2.
- completely remove all XFree86 files in /usr/portage/distfiles/, /tmp/portage and /var/tmp/portage/ and then emerge fresh from there.
- use ebuild to step through the compilation process. This won't solve your problem, but it may produce some more valuable debugging information which can be appended to your bug report. man ebuild for more information about the necessary steps, but it's basically a series of steps using ebuild -- clean, fetch, unpack, compile, install, qmerge. (clean isn't strictly necessary)
If you do step 3, make sure you do step 2 as well before starting on 3. It's always best to have a clean slate before starting.
hth.
--kurt _________________ The problem with political jokes is that they get elected |
|
Back to top |
|
|
Jammen Guest
|
Posted: Sun Aug 04, 2002 11:43 am Post subject: |
|
|
I've done the steps and appears the same error! |
|
Back to top |
|
|
klieber Bodhisattva
Joined: 17 Apr 2002 Posts: 3657 Location: San Francisco, CA
|
Posted: Sun Aug 04, 2002 11:53 am Post subject: |
|
|
Jammen wrote: | I've done the steps and appears the same error! |
OK, did you get any other pertinent information when using ebuild instead of emerge?
--kurt _________________ The problem with political jokes is that they get elected |
|
Back to top |
|
|
Jammen Guest
|
Posted: Sun Aug 04, 2002 12:10 pm Post subject: |
|
|
No, when it's compiling suddenly aborted for the error... |
|
Back to top |
|
|
Jammen Guest
|
Posted: Mon Aug 05, 2002 7:32 pm Post subject: |
|
|
Help! |
|
Back to top |
|
|
Jammen Guest
|
Posted: Wed Aug 07, 2002 12:57 pm Post subject: |
|
|
The problem is solved! It was the RAM, a cheap and bad RAM.
Thank you for all!!!!
|
|
Back to top |
|
|
jamesb n00b
Joined: 08 Aug 2002 Posts: 8 Location: Cambridge, UK
|
Posted: Thu Aug 08, 2002 6:43 am Post subject: |
|
|
I had the exact same error, but for me it was down to having "-j 4" in MAKE_OPTS.
James |
|
Back to top |
|
|
mikulus Tux's lil' helper
Joined: 03 Jun 2002 Posts: 77
|
Posted: Sat Aug 10, 2002 5:22 pm Post subject: |
|
|
I was having the same problem as you. I could compile anything except really big stuff like xfree. In addition to your error I was getting "unable to handle kernel NULL pointer" error. A search on the Google revealed a possible memory problem. What I did is this:
Code: | emerge memtest86
nano -w /boot/grub/menu.lst
title=Memory Test
root (hd0,0)
kernel /boot/memtest86/memtest.bin |
I rebooted into "Memory Tests" and ran All Tests overnight. The first 256MB DIMM had over 1500 errors. The other 2 were fine. I took out the defective DIMM and everything compiles flowlessly now. |
|
Back to top |
|
|
|