From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Olumide <50295@web.de>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Compiling gcc-4.1.2 on 64-bit Ubuntu machines
Date: Tue, 25 Jan 2011 10:59:00 -0000 [thread overview]
Message-ID: <AANLkTimfDsA5w7R_YgHb7ZrRsLr7KwDhNLYX-Jo8P=6U@mail.gmail.com> (raw)
In-Reply-To: <4D3EA686.4090806@web.de>
On 25 January 2011 10:31, Olumide wrote:
>
> I would like to roll out the build to other machines (several dozen
> actually). I've tried copying the entire hierarchy (source and build) to the
> target machines and then running make install but I'm getting the error
> message (I'd appreciate help solving this problem -- thanks):
The problem is that "make install" checks if it needs to rebuild, and
notices that system headers and other things have changed.
Don't do it that way, instead use "DESTDIR"
http://www.gnu.org/prep/standards/html_node/DESTDIR.html
This allows you to copy the entire installed tree (not the source and
build trees) to a temporary staging area, from where it can be
packaged up into an archive, then extracted on the destination
machines.
next prev parent reply other threads:[~2011-01-25 10:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 14:48 Olumide
2011-01-19 15:01 ` Cedric Roux
2011-01-19 15:51 ` Olumide
2011-01-19 16:21 ` Ian Lance Taylor
2011-01-19 16:37 ` Olumide
2011-01-19 16:39 ` Andrew Haley
2011-01-19 17:08 ` Olumide
2011-01-19 17:11 ` Andrew Haley
2011-01-19 20:13 ` Olumide
2011-01-19 21:51 ` David Daney
2011-01-20 13:56 ` Olumide
2011-01-20 17:23 ` Olumide
2011-01-20 20:04 ` Jonathan Wakely
2011-01-25 10:30 ` Olumide
2011-01-25 10:59 ` Kai Ruottu
2011-01-25 10:59 ` Jonathan Wakely [this message]
2011-01-25 11:34 ` Olumide
2011-01-25 11:56 ` Jonathan Wakely
2011-01-25 13:51 ` Olumide
2011-01-19 16:43 ` Cedric Roux
2011-01-19 16:47 ` Jonathan Wakely
2011-01-19 15:19 ` Jeff Law
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='AANLkTimfDsA5w7R_YgHb7ZrRsLr7KwDhNLYX-Jo8P=6U@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=50295@web.de \
--cc=gcc-help@gcc.gnu.org \
/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).