public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: mutazilah@gmail.com (Paul Edwards)
Cc: Ulrich.Weigand@de.ibm.com (Ulrich Weigand), gcc@gcc.gnu.org
Subject: Re: i370 port - constructing compile script
Date: Sat, 24 Oct 2009 04:11:00 -0000	[thread overview]
Message-ID: <200910240228.n9O2SYAV011735@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <CCE7532DF0824C928FB70535B6DCBF09@Paullaptop> from "Paul Edwards" at Oct 24, 2009 10:19:11 AM

Paul Edwards wrote:

> > Are you running the top-level configure?  (If you run a
> > subdirectory configure, e.g. the one in gcc/, directly,
> > things may not work correctly.)
> 
> Yes I am.
> 
> One other thing I did - I compiled the cross-compiler, and installed it.
> 
> Then I wiped out the directory and extracted a fresh version and did
> the configure for building the host.  I thought that would make things
> clean.  But maybe the previous build had the correct auto-build.h
> that I need, and without it I get some sort of dummy auto-build.h?

No, you definitely should start from a clean build directory when
building the native compiler.  In fact, you should not build in the
source directory at all; this has been known to not always work
reliably for GCC, in particular when doing more complex builds ...

This means that if your GCC source tree resides in a directory, say,
  ~/gcc-src
you should *not* run ./configure while in ~/gcc-src.  Instead, you
should create a second, empty directory
  ~/gcc-build
(which is not a subdirectory of ~/gcc-src), and run
  ../gcc-src/configure ...
while in ~/gcc-build.

The "make" process then operates wholly in the build directory, without
changing anything in the source directory.  For doing the second compiler
build, you can either delete the build directory, or just use yet another
directory.

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com

  reply	other threads:[~2009-10-24  2:28 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OF0A51B575.29A29744-ON42257656.0067E35B-42257656.00682411@de.ibm.com>
2009-10-22  9:06 ` Paul Edwards
2009-10-22 19:26   ` Ulrich Weigand
2009-10-22 22:04     ` Paul Edwards
2009-10-23 14:36     ` Paul Edwards
2009-10-23 14:58       ` Ian Lance Taylor
2009-10-23 15:16       ` Ulrich Weigand
2009-10-24  0:20         ` Paul Edwards
2009-10-24  4:11           ` Ulrich Weigand [this message]
2009-10-27 12:18             ` Paul Edwards
2009-11-02 14:45 Paul Edwards
  -- strict thread matches above, loose matches on Subject: below --
2009-09-25 15:20 i370 port Ulrich Weigand
2009-09-30 17:24 ` i370 port - constructing compile script Paul Edwards
2009-09-30 17:36   ` Richard Henderson
2009-09-30 21:40     ` Paul Edwards
     [not found]       ` <mcrpr98x9w8.fsf@dhcp-172-17-9-151.mtv.corp.google.com>
2009-10-01  0:16         ` Joseph S. Myers
2009-10-01 14:00           ` Paul Edwards
2009-10-02 12:41           ` Paul Edwards
2009-10-02 16:00             ` Ian Lance Taylor
2009-10-02 22:53               ` Paul Edwards
2009-10-04  4:11                 ` Ian Lance Taylor
2009-10-04  5:14                   ` Paul Edwards
2009-10-04  6:04                     ` Ian Lance Taylor
2009-10-04  6:50                       ` Paul Edwards
2009-10-04 15:38                         ` Ulrich Weigand
2009-10-04 22:51                           ` Paul Edwards
2009-10-05 13:15                             ` Ulrich Weigand
2009-10-06  9:32                               ` Paul Edwards
2009-10-06 13:15                                 ` Ulrich Weigand
2009-10-06 13:38                                   ` Paul Edwards
2009-10-06 14:01                                     ` Ulrich Weigand
2009-10-14 14:33                                       ` Paul Edwards
2009-10-19 14:19                               ` Paul Edwards
2009-10-19 17:37                                 ` Ulrich Weigand
2009-10-20 14:18                                   ` Paul Edwards
2009-10-20 15:30                                     ` Ulrich Weigand
2009-11-12 14:03                                   ` Paul Edwards
2009-11-12 20:06                                     ` Ralf Wildenhues
2009-11-12 20:56                                       ` Paul Edwards
2009-11-13 11:43                                       ` Paul Edwards
2009-11-13 12:01                                         ` Ulrich Weigand
2009-11-13 12:18                                           ` Paul Edwards
2009-11-13 12:57                                             ` Ulrich Weigand
2009-11-14  8:52                                               ` Paul Edwards
2009-11-14 10:49                                                 ` Ralf Wildenhues
2009-11-14 11:28                                                   ` Paul Edwards
2009-11-22  0:51                                                     ` Paolo Bonzini
2009-11-18 10:51                                                   ` Paul Edwards
2009-11-19 14:27                                                     ` Ulrich Weigand
2009-11-21 13:40                                                       ` Paul Edwards
2009-11-22  0:46                                         ` Paolo Bonzini
2009-11-13 12:08                                     ` Ulrich Weigand
2009-10-05 13:17                         ` Michael Matz
2009-10-05 13:38                           ` Paul Edwards
2009-10-05 13:46                             ` Michael Matz
2009-10-01 14:28   ` Paul Brook
2009-10-01 16:00     ` Paul Edwards
2009-10-01 18:36       ` Ian Lance Taylor
2009-10-01 23:43         ` Paul Edwards
2009-10-01 21:10       ` David Edelsohn
2009-10-01 22:22         ` Toon Moene
2009-10-02  0:19           ` Paul Edwards

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=200910240228.n9O2SYAV011735@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=gcc@gcc.gnu.org \
    --cc=mutazilah@gmail.com \
    /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).