From: Jonny Grant <jg@jguk.org>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: host-x86_64-pc-linux-gnu/gcc/xgcc: No such file or directory
Date: Mon, 4 Dec 2023 00:34:39 +0000 [thread overview]
Message-ID: <c8978260-1bb2-47d2-a4f0-8dd43f29853e@jguk.org> (raw)
In-Reply-To: <CAH6eHdTbvRR+nXNBNB1bgQwf+6xELYYww-rcFWpg8v7yJSAxNQ@mail.gmail.com>
On 30/11/2023 09:31, Jonathan Wakely wrote:
>
>
> On Wed, 29 Nov 2023, 23:53 Jonny Grant, <jg@jguk.org <mailto:jg@jguk.org>> wrote:
>
>
>
> On 29/11/2023 15:55, Jonathan Wakely wrote:
> > On Wed, 29 Nov 2023 at 14:44, Jonny Grant <jg@jguk.org <mailto:jg@jguk.org>> wrote:
> >>
> >>
> >>
> >> On 29/11/2023 13:05, Jonathan Wakely wrote:
> >>> On Wed, 29 Nov 2023 at 12:59, Jonny Grant <jg@jguk.org <mailto:jg@jguk.org>> wrote:
> >>>>
> >>>> Hello
> >>>>
> >>>> Has anyone encountered this when compiling gcc from source? libgomp doesn't build due to xgcc missing
> >>>>
> >>>> I got latest git, did
> >>>> ./configure --disable-multilib
> >>>
> >>> Don't build in the source directory: https://gcc.gnu.org/wiki/FAQ#configure <https://gcc.gnu.org/wiki/FAQ#configure>
> >>>
> >>>> make html
> >>>
> >>> Try make all-gcc before make html.
> >>
> >>
> >> Sure.
> >>
> >> It gets stuck on genmodes.cc
> >>
> >>
> >>
> >> ../gcc_doc/configure --prefix=/home/jonny/code/repos/gcc_tests/gcc_install --disable-multilib
> >
> > This belongs on the gcc-help list, not here.
> >
> > Are you sure you ran configure in an empty dir, not one you'd already
> > fouled up with previous configurations or previous 'make html'
> > commands?
>
> May I ask if "make distclean" clean up the 24 files that are left as untracked files? "git status" shows them. Anyway, as you have suggested, I'll always run on a separate build dir.
>
> My build dir worked after I removed these 3:
>
> gcc/collect-ld
> gcc/bconfig.h
> gcc/auto-host.h
>
>
> The full 24 I local files I removed. Sharing for completeness.
> gcc/Make-hooks
> gcc/ada/Makefile
> gcc/ada/gcc-interface/Makefile
> gcc/as
> gcc/auto-host.h
> gcc/bconfig.h
> gcc/collect-ld
> gcc/config.h
> gcc/configargs.h
> gcc/cs-bconfig.h
> gcc/cs-config.h
> gcc/cs-tm.h
> gcc/cs-tm_p.h
> gcc/cstamp-h
> gcc/dsymutil
> gcc/gcc-driver-name.h
> gcc/gcc-vers.texi
> gcc/m2/Make-maintainer
> gcc/m2/config-make
> gcc/nm
> gcc/option-includes.mk <http://option-includes.mk>
> gcc/plugin-version.h
> gcc/tm.h
> gcc/tm_p.h
>
>
> > You should start in a completely empty directory. And I assume
> > ../gcc_doc is not the same directory as .
>
> Yes, have gcc_build directory too. I'd expected "make distclean" to have been enough. But I'll always build from a separate directory now.
>
>
> Just remove the whole directory and start again in a clean one.
Fair enough, I did that, it works now.
> I'll add that to the FAQ.
Is it this page?
https://gcc.gnu.org/install/configure.html
How about changing this line to clarify make just say building within the src tree does not work, and is unsupported?
Change from:
"First, we highly recommend that GCC be built into a separate directory"
To:
"First, we only support building GCC from a separate directory"
Kind regards, Jonny
next prev parent reply other threads:[~2023-12-04 0:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9eed991c-7def-440a-bb3b-96ea4f26a19e@jguk.org>
[not found] ` <CAH6eHdQNRRQH09J_x+vUBF1WUXGEaVkBy+_gC8BWXZ3EkhKxFg@mail.gmail.com>
[not found] ` <8b1d2871-b1e1-4f6a-985a-a66d1b2fe40e@jguk.org>
[not found] ` <CAH6eHdRfqegjidsvAka4RQHCWqPD1y0RBBrn4NHHT64fppJjmA@mail.gmail.com>
2023-11-29 23:53 ` Jonny Grant
2023-11-30 9:31 ` Jonathan Wakely
2023-12-04 0:34 ` Jonny Grant [this message]
2023-12-04 4:38 ` Xi Ruoyao
2023-12-04 10:44 ` Jonathan Wakely
2023-12-04 23:22 ` Jonny Grant
2023-12-05 4:04 ` Xi Ruoyao
2023-12-05 14:44 ` Jonny Grant
2023-12-05 14:49 ` Jonathan Wakely
2023-12-06 21:48 ` Jonny Grant
2023-12-07 0:17 ` Jonathan Wakely
2023-12-07 9:47 ` Jonny Grant
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=c8978260-1bb2-47d2-a4f0-8dd43f29853e@jguk.org \
--to=jg@jguk.org \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
/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).