Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Subject: configure and asinl function problem
From: Joost Kraaijeveld <J DOT Kraaijeveld AT Askesis DOT nl>
To: Cygwin <cygwin AT cygwin DOT com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Sat, 08 Oct 2005 12:09:56 +0200
Message-Id: <1128766196.20665.124.camel@Panoramix>
Mime-Version: 1.0
X-IsSubscribed: yes

Hi,

I am trying to compile MICO, a CRBA implementation. It uses configure
for it's configuration.

Using "AC_CHECK_FUNCS(infnanl isnanl isinfl asinl ldexpl frexpl fabsl
floorl ceill):" in configure.in results in  "#define HAVE_ASINL 1" in
config.h

This appears however to be not true: during the actual compilation the
compiler complains when encountering the function. There is actually no
header that defines the function, so the compiler is right ;-).

According to a mail I found on internet
(http://www.mico.org/pipermail/mico-devel/2005-March/009248.html) this
happens because configure does not uses a compiler header but creates
its own function prototype and the function is included in the libraries
(as far as I can see it appears to be in libstdc++.a) 

1. Is the diagnose of the problem correct (I have looked into the macros
but I have to admit that I do not understand what they do) ?
2. If so, is there a solution for this problem?
3. If stdc++ contains asinl, is there a reason why it is not used?

TIA


-- 
Groeten,

Joost Kraaijeveld
Askesis B.V.
Molukkenstraat 14
6524NB Nijmegen
tel: 024-3888063 / 06-51855277
fax: 024-3608416
e-mail: J DOT Kraaijeveld AT Askesis DOT nl
web: www.askesis.nl 



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/