unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: Vivien Kraus <vivien@planete-kraus.eu>
Cc: 37403@debbugs.gnu.org
Subject: bug#37403: Cannot 'guix guix build --target=x86_64-w64-mingw32 perl'
Date: Sat, 14 Sep 2019 14:23:38 +0200	[thread overview]
Message-ID: <20190914142338.41be36cb@scratchpost.org> (raw)
In-Reply-To: <20190914135953.6adaef8b@scratchpost.org>

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

Further information:

According to gnu/packages/cross-base.scm, cross-gcc contains either "libc" or
"mingw-source" in the mingw case--I don't know why, but that's what it says.

The purpose of "remove-extra-references" seems to be to shrink the
number of recorded dependencies, so maybe compare it with the unshrinked
list of dependencies by printing the latter out (apparently it should be
inside Config_heavy.pl and Config.pm in the temporary build
directory--could you post those?).

I tried it myself (with mingw target) and I got:

loclibpth='/gnu/store/h90vnqw0nwd0hhm1l5dgxsdrigddfmq4-glibc-2.28/lib'

Hmm.

Also, perl seems to fetch libc from the %build-inputs just fine earlier.

So try putting (assoc-ref native-inputs "libc") instead of
(assoc-ref inputs "libc") in the perl package definition (make sure to
accept native-inputs in the function in the first place) in order to debug
the problem (or maybe (assoc-ref inputs "mingw-source")).

When cross compiling it's important to get right which parts you get
from the host libs and which from the target libs, maybe that's messed
up there.

Also possible would be not to do that shrinking if libc is unavailable,
but not sure whether we want that.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-09-14 12:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-14  7:53 bug#37403: Cannot 'guix guix build --target=x86_64-w64-mingw32 perl' Vivien Kraus
2019-09-14 11:16 ` P via Bug reports for GNU Guix
2019-09-14 11:28   ` Vivien Kraus
2019-09-14 11:59 ` Danny Milosavljevic
2019-09-14 12:23   ` Danny Milosavljevic [this message]
2019-09-14 17:24     ` Vivien Kraus
2019-09-14 13:16 ` Jan Nieuwenhuizen
2019-09-14 17:25   ` Vivien Kraus
2019-09-15 12:16     ` Jan Nieuwenhuizen
2020-03-25 19:49       ` 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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190914142338.41be36cb@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=37403@debbugs.gnu.org \
    --cc=vivien@planete-kraus.eu \
    /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 public inbox

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

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).