From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/oprofile: needs zlib
Date: Mon, 1 Nov 2021 09:47:52 +0100 [thread overview]
Message-ID: <20211101094752.4f0e6943@windsurf> (raw)
In-Reply-To: <20211030214734.2154583-1-fontaine.fabrice@gmail.com>
On Sat, 30 Oct 2021 23:47:34 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> oprofile needs zlib to avoid the following build failure which is, for
> an unknown reason, only raised since August 2021:
I don't really like changes that are made "for an unknown reason".
Indeed, if you look at
http://autobuild.buildroot.net/?reason=oprofile-1.4.0, this issue only
appeared 3 times, and only on static-linking configurations.
So, I would really like to see a better investigation than just "adding
this fixes the problem". We are clearly building OProfile many many
times in the autobuilder, and it doesn't need zlib, except in this
particular statically linked configuration.
So I'm afraid we need a more in-depth exploration of this issue.
Best regards,
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:[~2021-11-01 8:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-30 21:47 [Buildroot] [PATCH 1/1] package/oprofile: needs zlib Fabrice Fontaine
2021-11-01 8:47 ` Thomas Petazzoni [this message]
2021-11-09 21:40 ` Arnout Vandecappelle
2021-11-09 22:25 ` Yann E. MORIN
2021-11-09 22:37 ` Fabrice Fontaine
2021-11-10 9:12 ` Yann E. MORIN
2021-11-10 9:40 ` Fabrice Fontaine
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=20211101094752.4f0e6943@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox