From: Petr Ovtchenkov <firstname.lastname@example.org>
To: "Érico Nogueira" <email@example.com>
Subject: Re: [PATCH 1/1] support cross compilation
Date: Wed, 26 May 2021 19:34:28 +0300 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On Wed, 26 May 2021 12:41:51 -0300
Érico Nogueira <email@example.com> wrote:
> Yes, we really cross.
It doesn't matter because
> We always use the release tarballs, which already have the %_dis.h
> files. This explains why we haven't hit any issues.
> Anyway, couldn't you (re)use the distribution tarball generation stuff
> for cross setups from git master?
I can. But I haven't problems with building it "directly from VCS" too,
as you see. Nevertheless there are opinion that code from VCS
could be smoothly building without procedures behind scene.
> Otherwise this would add a
> dependency on autoconf-archive for anyone generating the configure
> script locally...
Well, anyone who generate configure locally has it. Otherwise it is a
big pain ;).
> I think a final version of this patch should
> document the autoconf-archive requirement, if it's merged.
May be addition of m4/ax_prog_cc_for_build.m4 make sense?
next prev parent reply other threads:[~2021-05-26 16:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <firstname.lastname@example.org>
2021-05-26 7:32 ` Petr Ovtchenkov
2021-05-26 13:09 ` Érico Nogueira
2021-05-26 13:58 ` Petr Ovtchenkov
2021-05-26 15:41 ` Érico Nogueira
2021-05-26 16:34 ` Petr Ovtchenkov [this message]
2022-12-21 12:26 ` Mark Wielaard
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).