quip_wrapper_simple_example_C.c does not compile with Intel compilers about quip

[gabor1]

I guess it's a linking issue. On the Mac, I had to link with fortran otherwise the cross language call didn't work. Is it possible that the Intel fortran linker will put in a main function even if the object already has one? Stupid machine.

-- Gábor

On 13 Jul 2016, at 13:00, Tom Daff [email protected] wrote:

Seems like it is trying to make something in the Fortran main() too.

quip_wrapper_simple_example_C.o: In function main': /scratch/quip/QUIP/src/Programs/quip_wrapper_simple_example_C.c:6: multiple definition ofmain'
/opt/intel/Compiler/11.1/069/lib/intel64/for_main.o:/export/users/nbtester/efi2linux_nightly/branch-11_1/20100204_010000/libdev/frtl/src/libfor/for_main.c:(.text+0x0): first defined here
/opt/intel/Compiler/11.1/069/lib/intel64/for_main.o: In function main': /export/users/nbtester/efi2linux_nightly/branch-11_1/20100204_010000/libdev/frtl/src/libfor/for_main.c:(.text+0x38): undefined reference toMAIN__'
make[1]: *** [quip_wrapper_simple_example_C] Error 1
make[1]: Leaving directory `/scratch/quip/QUIP/build/linux_x86_64_ifort_icc_mpi'
make: *** [Programs] Error 2
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[albapa]

If the main program is in C I think it should be possible to link with gcc/icc and link with the appropriate fortran library: -lgfortran for GNU and -lifcore -lifport for intel.

[jameskermode]

I think adding the -nofor_main argument to ifort link line should fix this.

On 13 Jul 2016, at 13:23, albapa [email protected] wrote:

If the main program is in C I think it should be possible to link with gcc/icc and link with the appropriate fortran library.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[tdaff]

Yep, -nofor-main does the trick, thanks. I'll push it in a minute.

[gabor1]

Could ppl pls sign their comments? Github emails contain no from field...

-- Gábor

On 13 Jul 2016, at 14:49, Tom Daff [email protected] wrote:

Yep, -nofor-main does the trick, thanks. I'll push it in a minute.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[jameskermode]

That’s interesting, identification works for me in Mail.app: I see gabor1<[email protected] mailto:[email protected]>

James.

On 13 Jul 2016, at 15:15, gabor1 [email protected] wrote:

Could ppl pls sign their comments? Github emails contain no from field...

-- Gábor

On 13 Jul 2016, at 14:49, Tom Daff [email protected] wrote:

Yep, -nofor-main does the trick, thanks. I'll push it in a minute.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub #34 (comment), or mute the thread https://github.com/notifications/unsubscribe/ABAFTJOSmEH7z28q6pQ-ejkGEIDTrjChks5qVPLngaJpZM4JLV9T.