From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: dev@keyslapper.net
Cc: gdb@sources.redhat.com
Subject: Re: gdb 6.3 build fails on Solaris
Date: Sun, 15 May 2005 21:58:00 -0000 [thread overview]
Message-ID: <200505152158.j4FLwYhY001085@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20050513201001.GE42535@keyslapper.net> (message from Louis LeBlanc on Fri, 13 May 2005 16:10:01 -0400)
Date: Fri, 13 May 2005 16:10:01 -0400
From: Louis LeBlanc <dev@keyslapper.net>
Hey folks. I'm new on this particular list, but I have tried
searching the archives (and Google) for any solution to my problem.
I've tried building gdb 6.3 on several versions of Solaris, both Intel
and Sparc architectures, and have yet to see it build completely.
Uh yeah, gdb 6.3 was a bit goofed on SPARC.
On Solaris 8 Sparc, the failure is as follows:
. . .
gcc -c -g -O2 -I. -I../../gdb -I../../gdb/config -DLOCALEDIR="\"/usr/local/share/locale\"" -DHAVE_CONFIG_H -I../../gdb/../include/opcode -I../../gdb/../readline/.. -I../bfd -I../../gdb/../bfd -I../../gdb/../include -I../intl -I../../gdb/../intl -DMI_OUT=1 -DTUI=1 -Wimplicit -Wreturn-type -Wcomment -Wtrigraphs -Wformat -Wparentheses -Wpointer-arith -Wuninitialized -Wformat-nonliteral -Wunused-label -Wunused-function ../../gdb/procfs.c
In file included from ../../gdb/procfs.c:37:
/usr/include/sys/procfs.h:153: error: parse error before "taskid_t"
/usr/include/sys/procfs.h:157: error: parse error before '}' token
/usr/include/sys/procfs.h:269: error: parse error before "taskid_t"
/usr/include/sys/procfs.h:271: error: conflicting types for `pr_filler'
/usr/include/sys/procfs.h:155: error: previous declaration of `pr_filler'
/usr/include/sys/procfs.h:272: error: conflicting types for `pr_lwp'
/usr/include/sys/procfs.h:156: error: previous declaration of `pr_lwp'
/usr/include/sys/procfs.h:273: error: parse error before '}' token
../../gdb/procfs.c:329: error: parse error before "gdb_prstatus_t"
../../gdb/procfs.c:329: warning: type defaults to `int' in declaration of `gdb_prstatus_t'
../../gdb/procfs.c:329: warning: data definition has no type or storage class
I've never seen this failure. I've been building gdb on SPARC Solaris
2.6, 7 and 9 from time to time and I can't remember ever seeing this
particular failure. Could you try building a recent gdb snapshot on
your system. See http://sourceware.org/gdb on how to obtain a
snapshot.
It's slightly different on Solaris 10 Intel:
. . .
gcc -c -g -O2 -I. -I../../gdb -I../../gdb/config -DLOCALEDIR="\"/usr/local/share/locale\"" -DHAVE_CONFIG_H -I../../gdb/../include/opcode -I../../gdb/../readline/.. -I../bfd -I../../gdb/../bfd -I../../gdb/../include -I../intl -I../../gdb/../intl -DMI_OUT=1 -DTUI=1 -Wimplicit -Wreturn-type -Wcomment -Wtrigraphs -Wformat -Wparentheses -Wpointer-arith -Wuninitialized -Wformat-nonliteral -Wunused-label -Wunused-function ../../gdb/tui/tui.c
In file included from ../../gdb/tui/tui.c:48:
/usr/include/term.h:1060: error: parse error before "SGTTY"
/usr/include/term.h:1120: error: parse error before '}' token
Ah, this defenitely has been fixed a while ago.
Mark
next prev parent reply other threads:[~2005-05-15 21:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 20:10 Louis LeBlanc
2005-05-15 21:58 ` Mark Kettenis [this message]
2005-05-16 21:55 ` Louis LeBlanc
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=200505152158.j4FLwYhY001085@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=dev@keyslapper.net \
--cc=gdb@sources.redhat.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