>>> It *looks* like libf95.a needs to be rebuilt with -fPIC. I misread this
>>> earlier but it's not a chr error it's a libf95.a error. In principle you
>>> can download the g95 source and remake just the libf95.a with -fPIC (it's
>>> not a big job - it's a tar ball within the g95 tarball so you don't need
>>> to build g95 from source to rebuild the run time library).
I've tried building g95 from the source and have the same linker error. I
did notice as it was building both g95 and libf95.a that no -fPIC option
was specified in the command line to the c compiler. I grep'd fPIC in the
source directories and configure does *check* to see if the fPIC flag
works with the compiler, but then doesn't appear to pass it to the
Makefile. I didn't see an obvious note about this in ./configure --help;
what would be the easiest way to force g95 to compile with -fPIC (at this
point maybe it's worth asking the g95 folks...)
> Well, the fact that it all works fine building SMURF if you are using a
> prebuilt stardev is indicative that the compiler itself works.
>
> Maybe you should just rsync from Andy's computer for the moment?
For now I'm just working from Andy's machine
Ed
--
+----------------------------------------------------------------+
| Dr. Edward Chapin (604) 822-6709 (work) |
| Dept. of Physics and Astronomy (604) 602-2382 (home) |
| University of British Columbia |
| 6224 Agricultural Road, Vancouver, B.C. |
| V6T 1Z1, Canada [log in to unmask] |
+----------------------------------------------------------------+
|