Re: [d-i] Yet Another bug with pre-sprintf malloc:ing
* Martin Sjögren | ons 2002-08-28 klockan 16.45 skrev Tollef Fog Heen: | * Colin Walters | | | I guess this is up to Mithrandir...what do you think? | | I'd say go ahead. | | Are there any implications for debian/freebsd, or should we take them | when we get there? asprintf, as it so happens, exists on *bsd too, but | if we start using _GNU_SOURCE all over we might have problems later. (Just recording what we said on IRC) So far -bsd haven't even properly decided on what libc to use. We need to have a lot more working Debian/*BSD before we think about writing an installer for *BSD. Still, keeping the portability at maximum would be good. (-bsd Cc-ed, so they can voice their opinions, if any.) -- Tollef Fog Heen,''`. UNIX is user friendly, it's just picky about who its friends are : :' : `. `' `-
Re: [d-i] Yet Another bug with pre-sprintf malloc:ing
(Just recording what we said on IRC) So far -bsd haven't even properly decided on what libc to use. We need to have a lot more working Debian/*BSD before we think about writing an installer for *BSD. Still, keeping the portability at maximum would be good. (-bsd Cc-ed, so they can voice their opinions, if any.) I don't know what needs to happen for any decision about Debian/*BSD to be considered proper, but the de facto status right now seems to be that it's the BSD libc, since ports of the GNU libc are either experimental or nonexistent... - Michael = -BEGIN GEEK CODE BLOCK- Version: 3.12 GCS/MU d-+ s++:+ a--- C++ ULISBH+++ P+++ L++(-) E- W--(+) N+ o? K? w--- !O !M V? PS+++ !PE Y+ PGP- t+(-) 5 X R tv-- b+++ DI(+) D G e+++ h r-- y --END GEEK CODE BLOCK-- __ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com
Re: [d-i] Yet Another bug with pre-sprintf malloc:ing
Michael Goetze wrote: (Just recording what we said on IRC) So far -bsd haven't even properly decided on what libc to use. We need to have a lot more working Debian/*BSD before we think about writing an installer for *BSD. Still, keeping the portability at maximum would be good. (-bsd Cc-ed, so they can voice their opinions, if any.) I don't know what needs to happen for any decision about Debian/*BSD to be considered proper, but the de facto status right now seems to be that it's the BSD libc, since ports of the GNU libc are either experimental or nonexistent... The FreeBSD port of glibc is working. Most Debian sources I've tried build and work perfectly. There are two basic issues: 1. Thread support isn't finished 2. Massive work needed on kernel headers ---Nathan
