Re: failure of cross-compilation detection on BlueGene/L

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

 



Ralf Wildenhues wrote:
* Christian Rössel wrote on Sat, Jun 06, 2009 at 08:52:31AM CEST:
at the moment I'm just thinking of an external macro that sets $host if it is not set by the user. Depending on $cpu and $os of the build system you check for some special directories (e.g. /bgsys for Blue Gene/P). Usually todays supercomputers have such special and distinct directories. This is not the holy grail but works quite reliable for us. I think that these heuristics is not general and reliable enough to be included in autoconf/config.guess,

You can try; config.guess is maintained by config-patches@xxxxxxxx

config.guess should definitely be patched to recognize new host triplets for BlueGene and any other missing systems.

However, I think it's a bad idea to make ./configure cross-compile by default on these supercomputers, which breaks the expectation on every other platform that ./configure should compile for the build system by default.



_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf

[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux