[Top][All Lists]

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

Re: Folder naming bug.

From: Eric Blake
Subject: Re: Folder naming bug.
Date: Mon, 06 Aug 2012 06:58:13 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120717 Thunderbird/14.0

On 08/04/2012 12:45 PM, illusionoflife wrote:
> Hello. I just encountered following bug: 
> I have folloing configure.ac:
>     AC_PREREQ([2.69])
> Now I run `autoreconf -fi` and then ./configure.
> All okay. And now focus: `mkdir core`

Don't do that.  The name 'core' is reserved for core dump regular files,
and creating a directory by the same name will interfere with years of
traditional handling of regular files for core dumps.

> Now ./configure returns following:
> checking for g++... g++
> checking whether the C++ compiler works... yes
> checking for C++ compiler default output file name... a.out
> checking for suffix of executables... 
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C++ compiler... rm: cannot remove 
> 'core': Is a directory
> yes

This is evidence of you violating common assumptions by creating a
directory named 'core'.

> If I rename `core' to `foo', for example, all okay. I bet,

Yep.  You need to pick a different name.  Autoconf is probably not going
to change to work around your one-off naming.

Eric Blake   address@hidden    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

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