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>
Cc: oecore.mailinglist@gmail.com, 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 14:01:58 +0300	[thread overview]
Message-ID: <ee879f4e-3388-6734-ca7f-a5957af98639@gmail.com> (raw)
In-Reply-To: <20200430211745.GC410632@pcleri>

Hi,

Please see my comments in-line.

On 01/05/2020 00:17, Richard Leitner wrote:
>>
>> Like this I should be able to retrieve the host gcc version dynamically and
>> be able to add and remove CFLAGS e.g. depending on the major version of the
>> host gcc.
> 
> If I understand you correctly we have something like this already [3].
> Used for example at [4].
> 
> Or did I got something wrong?

I think this is along the lines of what I want.

... but ...

Why do we need to use "custom" meta-java stuff instead of what's already 
available from OE out of the box?

HOST_COMPILER_MAJOR="${@oe.utils.get_host_compiler_version(d)[1].split(".", 
2)[0]}"
CFLAGS_append = " ${@oe.utils.conditional('HOST_COMPILER_MAJOR', '9', 
'-Wno-error=format-overflow', '', d)}"

works for me.

... and ...

It looks like your and my build environment with gcc-9 (RH) and gcc-9 
(UB) behave differently?

This is totally crazy. Not only do we have a host compiler dependency 
with meta-java, but also 9.2 vs. 9.3 and maybe RH and UB hacked 
different things there?

Also we are just turning off warnings/errors, in this case buffer 
overflows, instead of fixing them, which is not good as well. So the 
problem might also be in some library/header or so. But I guess with 
OpenJDK to fix those it's another cup of tea.

... or ...

somewhere magic host CFLAGS are being added.

... one more thing ...

Do you think it should work on one of those distros out of the box, so I 
can try to reproduce what you have on my end?

https://github.com/RobertBerger/yocto-dockerfiles/tree/master/dockerfiles

How is meta-java usually tested?

> 
> regards;rl
> 

Regards,

Robert

  parent reply	other threads:[~2020-05-01 11:02 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 [this message]
     [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

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=ee879f4e-3388-6734-ca7f-a5957af98639@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.