From: Andrew Bradford <andrew@bradfordembedded.com>
To: samuel@sholland.net
Cc: musl@lists.openwall.com
Subject: Re: libgcc errors
Date: Thu, 09 Oct 2014 08:13:42 -0400 [thread overview]
Message-ID: <54367BF6.80203@bradfordembedded.com> (raw)
In-Reply-To: <5434704E.8080504@sholland.net>
Hi Samuel,
On 10/07/2014 06:59 PM, Samuel Holland wrote:
> On 10/07/2014 04:32 PM, Stephen Turner wrote:
>> I apologize for my lack of experience with building toolchains. if
>> there is a known good tutorial for this i will gladly ref it however
>> the best i have found is lfs embedded which i am currently using (and
>> not working).
>
> Embedded/Cross LFS make things much more complicated than you need. You
> can use the main LFS instructions to generate a native complier,
> applying these modifications:
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.
Thanks,
Andrew
next prev parent reply other threads:[~2014-10-09 12:13 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 [this message]
2014-10-09 14:46 ` stephen Turner
2014-10-09 15:49 ` stephen Turner
2014-10-09 19:38 ` Samuel Holland
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=54367BF6.80203@bradfordembedded.com \
--to=andrew@bradfordembedded.com \
--cc=musl@lists.openwall.com \
--cc=samuel@sholland.net \
/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).