public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: syseng@gfsys.co.uk
To: insight-gnats@sources.redhat.com
Subject: insight/360: Build under solaris 10 sparc
Date: Fri, 04 Mar 2011 15:53:00 -0000 [thread overview]
Message-ID: <20110304154426.7003.qmail@sourceware.org> (raw)
>Number: 360
>Category: insight
>Synopsis: Build under solaris 10 sparc
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Mar 04 15:53:01 UTC 2011
>Closed-Date:
>Last-Modified:
>Originator: Chris Quayle
>Release: 6.8-1
>Organization:
>Environment:
Solaris 10 Sparc
>Description:
Perhaps more of a report, rather than a serous bug...
Building insight 6.8-1, with gmake, gcc, etc, Get several warnings about a #pragma ident, which are ignored and the build continues, until we get to:
In file included from /usr/local/src/Insight-6.8.1/insight-6.8-1/tk/generic/tk.h:96,
from /usr/local/src/Insight-6.8.1/insight-6.8-1/itcl/itk/generic/itk.h:61,
from .././gdb/gdbtk/generic/gdbtk.c:46:
/usr/openwin/include/X11/Xlib.h:39: warning: ignoring #pragma ident
gmake[2]: *** [gdbtk.o] Error 1
gmake[1]: *** [all-gdb] Error 2
gmake: *** [all] Error 2
gmake[2]: Leaving directory `/usr/local/src/Insight-6.8.1/insight-6.8-1/gdb'
gmake[1]: Leaving directory `/usr/local/src/Insight-6.8.1/insight-6.8-1'
which is just like the earlier #pragma ident warnings, but the build halts. Tracked down to a line in /usr/openwin/X11/Xlib.h:
#pragma ident "@(#)Xlib.h 1.12 04/07/14 SMI".
Temporarily commented out, the build completes fine and insight installs without a problem. I wonder if there is a more tidy solution ?. Since the earlier similar warnings didn't halt the build, it looks like a configure / makefile issue, but I don't have enough osf makefile knowledge to attempt a more tidy fix.
Other than that, everything looks good and many thanks to all those who have worked hard on this project. Still need 6.1 for angel support, but this version will be used to talk to openocd via the local network...
Regards,
Chris
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
reply other threads:[~2011-03-04 15:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20110304154426.7003.qmail@sourceware.org \
--to=syseng@gfsys.co.uk \
--cc=insight-gnats@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).