This is the mail archive of the libc-ports@sources.redhat.com mailing list for the libc-ports project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: glibc port to kfreebsd/mips

From: Robert Millan <rmh at debian dot org>
To: "Carlos O'Donell" <carlos at codesourcery dot com>
Cc: debian-bsd at lists dot debian dot org, debian-mips at lists dot debian dot org, freebsd-mips at freebsd dot org, libc-ports at sourceware dot org
Date: Fri, 25 Feb 2011 17:18:44 +0100
Subject: Re: glibc port to kfreebsd/mips
References: <AANLkTimMZAMX6ymhXRhaxng3_xOjHB-MK07fqtrpPv9c@mail.gmail.com> <4D67CAD0.5020604@codesourcery.com>

2011/2/25 Carlos O'Donell <carlos@codesourcery.com>:
>> - Static binaries only; Dynamic linker crashes (both ld.so and libdl,
>> although libdl works for small objects).
>> - NSS (hence getpwuid et al) crashes as it relies on libdl.
>> - TLS not implemented as it requires some kernel fixes first.
>> - Thread support not implemented either (but LinuxThreads is needed for build).
>
> Please don't use LinuxThreads for a new port. It is unmaintained.

I know, but other kfreebsd-gnu ports already use LinuxThreads, so
getting it to build on mips*-kfreebsd-gnu was much easier this way.

> Is there any reason you aren't using NPTL? Lack of futex-compatible
> syscall?

To be honest, I haven't really investigated if the syscalls used by
FreeBSD userland (libkse and libthr) can be used to implement
futex funcionality.  I believe that porting NPTL to kernel of FreeBSD
would require significant effort.

Thanks

-- 
Robert Millan

References:
- glibc port to kfreebsd/mips
  - From: Robert Millan
- Re: glibc port to kfreebsd/mips
  - From: Carlos O'Donell

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]