Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID: <08e401c221c2$77201b00$6132bc3e@BABEL>
From: "Conrad Scott" <Conrad DOT Scott AT dsl DOT pipex DOT com>
To: <cygwin AT cygwin DOT com>
References: <20020702013043 DOT GC14478 AT redhat DOT com> <LLEGJLFMJCCMMIIJBIKDOEDLCNAA DOT pri AT ddf DOT dk> <20020702104458 DOT G23555 AT cygbert DOT vinschen DOT de> <089101c221ba$e5a1e020$6132bc3e AT BABEL> <20020702133513 DOT D21857 AT cygbert DOT vinschen DOT de>
Subject: Re: C99 macros in math.h
Date: Tue, 2 Jul 2002 13:17:42 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

"Corinna Vinschen" <corinna-cygwin AT cygwin DOT com> wrote:
> It would help a lot if you could prefilter your list.  It's not
really
> thrilling to get a long list of symbols with the hint "here's the
list,
> I left the work for you".
>
> If you want some of these symbols to get exported, compare them e.
g. to
> SUSv3 and report back.

Sorry Corinna, I know it was a bit of an imposition just to dump the
list on you but as I said, I assume that some of these might not be
appropriate to export from the cygwin DLL and I'm not qualified to
spot which ones.  But I accept I could still have filtered the list
somewhat (e.g. I assume the DLL shouldn't export `errno'). Sorry.

I didn't mention it in my original email, but the problem is that the
header files for all these symbols go out with the cygwin
installation. Thus you then get the same problem that existed with the
cygserver / shm merge into HEAD: the header files exist but the entry
points don't. Thus any configuration script that notices the header
files will almost certainly get into problems (e.g. throwing up an
"entry point not found" dialogue either at configuration time or at
run time).

Thus as I understand it, it's not an issue of SUSv3 or whatever
compliance but one of the DLL being consistent with the header files.
On that basis, everything on the list I sent you should be exported
except those things that would cause a problem (e.g. `errno' AFAIK;
but are there any more like that?).

// Conrad




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/