From: Joel Brobecker <brobecker@adacore.com>
To: Klaus Zeitler <kzeitler@alcatel-lucent.com>
Cc: gdb-patches@sourceware.org
Subject: Re: CVS build for Solaris 5.8 fails: elfcore_write_prpsinfo undefined
Date: Sat, 01 Nov 2008 01:19:00 -0000 [thread overview]
Message-ID: <20081101011851.GA15606@adacore.com> (raw)
In-Reply-To: <q5gfxmd9b9d.fsf@sfsw51.de.lucent.com>
> Undefined first referenced
> symbol in file
> elfcore_write_prpsinfo libgdb.a(procfs.o)
> elfcore_write_prstatus libgdb.a(procfs.o)
> ld: fatal: Symbol referencing errors. No output written to gdb
I can reproduce. Looks like a problem in the bfd configure script,
as the following check returns "no":
AC_CHECK_HEADERS(sys/procfs.h)
Extract from the config.log file:
configure:19338: checking for sys/procfs.h
configure:19343: result: no
Not much information there. In any case, as a result, the checks
for the various types in procfs.h are skipped:
BFD_HAVE_SYS_PROCFS_TYPE(prstatus_t)
BFD_HAVE_SYS_PROCFS_TYPE(prstatus32_t)
[...]
BFD_HAVE_SYS_PROCFS_TYPE(prpsinfo_t)
[etc]
And so HAVE_PRPSINFO_T doesn't get defined as it should.
I have to run, now. I will look deeper into this hopefully tomorrow.
--
Joel
next prev parent reply other threads:[~2008-11-01 1:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 17:57 Klaus Zeitler
2008-11-01 1:19 ` Joel Brobecker [this message]
2008-11-01 22:18 ` Joel Brobecker
2008-11-01 23:31 ` Daniel Jacobowitz
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=20081101011851.GA15606@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=kzeitler@alcatel-lucent.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