From: Oliver Schneider <musl-mailinglist@f-prot.com>
To: musl@lists.openwall.com
Subject: Re: Out-of-tree builds
Date: Thu, 06 Feb 2014 18:25:18 +0000 [thread overview]
Message-ID: <52F3D38E.80907@f-prot.com> (raw)
In-Reply-To: <20140206173932.GB1685@port70.net>
On 2014-02-06 17:39, Szabolcs Nagy wrote:
> not supported (yet)
>
> it probably wouldn't be hard to add though
Thanks for your quick response.
I'll see whether I'm allowed to spend time on this and contribute a
patch back. I certainly hope so.
Thanks for musl-libc!
// Oliver
next prev parent reply other threads:[~2014-02-06 18:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 17:15 Oliver Schneider
2014-02-06 17:39 ` Szabolcs Nagy
2014-02-06 18:25 ` Oliver Schneider [this message]
2014-02-06 19:04 ` Rich Felker
2014-02-06 23:27 ` Szabolcs Nagy
2014-02-06 23:31 ` Szabolcs Nagy
2014-02-07 1:01 ` Szabolcs Nagy
2014-02-07 1:07 ` Rich Felker
2014-02-08 2:49 ` Szabolcs Nagy
2014-02-26 22:56 ` Szabolcs Nagy
2014-02-27 13:29 ` 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=52F3D38E.80907@f-prot.com \
--to=musl-mailinglist@f-prot.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).