This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
RE: build problem on cygwin
Hi!
I found an error in the config.log regarding the FILE type. The reason
were misplaced header files for the *cross-compiler* in /usr/local/include
that, of course, did not know about the FILE type. It seems that
/usr/local/include is a default include path for gcc that does not need to
be in the $PATH.
Thanks for your support!
Regards,
Marten
On Fri, 10 Aug 2007, Dave Korn wrote:
> On 10 August 2007 16:45, Marten Bandholz wrote:
>
> Please keep this thread on the binutils list Marten, thank you. (There are
> more people on that list than just me, and I'm off home for the weekend
> now...)
>
> > On Fri, 10 Aug 2007, Dave Korn wrote:
> >
> >> On 10 August 2007 15:55, mba wrote:
> >>
> >>> I experience a build error when trying to configure the binutils on
> >>> cygwin:
> >>>
> >>> cd binutils-2.17/
> >>> ./configure --prefix=/usr/local/msp430 --target=msp430
> >>> make
> >>> [...]
> >>> checking for long long... yes
> >>> checking for long long... yes
> >>> checking sizeof long long... configure: error: cannot compute the sizeof
> >>> (long long), 77
>
> >> Dunno, but something else must be going wrong here, because it worked
> >> fine for me.
> >
> > I was already guessing so ;)
> >
> >> Try again, but this time add the "-v" option to your command line. That
> >> should get more diagnostic output from configure.
> >
> > Actually, the configure is quite short and works ok. The error shows up
> > during a longish make.
>
> That's just the way binutils works: the initial configure just configures
> the top level, then as make descends into each subdir, it configures and
> builds each one as it goes along.
>
> > I attached the two log files (performing configure with -v, and make
> > afterwards). As you can see make aborts and I get an 'error: cannot
> > compute sizeof (long long), 77' on the console.
> >
> > ./configure -v --prefix=/usr/local/msp430 --target=msp430 >
> > configure_log.txt
> >
> > make > make_log
> >
> > Please let me know if you have any idea what I could try.
>
> As a result of the -v, there should be detailed configure output in
> bfd/config.log. That's what you need to look at, not just the output that you
> get on the command line; it's got far more detail.
>
>
>
> cheers,
> DaveK
> --
> Can't think of a witty .sigline today....
>