Martin Lambers <[EMAIL PROTECTED]> writes:
> On Wed, 07. Jun 2006, 14:31:34 +0200, Simon Josefsson wrote:
>> > Is there any interest in this module?
>>
>> Yes. I think it looks good. Unless someone objects soonish, I think
>> we should install it.
>
> I integrated the lates changes to the sys_s
On Wed, 07. Jun 2006, 14:31:34 +0200, Simon Josefsson wrote:
> > Is there any interest in this module?
>
> Yes. I think it looks good. Unless someone objects soonish, I think
> we should install it.
I integrated the lates changes to the sys_socket module.
I also filled in Simon as the maintaine
Eric Blake wrote:
> Using cygwin to cross-compile to mingw, I got:
>
> $ CFLAGS='-Wall -O2' CC='gcc -mno-cygwin' ./gnulib-tool --test mbchar
> ...
> gcc -mno-cygwin -DHAVE_CONFIG_H -I. -I../../lib -I.. -Wall -O2 -
> c ../../lib/mbchar.c
> In file included from ../../lib/mbchar.c:24:
> ../../li
Mark D. Baushke writes:
>
> It would be good to understand how to fix the IRIX 5.x without breaking
> the IRIX 6.x compilation. It appears that the testing of the last run
> on an SGI box failed during the sshstdio-6 test.
Yep -- maybe more cleanup is needed in the test?
--- wrapper.dif Mon Jun
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Martin,
I have Installed Bruno's latest GNULIB changes into the CVS sources.
If there are still problems, it would be good to know what you are
seeing out of the 'configure' command... both the output and selected
parts of the config.log file.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Martin,
As an FYI, one of the test machines that builds the CVS sources nightly
is an SGI IRIX64 running 6.5 (Hmmm... I had thought we also had an SGI
IRIX 5.3 out there somewhere, but I must have been confused as I do not
see any results from such
Martin Neitzel wrote:
> > > # if > 32 ||<=== flagged error here
> > This is valid ANSI C and ISO C 99 code. When you don't pass "-w2" to your
> > compiler, does it show an error or a warning about this?
>
> Omitting -w2 doesn't change anything.
OK, thanks, I'
Using cygwin to cross-compile to mingw, I got:
$ CFLAGS='-Wall -O2' CC='gcc -mno-cygwin' ./gnulib-tool --test mbchar
...
gcc -mno-cygwin -DHAVE_CONFIG_H -I. -I../../lib -I.. -Wall -O2 -
c ../../lib/mbchar.c
In file included from ../../lib/mbchar.c:24:
../../lib/mbchar.h: In function `mb_width_
Just for completeness' sake:
> > I'm using -w2 which turns all warnings into serious errors
> > requiring some treatment (just like gcc -Werror does).
> But this is something we cannot support. [...]
I am perfectly happy with that position. The -w2 treatment is my
personal entertainment. I'd o
> > # if > 32 || <=== flagged error here
> This is valid ANSI C and ISO C 99 code. When you don't pass "-w2" to your
> compiler, does it show an error or a warning about this?
Omitting -w2 doesn't change anything. (Not surprisingly, since -w2 doesn't
soften
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
13 matches
Mail list logo
