On Thu, Oct 06, 2005 at 06:27:32PM +0200, Ralf Wildenhues wrote:
Hi Nicolas,
* Nicolas Joly wrote on Thu, Oct 06, 2005 at 03:00:51PM CEST:
On Thu, Oct 06, 2005 at 02:27:26PM +0200, Ralf Wildenhues wrote:
* Nicolas Joly wrote on Wed, Oct 05, 2005 at 03:22:10PM CEST:
Got 3
Hi Nicolas,
To the Fortran part of your answer:
* Nicolas Joly wrote on Wed, Oct 05, 2005 at 03:22:10PM CEST:
On Wed, Oct 05, 2005 at 10:43:40AM +0200, Ralf Wildenhues wrote:
Could you also try the new test suite?
make check TESTS=
and send tests/testsuite.log for errors.
Got 3
On Thu, Oct 06, 2005 at 02:27:26PM +0200, Ralf Wildenhues wrote:
Hi Nicolas,
To the Fortran part of your answer:
* Nicolas Joly wrote on Wed, Oct 05, 2005 at 03:22:10PM CEST:
On Wed, Oct 05, 2005 at 10:43:40AM +0200, Ralf Wildenhues wrote:
Could you also try the new test suite?
Hi Nicolas,
* Nicolas Joly wrote on Tue, Oct 04, 2005 at 03:36:48PM CEST:
On Tue, Oct 04, 2005 at 12:09:26PM +0200, Ralf Wildenhues wrote:
* Nicolas Joly wrote on Mon, Oct 03, 2005 at 05:57:01PM CEST:
Here follow a small summary for libtool HEAD on my Tru64 v5.1B
workstation.
On Tue, Oct 04, 2005 at 12:09:26PM +0200, Ralf Wildenhues wrote:
Hi Nicolas,
I've removed libtool@ from the list of recipients -- no need to discuss
this on both lists.
* Nicolas Joly wrote on Mon, Oct 03, 2005 at 05:57:01PM CEST:
On Wed, Jul 06, 2005 at 05:08:11AM +0200, Ralf Wildenhues
On Wed, Jul 06, 2005 at 05:08:11AM +0200, Ralf Wildenhues wrote:
Hi Nicolas, others,
Hi Ralf,
This is a gentle reminder that this issue with Libtool HEAD/branch-2-0
on Tru64 sh is still unsolved. It'd be nice to get a solution into the
next 2.0 release candidate, should such a solution
This is the ancient bug report about the Tru64 shell.
* Nicolas Joly wrote on Tue, Jun 07, 2005 at 12:10:47PM CEST:
In the mean time, i tested the solution where `print -r' and `ksh'
tests are swapped (attached patch). It seems to go a little further
(no more `print' error messages), but
On Sun, Jul 10, 2005 at 11:34:13AM +0900, Peter O'Gorman wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Albert Chin wrote:
|05:00 PM dogbert ~$PS1='$ ' /bin/sh
|$ echo Xbla | sed 1s,^X,,
|X,,: not found
|$ sed: Function 1s, cannot be parsed.
|
|
| What system is this? Works
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Albert Chin wrote:
|05:00 PM dogbert ~$PS1='$ ' /bin/sh
|$ echo Xbla | sed 1s,^X,,
|X,,: not found
|$ sed: Function 1s, cannot be parsed.
|
|
| What system is this? Works fine on 4.0D and 5.1.
|
I don't think you tried /bin/sh. Works okay with zsh
On Thu, Jul 07, 2005 at 05:02:26PM -0500, Tim Mooney wrote:
In regard to: Re: FYI: ksh bug on Tru64 UNIX causes current libtool...:
* Ralf Wildenhues wrote on Wed, Jul 06, 2005 at 05:08:11AM CEST:
This is a gentle reminder that this issue with Libtool HEAD/branch-2-0
on Tru64 sh is still
In regard to: Re: FYI: ksh bug on Tru64 UNIX causes current libtool...:
* Ralf Wildenhues wrote on Wed, Jul 06, 2005 at 05:08:11AM CEST:
This is a gentle reminder that this issue with Libtool HEAD/branch-2-0
on Tru64 sh is still unsolved. It'd be nice to get a solution into the
next 2.0
* Ralf Wildenhues wrote on Wed, Jul 06, 2005 at 05:08:11AM CEST:
This is a gentle reminder that this issue with Libtool HEAD/branch-2-0
on Tru64 sh is still unsolved. It'd be nice to get a solution into the
next 2.0 release candidate, should such a solution exist.
Stupid question: Does
* Ralf Wildenhues wrote on Wed, Jul 06, 2005 at 05:08:11AM CEST:
This is a gentle reminder that this issue with Libtool HEAD/branch-2-0
on Tru64 sh is still unsolved. It'd be nice to get a solution into the
next 2.0 release candidate, should such a solution exist.
Stupid question: Does
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
+++
[ This thread starts at
http://lists.gnu.org/archive/html/libtool/2005-05/msg00137.html
and continues at
http://lists.gnu.org/archive/html/libtool/2005-06/msg5.html ]
* Nicolas Joly wrote on Thu, May 19, 2005 at 12:39:43AM CEST:
On Wed, May 18, 2005 at 11:09:21PM +0200, Ralf Wildenhues
On Sun, Jun 05, 2005 at 07:38:59PM +0200, Ralf Wildenhues wrote:
* Nicolas Joly wrote on Thu, Jun 02, 2005 at 09:00:16PM CEST:
On Thu, Jun 02, 2005 at 10:37:27AM +0200, Ralf Wildenhues wrote:
* Nicolas Joly wrote on Thu, Jun 02, 2005 at 01:02:32AM CEST:
On Wed, May 25, 2005 at 06:22:37PM
* Nicolas Joly wrote on Tue, Jun 07, 2005 at 12:10:47PM CEST:
On Sun, Jun 05, 2005 at 07:38:59PM +0200, Ralf Wildenhues wrote:
CONFIG_SHELL=/bin/foosh /bin/foosh path/to/configure [OPTIONS..]
and you should provide an echo which does not interpret backslashes
(one of `echo',
On Tue, Jun 07, 2005 at 12:35:00PM +0200, Ralf Wildenhues wrote:
* Nicolas Joly wrote on Tue, Jun 07, 2005 at 12:10:47PM CEST:
On Sun, Jun 05, 2005 at 07:38:59PM +0200, Ralf Wildenhues wrote:
CONFIG_SHELL=/bin/foosh /bin/foosh path/to/configure [OPTIONS..]
and you should provide
* Nicolas Joly wrote on Tue, Jun 07, 2005 at 01:27:25PM CEST:
On Tue, Jun 07, 2005 at 12:35:00PM +0200, Ralf Wildenhues wrote:
* Nicolas Joly wrote on Tue, Jun 07, 2005 at 12:10:47PM CEST:
In the mean time, i tested the solution where `print -r' and `ksh'
tests are swapped (attached
On Tue, Jun 07, 2005 at 03:31:22PM +0200, Ralf Wildenhues wrote:
* Nicolas Joly wrote on Tue, Jun 07, 2005 at 01:27:25PM CEST:
On Tue, Jun 07, 2005 at 12:35:00PM +0200, Ralf Wildenhues wrote:
* Nicolas Joly wrote on Tue, Jun 07, 2005 at 12:10:47PM CEST:
In the mean time, i tested
* Nicolas Joly wrote on Thu, Jun 02, 2005 at 09:00:16PM CEST:
On Thu, Jun 02, 2005 at 10:37:27AM +0200, Ralf Wildenhues wrote:
* Nicolas Joly wrote on Thu, Jun 02, 2005 at 01:02:32AM CEST:
On Wed, May 25, 2005 at 06:22:37PM +0200, Ralf Wildenhues wrote:
OK to apply this patch to
Hi Nicolas,
* Nicolas Joly wrote on Thu, Jun 02, 2005 at 01:02:32AM CEST:
On Wed, May 25, 2005 at 06:22:37PM +0200, Ralf Wildenhues wrote:
OK to apply this patch to branch-2-0 and HEAD, and then backport to
branch-1-5?
Sorry for the delay.
No problem. Sorry for not providing a
Greetings,
On 2005 Jun 2 , at 10.37, Ralf Wildenhues wrote:
Alternatively, the better option might be to tweak *DETECT_BETTER_SHELL
to prefer ksh over bin/sh..
I don't really want to intervene in this debate, but: wince. ksh has
at least the unfortunate property that all file descriptors
Ralf,
On 2005 Jun 2 , at 13.03, Ralf Wildenhues wrote:
ksh has at least the unfortunate property that all file descriptors
other than 0, 1, 2 are closed before an exec, and so aren't inherited
by process children. Ksh seems unique in this, though it isn't listed
as a problem in the autoconf
In regard to: Re: ksh bug on Tru64 UNIX causes current libtool failure,...:
Oooh yes; oh yes indeedy. I've come to the conclusion that if your
application builds on Tru64 and OS X, then it'll build just about anywhere.
I'm surprised by this comment. Tru64 has a more common C API than say
Tim,
On 2005 Jun 2 , at 17.50, Tim Mooney wrote:
In regard to: Re: ksh bug on Tru64 UNIX causes current libtool
failure,...:
Oooh yes; oh yes indeedy. I've come to the conclusion that if your
application builds on Tru64 and OS X, then it'll build just about
anywhere.
I'm surprised
On Wed, May 25, 2005 at 06:22:37PM +0200, Ralf Wildenhues wrote:
[ Alexander, the patch to work around shell bugs on your platform breaks
on other ones. As the failure on yours are more harmless, I'd like to
revert them. See the thread on the libtool mailing list. ]
* Nicolas Joly wrote on
[ Alexander, the patch to work around shell bugs on your platform breaks
on other ones. As the failure on yours are more harmless, I'd like to
revert them. See the thread on the libtool mailing list. ]
* Nicolas Joly wrote on Thu, May 19, 2005 at 12:39:43AM CEST:
On Wed, May 18, 2005 at
[ Alexander, the patch to work around shell bugs on your platform breaks
on other ones. As the failure on yours are more harmless, I'd like to
revert them. See the thread on the libtool mailing list. ]
* Nicolas Joly wrote on Thu, May 19, 2005 at 12:39:43AM CEST:
On Wed, May 18, 2005 at
On Sun, May 15, 2005 at 06:35:33AM +0200, Ralf Wildenhues wrote:
Hi Albert,
* Albert Chin wrote on Sun, May 15, 2005 at 04:27:05AM CEST:
* ltmain.in: New variable quote_scanset to work around SunOS ksh
`case' backslash-escaping bug: protect character class by variable
expansion.
Hi Albert,
* Albert Chin wrote on Tue, May 17, 2005 at 11:04:33PM CEST:
On Sun, May 15, 2005 at 06:35:33AM +0200, Ralf Wildenhues wrote:
* Albert Chin wrote on Sun, May 15, 2005 at 04:27:05AM CEST:
case foobar in
*\)*)
echo bar ;;
esac
$ ./quote
+ echo bar
bar
On Wed, May 18, 2005 at 08:33:01AM +0200, Ralf Wildenhues wrote:
If not, let me see: This failure only causes quote.test to fail, and
causes a lot of extra quotes in the libtool output, but no real failure.
Is that correct?
Not really.
I can't even compile libtool 1.5.18 on my Tru64 unix
On Wed, May 18, 2005 at 08:33:01AM +0200, Ralf Wildenhues wrote:
* Albert Chin wrote on Tue, May 17, 2005 at 11:04:33PM CEST:
On Sun, May 15, 2005 at 06:35:33AM +0200, Ralf Wildenhues wrote:
* Albert Chin wrote on Sun, May 15, 2005 at 04:27:05AM CEST:
case foobar in
*\)*)
On Wed, May 18, 2005 at 05:03:05PM +0200, Nicolas Joly wrote:
On Wed, May 18, 2005 at 08:33:01AM +0200, Ralf Wildenhues wrote:
If not, let me see: This failure only causes quote.test to fail, and
causes a lot of extra quotes in the libtool output, but no real failure.
Is that correct?
Hi Nicolas,
* Nicolas Joly wrote on Wed, May 18, 2005 at 05:03:05PM CEST:
On Wed, May 18, 2005 at 08:33:01AM +0200, Ralf Wildenhues wrote:
If not, let me see: This failure only causes quote.test to fail, and
causes a lot of extra quotes in the libtool output, but no real failure.
Is
In regard to: Re: ksh bug on Tru64 UNIX causes current libtool failure,...:
And for possible workarounds: Does Tru64 ship another shell suitable
for use as CONFIG_SHELL? Please try with
CONFIG_SHELL=/bin/foosh /bin/foosh path/to/libtool/configure [OPTIONS]
You might try /usr/bin/posix/sh . I'm
On Wed, May 18, 2005 at 11:09:21PM +0200, Ralf Wildenhues wrote:
Hi Nicolas,
* Nicolas Joly wrote on Wed, May 18, 2005 at 05:03:05PM CEST:
On Wed, May 18, 2005 at 08:33:01AM +0200, Ralf Wildenhues wrote:
If not, let me see: This failure only causes quote.test to fail, and
causes a
On Wed, May 18, 2005 at 05:34:45PM -0500, Tim Mooney wrote:
In regard to: Re: ksh bug on Tru64 UNIX causes current libtool failure,...:
And for possible workarounds: Does Tru64 ship another shell suitable
for use as CONFIG_SHELL? Please try with
CONFIG_SHELL=/bin/foosh /bin/foosh path
Hi Albert,
* Albert Chin wrote on Sun, May 15, 2005 at 04:27:05AM CEST:
* ltmain.in: New variable quote_scanset to work around SunOS ksh
`case' backslash-escaping bug: protect character class by variable
expansion. Reported by Alexander Kurz [EMAIL PROTECTED].
Unfortunately, due to
On branch-1-5, the following change was checked in 2004/12/28:
revision 1.334.2.45
date: 2004/12/28 12:39:15; author: rwild; state: Exp; lines: +18 -14
* ltmain.in: New variable quote_scanset to work around SunOS ksh
`case' backslash-escaping bug: protect character class by variable
40 matches
Mail list logo
