From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] libelf: version bump 0.170 -> 0.171
Date: Wed, 6 Jun 2018 12:03:38 +0200 [thread overview]
Message-ID: <20180606100337.GA2632@archibald.tuxnet> (raw)
In-Reply-To: <20180606063136.yakbbyiypaoc55z4@pengutronix.de>
On Wed, Jun 06, 2018 at 08:31:36AM +0200, Michael Olbrich wrote:
> On Tue, Jun 05, 2018 at 03:36:25PM -0400, Jon Ringle wrote:
> > On Tue, Jun 5, 2018 at 3:34 PM, Jon Ringle <jon@ringle.org> wrote:
> > > On Tue, Jun 5, 2018 at 3:04 PM, Alexander Dahl <post@lespocky.de> wrote:
> > >> On Tue, Jun 05, 2018 at 02:20:37PM -0400, Jon Ringle wrote:
> > >> > The bump to 0.171 fixed the errors I was getting when building 0.170,
> > >> so I
> > >> > think the patch is not needed
> > >>
> > >> I already saw your v2 also removing the patch.
> > >>
> > >> The reason Clemens introduced the patch was compilation failed with
> > >> GCC >= 8. Did you test that? (I can't, don't have a bleeding edge
> > >> system at hand.) Maybe Clemens can elaborate?
> > >>
> > >>
> > > I was getting errors when building 0.170 with gcc-7.3.1 and the errors
> > > went away when I bumped to 0.171. I don't have gcc-8 to test with
> > >
> > > The 0.171 was only just released in June 1st, so maybe Clemens can test
> > building with 0.171?
>
> I've built host-libelf with gcc 8.1. 0.170 needs the patch and 0.171 builds
> without the patch. Just removing the Patch is ok.
Same here, libelf build succeeded without the patch.
Clemens
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2018-06-06 10:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 17:18 jon
2018-06-05 18:05 ` Alexander Dahl
2018-06-05 18:20 ` Jon Ringle
2018-06-05 19:04 ` Alexander Dahl
2018-06-05 19:34 ` Jon Ringle
2018-06-05 19:36 ` Jon Ringle
2018-06-06 6:31 ` Michael Olbrich
2018-06-06 10:03 ` Clemens Gruber [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=20180606100337.GA2632@archibald.tuxnet \
--to=clemens.gruber@pqgruber.com \
--cc=ptxdist@pengutronix.de \
/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