All of lore.kernel.org
 help / color / mirror / Atom feed
* specify compiler version in recipe
@ 2015-09-22  2:47 Trevor Woerner
  2015-09-22  5:27 ` Khem Raj
  0 siblings, 1 reply; 2+ messages in thread
From: Trevor Woerner @ 2015-09-22  2:47 UTC (permalink / raw)
  To: yocto

Hello,

It looks like I already know the answer to this one... ;-)

I'm guessing it isn't possible to specify the compiler version in a
recipe? That's probably way too late in the parse stage?

There are some vendor Linux kernels for some BSPs that are old enough to
pre-date the:

    fatal error: linux/compiler-gcc5.h: No such file or directory

issue. Which means we have to rely on users reading the README and
updating their conf/local.conf files to include

    GCCVERSION = "4.9%"

Unfortunately that process is error-prone. It would be great to have
that occur automatically. In other words: if you want to use the
community/default/upstream kernel then use the latest compiler (but you
won't have accelerated graphics). If you want accelerated graphics then
you have to PREFER an older kernel *and* specify which version of gcc to
use in your conf/local.conf.

Can anyone think of a clever trick for this one?

Are BSP maintainers patching their old kernels to support post-gcc-5.0
versions?

Best regards,
    Trevor


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: specify compiler version in recipe
  2015-09-22  2:47 specify compiler version in recipe Trevor Woerner
@ 2015-09-22  5:27 ` Khem Raj
  0 siblings, 0 replies; 2+ messages in thread
From: Khem Raj @ 2015-09-22  5:27 UTC (permalink / raw)
  To: Trevor Woerner; +Cc: yocto


> On Sep 21, 2015, at 7:47 PM, Trevor Woerner <twoerner@gmail.com> wrote:
> 
> Hello,
> 
> It looks like I already know the answer to this one... ;-)
> 
> I'm guessing it isn't possible to specify the compiler version in a
> recipe? That's probably way too late in the parse stage?
> 
> There are some vendor Linux kernels for some BSPs that are old enough to
> pre-date the:
> 
>    fatal error: linux/compiler-gcc5.h: No such file or directory

back port the needed patch from upstream kernel. No other solution will be comprehensive.

> 
> issue. Which means we have to rely on users reading the README and
> updating their conf/local.conf files to include
> 
>    GCCVERSION = "4.9%"
> 
> Unfortunately that process is error-prone. It would be great to have
> that occur automatically. In other words: if you want to use the
> community/default/upstream kernel then use the latest compiler (but you
> won't have accelerated graphics). If you want accelerated graphics then
> you have to PREFER an older kernel *and* specify which version of gcc to
> use in your conf/local.conf.
> 
> Can anyone think of a clever trick for this one?
> 
> Are BSP maintainers patching their old kernels to support post-gcc-5.0
> versions?
> 
> Best regards,
>    Trevor
> -- 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-09-22  5:27 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-09-22  2:47 specify compiler version in recipe Trevor Woerner
2015-09-22  5:27 ` Khem Raj

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.