public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: crossgcc@sourceware.org
Cc: Trevor Woerner <twoerner@gmail.com>
Subject: Re: [PATCH 2 of 2] docs: Add strategies for assembling root filesystems
Date: Wed, 16 Nov 2011 23:29:00 -0000	[thread overview]
Message-ID: <201111170029.28065.yann.morin.1998@anciens.enib.fr> (raw)
In-Reply-To: <8bd0d6bdba97ba1f9a80.1321483527@codei7.fpelectronics.com>

Trevor, All,

On Wednesday 16 November 2011 23:45:27 Trevor Woerner wrote:
> # HG changeset patch
> # User Trevor Woerner <twoerner@gmail.com>
> # Date 1321482977 18000
> # Node ID 8bd0d6bdba97ba1f9a80be56daf1e6b4161cb9b4
> # Parent  c1c4d9174fbfd7d76e0e520dc6657cf239a7d718
> docs: Add strategies for assembling root filesystems.
> 
> Expand the documentation for using a crosstool-NG-generated toolchain for
> building a root filesystem for a target device.

Not much to say, I wrote much of it! :-)
But still, a few comments below...

> Signed-off-by: "Trevor Woerner" <twoerner@gmail.com>
> 
> diff -r c1c4d9174fbf -r 8bd0d6bdba97 docs/5 - Using the toolchain.txt
> --- a/docs/5 - Using the toolchain.txt	Wed Nov 16 16:06:42 2011 -0500
> +++ b/docs/5 - Using the toolchain.txt	Wed Nov 16 17:36:17 2011 -0500
[--SNIP--]
> +2) Copy the toolchain's sysroot to the 'staging' area.
[--SNIP--]
> +   $ ./configure --prefix=/usr --enable-foo-bar...          \
> +         CC="<host tuple>-gcc --syroot=/path/to/staging"    \
> +         CXX="<host tuple>-g++ --sysroot=/path/to/staging"  \
> +         LD="<host tuple>-ld --sysroot=/path/to/staging"    \
> +         AND_SO_ON=tuple-andsoon --sysroot=/path/to/staging"

It is still required to pass --build and --host.

[--SNIP--]
> +3) Use separate staging and sysroot directories.
[--SNIP--]
> +   $ CPPFLAGS="-I/path/to/staging/usr/include" \
> +         LDFLAGS="-L/path/to/staging/lib -L/path/to/staging/usr/lib" \
> +         ./configure --prefix=/usr --enable-foo-bar...

Ditto.

> +4) A mix of 2) and 3), using carefully crafted union mounts.

This one is really coplex, convoluted, and not really possible without
much trouble and expertise. It could be confusing for newcomers (if it
was not confusing enough as it is!), and experts would probably be able
to come up with that solution on their own...

Otherwise, pretty nice. I'll fix the few nit-picks here and there, and
do a re-read pass, then I'll push.

I'm glad you took the time to format it properly, I was going to suggest
this went to the docs, you read my mind! :-)

Thank you!

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

--
For unsubscribe information see http://sourceware.org/lists.html#faq

  reply	other threads:[~2011-11-16 23:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-16 22:46 [PATCH 0 of 2] documentation update Trevor Woerner
2011-11-16 22:46 ` [PATCH 1 of 2] docs: --target versus --host Trevor Woerner
2011-11-16 23:18   ` Yann E. MORIN
2011-11-16 23:24     ` Trevor Woerner
2011-11-17 19:26     ` Thomas Petazzoni
2011-11-17 21:56       ` Trevor Woerner
2011-11-16 22:46 ` [PATCH 2 of 2] docs: Add strategies for assembling root filesystems Trevor Woerner
2011-11-16 23:29   ` Yann E. MORIN [this message]
2011-11-17 19:29     ` Thomas Petazzoni
2011-11-17 20:15       ` David Wuertele
2011-11-17 20:32         ` Thomas Petazzoni
2011-11-17 23:05       ` Trevor Woerner

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=201111170029.28065.yann.morin.1998@anciens.enib.fr \
    --to=yann.morin.1998@anciens.enib.fr \
    --cc=crossgcc@sourceware.org \
    --cc=twoerner@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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).