public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Ryan Burns <rtburns@protonmail.com>
To: "libc-help@sourceware.org" <libc-help@sourceware.org>
Subject: Unable to override OBJCOPY during configure
Date: Thu, 04 Feb 2021 02:01:30 +0000	[thread overview]
Message-ID: <8zYgCGLOYwM4QgJYHpcrbsF6DkO65RlDeRBJnrDbMymP-oZNm2DkmzE6rd87MdmiS6nRtZF_iKpLXw3Nr3OuvhnCNfZwNPoEzv6zk_yQtNA=@protonmail.com> (raw)

Hi Libc-help,

I'm having trouble cross-compiling glibc to powerpc64le. Compiling to powerpc64le requires a working objcopy, which I have available via powerpc64le-unknown-linux-gnu-objcopy, and I can provide that at build time using "make OBJCOPY=powerpc64le-unknown-linux-gnu-objcopy".
But the toplevel ./configure does OBJCOPY=`$CC -print-prog-name=objcopy` unconditionally, and is unable to find powerpc64le-unknown-linux-gnu-objcopy, so the later version check (to enforce the objcopy 2.26 minimum requirement) fails.
Is it possible to manually specify the objcopy binary at configure time, or bypass the configure check for the objcopy version?

Thanks,
Ryan

                 reply	other threads:[~2021-02-04  2:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='8zYgCGLOYwM4QgJYHpcrbsF6DkO65RlDeRBJnrDbMymP-oZNm2DkmzE6rd87MdmiS6nRtZF_iKpLXw3Nr3OuvhnCNfZwNPoEzv6zk_yQtNA=@protonmail.com' \
    --to=rtburns@protonmail.com \
    --cc=libc-help@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).