All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: Where did my preferred version go?
Date: Thu, 15 May 2014 21:53:40 +0100	[thread overview]
Message-ID: <1400187220.28353.15.camel@ted> (raw)
In-Reply-To: <5373B0AB.4070204@mlbassoc.com>

On Wed, 2014-05-14 at 12:06 -0600, Gary Thomas wrote:
> 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

How are you doing this? Have you a completely separate set of gcc
recipes including the include files or is this using the current include
files. You basically have two options:

a) Apply the changes that were made in master gcc to the 4.7 recipes,
you can then probably share includes.

b) Use a separate set of 4.7 files and "undo" some of the changes in
master using creative variable names. E.g., libgcc-initial was added:

recipes-core/eglibc/eglibc-initial.inc:DEPENDS = "linux-libc-headers virtual/${TARGET_PREFIX}gcc-initial libgcc-initial"
recipes-core/eglibc/eglibc.inc:DEPENDS = "virtual/${TARGET_PREFIX}gcc-initial libgcc-initial linux-libc-headers virtual/${TARGET_PREFIX}libc-initial"

so you could do a:

DEPENDS_remove_pn-eglibc-initial - "libgcc-initial"
DEPENDS_remove_pn-eglibc - "libgcc-initial"

Thinking a bit more, the issue that is going to hit you hard are the -PN
additions to the cross recipe changes (and their change in arch). My
strong recommendation is therefore a) and then replaying the gcc changes
made in master against the 4.7 version. These were:

http://git.yoctoproject.org/cgit.cgi/poky/log/meta/recipes-devtools/gcc

there are about 10 or so changes there you'd need to check in your 4.7
recipes (since the 25th April) but nothing particularly difficult.

Cheers,

Richard



  parent reply	other threads:[~2014-05-15 20:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-14 18:06 Where did my preferred version go? Gary Thomas
2014-05-14 19:49 ` Paul Barker
2014-05-15 20:53 ` Richard Purdie [this message]
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=1400187220.28353.15.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=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.