From: Dan Wilder <Dan.Wilder@watchguard.com>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
"crossgcc@sourceware.org" <crossgcc@sourceware.org>,
Bryan Hundven <bryanhundven@gmail.com>
Subject: RE: Any chance of bringing gcc 4.7 support back to crosstool-ng 1.23
Date: Wed, 17 Feb 2016 16:36:00 -0000 [thread overview]
Message-ID: <13D890DAAABFB44887D834721D06CF4B021DF03E4A@mbx2.wgti.net> (raw)
In-Reply-To: <131d864f4b3c4f41be6de763dd24a17d@svr-chch-ex1.atlnz.lc>
We are in a similar situation. We simply use an older version of crosstool-ng, updating those few things that may need updates.
Maintaining a toolchain build isn't a simple matter, and maintaining it for all versions of everything, is maybe a recipe for Nothing Good. Eliminating older versions of inputs from the current version of the build system, seems an effective way to reduce clutter and risk.
--
Dan Wilder
________________________________________
From: crossgcc-owner@sourceware.org [crossgcc-owner@sourceware.org] on behalf of Chris Packham [Chris.Packham@alliedtelesis.co.nz]
Sent: Tuesday, February 16, 2016 7:42 PM
To: crossgcc@sourceware.org; Bryan Hundven
Subject: Any chance of bringing gcc 4.7 support back to crosstool-ng 1.23
Hi Bryan,
I realize this is probably re-hashing something that was discussed a few
months ago but is there any chance of bringing back support for gcc 4.7.x?
We have a vendor toolchain based on this. Fortunately the vendor
provides source but updating this source against a newer gcc is a bit
beyond our capabilities. We've asked the vendor if they can provide
their toolchain based on a current gcc but so far no movement on that.
Alternatively would it be possible to have a "custom" gcc version in the
configuration so we could point it at the vendors source tarball. I
think we'd want the same for binutils and glibc but I think we could get
away with those being patches on top of the upstream source.
Thanks,
Chris
--
For unsubscribe information see http://sourceware.org/lists.html#faq
--
For unsubscribe information see http://sourceware.org/lists.html#faq
prev parent reply other threads:[~2016-02-17 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 3:41 Chris Packham
2016-02-17 16:36 ` Dan Wilder [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=13D890DAAABFB44887D834721D06CF4B021DF03E4A@mbx2.wgti.net \
--to=dan.wilder@watchguard.com \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=bryanhundven@gmail.com \
--cc=crossgcc@sourceware.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).