[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NEW: xvidcore

Marc Espie wrote,

> On Sat, Jul 17, 2004 at 11:37:08PM +0200, Waldemar Brodkorb wrote:
> > Thanks for your comments. Attached is a port which should fix all
> > issues you mentioned. Only one thing left out. Is it really needed
> > to compile and link with -fPIC? Or is it enough to compile the
> > object files with -fPIC and link with -shared?
> YES, it is needed. There are gory details. In some cases, the compiler
> may have to compile stub code to `finish' the library. In some cases,
> it will pick up different `internal' library versions depending on -fpic
> (libgcc, libsupc++...).
> So, always link shared libraries using gcc -shared -fPIC (or g++ -shared
> -fPIC, or -fpic, depending).
> To me, your question reads like `can I get away with not using -fpic for
> linking' ? And my answer will be:
> sometimes it works, sometimes it doesn't. It's not worth it. You don't
> want to have to figure it out, it's unimportant. *I* don't want to have
> to figure it out, and I/pvalchev/naddy invariably get to debug and figure
> it out three months from now when one port stops working on one arch, and
> we trace it back to somebody who tried to get away with it...

Okay, thanks for your hints. Attached a new port, which patches the
Makefile a little bit more.


CE94 5F99 BA88 65B1 25B9  8CD1 305A FF6B F8F8 1846
gpg --keyserver x-hkp://pgp.mit.edu --recv-keys F8F81846

*** http://www.openbsd.de/~wbx ***

Attachment: xvidcore-port.tgz
Description: application/tar-gz

Visit your host, monkey.org