From: toddpw@wrs.com (Todd Whitesel)
To: shebs@cygnus.com (Stan Shebs)
Cc: toddpw@wrs.com, 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: <199903112206.OAA00209@alabama.wrs.com> (raw)
In-Reply-To: <199903112057.MAA03679@andros.cygnus.com>
> - GDB does not build bfd/dwarf1.c, but attempts to archive it in
> libbfd, and fails.
>
> Are you sure this is a clean set of sources? The dwarf1 need comes from
Generally I download the tarball from private/gdb, extract it into a
directory (/alabama2/toddpw/gdb-4.17.85 in this case) and chmod -R -w it.
Perhaps the read-only-ness has something to do with it?
I also tend not to have GNU stuff early in my path, so if some recent
change depends on updated, sane tool binaries, perhaps the fault lies
there.
Unfortunately I don't have a lot of time to diagnose this right now.
I'm getting lots of failures from 'make check' too, and when I ran
make check again (because I forgot to tee the output the first time)
it hung...
toddpw 28308 28305 99 12:12:36 pts/7 111:46 /alabama2/sandbox/gdb/testsuite/gdb.hp/more-steps
--
Todd Whitesel
toddpw @ wrs.com
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
1999-04-01 0:00 ` Stan Shebs
1999-04-01 0:00 ` Todd Whitesel [this message]
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=199903112206.OAA00209@alabama.wrs.com \
--to=toddpw@wrs.com \
--cc=gdb@cygnus.com \
--cc=shebs@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