mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Richard Pennington <rich@pennware.com>
To: musl@lists.openwall.com
Cc: "Lucas Simões" <simoes.lucas.silva@gmail.com>,
	"Justin Cormack" <justin@specialbusservice.com>,
	"Paulo Castro" <p.oliveira.castro@gmail.com>
Subject: Re: Using Musl with LLVM/Clang
Date: Tue, 26 May 2015 20:20:46 -0500	[thread overview]
Message-ID: <55651BEE.1050404@pennware.com> (raw)
In-Reply-To: <CADP2nB+cwS3kAOTpkPpO1LvyeDYe5Om8YOWwKS-iHp01Ebef=g@mail.gmail.com>

On 05/26/2015 07:23 PM, Lucas Simões wrote:
> Thank you for the quick response guys!
> That's really sad, I was truly hoping to find a way to use musl out of 
> the box with Clang (on my Arch)
> Guess I'll just have to check the toolchains on this ELLCC project
>
Hi Lucas,

I did make some modifications to clang to make it easier (for me at 
least) to cross compile stuff, including musl, libc++, etc.My changes 
are pretty simple, but involve adding configuration files for different 
architectures. Most recently, I was playing with ARM Cortex-M3 
(http://ellcc.org/blog/?p=23234), but similar stuff can be used for 
several different targets 
(http://ellcc.org/viewvc/svn/ellcc/trunk/libecc/config/). I did it 
because I like to compile from the command line without a bunch of 
options for #includes, etc, because I'm essentially lazy. If you decide 
to try ELLCC, don't hesitate to ask for help if you encounter any problems.

-Rich (not *that* rich)


  reply	other threads:[~2015-05-27  1:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-25 20:32 Lucas Simões
2015-05-26  1:33 ` Shiz
2015-05-26  1:37   ` Rich Felker
2015-05-26  1:53     ` Shiz
2015-05-26  7:48       ` Justin Cormack
2015-05-27  0:23         ` Lucas Simões
2015-05-27  1:20           ` Richard Pennington [this message]
2015-05-27  1:38           ` Shiz

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=55651BEE.1050404@pennware.com \
    --to=rich@pennware.com \
    --cc=justin@specialbusservice.com \
    --cc=musl@lists.openwall.com \
    --cc=p.oliveira.castro@gmail.com \
    --cc=simoes.lucas.silva@gmail.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).