From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Markus Mayer via buildroot <buildroot@buildroot.org>
Cc: Buildroot Mailing List <buildroot@busybox.net>,
Fabrice Fontaine <fontaine.fabrice@gmail.com>,
Markus Mayer <mmayer@broadcom.com>
Subject: Re: [Buildroot] BR2_FORCE_HOST_BUILD broken
Date: Mon, 5 Aug 2024 23:48:08 +0200 [thread overview]
Message-ID: <20240805234808.36e94ee7@windsurf> (raw)
In-Reply-To: <CAGt4E5vg3nF-T3vbbhCmu6Qd+EXjH3fOB63KaB1LpSdb9nw0cA@mail.gmail.com>
Hello,
+Fabrice in Cc.
On Mon, 5 Aug 2024 14:29:05 -0700
Markus Mayer via buildroot <buildroot@buildroot.org> wrote:
> I haven't determined the actual circular dependency yet. Are there any
> tips for narrowing this down? These circular dependencies don't seem
> to be easy to track down.
Thanks for reporting the issue. The problem is that AUTORECONF = YES
adds host-autoconf as a dependency to host-xz... but host-autoconf
extracts a .tar.xz tarball, which requires host-xz (when you have
BR2_FORCE_HOST_BUILD=y).
Since the reason why we autoreconf xz is only relevant for the target
build, I think we could use the same trick as the one I've done in the
tar package in commit 69cbb563a124002fcb3e2725c3516b502587f9cc. I.e, we
do the autoreconf only for the target variant, and not the host
variant, which requires a bit of trickery.
Fabrice, or Markus, do you want to have a look?
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:[~2024-08-05 21: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 [this message]
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
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=20240805234808.36e94ee7@windsurf \
--to=buildroot@buildroot.org \
--cc=buildroot@busybox.net \
--cc=fontaine.fabrice@gmail.com \
--cc=mmayer@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox