Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New packages: python3-breathe and python3-pybind11
Date: Thu, 19 Mar 2020 20:01:15 +0100	[thread overview]
Message-ID: <20200319190115.8uysQ0EaFC7PPnHsrTJbtnIR5cuD-caUR0A-WHi2NJs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20218@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]

New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/pull/20218#issuecomment-601360449

Comment:
> Some cross compilation fail. Approach to [use cmake build-style](https://github.com/void-linux/void-packages/pull/18873#issuecomment-597118155) shown by @yopito and @gspe have better chance to work, because this build step is more complex.

There is no clean way around this. The problem is that the cmake modules invoke the Python interpreter to determine the size of a pointer on the target platform and compare it to the size of the pointer expected by the C++ compiler. The C++ (cross-) compiler returns a 4-byte pointer as expected. The Python interpreter is always native, and returns an 8-byte pointer. The test fails. We can never invoke the Python interpreter for the target arch because its binaries are not compatible with the host architecture.

The only useful thing the cmake build step does is prepare some configuration modules for cmake. I've just copied the relevant modules into `files/` and install them where they need to go in `post_install`. The modules do not appear to be architecture dependent and should be usable on all architectures supported by Void.

  parent reply	other threads:[~2020-03-19 19:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20218@inbox.vuxu.org>
2020-03-19 18:25 ` Chocimier
2020-03-19 18:28 ` Chocimier
2020-03-19 18:56 ` ahesford
2020-03-19 19:01 ` ahesford [this message]
2020-03-20 19:56 ` Chocimier
2020-03-23 14:07 ` ahesford
2020-03-23 15:06 ` ahesford
2020-05-01  1:39 ` [PR PATCH] [Updated] " ahesford
2020-05-01  1:44 ` ahesford
2020-05-18 15:22 ` [PR PATCH] [Updated] " ahesford
2020-05-18 15:24 ` ahesford
2020-05-18 15:27 ` ahesford
2020-05-18 17:42 ` [PR PATCH] [Merged]: " abenson

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=20200319190115.8uysQ0EaFC7PPnHsrTJbtnIR5cuD-caUR0A-WHi2NJs@z \
    --to=ahesford@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).