From: Khem Raj <raj.khem@gmail.com>
To: "Taborski,
Krzysztof (Nokia - PL/Wroclaw)" <krzysztof.taborski@nokia.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Recipes for gcc-native
Date: Mon, 22 Jul 2019 13:22:21 -0700 [thread overview]
Message-ID: <CAMKF1spu+sTqG=_hMBg5rNqHVkRythDijbPf33ivW3Yaz6Z7_A@mail.gmail.com> (raw)
In-Reply-To: <AM6PR07MB48681013AFE59E28FAC8E5F38CCB0@AM6PR07MB4868.eurprd07.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]
On Mon, Jul 22, 2019 at 1:14 PM Taborski, Krzysztof (Nokia - PL/Wroclaw) <
krzysztof.taborski@nokia.com> wrote:
> Hello,
> I am wondering, if there is any reason, that yocto project does not
> delivers recipes for gcc-native ( in similar way as python-native for
> example)?
>
> It would allow to build native recipes with different/higher version of
> gcc, than this, which user has on my build servers.
>
This would not solve the problem fully and yet create more maintainer
burden since the supporting libraries are still coming from distribution
underneath and this would create yet another combination for variable
I think container approach would solve this for us in a nicer way
Most supported distribution do support newer compiler packages and that’s a
better option since they would have tested it on that distribution to some
extent
>
> Best regards,
>
> Krzysztof Taborski
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
[-- Attachment #2: Type: text/html, Size: 2975 bytes --]
next prev parent reply other threads:[~2019-07-22 20:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 15:47 Recipes for gcc-native Taborski, Krzysztof (Nokia - PL/Wroclaw)
2019-07-22 20:22 ` Khem Raj [this message]
2019-07-23 21:33 ` ODP: " Taborski, Krzysztof (Nokia - PL/Wroclaw)
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='CAMKF1spu+sTqG=_hMBg5rNqHVkRythDijbPf33ivW3Yaz6Z7_A@mail.gmail.com' \
--to=raj.khem@gmail.com \
--cc=krzysztof.taborski@nokia.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.