Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nathanael Nerode <neroden@twcny.rr.com>
To: gdb@sources.redhat.com
Subject: Re: "cd dir && $(MAKE)", not "cd dir; $(MAKE)"
Date: Thu, 19 Dec 2002 16:24:00 -0000	[thread overview]
Message-ID: <20021220002314.GA15166@doctormoo> (raw)

Regarding the subject line, please do it; I just hadn't gotten around to 
it for all targets.

Doug Evans said:
>I've been playing around trying to get things to build.
>Since gcc is in another tree and yet requires installed binutils (*1),
>I let the make run long enough to build binutils,gas,ld, and
>then did a "make install".  That's how this happened.
>[Actually that's not entirely true.  I'm summarizing, but
>I'm guessing the effect is the same.]
Not necessarily.  :-/  But interrupting 'make' in the middle can give 
all manner of screwy results now; don't rely on it.

If you want to build just binutils, gas, and ld, and then install them, 
I strongly suggest doing the following:
make all-binutils all-gas all-ld
make install-binutils install-gas install-ld

This should do exactly what it says.

If you had other directories in the same source tree (such as etc) when 
you were configuring, then they may get automagically configured and 
built.  If you deleted the directories you didn't want *before* running 
toplevel configure, you should be OK.

We're also planning on a way to specify to top level configure "Just 
don't configure this directory" -- probably something like 
--without-<subdir> -- it should be easy but it hasn't actually 
happened yet.

>Has anyone gotten a "one-tree" tree to build yet under the
>new configure regime?
Yep, I have.  I wouldn't have committed it otherwise.  And obviously I 
missed a lot of subtle points, but I've been fixing them as they appear.

You should be able to build the gcc tree, the complete src tree, or the 
merged gcc-src tree.  You should also be able to build the trees 
corresponding to a gdb distribution, an insight distribution, a binutils 
distribution, a newlib distribution, or any of the gcc 
'sub-distributions'.  I haven't tested all of these at once (since it's 
a pain in the neck), but I have tested each of them at one time or 
another during the process; and the code is theoretically correct.

If a problem is encountered in any one of these, I will strive to fix 
it (and it will probably be pretty straightforward, unless it's 
gdb vs. insight, which is a bit messier).

--Nathanael


                 reply	other threads:[~2002-12-20  0:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20021220002314.GA15166@doctormoo \
    --to=neroden@twcny.rr.com \
    --cc=gdb@sources.redhat.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