public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113648] Cross compiler cannot find cross binutils on macOS
Date: Mon, 29 Jan 2024 05:53:15 +0000 [thread overview]
Message-ID: <bug-113648-4-hcXdPi0Ucq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113648-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113648
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2024-01-29
Status|UNCONFIRMED |WAITING
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Works for me for a cross from Linux:
[apinski@xeond2 upstream-full-cross]$ ./install/bin/aarch64-linux-gnu-gcc
-print-prog-name=ld
/bajas/pinskia/src/upstream-full-cross/install/bin/../lib/gcc/aarch64-linux-gnu/14.0.1/../../../../aarch64-linux-gnu/bin/ld
My configure line:
Configured with: ../configure --target=aarch64-linux-gnu
--prefix=/home/apinski/src/upstream-full-cross/install
--enable-languages=c,c++,fortran,go
--with-sysroot=/home/apinski/src/upstream-full-cross/install//sysroot
Can you do:
provide the output of `strace aarch64-linux-gnu-gcc -print-prog-name=ld ` ?
Also provide the config.log from the original build?
next prev parent reply other threads:[~2024-01-29 5:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 5:38 [Bug target/113648] New: " galaxyking0419 at gmail dot com
2024-01-29 5:53 ` pinskia at gcc dot gnu.org [this message]
2024-01-29 6:46 ` [Bug target/113648] " galaxyking0419 at gmail dot com
2024-01-29 8:47 ` schwab@linux-m68k.org
2024-01-29 8:50 ` schwab@linux-m68k.org
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=bug-113648-4-hcXdPi0Ucq@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.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.
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).