[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Problem with configure falsely detecting presence ofsystemroutines(w
Derek Robert Price
Re: Problem with configure falsely detecting presence ofsystemroutines(while porting to NSK)
Fri, 03 Oct 2003 15:12:11 -0400
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
-----BEGIN PGP SIGNED MESSAGE-----
Kelly F. Hickel wrote:
| [Kelly Hickel] I fully understand and support the fact that this doesn't
|have to be in the autoconf, I have no problem with telling people they
|have to get Floss and then do the CC above. The problem is that this
|still generates a broken cvs, in that it can't handle files over 52k.
|The patch that I'm proposing to submit only deals with the 52k issue,
|not fixing autoconf. I have previously submitted patches for detecting
|the NSK/OSS environment, I do not believe they've been accepted, but
|they haven't been bounced either. They've vanished into the bit bucket.
The Autoconf or CVS bit bucket? In any case, I thought this was the
subject of a different email thread and hadn't decided how to respond to
| [Kelly Hickel] I suspect that getting a fully functioning AutoConf on
|NSK/OSS is beyond my time availability right now, even if I could
|interest them in it.
It might be enough to say, "hey, configuring on this system fails
because the linker doesn't report errors correctly and Floss deals with
it like this! Would you find this useful?"
| [Kelly Hickel] As far as the _XOPEN_SOURCE_EXTENDED stuff goes, my quick
|googling shows that it's present on several systems (including hpux,
|z-os, tru-64). On the NSK it was needed to resolve some socket calls.
|It may be needed for other things, but it was definitely needed for
Could you write a configure test that can determine that it is necessary
to define _XOPEN_SOURCE_EXTENDED? It is possible that the alternative
is simply putting a note in INSTALL that it was necessary to supply this
option on Tandem. I have a dim recollection of a discussion on
bug-gnulib about defining _XOPEN_SOURCE causing problems due to a
difference of interpretation between platforms. I don't recall if the
bugs were gross or subtle. Not sure what _XOPEN_SOURCE's relationship
to _XOPEN_SOURCE_EXTENDED is either.
Get CVS support at <http://ximbiot.com>!
We have plenty of youth, how about a fountain of smart?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----