From: Adrian Bunk <bunk@stusta.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 02/15] libdnf: upgrade 0.28.1 -> 0.38.1
Date: Tue, 3 Dec 2019 00:55:23 +0200 [thread overview]
Message-ID: <20191202225523.GA26056@localhost> (raw)
In-Reply-To: <CAMKF1soeGLC48o0nsn=hZ2p89L43edF3SKuqXUP18-U=1=g99g@mail.gmail.com>
On Mon, Dec 02, 2019 at 02:44:47PM -0800, Khem Raj wrote:
> On Mon, Dec 2, 2019 at 7:25 AM Alexander Kanavin <alex.kanavin@gmail.com> wrote:
> >
> > It's using -std=c++11. I'm not sure if switching to gnu flavour would have made a difference with gcc 4.8 provided in centos 7 and gcc 4.9 from Debian 8 - is it worth trying? Newer gcc versions don't complain and build this without error while still using -std=c++11.
> >
> > I'm leaning towards taking out the dnf/libdnf updates until these distros are retired from the supported distro list.
>
> try adding #include <atomic> in libdnf/dnf-context.cpp
Same failure.
cu
Adrian
next prev parent reply other threads:[~2019-12-02 22:55 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 13:11 [PATCH 01/15] rpm: upgrade to 4.15.1 Alexander Kanavin
2019-11-29 13:11 ` [PATCH 02/15] libdnf: upgrade 0.28.1 -> 0.38.1 Alexander Kanavin
2019-12-02 14:55 ` Ross Burton
2019-12-02 15:10 ` Adrian Bunk
2019-12-02 15:24 ` Alexander Kanavin
2019-12-02 21:37 ` Adrian Bunk
2019-12-02 22:44 ` Khem Raj
2019-12-02 22:55 ` Adrian Bunk [this message]
2019-12-02 23:25 ` Khem Raj
2019-11-29 13:11 ` [PATCH 03/15] dnf: upgrade 4.2.2 -> 4.2.16 Alexander Kanavin
2019-11-29 13:11 ` [PATCH 04/15] gettext-minimal-native: update to 0.20.1 Alexander Kanavin
2019-11-29 13:11 ` [PATCH 05/15] gettext: " Alexander Kanavin
2019-11-29 13:11 ` [PATCH 06/15] lrzsz: fix issues with newer versions of gettext Alexander Kanavin
2019-11-29 13:11 ` [PATCH 07/15] p11-kit: convert to meson Alexander Kanavin
2019-11-29 22:56 ` Ross Burton
2019-12-02 12:00 ` Alexander Kanavin
2019-11-29 13:11 ` [PATCH 08/15] psmisc: revert to default autopoint exclusion Alexander Kanavin
2019-11-29 13:11 ` [PATCH 09/15] sed: upgrade to 4.7 Alexander Kanavin
2019-11-29 13:11 ` [PATCH 10/15] bind: update 9.11.5-P4 -> 9.11.13 Alexander Kanavin
2019-11-29 13:11 ` [PATCH 11/15] flex: update to 2.6.4 Alexander Kanavin
2019-11-29 13:11 ` [PATCH 12/15] gettext: fix failing ptests Alexander Kanavin
2019-11-29 13:11 ` [PATCH 13/15] libffi: update to 3.3 final Alexander Kanavin
2019-12-02 16:19 ` Ross Burton
2019-12-02 16:21 ` Ross Burton
2019-12-02 16:24 ` Alexander Kanavin
2019-12-02 16:31 ` Adrian Bunk
2019-11-29 13:11 ` [PATCH 14/15] libcomps: update to 0.1.12 Alexander Kanavin
2019-11-29 13:11 ` [PATCH 15/15] python3: update to 3.8.0 Alexander Kanavin
2019-11-29 22:54 ` Ross Burton
2019-11-29 22:55 ` Ross Burton
2019-11-29 22:56 ` Ross Burton
2019-12-02 11:43 ` Alexander Kanavin
2019-11-29 23:25 ` Adrian Bunk
2019-12-02 11:13 ` Ross Burton
2019-12-03 8:56 ` Ross Burton
2019-11-29 13:32 ` ✗ patchtest: failure for "rpm: upgrade to 4.15.1..." and 14 more Patchwork
2019-11-29 20:52 ` [PATCH 01/15] rpm: upgrade to 4.15.1 Ross Burton
2019-11-29 21:28 ` Alexander Kanavin
2019-11-29 22:08 ` Ross Burton
2019-12-03 23:05 ` Ross Burton
2019-12-03 23:52 ` Ross Burton
2019-12-04 10:17 ` Alexander Kanavin
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=20191202225523.GA26056@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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.