unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: Guile 1.6.6 build comments ... solaris NSIG
Date: Thu, 02 Dec 2004 10:37:51 +1100	[thread overview]
Message-ID: <87y8gha8ts.fsf@zip.com.au> (raw)
In-Reply-To: <CMM.0.92.0.1101921856.beebe@psi.math.utah.edu> (Nelson H. F. Beebe's message of "Wed, 1 Dec 2004 10:24:16 -0700 (MST)")

"Nelson H. F. Beebe" <beebe@math.utah.edu> writes:
>
> ------------------------------------------------------------------------
> Machinetype:            Sun Ultra 2/2400 (400 MHz);     Solaris 2.9
> Configure environment:  CC=/opt/studio9/SUNWspro/bin/c89 \
> 			CFLAGS=-I/usr/local/include \
> 			CXX=/opt/studio9/SUNWspro/bin/CC \
> 			CXXFLAGS=-I/usr/local/include LDFLAGS="-R/usr/local/lib -L/usr/local/lib" 
>
>  /opt/studio9/SUNWspro/bin/c89 -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I./.. -I../libguile-ltdl -I/usr/local/include -c scmsigs.c  -KPIC -DPIC -o .libs/scmsigs.o
> "scmsigs.c", line 112: undefined symbol: NSIG
> "scmsigs.c", line 151: undefined symbol: sigset_t

I'd have thought that system would have both those.  Are they hiding
somewhere other than <signal.h>?


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  parent reply	other threads:[~2004-12-01 23:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-01 17:24 Guile 1.6.6 build comments Nelson H. F. Beebe
2004-12-01 23:18 ` Guile 1.6.6 build comments ... alpha ncurses Kevin Ryde
2004-12-01 23:23 ` Guile 1.6.6 build comments ... aix putenv Kevin Ryde
2004-12-01 23:37 ` Kevin Ryde [this message]
2004-12-02  0:04 ` Guile 1.6.6 build comments ... SGI vs execle Kevin Ryde
2004-12-02  0:11 ` Guile 1.6.6 build comments ... yellow dog powerpc Kevin Ryde

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y8gha8ts.fsf@zip.com.au \
    --to=user42@zip.com.au \
    --cc=guile-devel@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).