From: James B <jamesbond3142@gmail.com>
To: musl@lists.openwall.com
Subject: Re: embedded newbies site.
Date: Sat, 20 Jul 2013 22:17:51 +0700 [thread overview]
Message-ID: <CA+wkPBSVF1nbB5DO9fJZo5NzQxYCMr3tw8pQAdUyjovxpoQNjQ@mail.gmail.com> (raw)
In-Reply-To: <CAL3m8eDFTf=sx9GSH06XiY_1VLNERuWZFuUECczkP4scv97WsQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]
On Tue, Jul 16, 2013 at 10:18 AM, Strake <strake888@gmail.com> wrote:
> On 15/07/2013, Rob Landley <rob@landley.net> wrote:
> > - creating a development environment (building binutils, gcc,
> > make...)
> > - requirements for self-hosting
> > - requirements for natively building Linux From Scratch
> > - cross vs native compiling
> > - bootstrapping to native compiling under emulation.
>
> This. For me, at least, this is often the greatest hindrance.
>
> That makes two of us. There are many tools for making cross compiler
(aboriginal, crosstools-ng, buildroot, etc) but I haven't found one that
guides how to move to native compiling (=create the native compilers) once
one has the cross-compilers and bootable rootfs (I know, aboriginal *does*
create native compilers so I should read Rob's scripts for that ...).
That being said, the other topics are pretty relevant too.
Also, anyone thinks that CLFS is good start for this? One thing that I
notice about (C)LFS is that the steps are there but the rationale and
explanation isn't; so it encourages people to follow a recipe without
knowing *why* things have to be done in a certain way (to be fair, the main
LFS (not its CLFS variants) does have some kind of explanation but it could
be improved).
cheers!
[-- Attachment #2: Type: text/html, Size: 1855 bytes --]
next prev parent reply other threads:[~2013-07-20 15:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 2:03 Rob Landley
2013-07-16 3:18 ` Strake
2013-07-17 12:07 ` LM
2013-07-17 13:58 ` Rich Felker
2013-07-20 15:17 ` James B [this message]
2013-07-22 12:27 ` Andrew Bradford
2013-07-22 4:40 ` Rob Landley
2013-07-23 0:12 ` Strake
2013-07-27 0:58 ` Rob Landley
2013-07-27 2:01 ` Strake
2013-07-27 2:50 ` Rich Felker
2013-07-29 20:01 ` Rob Landley
2013-07-29 19:54 ` Rob Landley
2013-07-30 1:35 ` Strake
2013-08-01 6:20 ` Rob Landley
2013-08-03 16:52 ` Strake
2013-07-16 11:50 ` LM
2013-07-16 13:56 ` Szabolcs Nagy
2013-07-16 14:00 ` Rich Felker
2013-07-16 17:49 ` Strake
2013-07-22 6:00 ` Rob Landley
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=CA+wkPBSVF1nbB5DO9fJZo5NzQxYCMr3tw8pQAdUyjovxpoQNjQ@mail.gmail.com \
--to=jamesbond3142@gmail.com \
--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).