This is the mail archive of the
mailing list for the GCC project.
automation: Problem with builddir != srcdir requirement
- From: Claudio Fontana <sick_soul at yahoo dot it>
- To: gcc at gcc dot gnu dot org
- Date: Thu, 2 Mar 2006 16:23:42 -0800 (PST)
- Subject: automation: Problem with builddir != srcdir requirement
I am building a generic installation program for GNU
coding standards-compliant packages.
I am also helping all GNU projects with a
non-compliant build system make the move to the GNU
coding standards, with patches and support.
I have a problem with current builddir != srcdir
requirement in glibc and recent versions of gcc.
Maybe you can give me an advice, or tweak your build
system around this problem.
This program is general enough to build most parts of
a GNU/Linux system automatically from source without
any overhead, or manual tweak.
The problem is that, while an user can read a message
configure: error: you must configure in a separate
A program does not expect this. The trivial solution,
to modify the program to build all packages from a
separate directory, breaks many other packages, which
rely on srcdir == builddir .
There is no mention in the GNU coding standards about
such a requirement. The result is that many packages
break if not built with srcdir == builddir.
If it is really not possible to build in the source
directory, could you detect this and automatically
create a directory "build"? There could also be a
configure option to specify an alternative directory
name, if name clashes are possible.
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB