Re: xlf90 8.1 on Mac OS X bug?
Not knowing much about F90 (I'm still stuck in F77 land I'm afraid) I'd
think that since test.F does:
USE ppp_exch_types_module
that would be enough.
No, that only makes the symbol and interface information available at compile
time using the module (usually .mod) file, it doesn't tell the linker that the
module's object (.o) file should be pulled in.
There ar evarious workarounds for this akwardness.
1. Instead of the above command line, do something like
xlf90 test.o libsms.a
I tried this but it gives the same results.
That doesn't work because it's still a library, and the linker will still
only pull in symbols it knows about...and it doesn't know about this one.
It appears that g95 found a better solution to this problem.
You need to explicitly include the module's object file. You can either
specify it as such in the link command, or you use a linker switch that
tells it to pull in a particular object file from the library uncondition-
ally. I know linkers which can do that, I don't know the syntax (if any)
for the typical Unix linker. Look through the switches for ld.
Jan
.
Relevant Pages
- Re: NOCRYPT / NOSECURE
... > Mark Murray wrote: ... so the linker will pull whatever bits are ... needeed from the library at buildworld time. ...
(freebsd-arch) - Re: Need some help, Keil AARM
... i.e. tell the linker not to pull startup.s into the ... But then I would have to re-write startup.s:) ... All I wanna now is how to continue program execution in another file, ...
(comp.arch.embedded) - Re: Need some help, Keil AARM
... Whichever way you like. ... i.e. tell the linker not to pull startup.s into the ...
(comp.arch.embedded) - RE: [Q] How to override link flags?
... Still no joy! ... LINKER_NOREF and USE_INCREMENTAL_LINKING I am able to get the linker to use ... Michael ...
(microsoft.public.development.device.drivers) |
|
