Date: Fri, 25 Feb 2011 17:18:44 +0100 From: Robert Millan <rmh@debian.org> To: "Carlos O'Donell" <carlos@codesourcery.com> Cc: debian-mips@lists.debian.org, libc-ports@sourceware.org, freebsd-mips@freebsd.org, debian-bsd@lists.debian.org Subject: Re: glibc port to kfreebsd/mips Message-ID: <AANLkTikVQE5kYEYJ_HQPWcrBCQ6zckAkSZT0hF=7EXw_@mail.gmail.com> In-Reply-To: <4D67CAD0.5020604@codesourcery.com> References: <AANLkTimMZAMX6ymhXRhaxng3_xOjHB-MK07fqtrpPv9c@mail.gmail.com> <4D67CAD0.5020604@codesourcery.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTikVQE5kYEYJ_HQPWcrBCQ6zckAkSZT0hF=7EXw_>