From: Kai Ruottu <kai.ruottu@wippies.com>
To: gcc-help@gcc.gnu.org
Subject: Re: Built compiler cannot create executables during GCC 8.2.0 "make" from repository clone.
Date: Sun, 16 Sep 2018 16:26:00 -0000 [thread overview]
Message-ID: <d198cbaf-39d2-63a7-f16e-c22f1353f036@wippies.com> (raw)
In-Reply-To: <60E9363C-8F48-4642-B556-4AA7FC1F5804@gmail.com>
Bryan Dunphy kirjoitti 16.9.2018 klo 18.45:
> This is the contents of config.log with the same substitution as before. It APPEARS that the problem is invalid command line options being passed to GCC! How do I fix this?
No, it's this :
> configure:3725: checking for C compiler default output file name
> configure:3747: $HOME/Development/gcc-obj/./gcc/xgcc -B$HOME/Development/gcc-obj/./gcc/ -B$HOME/gcc-built/x86_64-apple-darwin17.7.0/bin/ -B$HOME/gcc-built/x86_64-apple-darwin17.7.0/lib/ -isystem $HOME/gcc-built/x86_64-apple-darwin17.7.0/include -isystem $HOME/gcc-built/x86_64-apple-darwin17.7.0/sys-include -g -O2 conftest.c >&5
> ld: library not found for -lgcc_ext.10.5
> collect2: error: ld returned 1 exit status
>
Something expects 'libgcc_ext.10.5.<something>' (I don't know what lib
name extensions MacOS X uses here). The 'specs' file would tell what the
linking spec expects....
prev parent reply other threads:[~2018-09-16 16:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 15:15 Built compiler cannot create executables during GCC 8.2.0 "make" Bryan Dunphy
2018-09-05 15:21 ` Jonathan Wakely
2018-09-06 14:46 ` Built compiler cannot create executables during GCC 8.2.0 "make" from repository clone Bryan Dunphy
2018-09-07 7:56 ` Jonathan Wakely
2018-09-16 15:46 ` Bryan Dunphy
2018-09-16 16:26 ` Kai Ruottu [this message]
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=d198cbaf-39d2-63a7-f16e-c22f1353f036@wippies.com \
--to=kai.ruottu@wippies.com \
--cc=gcc-help@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).