LAM/MPI logo

LAM/MPI General User's Mailing List Archives

  |   Home   |   Download   |   Documentation   |   FAQ   |   all just in this list

From: Andrew D. Fant (andrew.fant_at_[hidden])
Date: 2006-10-10 10:52:48


Kevin R Bryant wrote:
> The easiest thing you could do would be to just install your head node
> w/ 32bit linux, not 64bit linux. (unless for whatever reason you need
> 64bit libraries on the head node).
>
> If 32bit head node is not an option, then you could always setup command
> alias's to auto add in -m32. The only downside to this would be for
> users that actually want to compile some 64bit code....

We've been through the mill on the 32 vs 64 bit issues in our group meetings
here too many times. It comes down to the fact that we need 64 bit
applications, but the only way that we could do it was as a new head node. An
ugly compromise, but way above my pay-grade.

I have a wrapper shell script that does add -m32 to compiler commands that don't
already have -m64 on them, but I don't trust it to be bulletproof when
interacting with more complex drivers like mpicc. My question is based on the
way that the automake tools do pick up certain flags from the environment when
building LAM-MPI and embed them into the mpicc wrappers. It would seem like
there ought to be a way to expand that set. I'm sure it could be done in the
source, but it would be nice to see if a short-cut exists.

Thanks,
        Andy

-- 
Andrew Fant           | The lion and the calf shall lie   | Disclaimer:
andrew.fant_at_[hidden] | down together, but the calf won't | Do you REALLY
UIT/USG               | get much sleep.                   | think I can
Tufts University      |                  W. Allen         | speak for Tufts?