From: Klaus Zeitler <kzeitler@alcatel-lucent.com>
To: gdb-patches@sourceware.org
Subject: Re: gdb 6.8 build errors in Solaris 5.8
Date: Mon, 20 Oct 2008 11:57:00 -0000 [thread overview]
Message-ID: <q5gprlvlbt5.fsf@sfsw51.de.lucent.com> (raw)
In-Reply-To: <20081016124500.GD31057@caradoc.them.org> (Daniel Jacobowitz's message of "Thu\, 16 Oct 2008 08\:45\:00 -0400")
>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
Daniel>
Daniel> On Thu, Oct 16, 2008 at 02:19:16PM +0200, Klaus Zeitler wrote:
>> Are these known problems or should I file a bug report?
Daniel>
Daniel> You may want to check a CVS snapshot. I think they're both fixed.
Did that and yes you're right, both problems are gone.
I could verify that for remote.c, but the file gstdint.h doesn't exist
anymore (I assume that got solved in some other way).
Unfortunately I ran into new build problems with the CVS snapshot:
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'
Maybe somebody can give me a hint for this.
Klaus
--
--------------------------------------------------
| Klaus Zeitler Alcatel-Lucent |
| Email: kzeitler@alcatel-lucent.com |
--------------------------------------------------
---
Meeting, n.:
An assembly of people coming together to decide what person or
department not represented in the room must solve a problem.
prev parent reply other threads:[~2008-10-20 11:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 12:20 Klaus Zeitler
2008-10-16 12:45 ` Daniel Jacobowitz
2008-10-20 11:57 ` Klaus Zeitler [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=q5gprlvlbt5.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