Re: Final toolchain dir

["Yann E. MORIN" <yann dot morin dot 1998 at anciens dot enib dot fr>]

Andy, All,

On Friday 25 March 2011 20:49:16 ANDY KENNEDY wrote:
> Does the build chmod the final toolchain directory to rxrxrx (555)?

Yes, this is done on purpose.

The goal is to render the whole toolchain read-only, and especially the
sysroot of the toolchain, to avoid poluting the sysroot with alian stuff
from other packages.

Once the toolchain is built, nothing, really nothing should be added to
it, and especially the sysroot should not be modified.

If it was the case, and new headers and/or libs were added to the sysroot,
then it would not be possible to re-use the toolchain for a different
set of packages.

For example, if one were to add zlib headers and libs to the sysroot, then
it would not be possible to build another version of zlib in another set of
packages, as the sysroot is the first place the compiler and linker look
into to find headers and libs.

> If yes, is there a way to control that behavior so that it DOESN'T do
> that?

Yes, there is a way. See:
  Paths and misc options  --->
    [*] Render the toolchain read-only

But, do you really, really need the toolchain to be writable? What for?

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