Monkey stumbles upon warpdrive while coding

"I thought it would take 1000 monkeys 1000 years" says ape.

My Photo
Name:
Location: Sydney, New South Wales, Australia

Back from the US, and loving the beaches. Lucky enough to be working in science still.

Thursday, February 24, 2005

Troubles with mpi libraries

I've run into a tree at testMemory. Its wasn't linking, so I played around with this manually:

gcc -pipe -Wall -g -DDEBUG -O0 -o /home/cjoneill/StGermain/build/tests/testMemory1 /home/cjoneill/StGermain/build/tmp/test-libStGermainBaseFoundation/JournalWrappers.o -I/home/cjoneill/StGermain/build/include -I/home/cjoneill/StGermain/build/include/StGermain -I/opt1/site-sparc-sol8/mpich/include testMemory1.c /home/cjoneill/StGermain/build/lib/libStGermainBaseFoundation.a -L/opt1/site-sparc-sol8/mpich/lib -lmpich -lm

So this looks ok. But I'm getting the:

Undefined first referenced
symbol in file

-this usually means that a symbol is created somewhere (in a .h file) but no definition was made for it (in a .c file). This sounds to me like I haven't included something, but can't imagine what.
Funny thing is, I can compile it mpicc, with the option mpicc -cc=gcc.
(some of the options are a little funky without specifying gcc).
There is only one warning:
gcc: /home/cjoneill/StGermain/build/lib/libStGermainBaseFoundation.a: linker input file unused because linking not done
(why was linking not done? Sounds dodgy). Yet it compiles something that runs.

2 Comments:

Blogger code_monkey_craig said...

Feel free to put ANYTHING concerning how stupid I am and why you are smarter than me here.

3:14 PM  
Blogger code_monkey_craig said...

Works ok when I include the antelope stuff (ie. xml libraries)...

3:21 PM  

Post a Comment

<< Home