public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonny Grant <jg@jguk.org>
To: Jonathan Wakely <jwakely.gcc@gmail.com>, Xi Ruoyao <xry111@xry111.site>
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 23:22:05 +0000	[thread overview]
Message-ID: <dfdbabde-20ae-435a-9462-ba14f9821a5e@jguk.org> (raw)
In-Reply-To: <CAH6eHdSaw+LNQ-duaz7XLAcp9n_bUB0FBxbWA6MKieYNQ=z_dw@mail.gmail.com>



On 04/12/2023 10:44, Jonathan Wakely wrote:
> 
> 
> On Mon, 4 Dec 2023, 04:38 Xi Ruoyao, <xry111@xry111.site> wrote:
> 
>     On Mon, 2023-12-04 at 00:34 +0000, Jonny Grant wrote:
>     > Is it this page?
>     >
>     > https://gcc.gnu.org/install/configure.html <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"
> 
>     This paragraph has been updated to:
> 
>     First, we highly recommend that GCC be built into a separate directory
>     from the sources which does not reside within the source tree. This is
>     how we generally build GCC; building where objdir is a subdirectory of
>     srcdir should work as well; building where objdir == srcdir is
>     unsupported.
> 
>     Richard told me using a new subdirectory in srcdir as objdir works fine
>     and *is* supported (i. e. if it somehow stops to work we'll fix).  But
>     objdir == srcdir has been broken for a long time and there is no
>     intention to make it "work".
> 
>     The FAQ is a different page: https://gcc.gnu.org/wiki/FAQ#configure <https://gcc.gnu.org/wiki/FAQ#configure>
> 
> 
> i.e. the link I sent in my first reply.
> 

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".

I saw a spelling mistake on another page too.

Kind regards, Jonny




  reply	other threads:[~2023-12-04 23:22 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 [this message]
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=dfdbabde-20ae-435a-9462-ba14f9821a5e@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).