Re: ct-ng 1.8.2 how to select gcc 4.5.x ?

[Samson Luk <samsonluk at gmail dot com>]

Yann, All


> I am not sure how gcc et al. would behave should the second-level
> directory be named without the tuple. I am afraid it might break in
> horrible ways in some corner cases, so I better be safe than sorry.
>
> It works this way, I'm fine with it. If any one comes with an alternate
> naming scheme that he can justify is working, I'm all for making a config
> knob for this.

No complaint at all, as expected, there must be reason behind to setup
like this, thanks for the explanation!  If It's Not Broken, Don't Fix
It! :)

> As said earlier, you have to restart from scratch if you change the
> configuration. If you change a build script, you can restart from
> the failing step.

Understood, the rebuild process is in progress... let's keep the
fingers crossed!

>> > Is there easy way to figure out which is
>> > the current step or have to dig through the build log?
>
> Yes, the previous failing message will tell you something like:
> Â ÂBuild failed in step 'XXXX'

Noted, just want to be lazy :)

>> But, you can enable CT_DEBUG_CT and CT_DEBUG_CT_SAVE_STEPS, and you
>> should be able to restart at a step that failed. You have to restart
>> your build with 'ct-ng clean; ct-ng build' before you can use the
>> saved steps. If libc breaks again, and you somehow fix your issue, you
>> can try:
>> ct-ng RESTART=libc
>
> Or more conveniently:
> Âct-ng libc+ Â --> restart from step 'libc', continues onward
> Âct-ng libc  Â--> restart from step 'libc', stops just after it
> Âct-ng +libc  --> start from the begining, stops just before step 'libc'
>
> See the docs! ;-)

Yes, I am aware of this from 'ct-ng help' and the docs but
overview.txt doesn't explain things like under configuration changes
I've to 'ct-ng clean' and 'build' while a script step changes I can
just restart from where it breaks, etc.


> The documentation is suffering from these deficiencies, nonetheless:
> - parts of the process is still undocumented;
> - parts of the process is partially and/or poorly documented, or the doc
> Âis not up-to-date;
> - I have made a lot of assumptions when writing the doc, and some stuff
> Âthat seems obvious to me I simply left out.

That is a common problems for technical writing from the experts...
something ' obvious' to the experts is the biggest 'mystery' for new
comers or newbies!

> I believe that installing and running crosstool-NG is properly documented,
> but the docs for the internals is definitely in need of some love.
> Any ine? ;-]

Hey, how about that... now I start to collect missing pieces (from
newbie point of view) and I will try to make some notes from your
answers, once finished I can forward over for your consideration to
integrate some of them (only if you see fit) into the docs.

Regards,
Samson
PS, Step 'libc' JUST FINISHED!!!!

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