[Top][All Lists]

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

Re: new module 'ldd'

From: Bruno Haible
Subject: Re: new module 'ldd'
Date: Thu, 12 Jan 2006 21:13:49 +0100
User-agent: KMail/1.5

Ralf Wildenhues wrote:
> > The LDDPROG can also be used outside the shell wrapper, by other macros
> > or Makefile commands, where LC_ALL=C is not necessarily guaranteed. But
> > it will probably not hurt if I put LC_ALL=C before any LDDPROG value.
> Yes, good argument.  I think it would be even better to use
> to facilitate `exec $LDDPROG', and other situations where the first
> component is really supposed to be a program.  You could use exec in
> ldd.sh.

I cannot use exec in ldd.sh, since the output of the command is piped
through a sed command.

Even if I could use exec there, "exec env LC_ALL=C $LDDPROG" is slower
than "LC_ALL=C $LDDPROG", because "env" costs 1 fork() and 1 exec()
whereas "exec" optimizes away only the fork() - the exec() remains
additional burden. The optimal way to write it in this case is


reply via email to

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