Ticket #25362 (new defect)
mpich@1.2.7p1 fail to build in Mac OS X snow leopard
| Reported by: | josem.climate@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.9.1 |
| Keywords: | Cc: | ||
| Port: | mpich |
Description
I am using Xcode 3.2.2 for Mac SDK 10.6
:info:build /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_mpich/work/mpich-1.2.7p1/bin/mpicc -o overtake overtake.o test.o
:info:build ld: duplicate symbol _MPIR_Setup_base_datatype in /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_mpich/work/mpich-1.2.7p1/lib/libmpich.a(initdte.o) and /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_mpich/work/mpich-1.2.7p1/lib/libpmpich.a(initdte.o)
:info:build collect2: ld returned 1 exit status
:info:build make[4]: *** [overtake] Error 1
:info:build make[3]: [linktest1] Error 2 (ignored)
:info:build Could not link a C program with MPI libraries
:info:build make[3]: *** [linktest1] Error 1
:info:build make[2]: *** [linktest] Error 2
:info:build make[1]: *** [mpi-lib-test] Error 2
:info:build make: *** [mpi] Error 2
:info:build shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_science_mpich/work/mpich-1.2.7p1" && /usr/bin/make -j2 " returned error 2
:error:build Target org.macports.build returned: shell command failed
:debug:build Backtrace: shell command failed
while executing
"command_exec build"
(procedure "portbuild::build_main" line 8)
invoked from within
"$procedure $targetname"
Attachments
Change History
comment:3 Changed 3 years ago by ryandesign@…
- Cc josem.climate@… removed
I get the same error. I'm attaching a complete log.
But mpich is very old. You may want the newer mpich2.
Note you do not need to Cc yourself.
comment:4 follow-up: ↓ 5 Changed 3 years ago by josem.climate@…
I will try, but I thought that the protocols and api for mpich2 is different.
I will see
comment:5 in reply to: ↑ 4 Changed 3 years ago by ryandesign@…
Replying to josem.climate@…:
I will try, but I thought that the protocols and api for mpich2 is different.
That's certainly possible; I'm not familiar with the mpich software. What did you find out?
Note: See
TracTickets for help on using
tickets.


Please remember to fill in the Port field.