From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Nicolas Carrier <nicolas.carrier@orolia.com>
Cc: Herve Codina <herve.codina@bootlin.com>,
Tim Hammer <Tim.Hammer@orolia.com>,
Buildroot List <buildroot@buildroot.org>
Subject: Re: [Buildroot] ulog compilation issue with buildroot 2022.02.2
Date: Fri, 3 Jun 2022 11:47:24 +0200 [thread overview]
Message-ID: <20220603114724.5cf56736@windsurf> (raw)
In-Reply-To: <b203b8a90944c5f307c113ba8db8e377a627017a.camel@orolia.com>
On Fri, 03 Jun 2022 11:09:48 +0200
Nicolas Carrier <nicolas.carrier@orolia.com> wrote:
> Hello,
> I tested this morning against the master of buildroot (with an ubuntu 20.04) and the issue doesn't
> appear anymore.
> So there must be some change "recently" merged, which solves the issue.
>
> An idea anyone?
Not yet an idea, but I confirm that I was able to reproduce on
2022.02.2 (just so you know that your e-mail and issue have been seen!)
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-06-03 9:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 15:31 [Buildroot] ulog compilation issue with buildroot 2022.02.2 Nicolas Carrier
2022-06-03 9:09 ` Nicolas Carrier
2022-06-03 9:47 ` Thomas Petazzoni via buildroot [this message]
2022-06-03 10:44 ` Nicolas Carrier
2022-06-03 10:51 ` Nicolas Carrier
2022-06-03 12:53 ` Nicolas Carrier
[not found] <mailman.2413.1654341347.130377.buildroot@buildroot.org>
2022-06-05 6:05 ` Andreas Ziegler
2022-06-05 7:06 ` Thomas Petazzoni via buildroot
2022-06-05 11:46 ` Andreas Ziegler
2022-06-05 14:01 ` Romain Naour
2022-06-06 14:27 ` Tim Hammer
2022-06-06 18:09 ` Arnout Vandecappelle
2022-06-07 7:28 ` Nicolas Carrier
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=20220603114724.5cf56736@windsurf \
--to=buildroot@buildroot.org \
--cc=Tim.Hammer@orolia.com \
--cc=herve.codina@bootlin.com \
--cc=nicolas.carrier@orolia.com \
--cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox