[Top][All Lists]

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

Re: configure cd'ing to home

From: Eric Blake
Subject: Re: configure cd'ing to home
Date: Mon, 26 Jul 2010 07:40:21 -0600
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100720 Fedora/3.1.1-1.fc13 Lightning/1.0b2pre Mnenhy/0.8.3 Thunderbird/3.1.1

[adding bug-automake]

On 07/23/2010 05:31 PM, Sam Silla wrote:
> Hi,
> I'm getting the following error:
>  cd  && /bin/sh ./config.status Makefile
> /bin/sh: ./config.status: No such file or directory
> It seems the configure file is changing directories to home, which isn't
> correct. Any ideas what's wrong? I'm guessing the srcdir variable isn't
> being set properly.

Which package was this where you encountered the problem?  Perhaps it is
a problem specific to that package?

At any rate, I think the problem is more likely to be in automake than
in autoconf, since this is a case of bad quoting in the Makefile, which
is not under autoconf's control.

In particular, I note that automake generates the following:

            cd $(top_builddir) && $(SHELL) ./config.status $@
$(am__depfiles_maybe);; \

If, for some reason, $(top_builddir) didn't get defined correctly, then
that would explain your symptoms.  Automake could protect itself a bit
better by using

cd '$(top_builddir)' && ...

since "cd" will succeed but "cd ''" will fail, but that still doesn't
explain the root cause for $(top_builddir) not expanding correctly.

Or maybe the package you are compiling didn't use automake, and it is a
bug in their hand-written

Eric Blake   address@hidden    +1-801-349-2682
Libvirt virtualization library

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

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