Ralf Wildenhues wrote:
* Bruce Korb wrote on Wed, Jan 11, 2006 at 06:15:58PM CET:
Ralf Wildenhues wrote:
Which system are you on? Where is mktemp(1) from?
This is the crux of the issue: ``Where is mktemp(1) from?''
The code assumes that:
f=`mktemp -d -q xxxxx`
leaves the environment variable "f" containing the name of the
directory. "mktemp(1)" is not a well-established tool and the
``-q'' option caused the one I was using to create the directory
and not echo out its name. Consequently, the code assumed that
the ``mktemp -d'' failed when it had not. So, the fix is to
either test mktemp behavior before using it or to not use it.
(BTW, the one I am using I wrote more than a decade ago.
I changed the behavior of ``-q'', but nevertheless it is not
a standard tool...)
So, is your mktemp distributed at all anywhere? I mean, it's trivial
to remove the `-q', as we use `2>/dev/null' anyway.
I've given it away and posted it now and again over the years.
Since you redirect stderr to /dev/null, the ``-q'' does not
serve a purpose. So, remove that and the original variant will
work fine. Thanks! - Bruce
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf
