From: <lange92@2067.resnet.uni.edu>
To: Harry Putnam <reader@newsguy.com>
Cc: <gcc-help@gcc.gnu.org>
Subject: Re: Confused about build proceedure srcdir vs objdir
Date: Sun, 28 Oct 2001 08:58:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0110280456400.9985-100000@2067.resnet.uni.edu> (raw)
In-Reply-To: <m1bsirwy8n.fsf@reader.newsguy.com>
On Sun, 28 Oct 2001, Harry Putnam wrote:
> Florian Weimer <fw@deneb.enyo.de> writes:
>
> > Harry Putnam <reader@newsguy.com> writes:
> >
> >> We use srcdir to refer to the toplevel directory of GCC package.
> >> (Top level of unpacked GCC.tar.gz)
> >>
> >> We use `builddir' to refer to a user created sub-directory under
> >> the top level directory of GCC package. We recommend running the
> >> compile from `builddir'.
> >
> > Certainly not! objdir/builddir may not be a directory under srcdir,
> > otherwise the build process will fail in very obscure ways. (Yes,
> > I've made this mistake before.)
>
> Yikes, I meant the other way round? In the configure.html it
> appears as if srcdir is a subdirectory of objdir:
>
> To configure GCC:
> % mkdir objdir
> % cd objdir
> % srcdir/configure [options] [target]
>
> If one were to cd into objdir and call: `srcdir/configure' then srcdir
> would need to be a subdir of objdir. Is this correct?
No. you can (and probably should) specify scrdir with an absolute path
(one that starts with a /) So the srcdir actually has no relation
to where the objdir is, and vice versa.
next prev parent reply other threads:[~2001-10-28 8:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-26 22:30 Harry Putnam
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 [this message]
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=Pine.LNX.4.33.0110280456400.9985-100000@2067.resnet.uni.edu \
--to=lange92@2067.resnet.uni.edu \
--cc=gcc-help@gcc.gnu.org \
--cc=reader@newsguy.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).