Mark D. Baushke wrote:
> I suspect that something as simple as altering the stdint.m4 existing
> code:
>
> other_includes='
> /* Get those types that are already defined in other system include files. */
> #if defined(__FreeBSD__) && (__FreeBSD__ >= 3) && (__FreeBSD__ <= 4)
> # include
> #endi
Mark D. Baushke wrote:
> Paul Eggert <[EMAIL PROTECTED]> writes:
>
> > "Mark D. Baushke" <[EMAIL PROTECTED]> writes:
> >
> > > is it desirable to make those modules depend on stdint.m4 and avoid the
> > > HAVE_STDINT_H macro?
> >
> > Yes, I think so, in the long run. But in the short run, stdint.
Mark D. Baushke wrote:
> A system without an file, will have the stdint_.h turned into
> a valid one. However, the HAVE_STDINT_H will not be defined. This causes
> problems with files like cycle-check.h which does:
>
> # if HAVE_STDINT_H
> # include
> # endif
This by itself is not a problem. c
Paul Eggert writes:
>
> [EMAIL PROTECTED] (Larry Jones) writes:
> >
> > I don't understand that recommendation. Since is supposed
> > to #include , why isn't the recommendation:
>
> As I recall, it's for some older hosts where does not
> include . Sorry, I don't recall the details.
That's in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Larry Jones <[EMAIL PROTECTED]> writes:
> Paul Eggert writes:
> >
> > For cycle-check.h I'd think this wouldn't be a problem, since
> > cycle-check.h uses this Autoconf-recommended sequence:
> >
> > # if HAVE_INTTYPES_H
> > # include
> > # endif
>
[EMAIL PROTECTED] (Larry Jones) writes:
>> # if HAVE_INTTYPES_H
>> # include
>> # endif
>> # if HAVE_STDINT_H
>> # include
>> # endif
>
> I don't understand that recommendation. Since is supposed
> to #include , why isn't the recommendation:
As I recall, it's for some older hosts where doe
Paul Eggert writes:
>
> For cycle-check.h I'd think this wouldn't be a problem, since
> cycle-check.h uses this Autoconf-recommended sequence:
>
> # if HAVE_INTTYPES_H
> # include
> # endif
> # if HAVE_STDINT_H
> # include
> # endif
I don't understand that recommendation. Since is supposed
"Mark D. Baushke" <[EMAIL PROTECTED]> writes:
> and similar code in the generated stdint.h file, would be sufficient to
> make things work... in other words, leave out all of the hacks as to
> which OS may or may not define those files and just test for them.
That would be fine with me. Perhaps
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Eggert <[EMAIL PROTECTED]> writes:
> "Mark D. Baushke" <[EMAIL PROTECTED]> writes:
>
> > The HAVE_STDINT_H is defined, even though it is useless and there is an
> > stdint.h which is generated and includes the useless SGI version and
> > generat
"Mark D. Baushke" <[EMAIL PROTECTED]> writes:
> The HAVE_STDINT_H is defined, even though it is useless and there is an
> stdint.h which is generated and includes the useless SGI version and
> generates warnings for everything because of the include of
Ah, OK, so the problem is in the combinatio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Eggert <[EMAIL PROTECTED]> writes:
> "Mark D. Baushke" <[EMAIL PROTECTED]> writes:
>
> > is it desirable to make those modules depend on stdint.m4 and avoid the
> > HAVE_STDINT_H macro?
>
> Yes, I think so, in the long run. But in the short ru
"Mark D. Baushke" <[EMAIL PROTECTED]> writes:
> is it desirable to make those modules depend on stdint.m4 and avoid the
> HAVE_STDINT_H macro?
Yes, I think so, in the long run. But in the short run, stdint.m4 is
not yet reliable enough (as you're finding out with SGI), and some
packages don't wa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Bruno & Jim,
A system without an file, will have the stdint_.h turned into
a valid one. However, the HAVE_STDINT_H will not be defined. This causes
problems with files like cycle-check.h which does:
# if HAVE_STDINT_H
# include
# endif
Similar
13 matches
Mail list logo
