Re: Absolute srcdir

Akim Demaille wrote: > Ralf Corsepius sent me this morning a detailed PR with about the same > behavior. I'm highly tempted to consider this a bash bug, unless > someone can demonstrate the usefulness of the following feature... > [..] > > I suppose we should drop the use of [] here. Pfff. W

Re: Absolute srcdir

Alexandre Oliva wrote: > On Mar 27, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote: > > > I'm highly tempted to consider this a bash bug > > So am I. Which `bash' is that? I've just tested 2.04, and it *does* > present the bug :-( # bash --version GNU bash, version 2.03.0(1)-release (i686-pc-li

Re: Absolute srcdir

--- Alexandre Oliva <[EMAIL PROTECTED]> wrote: > > Or use `[/\\/]', which does work, even with bash 2.04. Or use `[\\/]', which also works. = --- Earnie Boyd: __Cygwin: POSIX on Windows__ Cygwin Newbies:

Re: Absolute srcdir

On Mar 27, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote: > I'm highly tempted to consider this a bash bug So am I. Which `bash' is that? I've just tested 2.04, and it *does* present the bug :-( > I suppose we should drop the use of [] here. Pfff. Or use `[/\\/]', which does work, even with

Re: Absolute srcdir

Akim Demaille writes: > Ralf Corsepius sent me this morning a detailed PR with about the same > behavior. I'm highly tempted to consider this a bash bug, unless > someone can demonstrate the usefulness of the following feature... I tend to agree. I ran your little script with /bin/sh and /bin/k

Re: Absolute srcdir

Ralf Corsepius sent me this morning a detailed PR with about the same behavior. I'm highly tempted to consider this a bash bug, unless someone can demonstrate the usefulness of the following feature... /tmp/build % cat /tmp/foo.sh nostromo 19:22 #! /bin/sh ca

Re: Absolute srcdir

I'm on something comparable in Autoconf. Don't know if it's the same, but I'll keep you informed. Akim

Absolute srcdir

Hello! Sorry for the crosspost. I don't know if it's a problem with Autoconf or with Automake. Libtool is probably just a victim in this case. Autoconf, Automake, Libtool are fresh from CVS. Linux PPC 1999 Q3, gcc-2.95.2, m4-1.4, bash-2.03.1 is /bin/sh. depdemo-make.test fails. It appears that

Re: Modulating library installation

On Mar 27, 2000, "Braden N. McDaniel" <[EMAIL PROTECTED]> wrote: > EXTRA_LTLIBRARIES = libfoo.la > Depending on what happens in configure, one of INSTALL_LIBFOO or > NOINSTALL_LIBFOO will resolve to "libfoo.la" and the other variable > will be empty. Unfortunately, when you build a libtool EX

Modulating library installation

I'm trying to allow configure to modulate whether or not a libtool library is installed. I have in my Makefile.am: lib_LTLIBRARIES = @INSTALL_LIBFOO@ noinst_LTLIBRARIES = @NOINSTALL_LIBFOO@ EXTRA_LTLIBRARIES = libfoo.la Depending on what happens in configure, one of INSTALL_LIBFOO or NOINS

Re: the appropriate location for depcomp

From: Akim Demaille <[EMAIL PROTECTED]> Subject: Re: the appropriate location for depcomp Date: 27 Mar 2000 10:16:49 +0200 > If you mean for *all* the files, I'm all for it. Amongst the various > choices, the best one is most probably the one which needs the > smallest amount of documentation, h

Re: the appropriate location for depcomp

> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes: Tom> So, I'm planning to change the rule to always choose top_srcdir Tom> as the default location (i.e., in the final step). Comments? If you mean for *all* the files, I'm all for it. Amongst the various choices, the best one is most probab

Re: flex -lfl

> "Sascha" == Sascha Ziemann <[EMAIL PROTECTED]> writes: Sascha> - How can I check for flex and bison instead of lex and yacc? Sascha> I use some flex/bison specific features, which would not work Sascha> with lex/yacc. Here's what I do: # I want flex, and only flex AM_PROG_LEX if test "$LE

Re: the appropriate location for depcomp

On Mar 25, 2000, Tom Tromey <[EMAIL PROTECTED]> wrote: > * Otherwise, this means the file wasn't found. If we're installing it, > install it locally. > So, I'm planning to change the rule to always choose top_srcdir as the > default location (i.e., in the final step). Comments? Sounds good