From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Doug Evans <dje@google.com>,
Jie Zhang <jie@codesourcery.com>
Subject: Re: Fix Makefile.in in data-directory
Date: Thu, 21 Oct 2010 14:46:00 -0000 [thread overview]
Message-ID: <20101021144556.GA2797@adacore.com> (raw)
In-Reply-To: <201010211107.42726.pedro@codesourcery.com>
> ># Traditionally "install" depends on "all". But it may be useful
> ># not to; for example, if the user has made some trivial change to a
> ># source file and doesn't care about rebuilding or just wants to save the
> ># time it takes for make to check that all is up to date.
> ># install-only is intended to address that need.
> >install: all install-only
>
> (enphasis on the comment.) Maybe it's the 'Traditionally "install" depends
> on "all".' part that's not so traditional afterall? I really don't know.
>
> (most users are better taught separate "make" and "make install" steps,
> because it's most often necessary to need extra previleges
> and "sudo make install" to install to /usr/local, but not to "make".)
AFAIK, the FSF recommends against making "make install" also do the build.
--
Joel
next prev parent reply other threads:[~2010-10-21 14:46 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
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 [this message]
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=20101021144556.GA2797@adacore.com \
--to=brobecker@adacore.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=jie@codesourcery.com \
--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