From: Jonny Grant <jg@jguk.org>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Xi Ruoyao <xry111@xry111.site>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: host-x86_64-pc-linux-gnu/gcc/xgcc: No such file or directory
Date: Wed, 6 Dec 2023 21:48:58 +0000 [thread overview]
Message-ID: <0be46239-551b-4fca-915d-2f119d6d0bb9@jguk.org> (raw)
In-Reply-To: <CAH6eHdTjHy6wJWCTyP66vHd763P0U6qKT4DrZymxTKcmOmpChQ@mail.gmail.com>
On 05/12/2023 14:49, Jonathan Wakely wrote:
> On Tue, 5 Dec 2023 at 14:44, Jonny Grant <jg@jguk.org> wrote:
>>
>>
>>
>> On 05/12/2023 04:04, Xi Ruoyao wrote:
>>> On Mon, 2023-12-04 at 23:22 +0000, Jonny Grant wrote:
>>>
>>> /* snip */
>>>
>>>>
>>>>
>>>> Thank you and Xi for the link again.
>>>>
>>>>
>>>> I signed up for a wiki account, but I can't see an "edit" button - is
>>>> there a step I need to follow? Wanted to make a spelling correction on
>>>> that page "hellgrind".
>>>
>>> https://gcc.gnu.org/wiki/EditorGroup
>>
>> I see, my username is JonnyGrant, I'm not on the list.
>>
>> Could you change "hellgrind" -> "helgrind" ?
>> https://gcc.gnu.org/wiki/FAQ
>>
>> The other change was "feed-back" -> "feedback"
>> https://gcc.gnu.org/wiki/Community
>
>
> Both fixed, thanks!
Great!
https://gcc.gnu.org/wiki/FAQ#configure
Current:
"Then make a peer gcc-build directory next to the GCC source code directory. This should be an empty directory before you start."
I suggest changing "peer" -> "separate" and "next to" -> "outside"
ie:
"Then make a separate gcc-build directory outside to the GCC source code directory. This should be an empty directory before you start."
I was thinking of submitting a patch to add a link to https://gcc.gnu.org/wiki/FAQ
to https://gcc.gnu.org/install/configure.html
Cheers, Jonny
next prev parent reply other threads:[~2023-12-06 21:49 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
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 [this message]
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=0be46239-551b-4fca-915d-2f119d6d0bb9@jguk.org \
--to=jg@jguk.org \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=xry111@xry111.site \
/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).