Bruno Haible <[EMAIL PROTECTED]> writes:
> Paul Eggert wrote:
>> While looking into an old Bison bug report for IRIX
>
> Where can I find the report, please?
The original bug report is here:
http://lists.gnu.org/archive/html/bug-bison/2005-09/msg00021.html
but alas the log is no longer availabl
Mark Baushke wrote:
> Okay, I tried your 'set -x' that and it appears the error message
> happens just after the func_import () finishes executing.
> ...
> + echo - invoke gl_INIT in ./configure.in.
> - invoke gl_INIT in ./configure.in.
> + exit 0
> + -
> ../gnulib/gnulib-tool: -: not found
I
A gnulib testdir with modules fts and quotearg fails to compile on IRIX 6.5
with CC="cc -O":
cc -O -DHAVE_CONFIG_H -I. -I. -I.. -g -c fts.c
"fts.c", line 244: error(1241): declaration may not appear after executable
statement in block
size_t maxarglen = fts_maxargle
Paul Eggert wrote:
> The output (when compiling Bison) contained oodles of "An enumerated
> type is mixed with another type" diagnostics, because the compiler
> didn't like mixing int values like 0 and 1 (which "false" and "true"
> evaluated to) with bool values. There were so many diagnostics, an
The obstack module does not compile on MacOS X:
Making all in lib
make all-am
gcc -DHAVE_CONFIG_H -I. -I../../../megatestdir/obstack/lib -I.. -g -O2 -c
../../../megatestdir/obstack/lib/exitfail.c
gcc -DHAVE_CONFIG_H -I. -I../../../megatestdir/obstack/lib -I.. -g -O2 -c
../../../megatest
Hi,
Building the module 'fts-lgpl' on Linux/glibc fails like this:
gcc -DHAVE_CONFIG_H -I. -I/packages/megatestdir/fts-lgpl/lib -I.. -g -O2 -c
/packages/megatestdir/fts-lgpl/lib/fts.c
/packages/megatestdir/fts-lgpl/lib/fts.c:75:20: lstat.h: No such file or
directory
The reason is that the
>
> I'm trying this patch. Does it work for you?
>
>
> 2006-01-25 Bruno Haible <[EMAIL PROTECTED]>
>
> * gnulib-tool (func_import): Use "trap :" instead of "trap -" to get
> rid of a trap command. For Solaris sh.
Wouldn't "trap ''" be better than "trap :"? trap '' is documented
Eric Blake wrote:
> Remember this thread, which patched the same bug in install-sh?
> http://lists.gnu.org/archive/html/bug-autoconf/2005-11/msg0.html
Thanks for this pointer. It is regrettable that no doc was added to
the autoconf manual about this pitfall.
> Wouldn't "trap ''" be better tha
Bruno Haible <[EMAIL PROTECTED]> wrote:
> A gnulib testdir with modules fts and quotearg fails to compile on IRIX 6.5
> with CC="cc -O":
>
> cc -O -DHAVE_CONFIG_H -I. -I. -I.. -g -c fts.c
>
> "fts.c", line 244: error(1241): declaration may not appear after executable
> state
Bruno Haible <[EMAIL PROTECTED]> wrote:
> Building the module 'fts-lgpl' on Linux/glibc fails like this:
>
> gcc -DHAVE_CONFIG_H -I. -I/packages/megatestdir/fts-lgpl/lib -I.. -g -O2
> -c /packages/megatestdir/fts-lgpl/lib/fts.c
> /packages/megatestdir/fts-lgpl/lib/fts.c:75:20: lstat.h: No such
Hi Jim,
> Regarding the second patch, I see no explanation for why it
> makes such a fundamental change (not appending `.'?).
Actually the end of that function was a bit incomplete. It should probably
look like this:
/* FILE refers to a symbolic link and the name ends with a slash.
Ca
Bruno Haible <[EMAIL PROTECTED]> writes:
> - "enum" is fundamentally the right concept for this; "enum" in C was
> introduced for exactly this kind of symbolic values,
Quite true, and we should use it when we know that it works.
> - We have already invested some effort
> in these mod
Bruno Haible <[EMAIL PROTECTED]> writes:
> The problem is that obstack.c uses HAVE_INTTYPES_H and HAVE_STDINT_H,
> but these are not set by the autoconf macros.
They ought to be set in the normal case if you are using Autoconf
2.59, since it does that for you if you ever use the default includes.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Bruno,
Bruno Haible <[EMAIL PROTECTED]> writes:
> Mark Baushke wrote:
>
> > Okay, I tried your 'set -x' that and it appears the error message
> > happens just after the func_import () finishes executing.
> > ...
> > + echo - invoke gl_INIT in .
On Mon, 2006-01-23 at 21:51 +0100, Bruno Haible wrote:
> [For the automake people: The problem is that a Makefile.am snippet like
>
> TESTS = test-lock
> check_PROGRAMS = test-lock
> test_LOCK_LDFLAGS = -lmyspeciallib
>
> when cross-compiling to mingw on a Unix system with 'wine',
Mark D. Baushke wrote:
> > I'm trying this patch. Does it work for you?
>
> Yes.
Thanks. I've committed the fix.
> | If argument is absent, all
> | trap(s) n are reset to their original values.
This explains how "trap" without arguments works, not how "trap 0 1 2 3 15"
work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bruno Haible <[EMAIL PROTECTED]> writes:
> Mark D. Baushke wrote:
> > > I'm trying this patch. Does it work for you?
> >
> > Yes.
>
> Thanks. I've committed the fix.
>
> > | If argument is absent, all
> > | trap(s) n are reset
Bruno Haible <[EMAIL PROTECTED]> writes:
> Eric Blake wrote:
>> http://lists.gnu.org/archive/html/bug-autoconf/2005-11/msg0.html
>
> It is regrettable that no doc was added to the autoconf manual about
> this pitfall.
Thanks for reminding me about this. I just now installed this patch:
2006
Bruno Haible <[EMAIL PROTECTED]> writes:
> POSIX says that "trap ''" makes the shell "ignore each specified condition
> if it arises". That means, if the user presses Ctrl-C, the shell will
> continue to run. That's not what I want here. I just wish the Ctrl-C
> to trigger no additional commands,
"Mark D. Baushke" <[EMAIL PROTECTED]> writes:
> I also have a memory of seeing the 'trap 0 1 2 3 15' idiom used
> somewhere
Yes, it's a common idiom and is almost universally supported, but
POSIX is quite clear that "trap 0 1 2 3 15" is supposed to execute the
command "0" when one of the signals
Jim Meyering <[EMAIL PROTECTED]> writes:
> [Hmm.. I see I've also included the change adding O_NOCTTY and O_NONBLOCK.
> I'll update the ChangeLog entry to include that. ]
But the change you checked in removed those rather than adding those.
It also reintroduces the performance bug where we try t
> Yes, it's a common idiom and is almost universally supported, but
> POSIX is quite clear that "trap 0 1 2 3 15" is supposed to execute the
> command "0" when one of the signals 1 2 3 15 arrive.
>
> I reviewed how ksh etc. actually behave, and it's pretty clear that
> this is a bug in POSIX. Non
Paul Eggert <[EMAIL PROTECTED]> wrote:
> Jim Meyering <[EMAIL PROTECTED]> writes:
>
>> [Hmm.. I see I've also included the change adding O_NOCTTY and O_NONBLOCK.
>> I'll update the ChangeLog entry to include that. ]
>
> But the change you checked in removed those rather than adding those.
> It al
23 matches
Mail list logo
