public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dennis Clarke <dclarke@blastwave.org>
To: gcc-help@gcc.gnu.org
Subject: one of those annoying little things
Date: Wed, 24 Aug 2022 00:21:46 -0400	[thread overview]
Message-ID: <49c6528e-13d9-fcff-2046-6a0a167c3fea@blastwave.org> (raw)


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
I extract the gcc 12.2.0 tarball of joy as the root user. Then inside
that directory structure I crack out the gmp/mpfr/mpc goodness and even
apply the correct patch for mpfr[1].

     So anyways, funny thing happens when I try to build out of tree :

.
.
.
config.status: creating tools/bench/Makefile
config.status: executing depfiles commands
config.status: executing libtool commands
gmake[3]: Entering directory 
'/opt/bw/build/gcc-12.2.0_NetBSD_9.3_AMD64.001/mpfr'
Making all in doc
gmake[4]: Entering directory 
'/opt/bw/build/gcc-12.2.0_NetBSD_9.3_AMD64.001/mpfr/doc'
restore=: && backupdir=".am$$" && \
am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd 
../../../gcc-12.2.0/mpfr/doc && \
rm -rf $backupdir && mkdir $backupdir && \
if (makeinfo --split-size=5000000 --split-size=5000000 
--split-size=5000000 --version) >/dev/null 2>&1; then \
   for f in ../../../gcc-12.2.0/mpfr/doc/mpfr.info 
../../../gcc-12.2.0/mpfr/doc/mpfr.info-[0-9] 
../../../gcc-12.2.0/mpfr/doc/mpfr.info-[0-9][0-9] 
../../../gcc-12.2.0/mpfr/doc/mpfr.i[0-9] 
../../../gcc-12.2.0/mpfr/doc/mpfr.i[0-9][0-9]; do \
     if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
   done; \
else :; fi && \
cd "$am__cwd"; \
if makeinfo --split-size=5000000 --split-size=5000000 
--split-size=5000000  --enable-encoding -I ../../../gcc-12.2.0/mpfr/doc \
  -o ../../../gcc-12.2.0/mpfr/doc/mpfr.info 
../../../gcc-12.2.0/mpfr/doc/mpfr.texi; \
then \
   rc=0; \
   CDPATH="${ZSH_VERSION+.}:" && cd ../../../gcc-12.2.0/mpfr/doc; \
else \
   rc=$?; \
   CDPATH="${ZSH_VERSION+.}:" && cd ../../../gcc-12.2.0/mpfr/doc && \
   $restore $backupdir/* `echo 
"./../../../gcc-12.2.0/mpfr/doc/mpfr.info" | sed 's|[^/]*$||'`; \
fi; \
rm -rf $backupdir; exit $rc
mkdir: .am388: Permission denied
../../../gcc-12.2.0/mpfr/doc/mpfr.info: Permission denied
gmake[4]: *** [Makefile:380: ../../../gcc-12.2.0/mpfr/doc/mpfr.info] Error 1
gmake[4]: Leaving directory 
'/opt/bw/build/gcc-12.2.0_NetBSD_9.3_AMD64.001/mpfr/doc'
gmake[3]: *** [Makefile:500: all-recursive] Error 1
gmake[3]: Leaving directory 
'/opt/bw/build/gcc-12.2.0_NetBSD_9.3_AMD64.001/mpfr'
gmake[2]: *** [Makefile:7094: all-stage1-mpfr] Error 2
gmake[2]: Leaving directory '/opt/bw/build/gcc-12.2.0_NetBSD_9.3_AMD64.001'
gmake[1]: *** [Makefile:27609: stage1-bubble] Error 2
gmake[1]: Leaving directory '/opt/bw/build/gcc-12.2.0_NetBSD_9.3_AMD64.001'
gmake: *** [Makefile:28222: bootstrap4] Error 2


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

-- 
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional

             reply	other threads:[~2022-08-24  4:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24  4:21 Dennis Clarke [this message]
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

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=49c6528e-13d9-fcff-2046-6a0a167c3fea@blastwave.org \
    --to=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).