Re: strtoul vs g77

[Dave Love <d dot love at dl dot ac dot uk>]

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

 >> The effect worked on SunOS systems IIRC, but
 >> it *broke* the configuration on some systems that *did* have a
 >> working ANSI C library, complete with bsearch() and strtoul(),
 >> and we couldn't figure out why.
 Jeffrey> Well, that's what we have autoconf for -- if it doesn't work
 Jeffrey> on some system that has bsearch and/or strtoul, then we'll
 Jeffrey> go fix autoconf.  This is precisely the kind of problem
 Jeffrey> autoconf should be solving for us.

Yes.  The only reason it wasn't just fixed or noted somewhere as a
problem was lack of a proper bug report; I think the information got
lost about what system it was on.

[I know of at least one system where the (constant?) status returned
by ld rendered autoconf rather useless, but I don't remember in what
direction this went -- whether it caused trouble or just fell back to
OK defaults.  AFAIR the autoconf maintainer declined to put in a
sanity check for such lossage.]

Assuming you did it the same way as originally, it's fine for cross
situations (insofar as the rest of things are); you necessarily have
the tools available when the configuration test is done because you're
about to build f771.

What would be nice would be if we could pick up stuff from libiberty
so that the appropriate routines were just available anyhow (possibly
even for the target by adding them to libgcc.a if appropriate).  I
initially thought that was why libiberty was included.