From: Gary Thomas <gary@mlbassoc.com>
To: Yocto Project <yocto@yoctoproject.org>
Subject: Where did my preferred version go?
Date: Wed, 14 May 2014 12:06:35 -0600 [thread overview]
Message-ID: <5373B0AB.4070204@mlbassoc.com> (raw)
I have a number of platforms which [for whatever reason]
need older versions of GCC. I've been supporting this by
keeping the older code around in my own layers - I need
4.7.x for some targets, even 4.6.x for others.
With the changes in the latest master (post 1.6/daisy), I
am no longer able to build those older compilers :-( First
I had to fix up some core changes to just get the recipes to
even parse (bb.utils.contains), but now I get a slew of errors
like these:
NOTE: preferred version 4.7% of libgcc-initial not available (for item libgcc-initial)
NOTE: versions of libgcc-initial available: 4.8.2 4.9.0
I looked at the old recipes and they don't provide these
packages which make them unsuitable.
I know I should move these targets to the newer GCC, but at
this moment there simply are not the resources to do so, but
we still want to benefit from other improvements in OE-core
(and Poky/Yocto).
How can I move forward? Is there some way to retrofit the
older compilers into the new [required] structures? Perhaps
I could use the older compilers as external tool chain, but
the last time I tried to use this (in place of the internal,
build in place) tools, I could never make things happy :-(
Any suggestions more than welcome, thanks
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2014-05-14 18:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 18:06 Gary Thomas [this message]
2014-05-14 19:49 ` Where did my preferred version go? Paul Barker
2014-05-15 20:53 ` Richard Purdie
2014-05-16 10:50 ` Gary Thomas
2014-05-16 11:16 ` Paul Eggleton
2014-05-16 11:31 ` Gary Thomas
2014-05-16 12:42 ` Paul Eggleton
2014-05-16 17:11 ` Gary Thomas
2014-05-17 5:30 ` Khem Raj
2014-05-22 16:00 ` Gary Thomas
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=5373B0AB.4070204@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=yocto@yoctoproject.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 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.