[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Cvs-dev] GNULIB update patch
From: |
Mark D. Baushke |
Subject: |
Re: [Cvs-dev] GNULIB update patch |
Date: |
Mon, 19 Jun 2006 09:08:45 -0700 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Derek R. Price <address@hidden> writes:
> Mark D. Baushke wrote:
> > I should also possibly have a pathname to use for
> >
> > #define FULL_PATH_STDINT_H </path/to/stdint.h>
> >
> > in there as well...
>
> Won't this be bad under Windows?
Well, I tried to '#undef HAVE_STDINT_H' in the config.h.in.in file, but
Jim said it must be '#define HAVE_STDINT_H 1' which implies that such
a file exists. I need to know what pathname it is as there is a
#if @HAVE_STDINT_H@
/* Other systems may have an incomplete <stdint.h>. */
# include @FULL_PATH_STDINT_H@
#endif
which will be turned into
#if 1
/* Other systems may have an incomplete <stdint.h>. */
# include
#endif
otherwise. Right now, I have a
sed -e 's/@''HAVE_STDINT_H''@/0/g' \
in the Makefile.am that generated the stdint.h as a sloppy work-around,
but really that just makes me uneasy.
> What happens if MSVC is installed to a
> different directory (through user choice or a change of defaults in
> different versions of the program)? Does MSVC6 support the
> #include_next directive?
I doubt it. To be perfectly honest, I suspect that there is some other
problem with the HAVE_STDINT_H macro that Jim has not found yet.
The GNULIB folks fixed m4/stdint.m4 and lib/alloca_.h per my bug report,
so I am running a few quick checks and then I'll commit the refresh of
GNULIB which I hope will get us closer to an SGI build that works.
-- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (FreeBSD)
iD8DBQFElswMCg7APGsDnFERAtkGAJoCEf9u1+i7Q/PzOIcCQKhjy++o/QCgxtWM
mhK+xvU7peFXQIdygJqxT18=
=dQ2L
-----END PGP SIGNATURE-----