Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Cc: jan.kratochvil@redhat.com, gdb-patches@sourceware.org
Subject: Re: Update rebuild rules in non-automake directories.
Date: Wed, 26 Aug 2009 17:57:00 -0000	[thread overview]
Message-ID: <83r5uycvh4.fsf@gnu.org> (raw)
In-Reply-To: <20090826173807.GA9074@gmx.de>

> Date: Wed, 26 Aug 2009 19:38:07 +0200
> From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
> Cc: gdb-patches@sourceware.org
> 
> But I have a more general question first:
> so far I was under the impression that GCC and all of src always only
> builds outside the source directory (and consequently, I never tested
> that for the autotools upgrade).  Which parts of src can (could) be
> built in-tree and for which parts is that usually done?

I don't know about the other parts of src, but GDB always supported
in-tree builds, even though we advise in README to do it outside the
source tree:

    You can build GDB right in the source directory:

	  cd gdb-6.3
	  ./configure
	  make
	  cp gdb/gdb /usr/local/bin/gdb     (or wherever you want)

    However, we recommend that an empty directory be used instead.
    This way you do not clutter your source tree with binary files
    and will be able to create different builds with different
    configuration options.


  reply	other threads:[~2009-08-26 17:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090628183334.GA5401@gmx.de>
2009-07-28 18:54 ` Ralf Wildenhues
2009-07-28 19:51   ` Paolo Bonzini
2009-07-28 21:35   ` Tom Tromey
2009-07-29  3:09     ` Samuel Bronson
2009-07-29  5:31       ` Tom Tromey
2009-07-29 16:15       ` Ralf Wildenhues
2009-07-29 18:35         ` Samuel Bronson
2009-07-29 18:37         ` Tom Tromey
2009-07-30 21:27     ` Ralf Wildenhues
     [not found]     ` <20090730210952.GD24465__15749.4424529888$1248988226$gmane$org@gmx.de>
2009-07-30 21:30       ` Tom Tromey
2009-07-29 15:16   ` Ben Elliston
2009-08-26 16:29   ` Jan Kratochvil
2009-08-26 16:54     ` Ralf Wildenhues
2009-08-26 17:10       ` Jan Kratochvil
2009-08-26 17:51         ` Ralf Wildenhues
2009-08-26 17:57           ` Eli Zaretskii [this message]
2009-08-26 19:13           ` Jan Kratochvil
2009-08-31 20:42         ` obtaining configure args from config.status (was: Update rebuild rules in non-automake directories.) Ralf Wildenhues
2009-09-01  1:10           ` obtaining configure args from config.status Paolo Bonzini
2009-09-06 18:15           ` obtaining configure args from config.status (was: Update rebuild rules in non-automake directories.) Ralf Wildenhues
2009-09-08 18:37             ` obtaining configure args from config.status Tom Tromey
2009-09-08 16:28           ` Jan Kratochvil
2009-09-08 18:26             ` Ralf Wildenhues
2009-09-08 18:38               ` Tom Tromey
2009-09-08 18:51                 ` Ralf Wildenhues

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=83r5uycvh4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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