On Wed, 30 Nov 2005, Edward Chapin wrote:
>>>> 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...)
Hi Ed,
the simplest way is just to set "CFLAGS" to "-fPIC" before configuring the
libf95 component. I just did that stage and copied the libf95.a library
into the latest g95 release, and my AMD64 build seems to have got past
CHR. See how far that gets in the morning.
Cheers,
Peter.
|