On Dec 16, 2006, at 1:54 PM, Jerome BENOIT wrote:
> My trouble can be reproduce with the sphere C source file cited below.
> If I do
>
> gcc -o sphere sphere.c $(pkg-configure gts --cflags --libs) -lm
>
> then I obtain an executable that works.
>
> Bu, if I compile with mpicc instead:
>
> mpicc -o sphere sphere.c $(pkg-configure gts --cflags --libs) -lm
I'm not quite sure why you would be linking a non-MPI application
with mpicc...? (you stated that "gcc ..." would product a working
executable, so I'm not sure why you need mpicc to compile/link it...?)
You should add "--showme" to the command line and see what flags
mpicc is adding to the overall command. Perhaps something there
conflicts with whatever sphere or gts is doing...?
> then I get an executable which give me only `Floating point
> exception'.
> I tried with both the options -fexception and -fno-exception but
> I get the same error message.
> I used the GTS (gts.sourceforge.net) packages distributed by Debian.
I am unfamiliar with these packages, and I don't know what sphere.c
is. You should probably try to single-step through this executable
with a debugger (recompile with -g) and see where the problem
occurs. Perhaps there is an inadvertent symbol clash somewhere...?
> Just before to receive you email,
> my plan was to make a static linking rather that a dynamic one:
> may this resolve the issue.
I somewhat doubt it. LAM defaults to building static by default.
--
Jeff Squyres
Server Virtualization Business Unit
Cisco Systems
|
