This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH 2 of 2] docs: Add strategies for assembling root filesystems


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]