unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Zheng Junjie <zhengjunjie@iscas.ac.cn>
To: 73006@debbugs.gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>
Subject: [bug#73006] [PATCH 2/2] gnu: glibc: Fix cross-compiling.
Date: Wed,  4 Sep 2024 00:33:21 +0800	[thread overview]
Message-ID: <9e62ab6b2ecb4bbb2ca5e863ca459b825104f157.1725379915.git.zhengjunjie@iscas.ac.cn> (raw)
In-Reply-To: <cover.1725379915.git.zhengjunjie@iscas.ac.cn>

* gnu/packages/base.scm (glibc)[arguments]<#:configure-flags>: When
cross-compiling, Set OBJCOPY and OBJDUMP.

Change-Id: I9abd3bda792619903233f5f48a57065da45da50c
---
 gnu/packages/base.scm | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/gnu/packages/base.scm b/gnu/packages/base.scm
index 4e8121ae2c..2802af2946 100644
--- a/gnu/packages/base.scm
+++ b/gnu/packages/base.scm
@@ -920,6 +920,10 @@ (define-public glibc
                                            '%build-inputs)
                                       "kernel-headers")
                            "/include")
+            ,@(if (%current-target-system)
+                  `((string-append "OBJCOPY=" ,(objcopy-for-target))
+                    (string-append "OBJDUMP=" ,(objdump-for-target)))
+                  '())
 
             ;; This is the default for most architectures as of GNU libc 2.26,
             ;; but we specify it explicitly for clarity and consistency.  See
-- 
2.45.2





  parent reply	other threads:[~2024-09-03 17:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-03 16:30 [bug#73006] [PATCH 0/2] gnu: glibc: Fix cross-compiling Zheng Junjie
2024-09-03 16:33 ` [bug#73006] [PATCH 1/2] utils: Add 'objcopy-for-target' and 'objdump-for-target' Zheng Junjie
2024-09-03 16:33 ` Zheng Junjie [this message]
2024-09-04 17:16 ` [bug#73006] [PATCH 0/2] gnu: glibc: Fix cross-compiling Ludovic Courtès
2024-09-05 15:52   ` Zheng Junjie
2024-09-27 12:24     ` Z572
2024-10-15 15:33     ` bug#73006: " Ludovic Courtès

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=9e62ab6b2ecb4bbb2ca5e863ca459b825104f157.1725379915.git.zhengjunjie@iscas.ac.cn \
    --to=zhengjunjie@iscas.ac.cn \
    --cc=73006@debbugs.gnu.org \
    --cc=ludo@gnu.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. 
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).