From: toddpw@wrs.com (Todd Whitesel)
To: jimb@cygnus.com (Jim Blandy)
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: <199903122240.OAA18861@alabama.wrs.com> (raw)
In-Reply-To: <np3e3a3kvz.fsf@zwingli.cygnus.com>
> This is mysterious to me; I always build using a path to configure,
> just as you said. Here's the config.status from my Solaris 2.5.1
> tests:
>
> #!/bin/sh
> # This file was generated automatically by configure. Do not edit.
> # This directory was configured as follows:
> ../../configure --host=sparc-sun-solaris2.5.1 --prefix=/stone/jimb/gdb-4.18 --norecursion
> # using "mh-frag"
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
> What is dejagnu doing in there? That's not a part of the GDB
> distribution.
I got it from gdb/private so I could try 'make check'. In the past I have
downloaded GDB+dejagnu from gdb/private but I have never been able to get
'make check' to totally succeed. With straight 4.17 I think only the solaris
thread tests failed though.
> > If more info than this is needed to fix the problem, let me know.
>
> I think so.
Looks like it, although I have a sinking feeling that it is some deficiency
in the sh/sed/grep/find/etc. binaries I have in my path, which is something
that only I can track down, and I don't know when I can get around to that.
I could always re-do the bad configure and send someone the tarball, but
the efficiency of that is questionable and there's no guarantee it will
yield results.
--
Todd Whitesel
toddpw @ wrs.com
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 ` Stan Shebs
1999-04-01 0:00 ` Todd Whitesel
1999-04-01 0:00 ` Todd Whitesel
1999-04-01 0:00 ` Jim Blandy
1999-04-01 0:00 ` Todd Whitesel [this message]
1999-04-01 0:00 ` Jim Blandy
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=199903122240.OAA18861@alabama.wrs.com \
--to=toddpw@wrs.com \
--cc=gdb@cygnus.com \
--cc=jimb@cygnus.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