On my GNU/Linux system, /usr/include/bits/utmpx.h defines a struct utmpx
that has a member ut_exit that is a struct __exit_status.
This check in m4/readutmp.m4:gl_READUTMP:
AC_CHECK_MEMBERS([struct utmpx.ut_exit],,,[$utmp_includes])
detects that as nonexistent:
| configure:6940: checking for s
Hello Bruno, all,
GCC 4.0.3 and newer (with `-Wall -Werror -fno-builtin' on a GNU/Linux
x86_64 system) errors out at some of the list implementation
"constructor" functions:
| gl_array_list.c: In function ‘gl_array_iterator’:
| gl_array_list.c:398: warning: ‘result.j’ is used uninitialized in this
On Friday 22 September 2006 00:14, Eric Blake wrote:
= > Where did pr enter the picture? We are talking about gm4 here...
=
= pr is a POSIX utility that has an option that takes an optional argument
= (most POSIX-specified utilities do not fit this bill, since POSIX has
= moved away from optional
Hello Simon,
OK to apply this patch? The changes allow
gcc -g -O2 -Wall -Werror -fno-builtin
to compile these files (on GNU/Linux).
Cheers,
Ralf
* gc-gnulib.c [GC_USE_HMAC_SHA1]: include hmac.h for hmac_sha1.
* md4.c (md4_process_block): Remove unused variable.
* rijn
Hello Simon, Jim, Paul, Bruno, all,
OK to apply these patches to make
./configure CC='gcc -Wall -Werror -fno-builtin'
work better (tested on GNU/Linux) with these tests?
(Mind you, I haven't tested any of these changes on other systems.)
Bruno, maybe it's time to kill signed.m4 or make it a no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Mikhail Teterin on 9/21/2006 10:02 PM:
> On Thursday 21 September 2006 23:54, Eric Blake wrote:
> = No, it is FreeBSD that is broken. If you use getopt_long to implement the
> = POSIX requirements of "pr -s _", the GNU version complies wh
On Thursday 21 September 2006 23:54, Eric Blake wrote:
= No, it is FreeBSD that is broken. If you use getopt_long to implement the
= POSIX requirements of "pr -s _", the GNU version complies whether or not
= POSIXLY_CORRECT is set (POSIX requires it to interpret -s with no [...]
Where did pr ente
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Mikhail Teterin on 9/21/2006 9:24 PM:
> FreeBSD's, surely, is fine:
>
> [EMAIL PROTECTED]:/tmp (67) uname -a
> FreeBSD aldan.algebra.com 6.1-STABLE FreeBSD 6.1-STABLE #0: Fri Jul 28
> 11:06:03 EDT 2006 [EMAIL PROTECTED]:/
Hello Jim, Paul, all,
Is this patch ok, or would you rather factor out clock_time.m4 into its
own module (as it is listed by 3 modules already)?
Cheers,
Ralf
* modules/fts-lgpl: Depend on openat.
* modules/mkancesdirs: Depend on savewd.
* modules/mkdir-p: Likewise.
Hello Paul,
* Paul Eggert wrote on Thu, Sep 21, 2006 at 12:18:31AM CEST:
> Ralf Wildenhues <[EMAIL PROTECTED]> writes:
>
> >> That doesn't sound like much of a real problem, but if it is, this
> >> looks to me like a band-aid that doesn't solve things; it'd cut down
> >> the number of bogus messa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
FYI.
My FreeBSD 4.x systems do not have a getopt.h file installed.
My FreeBSD 6.1-RELEASE i386 system says this:
$ ./foo
GNU getopt
$ POSIXLY_CORRECT=1 ./foo
OpenBSD getopt
$
-- Mark
Eric Blake-1 <[EMAIL PROTECTED]> writes:
>
> > > It s
> > It shouldn't be too hard to modify the example to find out for sure...
>
> Could you? I need an example to file a FreeBSD problem report.
>
> Thanks!
Cygwin includes this version of BSD getopt:
/* $OpenBSD: getopt_long.c,v 1.16 2004/02/04 18:17:25 millert Exp $
*/
/* $NetB
четвер 21 вересень 2006 15:14, Eric Blake написав:
> > This program is calling getopt(), not the getopt_long(), that gm4 uses.
> > Is there a similar difference between GNU and BSD getopt_long()
> > implementations?
>
> It shouldn't be too hard to modify the example to find out for sure...
Could y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Mikhail Teterin on 9/21/2006 12:48 PM:
> середа 20 вересень 2006 21:24, Eric Blake написав:
>> Yes. This program demonstrates why the m4 testsuite fails when compiled
>> with a BSD-flavored getopt_long:
>
> You mean, `gmake check'? That
середа 20 вересень 2006 21:24, Eric Blake написав:
> Yes. This program demonstrates why the m4 testsuite fails when compiled
> with a BSD-flavored getopt_long:
You mean, `gmake check'? That did not fail here, when I built it with the
BSD's getopt_long...
> #include
> #include "getopt.h"
>
> in
Mikhail Teterin <[EMAIL PROTECTED]> writes:
> I wonder, how GNU's getopt implementation, where flags' arguments can be
> optional, deals with the cases of such an option followed by something, that
> begins with a dash itself:
>
> m4 -d -X
It's the same way that (for example) 'pr -e' work
> = > Finally, does m4 actually use/document the short-options usage, that's
> = > affected by the POSIX vs. GNU differences in getopt()?
> =
> = Yes, the info documentation for m4's -d discusses the ramifications of
> its
> = argument being optional (and if that text is not clear enough for you,
On Thursday 21 September 2006 09:36, Eric Blake wrote:
= > Finally, does m4 actually use/document the short-options usage, that's
= > affected by the POSIX vs. GNU differences in getopt()?
=
= Yes, the info documentation for m4's -d discusses the ramifications of its
= argument being optional (and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Mikhail Teterin on 9/21/2006 6:57 AM:
>
> When using the short options, please, stick to the POSIX-provided semantics.
GNU m4 (and many other GNU utilities using getopt_long or argp) already do
just that. For the three short options req
On Thursday 21 September 2006 08:51, Eric Blake wrote:
= Sorry, but GNU coding standards require that GNU programs use long
= options, and that is already something that POSIX-specified getopt()
= cannot do.
That's alright -- the BSD getopt_long implementation can.
= Instead, gnulib makes it very
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Mikhail Teterin on 9/21/2006 6:43 AM:
> On Thursday 21 September 2006 08:33, Eric Blake wrote:
> = > getopt(c, v, "r::");
> =
> = ...even though the "::" in this line is what makes this test program leave
> = the realm of POSIX-specifie
On Thursday 21 September 2006 08:33, Eric Blake wrote:
= > getopt(c, v, "r::");
=
= ...even though the "::" in this line is what makes this test program leave
= the realm of POSIX-specified behavior (and why GNU and BSD differ on
= opinion on what should happen).
It would seem to me, that it is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 9/20/2006 7:24 PM:
> Yes. This program demonstrates why the m4 testsuite fails when compiled
> with a BSD-flavored getopt_long:
>
> #include
> #include "getopt.h"
>
> int main(int argc, char **argv) {
>
> int c = 3;
>
Eric Blake wrote:
> > . Although *snprintf code is compiled and linked into libm4, none of
> > > these functions make it into the m4 executable -- are the files
> > > obsolete?
>
> > I'll take a look at that. It may be that it was only used by the code
> > that I deleted when chopping out
24 matches
Mail list logo
