View previous topic :: View next topic |
Author |
Message |
mathew Guest
|
Posted: Fri Aug 02, 2002 1:22 am Post subject: raidtools-0.90-rc2 emerge failure |
|
|
I had the following error occur when attempting emerge system
Code: | gcc -o mkpv mkpv.o parser.o raidlib.o version.o raid_io.o popt.o
parser.o: file not recognized: File truncated
collect2: ld returned 1 exit status
make: *** [mkpv] error 1
make: *** Waiting for unfinished jobs....
!!! ERROR: The ebuild did not complete successfully.
!!! Function src_compile, Line 4, Exitcode 2
!!! (no error message)
!!! emerge aborting on /usr/portage/sys-apps/raidtools/raidtools-0.90-r2.ebuild
|
After some investigation I was able to fix this by:
changing CFLAGS="-mcpu=i686 -O3 -pipe" rather than CFLAGS="-march=i686 -O3 -pipe" (also CXXFLAGS)
running emerge -autoclean raidtools
After completing this, I typed emerge systeml, and things seem to be progressing okay. Is emerging raidtools with different CFLAGS going to cause problems further down the track? Note that I don't plan to use raid.
FYI, I'm installing gentoo on an IBM NetVista with celeron processor (Model 6339-64A) |
|
Back to top |
|
|
Cloim Tux's lil' helper
Joined: 02 Aug 2002 Posts: 99
|
Posted: Sun Aug 11, 2002 12:38 am Post subject: |
|
|
I just ran into this same error while doing emerge system.
Was using Code: | CFLAGS="-march=i686 -O3 -pipe -fomit-frame-pointer"
CXXFLAGS="-march=i686 -O3 -pipe -fomit-frame-pointer"
|
Tried changing to Code: | CFLAGS="-march=i686 -O3 -pipe
CXXFLAGS="-march=i686 -O3 -pipe
|
Then doing emerge raidtools, and received an 'invalid token' error. Thinking that it was a typo on my part, I changed the flags back and did an emerge raidtools so that I could check the error message again. This time, however, it compiled correctly. When I resumed the emerge system, everything completed.
Maybe a bug in the emerge system script? |
|
Back to top |
|
|
rasmussen Tux's lil' helper
Joined: 31 Aug 2002 Posts: 142 Location: .se
|
Posted: Sun Sep 01, 2002 10:30 am Post subject: |
|
|
I have the same problem with emerge system bombing on raidtools.
I have
Code: |
CFLAGS="-mcpu=i686 -O3 -pipe -fomit-frame-pointer"
CXXFLAGS="-mcpu=i686 -O3 -pipe -fomit-frame-pointer"
|
in my make.conf.
I then removed the '-fomit-frame-pointer' parts, followed by emerge raidtools. No problem then.
Put back in '-fomit-frame-pointer' before continuing emerge system.
BTW, system is Duron 800 on a ECS K7S5A board with 128Mb memory. |
|
Back to top |
|
|
2CUrious n00b
Joined: 17 Jun 2002 Posts: 9
|
Posted: Mon Sep 02, 2002 9:44 pm Post subject: Also raidtool error with emerge system |
|
|
During installation (launching from stage 2 to 3) I ran into the same problem.
I did not change any setting and just did an emerge raidtools.
This time raidtool compiled succesfully. After this I started emerge system again which continued okay
So, yes, it must be some bug in the emerge system procedure |
|
Back to top |
|
|
rac Bodhisattva
Joined: 30 May 2002 Posts: 6553 Location: Japanifornia
|
Posted: Mon Sep 02, 2002 9:50 pm Post subject: |
|
|
I see no bug report filed against raidtools, and the notion of it being "a bug in the emerge system script" doesn't make sense to me. Can anybody who omits frame pointers comment on whether they were able to compile raidtools this way? What editor did everybody in this thread who had problems use to change their make.conf? If the answer is "nano", is it possible that you forgot to use the "-w" switch at some point? _________________ For every higher wall, there is a taller ladder |
|
Back to top |
|
|
rasmussen Tux's lil' helper
Joined: 31 Aug 2002 Posts: 142 Location: .se
|
Posted: Mon Sep 02, 2002 10:02 pm Post subject: |
|
|
I used "nano -w" to remove my "-fomit-frame-pointer" in CFLAGS and CXXFLAGS.
After that I successfully did a manual "emerge raidtools".
As mentioned in my post I put the "-fomit-frame-pointer" back in before continuing with "emerge system". Yes, used "nano -w" for that too. |
|
Back to top |
|
|
2CUrious n00b
Joined: 17 Jun 2002 Posts: 9
|
Posted: Mon Sep 02, 2002 10:52 pm Post subject: emerge system |
|
|
I did also use nano -w. I closely followed the install instructions.
I think it's odd while performing an emerge system I ran into this problem...then I change nothing, just ran emerge raidtools (inspired by this post) succesfully and finished emerge system also succesfully.
Used the CFLAGS and CXXFLAGS setting "-march=i686 -O3 -pipe" |
|
Back to top |
|
|
rac Bodhisattva
Joined: 30 May 2002 Posts: 6553 Location: Japanifornia
|
Posted: Mon Sep 02, 2002 11:01 pm Post subject: |
|
|
Thanks for taking the time to respond. I'm still not sure what to take away from this. Does raidtools refuse to build with -fomit-frame-pointer on? The only thing I can say to 2CUrious is that I agree that it's odd. I note that the raidtools ebuild uses parallel make; could that be the source of it behaving different ways different times? I don't feel confident enough to file a bug report, because I haven't experienced the problem firsthand, and don't feel like I have a good enough understanding yet. I still can't get rid of the nagging feeling that there are multiple problems in this thread. _________________ For every higher wall, there is a taller ladder |
|
Back to top |
|
|
rasmussen Tux's lil' helper
Joined: 31 Aug 2002 Posts: 142 Location: .se
|
Posted: Mon Sep 02, 2002 11:56 pm Post subject: |
|
|
This is probably nonsense, but could it be that compiling with "-fomit-frame-pointer" takes a bit longer, causing some problems in the parallel build? (kinda race-condition thing)
It also looks as if the problem is associated to a truncated parser.o file, causing the linking to fail. |
|
Back to top |
|
|
kirkegard n00b
Joined: 03 Sep 2002 Posts: 11
|
Posted: Tue Sep 03, 2002 3:34 am Post subject: Same problem |
|
|
I'd like to confirm the same problem. I was doing an emerge system, and it aborted with the same error. I changed nothing, did an emerge raidtools, and it completed sucessfully. I then went back to emerge system, and it kept on going. I'm not sure what my exact CFLAGS are, although I can take a look if you'd like. |
|
Back to top |
|
|
rommel Veteran
Joined: 19 Apr 2002 Posts: 1145 Location: Williamsburg Virginia
|
Posted: Tue Sep 03, 2002 5:34 am Post subject: |
|
|
this has failed a couple of times for me but i just ran emerge raidtools when i noticed the system had stoped and it compiled and installed fine...not sure what the problem was....maybe its a memory issue or something...but it doesnt seem to be anything serious |
|
Back to top |
|
|
slais-sysweb Apprentice
Joined: 14 Jun 2002 Posts: 221 Location: London
|
Posted: Tue Sep 24, 2002 6:16 pm Post subject: |
|
|
Had this error several times now. Have tried all the cobinations of compile options suggested above with emerge raidtools still getting the error every time _________________ --
djc
sysweb SLAIS UCL |
|
Back to top |
|
|
|