From: MikeW <mw_phil@yahoo.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] Impossible to build EABI ARM gcc toolchain using Buildroot ?
Date: Fri, 1 Dec 2006 10:28:03 +0000 (UTC) [thread overview]
Message-ID: <loom.20061201T111848-976@post.gmane.org> (raw)
In-Reply-To: loom.20061201T110658-119@post.gmane.org
MikeW <mw_phil@...> writes:
> Since other people are building ARM EABI versions of gcc, there must
> be a patch that they are using which somehow has been omitted
> from Buildroot :(
>
> Regards,
> Mike
>
Incidentally, why don't projects using gcc just inherit all their
patches from gcc ... it seems (from searching) as if each dependent
project has to reinvent its own patches each time, whereas once a fix is found,
it should just go to gcc for everyone to use once & for all, thereby saving
everyone a lot of time and effort.
This should be part of the 'synergy' of open source ...
;-)
Regards,
MikeW
next prev parent reply other threads:[~2006-12-01 10:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 13:25 [Buildroot] Impossible to build EABI ARM gcc toolchain using Buildroot ? MikeW
2006-11-30 1:07 ` Pavel Roskin
2006-11-30 11:14 ` MikeW
2006-12-01 8:11 ` Pavel Roskin
2006-12-01 10:13 ` MikeW
2006-12-01 10:28 ` MikeW [this message]
2006-12-13 12:08 ` MikeW
2006-12-13 19:22 ` [Buildroot] Impossible to build EABI ARM gcc toolchain?using?Buildroot ? Bernhard Fischer
2006-12-14 9:40 ` [Buildroot] Impossible to build EABI ARM gcc toolchain using Buildroot ? MikeW
2006-12-18 11:37 ` MikeW
2006-12-18 12:15 ` [Buildroot] Impossible to build EABI ARM gcc toolchain?using?Buildroot ? Bernhard Fischer
2006-11-30 10:20 ` [Buildroot] Impossible to build EABI ARM gcc toolchain using Buildroot ? + MikeW
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=loom.20061201T111848-976@post.gmane.org \
--to=mw_phil@yahoo.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox