Hello Tony,
* Tony Goelz wrote on Mon, Feb 08, 2010 at 04:25:46PM CET:
I was not sure if I sure reply to the whole list with this, so I
went with caution and didn't.
If you ask me, then you may always Cc: the list. Unless discussing
security-related or personal issues, I typically prefer things being
searchable later. Also, Peter O'Gorman is our Darwin expert reading
the list, and I am not.
Anyway, I would be happy to assist in
porting libtool to Absoft's compilers on Darwin.
Great!
There are two separate compilers that we would like to see
supported: our 9.0 series Power PC Darwin (even though I am not sure
about the long term viability of that platform since Apple has
dropped Power PC support from new OS X releases) and our 10.0/11.0
and later series compilers on x86/x86-64 Darwin.
I've looked at
http://www.absoft.com/literature/Mac_v11_UserGuide.pdf and
http://www.absoft.com/literature/v9_5_UserGuideOSX.pdf
but neither seem to document anything about shared libraries.
Do these compilers support the creation of shared libraries at all?
If yes, how would you do it?
What is the output of
./libtool --tag=F77 --config
./libtool --tag=FC --config
for a package configured for these compilers?
1) The compiler is invoked through drivers named f77, f90, and f95.
Invoking f77,f90, or f95 with just "-v" (or with no arguments at
all) will write "Pro Fortran 9.2" or "Pro Fortran 9.5" to standard
out. The drivers will also write "ERROR: No input files." to
standard error.
What's the exit status in that case?
2) The compiler uses the GCC compiler to perform the actual link
after adding in the appropriate Absoft specific libraries.
Absoft 10.0/11.0 on x86/x86-64 Darwin.
1) The compiler is invoked through drivers named af77, af90, and
af95 and there are symbolic links from these drivers to f77, f90,
and f95. Invoking af77, af90, or af95 with just "-v" or with no
arguments at all) will write "Absoft Pro Fortran 10.x.y" ir "Absoft
Pro Fortran 11.x.y" to standard out. The drivers will also write
"ERROR: No input files." to standard error.
Again, exit status?
2) The compiler uses the GCC compiler to perform the actual link
after adding in the appropriate Absoft specific libraries.
As far as the simple test with the sed script you provided, the
section LIBTOOL TAG CONFIG: F77" already had "wl=-Wl," set for both
PowerPC and x86 Darwin. I also noticed that the generated libtool
had
xlcverstring="${wl}-compatibility_version ${wl}$minor_current
${wl}-cur
rent_version ${wl}$minor_current.$revision"
defined outside of the CONFIG: F77 block. This suggests to me that
the solution I proposed has been used for another compiler (maybe
IBM's XLC compiler?).
I'll look at that.
Thanks!
Ralf