This is the mail archive of the
cygwin-developers@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: glob_t, glob(), glob.h or similar : where in B20.1 ? (revisiting an issue)
- To: Mumit Khan <khan@xraylith.wisc.edu>
- Subject: Re: glob_t, glob(), glob.h or similar : where in B20.1 ? (revisiting an issue)
- From: Christopher Faylor <cgf@cygnus.com>
- Date: Wed, 11 Aug 1999 20:04:22 -0400
- Cc: cygwin-developers@sourceware.cygnus.com
- References: <19990223220606.B23568@cygnus.com> <Pine.SUN.3.93.990224023035.5761F-100000@modi.xraylith.wisc.edu>
I'm cleaning out my mailbox and came across this.
Does anyone have any opinions on exporting glob from the DLL?
-chris
On Wed, Feb 24, 1999 at 02:36:28AM -0600, Mumit Khan wrote:
>On Tue, 23 Feb 1999, Christopher Faylor wrote:
>> I think this was a recent change wasn't it? glob is actually used by
>> cygwin1.dll. I think it actually used to be in libcygwin.a, but I could
>> be wrong.
>
>b19 didn't export glob export either. I never noticed it simply because
>my configure scripts substitute my glob if system runtime doesn't provide
>it.
>
>> All it should need is for glob.h to be moved to include and for glob to
>> be added to cygwin.din, right?
>
>That's all there is to it.
>
>> I have no problems with exporting this. As far as I can tell, this
>> is actually a bug.
>
>I'm not sure I'll call it bug. Unless of course it really did become
>part of POSIX.2 (I haven't checked if .2 has been approved yet). I
>don't have my copy of Susv2 here, but I believe it's required there
>as well.