From: Samuel Holland <samuel@sholland.net>
To: musl@lists.openwall.com
Subject: Re: libgcc errors
Date: Thu, 09 Oct 2014 19:38:31 +0000 [thread overview]
Message-ID: <263E3217-740D-44F2-BC2A-BDCA4AFB38B8@sholland.net> (raw)
In-Reply-To: <54367BF6.80203@bradfordembedded.com>
On October 9, 2014 7:13:42 AM CDT, Andrew Bradford <andrew@bradfordembedded.com> wrote:
>Could you please provide more info on why you think the embedded Cross
>LFS way [1] is more complicated than is needed? How could it be made
>more simple? I'm happy to take suggestions for improvement.
>
>[1]:http://cross-lfs.org/view/clfs-embedded/arm/
>
>For the most part the toolchain building portion of embedded CLFS
>follows Gregor's musl-cross.
Because he doesn't need a cross compiler, only library isolation. Even the LFS method is more work than absolutely necessary. You could compile musl with your host GCC, then compile binutils and GCC with musl-gcc, and be done with it. I recommend the LFS way because 1) it works with C++ and 2) some people claim musl-gcc makes unreliable GCC builds.
Cross LFS makes sense when you're planning to use musl on another machine/architecture, but not (in my opinion) for making a native toolchain. I have no problems with CLFS; I just think it's the wrong tool for the job.
>Thanks,
>Andrew
--
Regards,
Samuel Holland <samuel@sholland.net>
next prev parent reply other threads:[~2014-10-09 19:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 18:54 stephen Turner
2014-10-07 19:51 ` Szabolcs Nagy
2014-10-07 21:32 ` stephen Turner
2014-10-07 22:59 ` Samuel Holland
2014-10-09 12:13 ` Andrew Bradford
2014-10-09 14:46 ` stephen Turner
2014-10-09 15:49 ` stephen Turner
2014-10-09 19:38 ` Samuel Holland [this message]
2014-10-09 21:08 ` stephen Turner
2014-10-09 21:43 ` Samuel Holland
2014-10-09 21:55 ` stephen Turner
2014-10-09 22:17 ` stephen Turner
2014-10-10 21:01 ` stephen Turner
2014-10-10 21:21 ` Rich Felker
2014-10-10 21:28 ` Samuel Holland
2014-10-10 21:30 ` Samuel Holland
2014-10-16 17:35 ` stephen Turner
2014-10-09 22:04 ` writeonce
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=263E3217-740D-44F2-BC2A-BDCA4AFB38B8@sholland.net \
--to=samuel@sholland.net \
--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).