From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Dennis Clarke <dclarke@blastwave.org>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: one of those annoying little things
Date: Wed, 24 Aug 2022 12:26:53 +0100 [thread overview]
Message-ID: <CAH6eHdQO7L=OW1zY641U7hRTRu6GP0gSg-2izRkny4suW4cxQA@mail.gmail.com> (raw)
In-Reply-To: <49c6528e-13d9-fcff-2046-6a0a167c3fea@blastwave.org>
On Wed, 24 Aug 2022 at 05:23, Dennis Clarke via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
>
>
> Dear ALL :
>
> Not sure who else have been doing bootstraps on machines wherein the
> common sense thing to do is protect the source tree. What I mean is that
The GCC build will not touch the source tree unless you configure with
--enable-maintainer-mode (in which case it will automatically try to
re-run some autotools scripts if some of the generated files in the
tree appear to be out of date).
> I extract the gcc 12.2.0 tarball of joy as the root user.
That's completely unnecessary. This doesn't seem like common sense,
but rather creating unnecessary problems for yourself.
> Then inside
> that directory structure I crack out the gmp/mpfr/mpc goodness and even
> apply the correct patch for mpfr[1].
Not sure what the [1] refers to, but I think I've said before that you
can just use the recommended versions that are downloaded by the
download_prerequisites script, and not worry about patching anything.
>
> So anyways, funny thing happens when I try to build out of tree :
> Turns out, wild, but that directory for the mpfr doc stuff has files
> that no user has rights to other than root. That has to be a bug right?
You extracted the tarballs as root.
> Could be the mpfr guys but hey this seems weird.
>
> So I did a chgrp "foo" on that whole dir and also allowed common dirt
> humans to read and write the mpfr.info file. That seems to allow
> bootstrap to continue for those dirty users. Not sure if anyone else
> sees this as a bug or just a feature.
Either way, it's not a GCC problem.
prev parent reply other threads:[~2022-08-24 11:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 4:21 Dennis Clarke
2022-08-24 5:20 ` Xi Ruoyao
2022-08-24 8:27 ` Matthew R. Wilson
2022-08-24 16:51 ` Dennis Clarke
2022-08-24 18:04 ` Matthew R. Wilson
2022-08-24 19:23 ` Vincent Lefevre
2022-08-24 19:43 ` Dennis Clarke
2022-08-24 20:00 ` Vincent Lefevre
2022-08-24 11:26 ` Jonathan Wakely [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='CAH6eHdQO7L=OW1zY641U7hRTRu6GP0gSg-2izRkny4suW4cxQA@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=dclarke@blastwave.org \
--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).