From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] host-libffi: Follow target libffi.
Date: Mon, 5 Aug 2024 08:49:40 +0200 [thread overview]
Message-ID: <20240805064940.890299-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20240717213557.2353045-2-christian.melki@t2data.com>
Thanks, applied as 4ed5009f75e1a8e6559499ccad8364698c571088.
Michael
[sent from post-receive hook]
On Mon, 05 Aug 2024 08:49:40 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> Add some useful options to the host build.
> We don't need docs, static, internal builddirs and we don't
> need multi-lib arch discovery via gcc.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20240717213557.2353045-2-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/host-libffi.make b/rules/host-libffi.make
> index fd97369282fb..41b0e72b48e8 100644
> --- a/rules/host-libffi.make
> +++ b/rules/host-libffi.make
> @@ -18,6 +18,9 @@ HOST_PACKAGES-$(PTXCONF_HOST_LIBFFI) += host-libffi
> HOST_LIBFFI_CONF_TOOL := autoconf
> HOST_LIBFFI_CONF_OPT := \
> $(HOST_AUTOCONF) \
> - --disable-static
> + --disable-builddir \
> + --disable-static \
> + --disable-docs \
> + --disable-multi-os-directory
>
> # vim: syntax=make
next prev parent reply other threads:[~2024-08-05 6:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 21:35 [ptxdist] [PATCH 1/2] libffi: Adjust build options Christian Melki
2024-07-17 21:35 ` [ptxdist] [PATCH 2/2] host-libffi: Follow target libffi Christian Melki
2024-08-05 6:49 ` Michael Olbrich [this message]
2024-08-05 6:49 ` [ptxdist] [APPLIED] libffi: Adjust build options 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=20240805064940.890299-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.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