From: DJ Delorie <dj@redhat.com>
To: neroden@doctormoo.dyndns.org
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com,
binutils@sources.redhat.com
Subject: Re: [patch] toplevel configure.in: topsrcdir->srcdir
Date: Thu, 30 May 2002 17:49:00 -0000 [thread overview]
Message-ID: <200205310031.g4V0VQx26201@greed.delorie.com> (raw)
In-Reply-To: <20020530233738.GA18997@doctormoo.dyndns.org> (message from Nathanael Nerode on Thu, 30 May 2002 19:37:38 -0400)
> 'topsrcdir' always refers to the top level directory where 'configure'
> is located. When 'configure.in' in the top directory is being run,
> srcdir is normally the same directory. In a subdirectory, srcdir and
> topsrcdir differ, but not at the top level.
The case I'm worried about is a src=build cross. In that case,
configure builds a whole new source tree! So we must make sure that
it doesn't run the toplevel configure that it may copy to some other
directory, or if it does, that topsrcdir refers to the original
toplevel, not the newly copied one.
I don't think it should do this (it should only copy subdirectories)
but this is one of the cases that often goes unworking for long
periods.
next prev parent reply other threads:[~2002-05-31 0:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 11:11 Nathanael Nerode
2002-05-30 12:08 ` DJ Delorie
2002-05-30 17:31 ` Nathanael Nerode
2002-05-30 17:49 ` DJ Delorie [this message]
2002-06-19 16:57 ` DJ Delorie
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=200205310031.g4V0VQx26201@greed.delorie.com \
--to=dj@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=neroden@doctormoo.dyndns.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