From: Jim Blandy <jimb@cygnus.com>
To: toddpw@wrs.com (Todd Whitesel)
Cc: gdb@cygnus.com
Subject: Re: 4.17.85 configure w/ relative path fails to build bfd/dwarf1.c
Date: Thu, 01 Apr 1999 00:00:00 -0000 [thread overview]
Message-ID: <npemmq4loe.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <199903122240.OAA18861@alabama.wrs.com>
> Mine (when I got the error) was basically equivalent, except that my build
> tree was not inside the source tree. My path to configure was
> ../toddpw/gdb-4.17.85/configure
I did my 4.17.86 Solaris and Linux builds in sibling trees, with no
ill effects.
next prev parent reply other threads:[~1999-04-01 0:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-01 0:00 Todd Whitesel
[not found] ` <199903160413.UAA13381.cygnus.gdb@alabama.wrs.com>
1999-04-01 0:00 ` Tom Tromey
1999-04-01 0:00 ` Todd Whitesel
1999-04-01 0:00 ` Jim Blandy
1999-04-01 0:00 ` Todd Whitesel
1999-04-01 0:00 ` Jim Blandy [this message]
1999-04-01 0:00 ` Stan Shebs
1999-04-01 0:00 ` Todd Whitesel
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=npemmq4loe.fsf@zwingli.cygnus.com \
--to=jimb@cygnus.com \
--cc=gdb@cygnus.com \
--cc=toddpw@wrs.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