This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: getopt_long behavior


On Thu, Jan 30, 2003 at 01:34:47AM -0000, Max Bowsher wrote:
>Christopher Faylor wrote:
>> On Wed, Jan 29, 2003 at 10:45:06PM -0000, Max Bowsher wrote:
>>> would you accept a patch making getopt respond to a
>>> "POSIXLY_INCORRECT_GETOPT" envvar?
>>
>> I'll make the change but it won't have the effect you think it will.
>> I guarantee it.  I will even make a snapshot and then you can watch
>> in horror and amazement as setting the environment variable has no
>> effect.
>>
>> And for an answer to the riddle of why this won't immediately do what
>> you want, try this in the winsup/cygwin directory:
>>
>>   grep -i getopt cygwin.din
>>
>> (Remember not to put the -i at the end!)
>
>Ah.  This suggests that the ideal fix would be to have alternate object
>files for getopt, such that programs which really can't cope with
>getopt's reordering can surpress it at link time - something along the
>lines of automode.o, textmode.o, etc.

No, it wouldn't suggest that at all.  Did you try the grep that I
suggested?  getopt isn't exported from cygwin1.dll.  It only lives in
libcygwin.a.

I don't know why the original designers of cygwin decided to do things
this way but it has been this way forever.

cgf

--
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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]