From: Greg Troxel <gdt@ir.bbn.com>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-devel@gnu.org
Subject: Re: complex support on solaris?
Date: Mon, 28 Jan 2008 20:19:37 -0500 [thread overview]
Message-ID: <rmi1w81o2c6.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <87myqsafhb.fsf@ossau.uklinux.net> (Neil Jerram's message of "Sat, 26 Jan 2008 13:22:40 +0000")
Neil Jerram <neil@ossau.uklinux.net> writes:
> Greg Troxel <gdt@ir.bbn.com> writes:
>
>> As pkgsrc maintainer of the guile package, I got a bug report about not
>> building on Solaris. The submitter doesn't have enough time for guile
>> any more, but the problem seems to be that Solaris's
>> /usr/include/complex.h expects the "compilation environment" to provide
>> _Complex_I.
>>
>> Adding this line to numbers.c allowed it to build:
>>
>> #define _Complex_I 1.0fi
>>
>> The full PR is at:
>>
>> http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=37556
>
> One initial question: what's the connection (or interaction) between
> Solaris and NetBSD?
Strictly speaking, none. pkgsrc is a multi-platform packaging system.
Originally it was just for NetBSD, but now supports quite a few
operating systems. pkgsrc lives administratively within the NetBSD
project (bug tracking, commit privs, means to assure that pkgsrc itself
is Free, etc.).
So my report really is about building guile on Solaris via pkgsrc, and
not about NetBSD. I have figured out a bit more since posting.
The real problem is that at least some versions of Solaris, when used
with gcc, provide complex.h but don't define all the required symbols.
I think the fix for guile is either
a) declare this broken and ignore it
b) change the configure test for HAVE_COMPLEX_H to instead try to
compile a program that includes complex.h and assigned _Complex_I to a
variable, thereby ignoring complex support on solaris.
prev parent reply other threads:[~2008-01-29 1:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 12:21 complex support on solaris? Greg Troxel
2008-01-26 13:22 ` Neil Jerram
2008-01-29 1:19 ` Greg Troxel [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
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=rmi1w81o2c6.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--cc=guile-devel@gnu.org \
--cc=neil@ossau.uklinux.net \
/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).