Hi!
Is there any special reason that automake 1.5 sets CDPATH to ':' in
some tests in auxdir.m4 and init.m4? This breaks automake (and
configure scripts generated from it) on platforms like Darwin (a.k.a
Mac OS X), where /bin/sh is zsh. What happens is that the 'cd' also
prints the new direct
On Sun, Sep 23, 2001 at 10:03:05AM +0200, Christoph Pfisterer wrote:
> Hi!
>
> Is there any special reason that automake 1.5 sets CDPATH to ':' in
That's something we are currently solving in the current CVS Automake :)
Yep, it's a pain :(
>>> "Ben" == Ben Smith <[EMAIL PROTECTED]> writes:
[...]
Ben> Another option for me may have been to put all the
Ben> optional stuff in a separate directory and add that
Ben> directory via @extra tests@ to one of the Makefile.am
Ben> files.
You could do it in a similar way, without playing
>> However, I wouldn't want Automake to move the comments. Automake
>> isn't, and doesn't try to be, a make-rule validator for the
>> user-written rules in Makefile.am. It should not move things around
>> inside the rules nor should it remove or add lines to those rules.
>
>Yes. Equally however
[snip]
> > /bin/sh: cd: SoNXLakeShore: Datei oder Verzeichnis nicht gefunden
>
> Can you translate the message to English? I'm guessing that the
> directory doesn't exist (since that's pretty much the main reason 'cd'
> would complain in a build tree).
Sorry, for the missing translation:
/bin/sh