f2c configure fix

Jeffrey A Law law@cygnus.com
Mon Feb 8 21:10:00 GMT 1999

  In message < rzqaeyoblom.fsf@djlvig.dl.ac.uk >you write:
  > Is this problem with configure related to the one that involves the
  > wrong libiberty.h (?) being picked up?  Someone submitted a patch for
  > that which I thought was going to be committed but doesn't seem to
  > have been.  It added a new -I location for the relevant header files,
  > which have moved on us at some stage.  On some systems it fails
  > because the header isn't found; on others it picks up the wrong stuff
  > installed by some other package.  There didn't seem to be a decent way
  > of preventing this happening again once it's fixed :-(.  I don't know
  > off-hand why configure doesn't fail -- I'd have thought it should.
  > Anyone have better ideas for extracting the relevant info?  (This was
  > more foolproof when the f/ directory looked after the runtime.)
The problem is we do not include the right -I arguments to ensure that
we get the right header files.

I do not believe we ever installed the submitted patch.   I don't see
any reference to it in the ChangeLog.


More information about the Gcc-patches mailing list