Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@ges.redhat.com>
To: law@redhat.com
Cc: tim@hollebeek.com,
	Nathanael Nerode <neroden@doctormoo.dyndns.org>,
	gcc@gcc.gnu.org, gdb@sources.redhat.com,
	binutils@sources.redhat.com
Subject: Re: Top Level Autoconfiscation Status
Date: Mon, 01 Jul 2002 09:21:00 -0000	[thread overview]
Message-ID: <3D20818E.1040706@ges.redhat.com> (raw)
In-Reply-To: <200207011603.g61G38421924@porcupine.slc.redhat.com>

> In message <20020630221237.A2110@hollebeek.com>, Tim Hollebeek writes:
>  >> * To avoid a lot of subtle problems, configure uses absolute pathnames
>  >> for most directories which it puts into the Makefile.  This means you
>  >> can no longer 'configure', relocate srcdir or builddir, and then 'make'.
>  >> I doubt that this is important.
> I do this regularly -- especially on machines where configure is slow
> (hpux, aix, solaris).

I believe that both BFD and READLINE (in src) are currently broken in 
this regard (DJE reported problems).  There was a somewhat underwelming 
response (see binutils) when it was suggested that developers should be 
responsible for ensuring that this obscure functionality continues to work.

>  >It could cause problems with mounted directories, which can have
>  >different names on different machines.  E.g. if I do a "make" in
>  >/usr/export/src/gcc and then try to do a "make install" in
>  >/net/src/gcc on a different machine.
> Also a real problem.

Andrew



  reply	other threads:[~2002-07-01 16:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-30 18:43 Nathanael Nerode
2002-06-30 19:43 ` Tim Hollebeek
2002-07-01  9:00   ` Jeff Law
2002-07-01  9:21     ` Andrew Cagney [this message]
2002-07-01 10:22       ` Jeff Law
2002-07-10 15:27         ` Andrew Cagney
2002-07-10 15:49           ` Doug Evans
2002-06-30 19:44 ` Daniel Jacobowitz
2002-06-30 21:19 ` Tom Tromey
2002-07-01  3:41 ` Andrea 'Fyre Wyzard' Bocci
2002-07-01  7:42 ` Ben Elliston

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=3D20818E.1040706@ges.redhat.com \
    --to=ac131313@ges.redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=law@redhat.com \
    --cc=neroden@doctormoo.dyndns.org \
    --cc=tim@hollebeek.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