[RFC] ct-ng build debugging

[Yann E. MORIN]

Johannes, All,

On Friday 28 September 2012 18:35:47 Johannes Stezenbach wrote:
> I hacked up the patch below which drops into a shell prompt
> when the ct-ng build breaks, with the environment properly set up.
> It allows one to check what went wrong and possibly hot-fix it.
> Of course a real patch should use a developer config option, but I'm
> out of time atm and can't finish it.  If you find it
> useful it would be nice if someone could pick it up
> and polish it for inclusion.

That a very interesting feature. Getting a shell with the current
environment already set is a pretty neat idea.

I've just skimmed over the patch, and basically I like the exit trick.
I think this behavior should be conditional, and the build should abort
by default, unless the user explicitly asked for the new behavior.

Also, we should use ${bash} to call the shell, because some folks may use
a specific bash (eg. the *BSD guys).

I'll give it a spin shortly, and see how we can adapt your patch.

> (The "backtrace" change at the top is actually a seperate
> bugfix for when things go wrong early in crosstool-NG.sh
> before CT_BUILD_DIR is set.)

Yep, that sounds reasonable, too, but that should be a separate patch.
Do you want to re-submit just that one, please?

> Signed-off-by: Johannes Stezenbach <js@sig21.net>
> 
> PS: I'm not good at writing bash scripts, maybe there's
> a better way to do it.

Well, basically, it's good.

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