On Wed, Aug 13, 2008 at 09:13:55AM +0000, Cliff McDiarmid wrote: > I'm trying to upgrade Gcc to 4.2.1 on my LFS 6.1 by placing it in a > different dir. to my old version. That's the easy bit, at the > moment I'm getting the following error message a long way into the > build and not only with this ver. but more recent as well:
In my experience when you see strings of parse errors like this it is due to a missing header file. Is there a warning about a missing header before the errors start? And, while we're on the subject, does anyone know why gcc chooses to continue parsing after failing to find a header? I've never seen it do anything except generate spurious errors that hide the real problem. Every time it's happened to me it would have been far more convenient if it had stopped when the #include failed. Is it just me or is gcc's behaviour here just plain dumb? Regards, Jeremy Henty -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
