From: RDBrown@mira.net
To: gdb@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: gdb March 2001 archive
Date: Tue, 27 Mar 2001 02:55:00 -0000 [thread overview]
Message-ID: <E14hrAI-00006p-00@urtur> (raw)
The gdb Mar 2001 archive hasn't moved past March 21 - is the mail getting
through or is it just the archive?
What do you want loaded on the testresults page?
gdb/testsuite/gdb.log or gdb/testsuite/gdb.sum?
Building from the 0324 snapshot on alpha-dec-osf4.0e and i586-sco-sysv5uw7.1.0
somewhat required the following patch - which should be done with autoconf.
Both provide NSIG but only if _XOPEN_SOURCE etc are undefined.
(Both using gcc-2.95.2)
On alpha-dec-osf4.0e the link failed missing `in_solib_dynsym_resolve_code'.
/usr/bin/ld:
Unresolved:
in_solib_dynsym_resolve_code
collect2: ld returned 1 exit status
--- expect/exp_trap.c.orig Tue Mar 27 00:17:00 2001
+++ expect/exp_trap.c Mon Mar 26 13:18:59 2001
@@ -22,6 +22,12 @@
#ifndef NSIG
#ifdef _NSIG
#define NSIG _NSIG
+#else
+#ifdef __osf__ /* alpha-dec-osf4.0e workaround */
+#define NSIG 49
+#else /* i586-sco-sysv5uw7.1.0 workaround */
+#define NSIG 35
+#endif
#endif
#endif
--- expect/exp_command.c.orig Tue Mar 27 00:17:15 2001
+++ expect/exp_command.c Mon Mar 26 13:18:50 2001
@@ -53,6 +53,12 @@
#ifndef NSIG
#ifdef _NSIG
#define NSIG _NSIG
+#else
+#ifdef __osf__ /* alpha-dec-osf4.0e workaround */
+#define NSIG 49
+#else /* i586-sco-sysv5uw7.1.0 workaround */
+#define NSIG 35
+#endif
#endif
#endif
next reply other threads:[~2001-03-27 2:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-27 2:55 RDBrown [this message]
2001-03-27 8:04 ` Kevin Buettner
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=E14hrAI-00006p-00@urtur \
--to=rdbrown@mira.net \
--cc=gdb-patches@sources.redhat.com \
--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