From: Luca Barbato <lu_zero@gentoo.org>
To: musl@lists.openwall.com
Subject: Re: [RFC] pcc support for configure
Date: Tue, 16 Oct 2012 11:39:22 +0200 [thread overview]
Message-ID: <507D2B4A.3030505@gentoo.org> (raw)
In-Reply-To: <20121015211231.08cbd071.idunham@lavabit.com>
On 10/16/2012 06:12 AM, Isaac Dunham wrote:
> *Note: pcc can be built with binutils (default) or yasm (--with-yasm).
> Apparently yasm is missing quite a few instructions, as even when I used yasm
> from git I got a quite spectacular FTBFS using pcc+yasm as compiler.
I thought yasm was just for the win32 target.
lu
next prev parent reply other threads:[~2012-10-16 9:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 4:12 Isaac Dunham
2012-10-16 9:39 ` Luca Barbato [this message]
2012-10-16 19:08 ` idunham
2012-10-16 10:17 ` Szabolcs Nagy
2012-10-16 13:21 ` Rich Felker
2012-10-16 18:55 ` idunham
2012-10-26 20:35 ` Rich Felker
2012-10-26 21:59 ` Szabolcs Nagy
2012-10-26 22:05 ` Rich Felker
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=507D2B4A.3030505@gentoo.org \
--to=lu_zero@gentoo.org \
--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).