From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Markus Mayer <markus.mayer@broadcom.com>
Cc: Buildroot Mailing List <buildroot@busybox.net>,
Fabrice Fontaine <fontaine.fabrice@gmail.com>,
Markus Mayer via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] BR2_FORCE_HOST_BUILD broken
Date: Tue, 6 Aug 2024 16:48:35 +0200 [thread overview]
Message-ID: <20240806164835.4d88e702@windsurf> (raw)
In-Reply-To: <CAGt4E5v3F3zJyNZPGtWRpOxbO9eNV4+H6bd6tKXR7fwqBiMWmw@mail.gmail.com>
On Mon, 5 Aug 2024 20:08:51 -0700
Markus Mayer <markus.mayer@broadcom.com> wrote:
> Patch submitted. Turns out this one seems to be a bit simpler than the
> "tar" case. In my tests there was no need for a post patch hook. Just
> setting "HOST_XZ_AUTORECONF=NO" seems to suffice.
Indeed, the tar case is different. In the tar case, we apply patches
that touch configure.ac/Makefile.am, so we have to autoreconf. The
patches are also applied when building host-tar, so if we don't do
anything, configure.ac has a newer timestamp than configure, and
therefore even with HOST_TAR_AUTORECONF = NO, and automagic-autoreconf
gets triggered at build time.
In the case of xz, we don't patch anything, it's just that the provided
configure/Makefile are slightly broken for static builds, which is
completely irrelevant for host-xz, so indeed HOST_XZ_AUTORECONF = NO is
sufficient.
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
prev parent reply other threads:[~2024-08-06 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 21:29 [Buildroot] BR2_FORCE_HOST_BUILD broken Markus Mayer via buildroot
2024-08-05 21:48 ` Thomas Petazzoni via buildroot
2024-08-06 2:19 ` Markus Mayer via buildroot
[not found] ` <CAGt4E5v3F3zJyNZPGtWRpOxbO9eNV4+H6bd6tKXR7fwqBiMWmw@mail.gmail.com>
2024-08-06 14:48 ` Thomas Petazzoni via buildroot [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=20240806164835.4d88e702@windsurf \
--to=buildroot@buildroot.org \
--cc=buildroot@busybox.net \
--cc=fontaine.fabrice@gmail.com \
--cc=markus.mayer@broadcom.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.