From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: crossgcc@sourceware.org
Cc: Stuart Longland <redhatter@gentoo.org>
Subject: Re: Crosstool-ng always starts from the top
Date: Wed, 31 Mar 2010 06:10:00 -0000 [thread overview]
Message-ID: <201003310810.07612.yann.morin.1998@anciens.enib.fr> (raw)
In-Reply-To: <4BB28090.4070009@gentoo.org>
Stuart, All,
On Wednesday 31 March 2010 00:52:00 Stuart Longland wrote:
> Is there a way to convince crosstool-ng to pick up where it left off?
This is a limitation: crosstool-NG was not designed to be restartable.
However, it appeared that debugging crosstool-NG itself was cumbersome
when a single script was modified, so a /kind of/ stop-and-restart
feature was added, that works _iff_ the configuration has not changed.
That way, I was able to try to patch gcc or it's build script and restart
again without loosing too much time.
To sum-up:
- no, it's not possible to restart where it left off, if the
configuration has changed
- yes you can stop-and-restart at any place iff the configuration
has *not* changed.
> The upshot is that I have to run `ct-ng menuconfig` again, and tweak
> the options for gcc and run it again. This is fine, but when I run
> `ct-ng build`, it starts right from scratch again building GMP, MPFR,
> PPL, Cloog and binutils... which all should be identical to before, and
> shouldn't need rebuilding.
That's right from a theorical point of view.
> Is there a reason why the builder can't just assume (or be convinced to
> assume) those components are already built and resume at the last
> component where the failure occurred?
Well, most notably a design issue. The /issue/ is that crosstool-NG has
(so far) no way to tell what changed in the configuration, related to
what component(s), and what following copmponent(s) the change does
impact.
And fixing this will need a *huge* amount of work, which I am not yet ready
to invest. Except if someone comes with a patch that I can review! ;-)
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
next prev parent reply other threads:[~2010-03-31 6:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 22:52 Stuart Longland
2010-03-31 6:10 ` Yann E. MORIN [this message]
2010-03-31 6:37 ` David Wuertele
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=201003310810.07612.yann.morin.1998@anciens.enib.fr \
--to=yann.morin.1998@anciens.enib.fr \
--cc=crossgcc@sourceware.org \
--cc=redhatter@gentoo.org \
/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).