public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jeff Deifik <jdeifik@weasel.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: bootstrap/3236
Date: Wed, 20 Jun 2001 06:26:00 -0000	[thread overview]
Message-ID: <20010620132601.31896.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR bootstrap/3236; it has been noted by GNATS.

From: Jeff Deifik <jdeifik@weasel.com>
To: "Joseph S. Myers" <jsm28@cam.ac.uk>, Zack Weinberg <zackw@stanford.edu>
Cc: Jeff Deifik <jeff.deifik@jpl.nasa.gov>, <gcc-gnats@gcc.gnu.org>,
   <gcc-bugs@gcc.gnu.org>
Subject: Re: bootstrap/3236
Date: Wed, 20 Jun 2001 06:14:28 -0700

 At 12:33 PM 6/20/01 +0100, Joseph S. Myers wrote:
 >On Tue, 19 Jun 2001, Zack Weinberg wrote:
 >
 > > I agree this is confusing.  It's also inaccurate; the second paragraph
 > > is true whether or not you are using CVS.
 >
 >The point of referring to CVS is that checking out from CVS will check out
 >into a "gcc" directory rather than a gcc-version directory.
 >
 > > # % cd *objdir*
 > > # % ../*srcdir*/configure [target] [options]
 > >
 > > to emphasize that *objdir* and *srcdir* must be entirely separate.
 >
 >Both relative and absolute paths for srcdir ought to work.
 >
 > > I would send a patch but I do not know where the master copy of this
 > > file lives or how to update all of its children.
 >
 >gcc/doc/install.texi on mainline (which should probably be merged to the
 >branch when the branch reopens), online version generated by
 >update_web_docs run from cron.
 
 This is jeff deifik (from my home domain).
 
 I was able to successfully build gcc-3.0 by building in the
 gcc-3.0 tree. I know you folks said not to do it, but someone else
 at work did it successfully, and I was at wits end due to the
 make bootstrap bug I reported.
 
 The build went fine, the install went fine, and my personal test cases work 
 fine.
 
 There does seem to be a problem with the 'make -k check' part, not
 being able to find a bunch of files, but I didn't report that, since I *was*
 building in the source directory.
 
 I suspect there is something wrong with the documented procedure to
 have objdir != srcdir, since I was able to build when objdir == srcdir.
 
          thanks,
          jeff deifik
          jeff.deifik@jpl.nasa.gov - work
          jdeifik@weasel.com - home
 


             reply	other threads:[~2001-06-20  6:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-20  6:26 Jeff Deifik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-20 11:26 bootstrap/3236 Zack Weinberg
2001-06-20 11:06 bootstrap/3236 Jeff Deifik
2001-06-20 10:56 bootstrap/3236 Zack Weinberg
2001-06-20 10:46 bootstrap/3236 Zack Weinberg
2001-06-20  4:36 bootstrap/3236 Joseph S. Myers

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=20010620132601.31896.qmail@sourceware.cygnus.com \
    --to=jdeifik@weasel.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).