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
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:
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.
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 proposed patches a
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
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
On 12/27/2010 05:03 AM, Bruno Haible wrote:
Your proposed answer don't do that would imply that every library
is distributed in different variants, one for each standards compliance.
No, I was thinking more along the lines don't use -xc99=all.
It's clearly a problem to do that, or anything like
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.
Output the
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
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
We're happy to announce the release of Autoconf 2.61a. This is a test
version, meant to shake out bugs in our switch from 'sed' to 'awk' to
implement 'configure'-time substitutions, and (if 'printf' is
available) from 'echo' to 'printf' to output strings containing
special characters. There is
We're happy to announce the release of Autoconf 2.61.
Please grab it from one of the gnu.org mirror sites.
The important changes since 2.60 are listed below. The BIN_SH change
may require special attention by installers on some older-style
platforms, but as far as we know this affects only
We're happy to announce the release of Autoconf 2.60b. This is a test
version. It is mostly a bug-fix release since 2.60. We hope to
generate Autoconf 2.61 soon, based on feedback from this test version.
The important changes since Autoconf 2.60a are listed below.
The sources and GPG detached
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
We're happy to announce the release of Autoconf 2.60a. This is a test
version. It is mostly a bug-fix release since 2.60. We hope to
generate Autoconf 2.61 soon, based on feedback from this test version.
The important changes since Autoconf 2.60 are listed below.
The sources (1.4 MB) and GPG
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 insanely picky compilers. Problem
, AC_PROG_OBJCPP.
* Major changes in Autoconf 2.59b
Released 2004-08-20, by Paul Eggert.
** AC_CHECK_ALIGNOF
New macro that computes the default alignment of a type.
** AC_CHECK_TOOL, AC_PATH_TOOL, AC_CHECK_TOOLS
When cross-compiling, these macros will give a warning if the tool
Ralf Wildenhues [EMAIL PROTECTED] writes:
OK to apply?
Yes, and thanks.
Do you think we need to announce this change in NEWS?
Not really.
___
http://lists.gnu.org/mailman/listinfo/libtool
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.
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.
The
Ralf Wildenhues [EMAIL PROTECTED] writes:
OK to apply this patch?
Yes, it looks good to me, except please change this:
AT_SETUP([AS@[EMAIL PROTECTED] and AS@[EMAIL PROTECTED])
to this:
AT_SETUP([AS@[EMAIL PROTECTED] and AS@[EMAIL PROTECTED])
Thanks.
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
Ralf Wildenhues [EMAIL PROTECTED] writes:
Likewise, I have been unable to reproduce any issues _without_ `sh -vx'.
I didn't quite follow everything in that thread, but as I understand
it the problem occurs only when one is using sh -vx configure on AIX.
Ralf Wildenhues [EMAIL PROTECTED]
Howard Chu [EMAIL PROTECTED] writes:
I was thinking that, or ((set -o posix) /dev/null 2*1); ... Will
give it a shot.
Another possibility, which I just thought of, is to redirect stdin as
well:
(set -o posix) /dev/null /dev/null 21
Another possibility is to try set +o posix instead of set -o
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 like to
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 still
Akim Demaille [EMAIL PROTECTED] writes:
Now that there are no doubts about the portability of shell functions
(in the sense that there's always a shell on the machine that supports
function ---and maybe the documentation should reflect this),
Yes, it should.
I'm curious about the support of
Bruno Haible [EMAIL PROTECTED] writes:
You are right, the presence of $(ARGZ_H) in $(BUILT_SOURCES) makes this
rule unnecessary. (Historically, the rule predates the use of BUILT_SOURCES.)
Thanks for the hint. I propose this patch in gnulib.
Thanks; I installed that. At the same time I
Ralf Wildenhues [EMAIL PROTECTED] writes:
* doc/autoconf.texi (Limitations of Builtins) case: Mention
Tru64 ksh pattern matching bug.
Thanks. I installed the following slightly-different patch into
autoconf.
--- autoconf.texi 8 Jun 2005 07:13:50 - 1.907
+++
Gary V. Vaughan [EMAIL PROTECTED] writes:
Now for the note to the FSF that explains why we need it... here
is a first cut to get the ball rolling:
That looks fine to me. Thanks.
___
Libtool mailing list
[EMAIL PROTECTED]
Gary V. Vaughan [EMAIL PROTECTED] writes:
However, even though our intentions are good, and we are merely
clarifying the existing spirit of the exception clauses we have used
all along, is it okay to just edit the license of existing files without
explicit permission from the authors?
It's a
Gary V. Vaughan [EMAIL PROTECTED] writes:
Was anybody unhappy with the exception wording in my last post in the
thread? If not we can start from there.
I worry that it's too generous, because it means that if the package
uses the .m4 file as input to autoconf, then the package can also use
Alexandre Duret-Lutz [EMAIL PROTECTED] writes:
or any derived output is a lame attempt to allow tools such as
aclocal (without singling out aclocal) to preprocess the file,
as long as the intent is to build a configure script.
I like the idea, but how about if we generalize it to allow
any
Alexandre Duret-Lutz [EMAIL PROTECTED] writes:
Some ideas:
1. prefix all the m4/*.m4 licenses with `##' so aclocal
omit them from aclocal.m4 (leaving only the unlimited
permission to ... license added by aclocal)
2. add an exception to all the m4/*.m4 files similar to
is discussed in the
Autoconf manual's Shellology section.
Anyway, here's the Autoconf patch I installed.
2004-07-27 Paul Eggert [EMAIL PROTECTED]
* lib/m4sugar/m4sh.m4 (_AS_BOURNE_COMPATIBLE): Use set -o posix
with pdksh, too. Problem reported by Patrick Welche via
Gary
Noah Misch [EMAIL PROTECTED] writes:
I tested this change on a Fedora Core 1 system and all Autoconf
tests continue to pass.
Thanks for your detective work and the fix. I installed your patch
into Autoconf CVS.
I really cannot run the Autoconf test suite on Mac OS X with zsh,
though. It
dropped the ball on that. I didn't like your patch, but
didn't have time to compose a better one at the time. I just took the
time, installed the following patch instead. Please try CVS Autoconf
on your compiler installation to see whether this approach works for
you.
2004-04-20 Paul Eggert
Autoconf 2.59 is now available from the following URLs:
ftp://ftp.gnu.org/gnu/autoconf/autoconf-2.59.tar.gz
ftp://ftp.gnu.org/gnu/autoconf/autoconf-2.59.tar.bz2
Here are the MD5 checksums:
d4d45eaa1769d45e59dcb131a4af17a0 autoconf-2.59.tar.gz
1ee40f7a676b3cfdc0e3f7cd81551b5f
Lars J. Aas [EMAIL PROTECTED] writes:
Is it possible that this is a local problem for the given MKS user I
am working with and that he may have a somewhat faulty MKS
installation or something?
Possibly. It'd be nice if we could have another MKS user report what
happens. Or perhaps you or
The Autoconf team -- Akim, Alexandre, Jim, Paul, and Tom -- is happy
to announce the birth of Autoconf 2.57, a bugfix release.
- Where can I find it?
ftp://ftp.gnu.org/gnu/autoconf/autoconf-2.57.tar.gz (1.1 MB)
ftp://ftp.gnu.org/gnu/autoconf/autoconf-2.57.tar.bz2(811 kB)
and soon
From: Sascha Schumann [EMAIL PROTECTED]
Date: Wed, 9 Oct 2002 19:49:57 +0200 (CEST)
Did you send a bug report? Do you have a test case?
I'm sorry, it was noticed by so many people, I supposed it
would make its way to you.
It's the first I've heard of it. Do you have a URL
From: Akim Demaille [EMAIL PROTECTED]
Date: 25 Sep 2002 12:03:42 +0200
Please, install!
OK, done. I did find some errors in my proposed text (it didn't give
the obvious workaround, and it credited the wrong people for the patch
-- ouch!), so I installed the following patch instead.
---
From: Akim Demaille [EMAIL PROTECTED]
Date: 24 Sep 2002 13:33:43 +0200
So as was kindly suggested by TED, we should have autoreconf work
around Libtool problems.
I missed that suggestion somewhere in my mailbox (currently with 2035
messages to read, sigh); if you think it preferable to the
From: Bruno Haible [EMAIL PROTECTED]
Date: Tue, 11 Dec 2001 15:28:30 +0100 (CET)
ftp://alpha.gnu.org/gnu/gettext/gettext-0.11-pre3.tar.gz.
Thanks. I downloaded it and took a very brief look. It doesn't build
on Solaris 8 + GCC 3.0.2 due to some really minor problems. If you've
already
From: Bruno Haible [EMAIL PROTECTED]
Date: Mon, 19 Nov 2001 19:08:59 +0100 (CET)
1) We don't change our packages. We only tell the user that he should have
used LDFLAGS=-L${prefix}/lib -rpath ${prefix}/lib
6) Let each package search for 'libtool' in $PATH and use it if found,
From: Tim Van Holder [EMAIL PROTECTED]
Date: Fri, 21 Sep 2001 18:44:43 +0200
bash's behaviour with regards to the 'set' builtin has changed in 2.05
This apparently lead to a broken config.cache when using bash 2.05
! ac_cv_path_install=${ac_cv_path_install='ginstall -c'}
---
From: Sascha Schumann [EMAIL PROTECTED]
Date: Tue, 18 Sep 2001 16:00:11 +0200 (CEST)
'{}' can only be used portably, if it is a separate argument.
It's worse than that. Not only must '{}' be separate and not part of
any other argument, it must not be followed by another argument '+'.
47 matches
Mail list logo
