Re: Python port

[Mike Hardy <mhardy@smithsonite.rice.edu>]

On Thu, 9 Dec 1999, Camiel Dobbelaar wrote:

> - a lot of warnings get generated about libreadline, like this one:
> ld: /usr/lib/libreadline.a(parens.o): RRS text relocation at 0xbd29 for
> "_rl_insert"
> 
>   Is this OK?

I just experienced this when trying to build PHP's imap.so dynamic module,
which links to imap-uw's c-client.a static library.

Adding a '-fPIC' CFLAG to the c-client.a's library compilation (via the
imap-uw port's Makefile) made the libraries' objects "Position Independent
Code" and thus re-locatable during linking in the PHP package.. That got
rid of my linker warnings.

If you add that CFLAG to whatever generates libreadline.a, you should be
fine too.

*HOWEVER* - and this is big to me, I haven't had anyone tell me whether
this is an OpenBSD-ports-approved practice. I know some machines can't do
dynamic loading, but I don't know what that means for the PIC compiler
option. Until someone tells me one way or another, I'll keep giving this
solution, with this warning...

Does anyone know if this solution to the "RRS text relocation" warnings is
okay?

Is there a better way to do it? Is it even necessary? I'd really like some
advice, and it might help Camiel too. Thanks-

-Mike