On Jul 28, 2000, Pavel Roskin <[EMAIL PROTECTED]> wrote:
> + * ltconfig.in: only load $cache_file if it's a regular file
Thanks, I'm checking this in
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.
Hello, Assar!
> > if test -n "$cache_file" && test -r "$cache_file" && test -f \
> > "$cache_file"; then
> >
> > Please check that it works for your ksh.
>
> Yeah, that works fine. Please commit that change and thanks for your
> help.
Maybe this patch will save time to somebody with write acc
Pavel Roskin <[EMAIL PROTECTED]> writes:
> Hello, Assar!
Hi, Pavel.
> if test -n "$cache_file" && test -r "$cache_file" && test -f \
> "$cache_file"; then
>
> Please check that it works for your ksh.
Yeah, that works fine. Please commit that change and thanks for your
help.
/assar
Hello, Assar!
> Is the following patch the right way of solving/working around this?
It's usually better not to rely of exact names and especially on the path
separator. The CVS version of Autoconf does it differently. It never
sources anything other that regular files. "test -f" is used to chec
I'm having problems using libtool-current on Ultrix 4.4
ltconfig re-execs ksh if it did not like the echo in the current shell
(/bin/sh in my case), and the Ultrix ksh seems to dislike doing
. /dev/null
Is the following patch the right way of solving/working around this?
/assar
Index: ltconfig
