GCC second pass make error

Ken Moffat ken at linuxfromscratch.org
Sun Jan 28 14:15:09 PST 2007


On Sun, Jan 28, 2007 at 05:27:48PM +0100, Steffen H. Larsen wrote:
> well now I get some other error  ^^
> 
> so I guess that I've either missed some of the things I read or I'm
> pretty bad at typeing what the guide says hehe ^^;
> now this error comes to the screen
> 
> ../../gcc-4.0.2/gcc/crtstuff.c:230: error: parameter '__dso_handle' is
> initializes
> ../../gcc-4.0.2/gcc/crtstuff.c:230: error: redefinition of parameter
> '__dso_handle'
>  ../../gcc-4.0.2/gcc/crtstuff.c:225: error: previous definition of
> '__dso_handle' was here
> ../../gcc-4.0.2/gcc/crtstuff.c:235: error: storage class specified for
> parameter '__exa_finalize'
> ../../gcc-4.0.2/gcc/crtstuff.c:235: error: weak declaration of
> '__exa_finalize'  must be public
> ../../gcc-4.0.2/gcc/crtstuff.c:258: error: storage class specified for
> parameter '__do_global_dtors_aux
> ../../gcc-4.0.2/gcc/crtstuff.c:258: error: warning: 'used' attribute ignored
> ../../gcc-4.0.2/gcc/crtstuff.c:258: error: syntax error before '{' token
> ../../gcc-4.0.2/gcc/crtstuff.c:260: error: storage class specified for
> parameter 'completed'
> ../../gcc-4.0.2/gcc/crtstuff.c:261: error: syntax error before 'func_ptr'
> ../../gcc-4.0.2/gcc/crtstuff.c:302: error: storage class specified for
> parameter 'frame_dummy'
> ../../gcc-4.0.2/gcc/crtstuff.c:302: error: warning: 'used' attribute ignored
> ../../gcc-4.0.2/gcc/crtstuff.c:302: error: syntax error before '{' token
> make[1]: *** [crtbegin.o] error 1
> make[1] Leaving directory '/mnt/hda1/tools/gcc-build/gcc'
> make: *** [all-gcc] error 2
> 
> again the [all-gcc] error but looks difrent to me ?
> is it another error unrelated or related to what I've shown yuo so far ?

 I'm willing to assume that 'gcc-4.0.2' is really 4.0.3, because
you've already stated you are copying this by hand, in the absence
of a network connection on the machine where you are building.  But,
it would not have hurt you to confirm that, or else explain, when you
were asked.

 Me, I don't know very much about the toolchain, I'm just good at
making errors and trying to learn from them.  I _have_ seen error
messages like this before - from broken headers, or from a toolchain
whose versions didn't work well together on the arch I was trying to
build.  If you are building on x86, and you have followed the book
to the second pass of gcc, neither of those possibilities should
exist.

 I was going to suggest that you were somehow using the host's
binutils, and that it was too new (or perhaps too old), but then I
remembered that you said you were using the LiveCD so that
possibility is also a non-starter.  It seems as if you have not
followed the book in some way, so I suggest you start afresh.  This
time, log all the output, including stderr ("I'm using the LiveCD"
isn't a valid excuse - you can always write to
/tools/build/something), and if you are going to power down during
the build from CD, dump your command history, e.g.

 history >/tools/hist1

- dumping the history isn't for our benefit, it's so that when
things go wrong you can look back at your commands to see what you
actually did, and compare that to what you intended to do.

ĸen
-- 
das eine Mal als Tragödie, das andere Mal als Farce



More information about the lfs-support mailing list