From: Matt Rice <ratmice@gmail.com>
To: Alan Modra <amodra@gmail.com>
Cc: Simon Marchi <simon.marchi@polymtl.ca>,
Simon Marchi <simon.marchi@ericsson.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Binutils <binutils@sourceware.org>
Subject: Re: Update autotools version for gdb and binutils
Date: Tue, 08 May 2018 20:39:00 -0000 [thread overview]
Message-ID: <CACTLOFod+Gu4SdOOaq35HhezVxhjCK2hb3x1eikQVQFeVWyzmw@mail.gmail.com> (raw)
In-Reply-To: <20180508023041.GV28782@bubble.grove.modra.org>
On Mon, May 7, 2018 at 7:30 PM, Alan Modra <amodra@gmail.com> wrote:
> *) The reason binutils-gdb and gcc share a top level dir, config, and
> most include files is to support combined tree builds. I don't know
> how many people try to do that nowadays, and a combined tree build
> with --enable-maintainer-mode running autotools seems a little
> insane to me.
While i haven't done this in a few years, but i used to do so in the
not terribly distant past,
using git read-tree/$GIT_DIR to check out binutils/gcc/newlib into one
working directory,
when building for multiple os * architecture combos shared code then
only had to be built once,
plus it allowed me to maintain patches directly in git.
next prev parent reply other threads:[~2018-05-08 20:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 18:44 [PATCH] gdb: Update autotools version used for gnulib import Simon Marchi
2018-05-04 19:34 ` Simon Marchi
2018-05-07 6:15 ` Alan Modra
2018-05-07 14:28 ` Simon Marchi
2018-05-08 2:30 ` Update autotools version for gdb and binutils Alan Modra
2018-05-08 20:39 ` Matt Rice [this message]
2018-05-08 22:12 ` Joseph Myers
2018-05-09 15:46 ` Simon Marchi
2018-05-10 14:40 ` Alan Modra
2018-06-15 0:49 ` Simon Marchi
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=CACTLOFod+Gu4SdOOaq35HhezVxhjCK2hb3x1eikQVQFeVWyzmw@mail.gmail.com \
--to=ratmice@gmail.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.com \
--cc=simon.marchi@polymtl.ca \
/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