All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert Berger" <robert.berger.oe.devel@gmail.com>
To: Richard Leitner <richard.leitner@skidata.com>,
	oecore.mailinglist@gmail.com
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-java] host gcc-9, icetea-7 gcc-9 but how older gcc versions?
Date: Fri, 1 May 2020 12:37:40 +0300	[thread overview]
Message-ID: <2b20147c-2312-e230-a437-d6d59b7b1c66@gmail.com> (raw)
In-Reply-To: <20200430211352.GB410632@pcleri>

Hi,

Please see my comments in-line.

On 01/05/2020 00:13, Richard Leitner wrote:
> On Thu, Apr 30, 2020 at 06:43:46PM +0300, Robert Berger wrote:
>> Hi,
>>
>> Is this supposed to work with host gcc 9?
> 
> Yes, for me it works with "gcc (GCC) 9.3.1 20200408 (Red Hat 9.3.1-2)"

Hmm for gcc (Ubuntu 9.2.1-17ubuntu1~16.04) 9.2.1 20191102

it needs additional CFLAGS.

Do we really need to distinguish also Distros and/or 9.3 vs. 9.2??

Does it do any harm if you add this?

https://github.com/RobertBerger/meta-java/commit/3db52ddcb7771e989cf39048a7b084d040d6b5b0

> 
>>
>> This was the first test I did and it bombed.
>>
>> I used all upstream unmodified dunfell branches plus your branch.
> 
> same did I on my Fedora box and it built and succeeded tests... That's
> strange.
> 
> Have you a clean build?

Yes all fresh and also no SSTATE or SSTATE cache.

If you would like to reproduce the problem I can provide you with ssh 
access to my build environment to show you quickly.

The build docker container I use is this one:

https://hub.docker.com/r/reliableembeddedsystems/poky-container/tags

Tag: ubuntu-16.04-gcc-9

Also I believe it can be easily reproduced with a "dirty" build as well, 
if I remove my 2 lines and just build icedtea-native.

> 
> regards;rl
> 
>> Regards,
>>
>> Robert
>>

Regards,

Robert

      reply	other threads:[~2020-05-01  9:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-20 16:53 [meta-java] host gcc-9, icetea-7 gcc-9 but how older gcc versions? robert.berger.oe.devel
2020-04-29 10:02 ` Richard Leitner
2020-04-29 11:41   ` Robert Berger
2020-04-29 13:02     ` Richard Leitner
2020-04-30 15:43       ` Robert Berger
2020-04-30 19:27         ` Robert Berger
2020-04-30 21:17           ` Richard Leitner
2020-05-01  7:16             ` Robert Berger
2020-05-01 11:01             ` Robert Berger
     [not found]             ` <160AE28F2E93B445.19580@lists.openembedded.org>
2020-05-01 14:46               ` [oe] " Robert Berger
2020-05-01 14:57                 ` Robert Berger
2020-05-05  5:35                   ` Richard Leitner
2020-05-05  6:37                     ` Robert Berger
2020-04-30 21:13         ` Richard Leitner
2020-05-01  9:37           ` Robert Berger [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=2b20147c-2312-e230-a437-d6d59b7b1c66@gmail.com \
    --to=robert.berger.oe.devel@gmail.com \
    --cc=oecore.mailinglist@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=richard.leitner@skidata.com \
    /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.