libf2c

[Dave Love]

>>>>> "Jeff" == Jeffrey A Law <law@hurl.cygnus.com> writes:

 >> I can't immediately point to anything mixing
 >> the compilers can break but what work I've done on the runtime has
 >> always assumed the target compiler is used generally.

 Jeff> It fails for cross compilers :-)  

I assumed without checking that it would DTRT for a cross-compiler :-)

 Jeff> Which is one of the big benefits of getting it out of the gcc
 Jeff> subdir, it's easier to get these issues dealt with correctly.

Perhaps I should again query the issues for criss-cross building, or
maybe they're moot now and won't affect new work.  I obviously
misunderstood what people have been saying for years about problems
with the configuration/build in the face of it working.  If I (or lots
of other keen people!) resume work on the runtime is there anything
obviously important to get into the proverbial thick skull?  Should it
be straightforward just to add code with autoconfism modelled on
what's there when the libf2c dir has settled down?