From: Jie Zhang <jie@codesourcery.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Doug Evans <dje@google.com>
Subject: Re: Fix Makefile.in in data-directory
Date: Thu, 21 Oct 2010 02:15:00 -0000 [thread overview]
Message-ID: <4CBFA227.8050501@codesourcery.com> (raw)
In-Reply-To: <201010210128.53843.pedro@codesourcery.com>
On 10/21/2010 08:28 AM, Pedro Alves wrote:
> On Thursday 21 October 2010 01:17:42, Jie Zhang wrote:
>> On 10/21/2010 08:14 AM, Pedro Alves wrote:
>>> On Thursday 21 October 2010 01:10:14, Jie Zhang wrote:
>>>> I don't think this is an issue. I think in the last more than 10 years,
>>>> no one did "make -j all install" since the same instance in
>>>> gdb/Makefile.in has been there since it was created. Actually if you do
>>>> that in current gdb, it will not install gdb at all. I usually issue
>>>>
>>>> make -j4 all
>>>> make install
>>>
>>> FWIW, I got surprised before learning that "make -j4 install" misbehaves
>>> like that. I'd rather have it fixed. It just sounds like a buglet people
>>> got used to dealing with.
>>>
>> I didn't mean that "make -j4 install" misbehaves for gdb. It's "make -j4
>> all install" that misbehaves.
>
> Well, okay, it's the same difference.
>
> It's caused by the same problem. If you stop making "install" depend
> on "all install-only", but make it depend on "all" only, as Doug was
> saying, then "make -j4 all install" stops misbehaving, because "install"
> depends on "all", so "install" only proceeds after "all" is done.
>
I don't think it's really necessary to fix that. binutils and gcc also
don't allow "make -j4 install" to directly after "configure". "make -j4
all install" also fails for binutils and gcc. I think it's already an
convention that those software are built with
./configure
make
make install
Do we really need the effort to fix GDB?
--
Jie Zhang
CodeSourcery
next prev parent reply other threads:[~2010-10-21 2:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 12:09 Jie Zhang
2010-10-20 20:13 ` Doug Evans
2010-10-21 0:10 ` Jie Zhang
2010-10-21 0:14 ` Pedro Alves
2010-10-21 0:17 ` Jie Zhang
2010-10-21 0:29 ` Pedro Alves
2010-10-21 2:15 ` Jie Zhang [this message]
2010-10-21 2:30 ` Doug Evans
2010-10-21 5:11 ` Jie Zhang
2010-10-21 21:06 ` Doug Evans
2010-10-21 23:52 ` Jie Zhang
2010-10-21 10:07 ` Pedro Alves
2010-10-21 14:46 ` Joel Brobecker
2010-10-22 1:14 ` Tom Tromey
2010-10-21 21:08 ` Doug Evans
2010-10-22 1:11 ` Tom Tromey
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=4CBFA227.8050501@codesourcery.com \
--to=jie@codesourcery.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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