[Boost-build] why is pathscale using mpicxx instead of pathCC ?

From: Alain Miniussi (alain.miniussi_at_[hidden])
Date: 2007-11-22 11:05:57

Hi,

Well, it's all in the subject, beeing a pathscale user, I just
downloaded the Milestone 12 and was surprised to see that the
original pathscale.jam uses in various places mpicxx, mpif77
and mpif90.
Is there a reason for that ? I do have mpi on most of my
computers but:
- why should I use it when I don't need it ?
- mpicxx is just one possible wrapper name (mpiCC is another possibility)
- pathCC is not necessarly the default underlying compiler of mpicxx

Also, the file mention pathf77 which does not exist (at least, not since
psc 2.5, as far as I can see) f77 compliancy can be acheived with
"path90 -ff77" instead.

I did the changes manually and it seems to be working but I suspect
I am overlooking something (I am new to boost build).

Also, I was able (well, I guess so, it's still building) to rebuild
boost using milestone 12 and pathscale, but I had to copy pathscale.jam
and fortran.jam (as a dependency of pathscale.jam) into the boost_1_34_1
distrib.
I suspect there is a way to use the site's boost build distrib files
instead of boot_1_34_1/tools/build/v2/tools but could not find a
way to do so in the documention.

Regards,

-- 
Alain Miniussi
Equipe CRIMSON                          Mesocentre de Calcul SIGAMM
[phone]                        https://crimson.oca.eu