Bug 51

Summary: GCC 4.3.2 complains about an incorrect Version of mpfr.h
Product: buildroot Reporter: Jan Kretschmer <kretschi>
Component: OtherAssignee: unassigned
Status: RESOLVED WORKSFORME    
Severity: major CC: buildroot, jacmet
Priority: P5    
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Host: Target: i386
Build: Current SVN
Attachments: File build_i386/gcc-4.3.2-target/config.log - it shows more details
.config file, that produces this error

Description Jan Kretschmer 2009-01-15 14:12:10 UTC
Created attachment 21 [details]
File build_i386/gcc-4.3.2-target/config.log - it shows more details

See the attached config.log for more details. I don't understand, why it's unhappy with this mpfr.
Comment 1 Peter Korsgaard 2009-01-19 12:20:37 UTC
Strange, I don't see that here. Could you try again with a clean tree?
Does the mpfr lib files in toolchain_build_i386/lib/ look sensible?
Comment 2 Jan Kretschmer 2009-01-19 15:46:32 UTC
Hmm...with a clean tree, it works.
I'll try to find out, which option breakes the build.
Perhaps there are problems, when you build the gmp/mpfr-packages for the target?

I'll find it out tomorrow or so ;)
Comment 3 Jan Kretschmer 2009-01-20 12:35:58 UTC
Created attachment 35 [details]
.config file, that produces this error

This configuration definitivly fails on my environment.
Comment 4 Jan Kretschmer 2009-01-20 12:38:36 UTC
I attached a configuration-file, that produces this error.

I'll try to find out the option, that brakes the build.
Comment 5 Peter Korsgaard 2009-01-20 13:06:00 UTC
Sorry, didn't notice it was gcc-target build. Haven't tried that in quite some time, will look into it tonight.
Comment 6 Jan Kretschmer 2009-01-24 14:47:06 UTC
Hm, today I tried again to compile the whole thing in a clean tree and it worked.
I think, one of my changes in the config-file was, that I've chosen strip instead of sstrip. Maybe sstrip is too aggressive, so that it has destroyed the mpfr-library?
Or perhaps someone others change has repaired it? :D
Now I have problems with tar, see the next Bug-report ;)
Comment 7 Peter Korsgaard 2009-01-28 13:40:48 UTC
Ok, closing then