From: Klaus Zeitler <kzeitler@alcatel-lucent.com>
To: gdb-patches@sourceware.org
Subject: CVS build for Solaris 5.8 fails: elfcore_write_prpsinfo undefined
Date: Fri, 31 Oct 2008 17:57:00 -0000 [thread overview]
Message-ID: <q5gfxmd9b9d.fsf@sfsw51.de.lucent.com> (raw)
The CVS version of gdb gives the following error for a Solaris 5.8 build:
gcc -g -O2 \
-o gdb gdb.o libgdb.a \
../readline/libreadline.a ../opcodes/libopcodes.a ../bfd/libbfd.a -lintl ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a -ldl -lncurses -lz -lsocket -lnsl -lm ../libiberty/libiberty.a gnulib/libgnu.a
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
collect2: ld returned 1 exit status
make[2]: *** [gdb] Error 1
make[2]: Leaving directory `/vol/freeware/SunOS-5.8/build/gdb-cvs/gdb'
make[1]: *** [all-gdb] Error 2
make[1]: Leaving directory `/vol/freeware/SunOS-5.8/build/gdb-cvs'
make: *** [all] Error 2
ERROR: gdb: make
I noticed that these 2 functions are defined in elf.c.
They are enclosed there with:
#if defined (HAVE_PRPSINFO_T) || defined (HAVE_PSINFO_T)
but the function calls in procfs.c are not.
I'm not sure if any of the 2 defines HAVE_PRPSINFO_T or HAVE_PSINFO_T
should be set for Solaris 5.8 (I guess I'd have to understand the code
in the configure script), but I think that the calls in procfs.c
need the same #ifs as in elf.c.
I enclosed the 2 function calls in procfs.c also with
#if defined (HAVE_PRPSINFO_T) || defined (HAVE_PSINFO_T)
and was able to build (and run) gdb.
Klaus
--
-----------------------------------------------------
| Klaus Zeitler Between a rock and a hard place |
| Email: kzeitler@alcatel-lucent.com |
-----------------------------------------------------
---
If you think nobody cares if you're alive, try missing
a couple of car payments. -- Earl Wilson
next reply other threads:[~2008-10-31 13:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 17:57 Klaus Zeitler [this message]
2008-11-01 1:19 ` Joel Brobecker
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=q5gfxmd9b9d.fsf@sfsw51.de.lucent.com \
--to=kzeitler@alcatel-lucent.com \
--cc=gdb-patches@sourceware.org \
/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