Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4E3F20FA.8000400@int3.at>
Date: Mon, 08 Aug 2011 01:34:18 +0200
From: "gs@...3.at" <gs@...3.at>
To: musl@...ts.openwall.com
Subject: Re: musl path


> By the way, I'm thinking of moving the gcc wrapper to a separate
> repository/tarball along with improving it, at some point in the near
> future. I don't really like the clutter of having it
> distributed/installed with musl, and as a separate standalone tool I
> could make it work with uclibc and other libcs as well..
>
> I'd welcome comments from users who like or dislike this idea.
improving the wrapper and supporting additional libc's sounds like a 
good thing.
tho having the wrapper automatically installed with the right paths set 
is also good.
i'd continue providing the wrapper with musl for now, since a newer 
version of the wrapper may not be compatible with an older musl version. 
also new users would have to configure two things instead of one.

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.