mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Gregor Richards <gr@purdue.edu>
To: musl@lists.openwall.com
Subject: Re: musl 0.9.4 released
Date: Sat, 18 Aug 2012 15:49:30 -0400	[thread overview]
Message-ID: <502FF1CA.5050305@purdue.edu> (raw)
In-Reply-To: <502FF15D.6030509@purdue.edu>

On 08/18/2012 03:47 PM, Gregor Richards wrote:
> On 08/18/2012 03:42 PM, Rich Felker wrote:
>> On Sat, Aug 18, 2012 at 12:40:22PM -0400, Gregor Richards wrote:
>>> On 08/18/2012 12:12 AM, Rich Felker wrote:
>>>> Hi all,
>>>>
>>>> Here's the release.
>>>>
>>>>      Major improvements to MIPS port, including support for dynamic
>>>>      linking. Password hashing (crypt) now supports blowfish hash
>>>>      algorithm. Further application compatibility improvements
>>>>      especially for BSD and SUSv3-targeted software. Performance
>>>>      improvements in printf and memcpy. Various bugfixes: strtod
>>>>      family, wcsstr, err.h functions, and many MIPS-specific bugs.
>>>>
>>>>      http://www.etalabs.net/musl/releases/musl-0.9.4.tar.gz
>>>>
>>>> Post-release priorities will be the gnuhash/dladdr patch, md5/sha
>>>> crypt, and perhaps integrating further ports (ppc and mips64 taking
>>>> priority). I know there are also various smaller pending patches
>>>> (vm86, etc.) that should get some attention too.
>>>>
>>>> Rich
>>> New musl cross compilers for all supported platforms finished:
>>> https://bitbucket.org/GregorR/musl-cross/downloads
>> Random question, but related: could you provide directions for
>> upgrading musl on your cross compilers? For example, what prefix
>> relative to the cross compiler root should be passed to musl's
>> configure, and are there any other files that need changing in the
>> cross tree when upgrading?
>>
>> Rich
>
> I've added this tidbit to the README:
>
> Upgrading cross compilers
> =========================
>
> It is possible to upgrade the musl version in a musl-cross cross compiler
> without rebuilding the entire cross compiler prefix from scratch. Simply
> download and extract the new version of musl, then configure it like so:
>
>     ./configure --prefix="<prefix>/<triple>" CC="<triple>-gcc"
>
> Where "<prefix>" is the prefix the cross compiler root was 
> installed/extracted
> to, and <triple> is the GNU-style target triple (e.g. 
> i486-linux-microcosm).
>
>
> No other changes are needed, upgrading is really quite trivial.
>
> With valediction,
>  - Gregor Richards
>
>

And I wrote "microcosm" because I am an idiot. Read that as "musl". X_X

With valediction,
  - Gregor Richards




      reply	other threads:[~2012-08-18 19:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-18  4:12 Rich Felker
2012-08-18 16:40 ` Gregor Richards
2012-08-18 19:42   ` Rich Felker
2012-08-18 19:47     ` Gregor Richards
2012-08-18 19:49       ` Gregor Richards [this message]

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=502FF1CA.5050305@purdue.edu \
    --to=gr@purdue.edu \
    --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).