From: Harry Putnam <reader@newsguy.com>
To: gcc-help@gcc.gnu.org
Subject: Confused about build proceedure srcdir vs objdir
Date: Fri, 26 Oct 2001 22:30:00 -0000 [thread overview]
Message-ID: <m17kthlkjg.fsf@reader.newsguy.com> (raw)
Setup: Redhat Linux 7.1
controversial gcc-2.96-85 installed
from stock RH 7.1 rpm
I'm attempting to install from tar.gz source gcc-3.0.2
The configure instructions at http://gcc.gnu.org/install/configure.html
are just a little to jargon riddled for my inexperienced layman eyes.
>> First, we highly recommend that GCC be built into a separate directory
>> than the sources which does not reside within the source tree. This is
>> how we generally build GCC; building where srcdir == objdir should
>> still work, but doesn't get extensive testing; building where objdir
>> is a subdirectory of srcdir is unsupported.
I'm not sure what an `objdir' refers to or what under gcc-3.0.2 is
considered `srcdir'. Or how one knows when they are outside the
`tree'. I don't see the familiar `src' subdirectory.
I'm familiar with the common setup that works like this:
Toplevel/src (and a number of other subdirectories)
Where the build is done in Toplevel like the steps below.
All gnu software that I've built here-to-fore, and that would only
number in the teens, used a procedure like this:
tar xzvf gnu_packgage-1.tar.gz
cd gnu_package-1
./configure [options]
make [options]
make install
From the discussion in the cited web page above, I can't tell if they
are describing something radically different or what.
I followed the above outline. Is it wrong?
Can someone hand hold a bit here and show brief steps as in the above
build proceedure I described, using actual directory names for a
gcc-3.0.2.tar.gz (or other recent source file)?
My first attemp failed and I posted here the fail messages. No one
has yet responded. I have a hunch I'm building this differently than
the recommended proceedure so want to get that nailed down before
discussing any more errors.
PS-In my previous attempt the `make' process lasted a very long time.
I lost track of the exact amount but well over an hour.
Is that normal on a 400mhz pc?
next reply other threads:[~2001-10-26 22:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-26 22:30 Harry Putnam [this message]
2001-10-27 2:14 ` Florian Weimer
2001-10-27 15:10 ` Harry Putnam
2001-10-28 1:13 ` Florian Weimer
2001-10-28 7:25 ` Harry Putnam
2001-10-28 7:37 ` Florian Weimer
2001-10-28 8:05 ` Harry Putnam
2001-10-28 8:58 ` lange92
2001-10-28 8:07 ` John Levon
2001-10-29 9:25 ` Florian Weimer
2001-10-29 4:59 ` John Love-Jensen
2001-10-29 10:10 ` Harry Putnam
[not found] <3BDA7B75.119F779D@unitus.it>
2001-10-27 4:10 ` Harry Putnam
2001-10-27 8:08 Paolo Carlini
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=m17kthlkjg.fsf@reader.newsguy.com \
--to=reader@newsguy.com \
--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).