From: Jeffrey A Law <law@cygnus.com>
To: Toon Moene <toon@moene.indiv.nluug.nl>
Cc: egcs@cygnus.com
Subject: Re: egcs-971201 on m68k-next-nextstep3; Status Report
Date: Tue, 02 Dec 1997 18:18:00 -0000 [thread overview]
Message-ID: <24593.881101122@cygnus.com> (raw)
In-Reply-To: <9712022154.AA18041@moene.indiv.nluug.nl>
In message < 9712022154.AA18041@moene.indiv.nluug.nl >you write:
> Jeff,
>
> You wrote:
>
> > I think this is the sequence to workaround the include problems.
>
> > cd objdir
> > make all-texinfo all-bison all-byacc all-binutils all-gas all-ld
> > cd gcc
> > make bootstrap
> > make install-headers-tar
> > cd ..
> > make bootstrap3
>
> I just tried this today on egcs-971201, but apparently this only
> works if the user doing the build also has write permission to the
> install directory; otherwise, `make install-headers-tar' won't
> succeed, and the subsequent `make bootstrap3' also fails.
Yup. No suprise there. I don't see a good way to solve the problem
in-place.
jeff
prev parent reply other threads:[~1997-12-02 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-30 8:38 egcs-971127 " Toon Moene
1997-11-30 14:29 ` Jeffrey A Law
1997-12-02 16:29 ` egcs-971201 " Toon Moene
1997-12-02 18:18 ` Jeffrey A Law [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=24593.881101122@cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=toon@moene.indiv.nluug.nl \
/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).