From: Yann E. MORIN <yann.morin.1998@anciens.enib.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit master 1/1] crosstool-ng: don't remove installation directory before installing
Date: Tue, 25 Jan 2011 22:28:23 +0100 [thread overview]
Message-ID: <201101252228.23801.yann.morin.1998@anciens.enib.fr> (raw)
In-Reply-To: <20110125211621.EA9998D245@busybox.osuosl.org>
Peter, All,
On Tuesday 25 January 2011 22:07:14 Peter Korsgaard wrote:
> crosstool-ng would normally delete its installation directory before
> installing the toolchain to ensure it wouldn't get confused by an earlier
> build. Now that we're installing directly into HOST_DIR/usr, this doesn't
> work very well - So get rid of the rm's.
Too late, but:
Acked-by: me
But anyway, I would like to carry as few patches against crosstool-NG as
possible in buildroot, and push as much as possible into upstream.
If you would rework that to be configurable, I would apply it, so it gets
in the next release.
As I plan to update the crosstool-NG backend during the next BDD in
Brussels, it means we could then get rid of that patch in buildroot.
And if you have patches against crosstool-NG, and they are not BR-related,
could you Cc: me (and the crossgcc ML) so I can apply them upstream? Thx.
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. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2011-01-25 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 21:07 [Buildroot] [git commit master 1/1] crosstool-ng: don't remove installation directory before installing Peter Korsgaard
2011-01-25 21:28 ` Yann E. MORIN [this message]
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=201101252228.23801.yann.morin.1998@anciens.enib.fr \
--to=yann.morin.1998@anciens.enib.fr \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.