From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] protobuf-c: binary disabled during cross-compiling
Date: Mon, 15 Nov 2021 00:30:10 +0100 [thread overview]
Message-ID: <20211114233010.eDoQvaHjq5EnGkcaKGf9ZtT08t1dDqSC9Ajsc_35NHA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34084@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
Closed issue by natrys on void-packages repository
https://github.com/void-linux/void-packages/issues/34084
Description:
I was building a nocross package (postgis) on aarch64, where the build somewhat confusingly failed because a dependency (protobuf-c) was missing its binary.
It appears that building the compiler binary was disabled for cross-compilation in the template, with reasoning being:
```
# buildprocess calls compiler while building, disable it on cross build
build_options="protoc"
desc_option_protoc="Build protoc-c compiler"
if [ -z "$CROSS_BUILD" ]; then
build_options_default="protoc"
fi
```
But I wonder if this is not a problem any more. To test, I have cross-compiled it with `protoc` option enabled on x86_64 host, and it seemed to build and then work fine on aarch64 target. Upstream issue tracker had resolved number of cross-compilation related issues since this, and I think this is expected to be fine now. Perhaps someone else can verify.
prev parent reply other threads:[~2021-11-14 23:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 23:22 [ISSUE] " natrys
2021-11-14 23:29 ` ericonr
2021-11-14 23:30 ` Johnnynator [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=20211114233010.eDoQvaHjq5EnGkcaKGf9ZtT08t1dDqSC9Ajsc_35NHA@z \
--to=johnnynator@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).