Re: FYI: fix m4_cdr

Ralf Wildenhues <[EMAIL PROTECTED]> writes: > Could this interface (m4_car/m4_cdr) be published? It'd be fine with me, if someone writes some reasonable documentation for that area. (Documentation is often the hard part, and that's certainly the case here.)

Re: pointer conversion errors

Ralf Wildenhues <[EMAIL PROTECTED]> writes: > [ Paul, the rest of this thread will be readable soon at > http://lists.gnu.org/archive/html/libtool-patches/2005-11/msg2.html > We'd be interested in your opinion on this matter -- thanks. ] My understanding is that even with the patch, you'll st

Re: CONFIG_SHELL and `./config.status --recheck'

Ralf Wildenhues <[EMAIL PROTECTED]> writes: > One possibility would be to restart once with /bin/sh, or, if part of > the environment, with CONFIG_SHELL, or, after parsing the command line, > with CONFIG_SHELL, if that is given there. All of this is very slow > (read: dog-slow), and I'd really li

Re: CONFIG_SHELL and `./config.status --recheck'

That patch looks good to me, except: > + CONFIG_SHELL=$SHELL exec $SHELL $[0] $ac_configure_args > \$ac_configure_extra_args --no-create --no-recursion Many shells treat "A=B exec COMMAND" differently; they ignore the assignment. For example, ksh M-11/16/88i, or Solaris 10 /bin/sh. I suspect t

Re: document AS_SHELL_SANITIZE and AS_BOURNE_COMPATIBLE

Ralf Wildenhues <[EMAIL PROTECTED]> writes: > * lib/m4sugar/m4sh.m4 (_AS_BOURNE_COMPATIBLE): Renamed to.. > (AS_BOURNE_COMPATIBLE): ..this. > (_AS_RUN, AS_SHELL_SANITIZE): Adjusted all callers. > * doc/autoconf.texi (Programming in M4sh): Document > AS_BOURN

Re: Tru64/OSF: BIN_SH revisited

Ralf Wildenhues <[EMAIL PROTECTED]> writes: > 0a) Revert the change to set BIN_SH in Autoconf, in order to be > consistent. > > 0b) Additionally, prepend /usr/bin/posix/ to the path walk of > _AS_DETECT_BETTER_SHELL, to choose the right shell right away, inside > Autoconf. This sounds good to me.

Re: Tru64/OSF: BIN_SH revisited

Stepan Kasal <[EMAIL PROTECTED]> writes: > These two changes would make the following patch; OK to commit? Yes, except you need to modify the Autoconf documentation accordingly.

Re: Avoid compiler warnings

Eric Blake <[EMAIL PROTECTED]> writes: > I don't know if this is worth fixing upstream in autoconf, Just barely. I installed this: 2006-08-22 Paul Eggert <[EMAIL PROTECTED]> * lib/autoconf/c.m4 (AC_C_CONST): Don't used shadowed vars, to pacify

Re: new config-h module, to remove the need for -DHAVE_CONFIG_H

Ralf Wildenhues <[EMAIL PROTECTED]> writes: > Before syncinc argz* with gnulib: why does gnulib/config/srclist.txt > list these files as GPL, as do the gnulib file headers, but modules/argz > says LGPL, and libltdl is distributed with LGPL + special exception? For the same reason libc files are l

Re: strings.h in argz.c?

Ralf Wildenhues <[EMAIL PROTECTED]> writes: > We got a bug report about Libtool 1.5.22 and SunOS 4.1.x this year, so > I'm not doing any C89 cleanup on branch-1-5. "this year" meaning 2007? Or in the last 12 months? I searched for such a bug report and found only

Re: strings.h in argz.c?

Ralf Wildenhues <[EMAIL PROTECTED]> writes: > IIRC that was because I could not get into contact with the bug reporter. My experience is that everyone who's reported a bug against SunOS 4.1.x for several years, is either (1) doing it only because they're worried we might still want to be portable

Re: Autotest-test failures on AIX with NFS and shared libraries

Ralf Wildenhues <[EMAIL PROTECTED]> writes: > 2007-02-12 Ralf Wildenhues <[EMAIL PROTECTED]> > > * lib/autotest/general.m4 (AT_INIT): With --clean, return exit > status of rm so we know when it failed. > If cleaning of test dir failed before running the test, warn. > Outp

Re: git-version-gen w/o git

On 11/29/2012 11:12 PM, Peter Rosin wrote: This seems to be stalled because of a misconception. Can I please get a second opinion? Please? I'm afraid I don't understand the problem well enough to offer an opinion -- maybe it's because I don't understand the desire to do maintenance without git

Re: git-version-gen w/o git

On 12/27/2012 03:41 PM, Peter Rosin wrote: If it helps I can regenerate with your redirection fix, but I assume whoever commits it can fix that part easily enough. Just let me know. How about if you do that, and we give Eric and/or others a week or two to comment, and if there's no objection t

[patch #10282] port libtool to grep 3.8 and to POSIX

mments: --- Date: Mon 19 Sep 2022 01:27:13 PM PDT By: Paul Eggert GNU grep 3.8 warns about some regular expressions that POSIX says have undefined effect, e.g., '\-'. Unfortunately Libtool uses regular expressions of this form. I'm attaching two pro

[patch #10282] port libtool to grep 3.8 and to POSIX

Follow-up Comment #1, patch #10282 (project libtool): This patch partly duplicates patch #10275, but it is more complete as it fixes more instances of the problem. Sorry I did not notice this earlier. I do not know how to merge the patch requests.

[patch #10275] link-order.at: fix tests with GNU grep 3.8

Follow-up Comment #1, patch #10275 (project libtool): Oh, I see I independently reported the bug and proposed a more-complete patch in patch #10202. Sorry about the duplication. ___ Reply to this item at:

[patch #10282] port libtool to grep 3.8 and to POSIX

Follow-up Comment #3, patch #10282 (project libtool): [comment #2 comment #2:] > Did you test to see if the new pattern still works with `grep` < 3.8 by any chance? Yes, it works. > Just to check my understanding here: the intention of `[[-]]L` is to escape `"[-]L"` in M4, taking advantage of th