From: "Adrian Bunk" <bunk@stusta.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Alexander Kanavin <alex.kanavin@gmail.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 01/15] rpm: upgrade to 4.15.1
Date: Mon, 27 Apr 2020 12:09:11 +0300 [thread overview]
Message-ID: <20200427090911.GA19242@localhost> (raw)
In-Reply-To: <a2ee87b585ad797813c6985218ae0e3ea360597e.camel@linuxfoundation.org>
On Sun, Apr 26, 2020 at 10:07:30PM +0100, Richard Purdie wrote:
> On Sun, 2020-04-26 at 22:40 +0200, Alexander Kanavin wrote:
>...
> > What is particularly odd is that the centos/debian failures are non-
> > deterministic: in some cases rpm-native fails to build due to missing
> > omp.h, in other cases it builds, but the resulting binaries segfault.
> >...
> > Ubuntu always segfaults, but maybe it's just coincidental.
>...
> We are aiming to support these using buildtools tarball which should
> already be active on centos7/debian8 (but not ubuntu1604) so I'm a
> little worried this may point to a problem with the buildtools tarball
> :(
>...
I don't see omp.h installed anywhere by the buildtools-extended tarball.
This would explain the build failures.
gcc 6 updated OpenMP support from OpenMP 4.0 to OpenMP 4.5.
This might be a plausible explanation for segfaults on systems
with older libgomp.
> Cheers,
>
> Richard
cu
Adrian
next prev parent reply other threads:[~2020-04-27 9:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 17:28 [PATCH 01/15] rpm: upgrade to 4.15.1 Alexander Kanavin
2020-04-25 17:28 ` [PATCH 02/15] libmodulemd: move from 1.x to 2.x version Alexander Kanavin
2020-04-25 17:28 ` [PATCH 03/15] libdnf: upgrade 0.28.1 -> 0.47.0 Alexander Kanavin
2020-04-25 17:28 ` [PATCH 04/15] dnf: upgrade 4.2.2 -> 4.2.21 Alexander Kanavin
2020-04-25 17:28 ` [PATCH 05/15] quilt: do not test patch-wrapper as it is not enabled Alexander Kanavin
2020-04-25 17:28 ` [PATCH 06/15] libinput: add ptest Alexander Kanavin
2020-04-25 17:28 ` [PATCH 07/15] libinput: update 1.15.2 -> 1.15.5 Alexander Kanavin
2020-04-25 17:28 ` [PATCH 08/15] perl: update to 5.30.2 Alexander Kanavin
2020-04-25 17:28 ` [PATCH 09/15] gobject-introspection: update to 1.64.1 Alexander Kanavin
2020-04-25 17:28 ` [PATCH 10/15] python3-pyparsing: add from meta-oe Alexander Kanavin
2020-04-25 17:28 ` [PATCH 11/15] python3-cython: " Alexander Kanavin
2020-04-25 17:28 ` [PATCH 12/15] maintainers.inc: add entries for cython and pyparsing Alexander Kanavin
2020-04-25 17:28 ` [PATCH 13/15] python3-cython: update to 0.29.16 Alexander Kanavin
2020-04-25 17:28 ` [PATCH 14/15] python3-pyparsing: update to 2.4.7 Alexander Kanavin
2020-04-25 17:28 ` [PATCH 15/15] python3-numpy: update to 1.18.3 Alexander Kanavin
2020-04-26 17:34 ` [OE-core] [PATCH 01/15] rpm: upgrade to 4.15.1 Richard Purdie
2020-04-26 18:29 ` Alexander Kanavin
[not found] ` <160972188EAFC253.2907@lists.openembedded.org>
2020-04-26 20:40 ` Alexander Kanavin
2020-04-26 21:07 ` Richard Purdie
2020-04-27 9:09 ` Adrian Bunk [this message]
2020-04-27 9:54 ` Alexander Kanavin
2020-04-27 10:08 ` Adrian Bunk
2020-04-27 12:24 ` Alexander Kanavin
2020-04-27 12:30 ` Richard Purdie
2020-04-27 12:33 ` Alexander Kanavin
2020-04-27 12:42 ` Richard Purdie
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=20200427090911.GA19242@localhost \
--to=bunk@stusta.de \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox