From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Compiling musl with tcc
Date: Thu, 4 Aug 2016 18:18:04 -0400 [thread overview]
Message-ID: <20160804221803.GM15995@brightrain.aerifal.cx> (raw)
In-Reply-To: <beeea191-de6c-3bcc-dc56-d2182c54e0f2@decentral.ch>
On Thu, Aug 04, 2016 at 10:08:47PM +0200, Tim Tassonis wrote:
> Hi all
>
> I was trying to build musl 1.1.15 with tcc 0.9.26, but got into an
> assembler error. Is tcc not supported to build musl?
tcc might have been able to build musl at some point in the past, but
it's not actually a conforming C99 compiler so even if whatever asm
issue you're hitting can be fixed or worked around, it wouldn't be
"supported". If you still want to try, I'd need more details than "an
assembler error" to be able to help.
Rich
prev parent reply other threads:[~2016-08-04 22:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 20:08 Tim Tassonis
2016-08-04 22:18 ` Rich Felker [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=20160804221803.GM15995@brightrain.aerifal.cx \
--to=dalias@libc.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).