mailing list of musl libc
 help / color / mirror / code / Atom feed
From: idunham@lavabit.com
To: musl@lists.openwall.com
Subject: Re: Priorities for next release?
Date: Fri, 10 Aug 2012 22:21:21 -0400 (EDT)	[thread overview]
Message-ID: <22761.132.241.65.128.1344651681.squirrel@lavabit.com> (raw)
In-Reply-To: <5025AD41.3060009@gentoo.org>

> On 8/11/12 2:05 AM, Rich Felker wrote:
>> On Sat, Aug 11, 2012 at 12:03:45AM +0200, Luca Barbato wrote:
>>> On 8/10/12 9:12 PM, Rich Felker wrote:
>>>> Hi all,
>>>> Since we have some major progress since 0.9.3, I'm thinking of making
>>>> the next release pretty soon. Big things so far:
>>>>
>>>> - Blowfish crypt
>>>> - MIPS dynamic linker
>>>> - Major MIPS bug fixes
>>>> - ARM hard float support
all very good...
Out of curiousity, have you (or anyone else, for that matter) checked how
much of the LSB ABI is supported as of yet?

Also, if we're talking about adding MD5 or SHA (of the two, I think sha is
the more important) along the line, I'd think that adding multiple
crypt-related APIs in one release makes sense. Not all that important,
though.

I'm guessing that merging ppc/mips64/microblaze ports will end up waiting
for another release?

>>>> Among the other improvements that are pending, what else would you
>>>> like to see in 0.9.4?
>>>
>>> As annoying as it is XOPEN ifdeffery would be a boon...
>>
>> What do you mean?
>
> -D_XOPEN_SOURCE=600 and such.

Points to consider:
1-it might slow down compiling and make headers ugly.
2-as the person who added _BSD_SOURCE, I can assure you that it's not a
quick project. And with school starting in 2 weeks, I'm not the one doing
it.
(I don't think it's going to happen timely enough for the next release,
certainly)
3- -D_GNU_SOURCE will do for building most of this stuff
4-if you want a header change, may I politely suggest that you do the
patches?

HTH,
Isaac Dunham




  parent reply	other threads:[~2012-08-11  2:21 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-10 19:12 Rich Felker
2012-08-10 19:23 ` Nathan McSween
2012-08-10 19:39   ` Unit/regression testing (was Re: [musl] Priorities for next release?) Rich Felker
2012-08-10 22:03 ` Priorities for next release? Luca Barbato
2012-08-11  0:05   ` Rich Felker
2012-08-11  0:54     ` Luca Barbato
2012-08-11  1:07       ` Rich Felker
2012-08-11  2:21       ` idunham [this message]
2012-08-11  2:36         ` Rich Felker
2012-08-11 12:21           ` Daniel Cegiełka
2012-08-11 12:27             ` Rich Felker
2012-08-11 12:35               ` Daniel Cegiełka
2012-08-11 16:09                 ` Rich Felker
2012-08-11 16:35                   ` Daniel Cegiełka
2012-08-11 16:50                     ` Rich Felker
2012-08-11 17:55                       ` orc
2012-08-11 18:41                         ` Daniel Cegiełka
2012-08-11 18:47                           ` orc
2012-08-11 19:05                             ` Daniel Cegiełka
2012-08-11 19:28                               ` Rich Felker
2012-08-11 19:56 ` Rich Felker
2012-08-11 20:26   ` Daniel Cegiełka
2012-08-11 20:51     ` Rich Felker
2012-08-11 20:56       ` Rich Felker
2012-08-11 21:22       ` Rich Felker
2012-08-12 12:52         ` Daniel Cegiełka
2012-08-11 22:25   ` Rich Felker
2012-08-12 12:40     ` Szabolcs Nagy
2012-08-13  8:40   ` Luca Barbato
2012-08-13 13:41     ` Rich Felker
2012-08-13 15:49       ` Szabolcs Nagy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=22761.132.241.65.128.1344651681.squirrel@lavabit.com \
    --to=idunham@lavabit.com \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).