From: toddpw@wrs.com (Todd Whitesel)
To: gdb@cygnus.com
Subject: 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: <199903110415.UAA13737@alabama.wrs.com> (raw)
Tried to build 4.17.85 for my sparc (solaris 2.5.1) tonight and found that
if one configures using a path to configure, like ../blah/blah/configure or
/blah/blah/configure then:
- GDB does not build bfd/dwarf1.c, but attempts to archive it in
libbfd, and fails.
- dejagnu-19990209 gets the following error during 'make install':
/usr/local/gnu/bin/install -c -m 644 ../../../toddpw/dejagnu-19990209/dejagnu/baseboards/arm-ice.exp /net/alabama/alabama2/gdb41785/share/dejagnu/baseboards/../../../toddpw/dejagnu-19990209/dejagnu/baseboards/arm-ice.exp
/usr/local/gnu/bin/install: /net/alabama/alabama2/gdb41785/share/dejagnu/baseboards/../../../toddpw/dejagnu-19990209/dejagnu/baseboards/arm-ice.exp: No such file or directory
*** Error code 1
Sorry to not include patches but I am not much of a configure wizard yet.
If more info than this is needed to fix the problem, let me know.
I usually keep read-only copies of GNU tarballs on my machine for reference,
and do all builds in 'sandbox' directories. I am running 'make check' on the
results of a build/install from writable copies of the source, and will send
that in when I get back in tomorrow. G'night.
--
Todd Whitesel
toddpw @ wrs.com
next 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 [this message]
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
[not found] ` <199903160413.UAA13381.cygnus.gdb@alabama.wrs.com>
1999-04-01 0:00 ` Tom Tromey
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=199903110415.UAA13737@alabama.wrs.com \
--to=toddpw@wrs.com \
--cc=gdb@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