all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: Jean Pierre De Jesus DIAZ <me@jeandudey.tech>
Cc: 56536@debbugs.gnu.org
Subject: [bug#56536] [PATCH]: gnu: newt: Fix cross-compilationn
Date: Sat, 06 Aug 2022 19:34:22 +0200	[thread overview]
Message-ID: <87edxtcm3l.fsf@gnu.org> (raw)
In-Reply-To: <Nb5Sm5NhnuG3SMQ5uEOLpGIgRScOisTQF2KSAK6pfv0MYX9xNDRwDbqnjgqtsIbvbnJIN2YTQ1sOjKSrp5skMOXb3r1EwyY48dxGZh-nRU8=@jeandudey.tech> (Jean Pierre De Jesus DIAZ's message of "Sat, 06 Aug 2022 16:54:14 +0000")


Hey,

> Because `python-config' output differs for the host and the target I
> believe.

Right, however moving python to native-inputs I have:

--8<---------------cut here---------------start------------->8---
mathieu@meije ~/guix [env]$ file /gnu/store/ib2xkrh9i2ff2b5zj1llf2x58zrm4zn6-newt-0.52.21-python/lib/python3.9/site-packages/_snack.so
/gnu/store/ib2xkrh9i2ff2b5zj1llf2x58zrm4zn6-newt-0.52.21-python/lib/python3.9/site-packages/_snack.so: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked, stripped
--8<---------------cut here---------------end--------------->8---

which seems fine. An issue could be that the headers it uses at compile
time are from the native Python so maybe we'd better take the one from
the target python.

All in all, I'll go with your original patch I guess.

Thanks,

Mathieu




  reply	other threads:[~2022-08-06 17:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13 12:08 [bug#56536] [PATCH]: gnu: newt: Fix cross-compilationn Jean Pierre De Jesus DIAZ via Guix-patches via
2022-08-06 16:40 ` Mathieu Othacehe
2022-08-06 16:54   ` Jean Pierre De Jesus DIAZ via Guix-patches via
2022-08-06 17:34     ` Mathieu Othacehe [this message]
2022-08-07  9:41       ` bug#56536: " Mathieu Othacehe

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=87edxtcm3l.fsf@gnu.org \
    --to=othacehe@gnu.org \
    --cc=56536@debbugs.gnu.org \
    --cc=me@jeandudey.tech \
    /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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.