Home Original page

HEAD b0rked re coff-tic80?

Dave Korn dave.korn@artimi.com
Thu Apr 28 12:19:00 GMT 2005 
----Original Message----
>From: Dave Korn
>Sent: 28 April 2005 11:44

> ----Original Message----
>> From: Nick Clifton
>> Sent: 28 April 2005 11:36
> 
>> Hi Dave,
>> 
>>>   There's something more fundamental here, isn't there?  Presumably
>>> obj-coff.h and tc-i386.h have not previously been being included in the
>>> same compilation unit.  Previously it was coff-tic80.h and the system's
>>> /usr/include/_ansi.h, so something's now pulling lots of coff-related
>>> headers into places they didn't used to be, perhaps?
>> 
>> Indeed.  How exactly did you configure this toolchain ?  And what type
>> of host are you building it on ?
> 
> 
> 
> dk@mace /usr/build/binutils-obj> head -7 config.status  | tail -1
> # /usr/build/binutils-src/src/configure  --prefix=/usr/build/install -v
> dk@mace /usr/build/binutils-obj> /usr/build/binutils-src/src/config.guess
> i686-pc-cygwin
> dk@mace /usr/build/binutils-obj>

  Oops.  Wrong build dir.  Host still applies, but configure command did of
course have all targets enabled:

dk@mace /usr/build/binutils-obj-new> head -7 config.status  | tail -1
# /usr/build/binutils-src/src/configure  --prefix=/usr/build/install
--enable-ta
rgets=all -v

..pardon the noise.  I'm just trying it again with a freshly-checkedout cvs
tree; if anything changes I'll report.

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....
More information about the Binutils mailing list