Re: feature sanity.sh failure on OpenBSD 3.5 sparc64

[Derek Robert Price]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alexander Taler wrote:

> Seeing another message about getopt from Derek made me realize
> that this isn't the actual problem.  The real problem is that
> autoconf thinks the local getopt is good, whereas it's not.  I
> have another getopt problem in log-14 also: "log -r HEAD" behaves
> like "log -rHEAD".  Looking in the configure output, I confirm
> that it's using the system getopt:
>
> checking getopt.h usability... yes
> checking getopt.h presence... yes
> checking for getopt.h... yes
> checking for getopt_long_only... yes
>
> Where are the autoconf checks found and how can we add a new one?


m4/getopt.m4, though that comes from GNULIB, so I'd rather not fork
it, but if you can send bug-gnulib@gnu.org (cc bug-cvs, please) a bug
report with an autoconf test that determines correctly if the system
getopt is usable or not, I can try and help get the patch into GNULIB
and import the change into CVS when done.

Glancing at m4/getopt, it looks like it is currently assuming that if
it can find getopt.h then GNU getopt is available.  Apparently your
OpenBSD version ships with both a getopt.h and a broken getopt.

Cheers,

Derek
- --
                *8^)

Email: derek@ximbiot.com

Get CVS support at <http://ximbiot.com>!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFBaHojLD1OTBfyMaQRAq3LAKD0Fp/a2Fd5CxjsSJE0qjfGG/4n2gCeO4/T
vHZqHQP4YncQJZbCi2ZzUwQ=
=JIcY
-----END PGP SIGNATURE-----