From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de, Lucas Stach <l.stach@pengutronix.de>
Cc: Michael Olbrich <m.olbrich@pengutronix.de>
Subject: Re: [ptxdist] [PATCH] fio: select ZLIB
Date: Fri, 21 May 2021 09:28:38 +0200 [thread overview]
Message-ID: <20210521072841.2133655-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20210504203506.20672-1-l.stach@pengutronix.de>
Hi,
On Tue, May 04, 2021 at 10:35:06PM +0200, Lucas Stach wrote:
> fio uses zlib when it is found, make the dependency explicit to
> get stable build results.
>·
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
So I tested this and immediately found another dependency like that to
libaio :-/. Probably uncovered by the changing build order.
So I think I'll make it possible to prevent the dependency with something
like this.
Michael
Michael Olbrich (2):
wrapper: add package variable to blacklist compiler flags
fio: don't try to use zlib or aio
doc/ref_make_variables.rst | 8 ++++++++
rules/fio.make | 4 ++++
rules/post/ptxd_make_world_common.make | 1 +
scripts/wrapper/libwrapper.sh | 6 ++++++
4 files changed, 19 insertions(+)
--
2.29.2
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2021-05-21 7:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 20:35 Lucas Stach
2021-05-21 7:28 ` Michael Olbrich [this message]
2021-05-21 7:28 ` [ptxdist] [PATCH 1/2] wrapper: add package variable to blacklist compiler flags Michael Olbrich
2021-05-21 7:28 ` [ptxdist] [PATCH 2/2] fio: don't try to use zlib or aio Michael Olbrich
2021-05-21 8:19 ` Lucas Stach
2021-05-21 10:47 ` Michael Olbrich
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=20210521072841.2133655-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=l.stach@pengutronix.de \
--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