Le Thu, Dec 14, 2006 at 08:56:27AM -0500, Daniel Jacobowitz écrivait/wrote:
Thanks to Daniel for his reply! > On Thu, Dec 14, 2006 at 10:19:12AM +0100, Basile STARYNKEVITCH wrote: > > In other words, should I make all my configurable flag visible by the > > toplevel configure and propagated (thru Makefile.tpl) to gcc/ or not? > No, you shouldn't. Only add them to subdirs that need them. This makes life much simpler to me, but then I do not understand how end- users compiling GCC are expected to configure it. Does this mean that the instructions on http://gcc.gnu.org/install/configure.html are no more valid for that case? What should be the user installation & configuration procedure replacing the # from http://gcc.gnu.org/install/configure.html mkdir objdir cd objdir srcdir/configure [options] [target] in that case? Should it become mkdir objdir cd objdir srcdir/configure [options-to-toplevel] [target] cd ../objdir/gcc # or simply gcc, but in the build tree srcdir/gcc/configure [options-to-gcc] [target] At last I do not understand why the MPFR & GMP stuff which has been discussed a lot is not already under the above scheme? Why is it cheched at toplevel and not only in gcc/ ? AFAIK the #include <gmp.h> appears only in gcc/real.h BTW, I am working on add stuff (heavy global static analysis) which should be disablable at configure time and at runtime, and uses several third parties (GPL or LGPL) libraries -- Basile STARYNKEVITCH http://starynkevitch.net/Basile/ email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359 8, rue de la Faïencerie, 92340 Bourg La Reine, France *** opinions {are only mines, sont seulement les miennes} ***
