From: Andrew Haley <aph@redhat.com>
To: Mike Stump <mikestump@comcast.net>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: building binutils from same directory as gcc
Date: Wed, 02 Nov 2011 17:18:00 -0000 [thread overview]
Message-ID: <4EB17B28.8060704@redhat.com> (raw)
In-Reply-To: <C04B7ACC-CDA9-4DC1-A354-B9F7D5FEB178@comcast.net>
On 11/02/2011 05:11 PM, Mike Stump wrote:
> On Nov 2, 2011, at 2:42 AM, Andrew Haley wrote:
>> On 11/01/2011 04:51 PM, Mike Stump wrote:
>>> On Nov 1, 2011, at 4:27 AM, Andrew Haley wrote:
>>>> On 10/30/2011 01:51 PM, Gerald Pfeifer wrote:
>>>>> Why not just declare
>>>>> that building from the same directory is not support and have one
>>>>> simple set of instructions that always works, as opposed to "this
>>>>> ought to work with snapshots but not with direct checkouts"?
>>>>
>>>> That's right. Is there ever any advantage to building in-srcdir?
>>>
>>> Yes. You can do configure && make && make install.
>>
>> Huh?
>
> Ah, yes, yet another advantage, one can also do:
>
> ./configure && make && make install
Of course. That's what "building in-srcdir" means.
> :-) I do realize that you may not choose to value the feature, but
> that doesn't mean that everyone has the same valuation you have.
Sure, but that doesn't answer the question, which was "is there ever
any advantage to building in-srcdir?" The answer "Yes: one can build
in srcdir" doesn't quite do it!
Andrew.
next prev parent reply other threads:[~2011-11-02 17:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BANLkTikmsXKgUT43wCjR5+djON7TBZKT6A@mail.gmail.com>
[not found] ` <BANLkTinXXM_2739KS-GFZBvWSgXUT-_hwA@mail.gmail.com>
2011-05-02 13:07 ` building binutils from same directory as gcc (was: Re: xgcc does not find gcc-4.6.0-go/./binutils/ar (because it is gcc-4.6.0-go/./binutils/binutils/ar)) Steffen Dettmer
2011-10-30 15:04 ` building binutils from same directory as gcc Gerald Pfeifer
2011-11-01 11:53 ` Andrew Haley
2011-11-01 16:52 ` Mike Stump
2011-11-02 10:03 ` Andrew Haley
2011-11-02 17:18 ` Mike Stump
2011-11-02 17:18 ` Andrew Haley [this message]
2011-11-02 17:45 ` Mike Stump
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=4EB17B28.8060704@redhat.com \
--to=aph@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikestump@comcast.net \
/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).