Re: Porting libc_r from -current to -stable

[ Available lists | Index of freebsd-hackers | Month of Aug 2002 | Week of 29 Aug 2002 | Raw email | Wrap long lines | Reply | Tag ]
From
Daniel Eischen <eischen@pcnet1.pcnet.com>
Date
29 Aug 2002 06:53:26
Subject
Re: Porting libc_r from -current to -stable
Message-ID
Pine.GSO.4.10.10208290939430.12954-100000@pcnet1.pcnet.com

In reply to

[ Hide this part ]
On Thu, 29 Aug 2002, Jonathon McKitrick wrote:
> I've volunteered to do this port, with the expectation that it's within my
> ability. I'm just a bit over my head, but that's how I'll learn, right?
>
> I've gotten the -current version to build and install, but I've found 2
> problems so far: gkrellm loads and cannot resolve the symbol _flockfile.
> Also, a build of xmms (which uses threads) fails in configure because it
> cannot find pthreads support.
>
> I'd like to solve this myself, but I need a little push in the right
> direction. Could someone give me a hint? Is it simply a matter of
> undefining functions that are not present in -stable?

In -current, we modified FILE (/usr/include/stdio.h) and added
(or changed) a field to use for holding a mutex that is used by
flockfile (lib/libc/stdio/_flock_stub.c). We broke the ABI
in order to do this, and it was very painful (just search for
"the whole stdio mess" or something like that in the -current
archives). You cannot do this for -stable.

You're going to have to keep the hashtable method of locking
FILEs.

--
Dan Eischen


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message



Elapsed time: 0.191 seconds