Karim Belabas on Fri, 31 Oct 2008 14:03:34 +0100 |
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
Re: One more ./Configure issue |
* Jeroen Demeyer [2008-10-31 12:33]: > the following is an issue which I encountered while doing 32bit/64bit > cross-compiling on a x86_64 GNU/Linux machine: > > When using linux32 ./Configure, this setting will be forgotten during make. > Once I have Configured PARI/GP as 32-bits it should remember that during > make instead of checking again (the culprit is the @dir=`config/objdir`; > line in the top-level Makefile). This is intentional. (1) To bypass it, just cd <your-objdir> && make <your-target>. (2) The reason for guessing $dir "at runtime" instead of hardcoding it at Configure time is that my home directory is mounted identically on a large number of different architectures. I can then use the very same sources simultaneously on each of these architecture. And just type 'Configure' or 'make <my-target>' from my main workdir without bothering to go to a specific directory first. This does simplify testing immensely ( and I'd rather include everything in a Makefile than depend on external scripts/aliases ) I understand it makes cross-compilation slightly more difficult. But I'd rather simplify development and testing than cross-compilation. Sorry, K.B. > PS: I remind you again about GNU autoconf+automake, which does not have > this issue. In this case, "solving" this issue (i.e. killing (2) above) would introduce a new hassle (for me, and I suspect for a number of other users), without solving any actual problem. -- Karim Belabas, IMB (UMR 5251) Tel: (+33) (0)5 40 00 26 17 Universite Bordeaux 1 Fax: (+33) (0)5 40 00 69 50 351, cours de la Liberation http://www.math.u-bordeaux.fr/~belabas/ F-33405 Talence (France) http://pari.math.u-bordeaux.fr/ [PARI/GP] `