Re: How does one identify HP-UX with broken inline math funs?

[Jeffrey A Law <law at cygnus dot com>]

  In message <3919620D.12B5D700@sco.com>you write:
  > Jeffrey A Law wrote:
  > >   > How?  Robert Lipe suggests:
  > >   >
  > >   > > $ uname -a
  > >   > > HP-UX udihp B.10.10 B 9000/816 946328291 16-user license
  > >   > >
  > >   > > There are no copyright strings.  Maybe '_INCLUDE_HPUX_SOURCE'
  > >   > > is enough of a clue.  Dunno.
  > >   >
  > >   > Comments?
  > > If I remember correctly, it is a problem with C++.  Even HP recognizes th
  > at
  > > their definitions of those inline fucntions are bogons -- in more recent
  > > versions of hpux the inlines are disabled.
  > > 
  > > If a port is dying because those inlines are removed, then there's someth
  > ing
  > > else more fundamentally wrong with that port as those inlines are broken.
  > > 
  > > Unfortunately, I can't find the discussion behind that code anymore (it w
  > as
  > > circa 1992 after all!)
  > 
  > Well, OK.  You're excused ;-)
  > 
  > I guess what I was really trying to ask was, "what is the
  > config.guess triplet associated with the brokenness?"
  > Presumably, this would include some version cut off whereafter
  > even HP-UX would not have this fix applied.  This way, we can
  > retire the hack in a decade or two :-)
You missed my point that a system which depends on those inlines _not_ being
deleted is broken in some other way.  Rather than disable a fix which removes
bogus inlines, why don't we investigate why Robert's system needs those broken
inline functions.

jeff