[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ksh bug on Tru64 UNIX causes current libtool failure

From: Norman Gray
Subject: Re: ksh bug on Tru64 UNIX causes current libtool failure
Date: Thu, 2 Jun 2005 15:49:56 +0200


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 section on shell portability issues.
It's not a major problem -- and may not be a problem at all for
libtool -- but it does make some otherwise attractive idioms

Could you be bothered to suggest a patch to the Autoconf folks?

A good idea -- I'll do that.

Aside from that, do you use this within any autoconf-generated configure
scripts?  Because the modified search *will* affect any package that

I did use this (inheriting FDs) in autoconf macros at one time, but had to rip it out when I discovered that autoconf-generated configure scripts preferred ksh to /bin/sh on Tru64, because /bin/sh didn't support $LINENO (as if I cared!).

Hehe.  I believe Libtool has got OS X covered quite well, unlike Tru64
(and maybe IRIX, HPUX).

Libraries are a headache on OS X, but not in any way libtool can help with, unfortunately. For what it's worth, in managing the build of a large software set libtool has always been fine for me on Tru64. So thanks for that....

All the best,


Norman Gray  :  Physics & Astronomy, Glasgow University, UK  :

reply via email to

[Prev in Thread] Current Thread [Next in Thread]