Re: linker can't find getsubopt()
On Fri, Jan 31, 2003 at 08:47:15PM -, Max Bowsher wrote: >Christopher Faylor wrote: >> On Mon, Jan 20, 2003 at 08:59:35PM -, Max Bowsher wrote: >>> Christopher Faylor wrote: I don't think it is that simple. Cygwin doesn't use the getopt that comes with newlib. >>> >>> Ah. Just because I'm curious, why? >>> Is there supposed to be any correspondence between the getopt version and the getsubopt version? >>> >>> I've just looked at newlib's getsubopt.c. It is completely >>> independent of getopt, and in fact, has only been in newlib since >>> 1.11.0. >>> So, unless I've overlooked something, it *is* just a matter of >>> cygwin.din/version.h. >> >> Ok, then. Thanks for checking. Getting ready to gratefully accept a >> patch. > >Just got round to looking at doing this. It uses a variable in the library, >extern'ed in the application, like getopt's optarg - i.e. problem. > >Since I'm not directly interested in this function, I'm not going to take >this further. Just wanted the archives to have all the info. NP. Thanks for researching. 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/
Re: linker can't find getsubopt()
Christopher Faylor wrote: > On Mon, Jan 20, 2003 at 08:59:35PM -, Max Bowsher wrote: >> Christopher Faylor wrote: >>> I don't think it is that simple. Cygwin doesn't use the getopt that >>> comes with newlib. >> >> Ah. Just because I'm curious, why? >> >>> Is there supposed to be any correspondence between >>> the getopt version and the getsubopt version? >> >> I've just looked at newlib's getsubopt.c. It is completely >> independent of getopt, and in fact, has only been in newlib since >> 1.11.0. >> So, unless I've overlooked something, it *is* just a matter of >> cygwin.din/version.h. > > Ok, then. Thanks for checking. Getting ready to gratefully accept a > patch. Just got round to looking at doing this. It uses a variable in the library, extern'ed in the application, like getopt's optarg - i.e. problem. Since I'm not directly interested in this function, I'm not going to take this further. Just wanted the archives to have all the info. Max. -- 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/
Re: linker can't find getsubopt()
On Mon, Jan 20, 2003 at 08:59:35PM -, Max Bowsher wrote: >Christopher Faylor wrote: >> I don't think it is that simple. Cygwin doesn't use the getopt that >> comes with newlib. > >Ah. Just because I'm curious, why? > >> Is there supposed to be any correspondence between >> the getopt version and the getsubopt version? > >I've just looked at newlib's getsubopt.c. It is completely independent of >getopt, and in fact, has only been in newlib since 1.11.0. >So, unless I've overlooked something, it *is* just a matter of >cygwin.din/version.h. Ok, then. Thanks for checking. Getting ready to gratefully accept a patch. 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/
Re: linker can't find getsubopt()
Christopher Faylor wrote: > I don't think it is that simple. Cygwin doesn't use the getopt that > comes with newlib. Ah. Just because I'm curious, why? > Is there supposed to be any correspondence between > the getopt version and the getsubopt version? I've just looked at newlib's getsubopt.c. It is completely independent of getopt, and in fact, has only been in newlib since 1.11.0. So, unless I've overlooked something, it *is* just a matter of cygwin.din/version.h. Max. -- 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/
Re: linker can't find getsubopt()
On Sun, Jan 19, 2003 at 05:53:02PM -, Max Bowsher wrote: >Christopher Faylor wrote: >> On Sun, Jan 19, 2003 at 04:49:04PM -, Max Bowsher wrote: >>> It appears getsubopt is in newlib, and so present in Cygwin's >>> , but not exported from cygwin1.dll >>> >>> One of Cygwin's core developers will need to tell us whether this is >>> accidental or on purpose. > >--meanmeanmean >Content-Language: cgf_mean > >> Oh, it's on purpose. Believe me. Caused someone some discomfort? >> Then our evil plan is succeeding. Core developers! Raise your >> glasses and repeat after me "We are the core developers and we are >> MEAN!" >> >> It's a well know fact that we put functions in unistd.h which are not >> actually exported by cygwin just to tantalize and confuse people. >> What other earthly reason would we have for dangling this tempting >> fruit in front of people, if not to frustrate them? >> >> Bwahahaha. >--meanmeanmean > >Attempting translation: cgf_mean -> en_gb ... >Translation not possible! >Gist comprehended... > >Will you make the necessary adjustments to cygwin.din/version.h, or should I >submit a patch? I don't think it is that simple. Cygwin doesn't use the getopt that comes with newlib. Is there supposed to be any correspondence between the getopt version and the getsubopt version? Take a look at cygwin/winsup/lib/getopt.c . Uh, I mean. Why should I care? Suffer! 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/
Re: linker can't find getsubopt()
Christopher Faylor wrote: > On Sun, Jan 19, 2003 at 04:49:04PM -, Max Bowsher wrote: >> It appears getsubopt is in newlib, and so present in Cygwin's >> , but not exported from cygwin1.dll >> >> One of Cygwin's core developers will need to tell us whether this is >> accidental or on purpose. --meanmeanmean Content-Language: cgf_mean > Oh, it's on purpose. Believe me. Caused someone some discomfort? > Then our evil plan is succeeding. Core developers! Raise your > glasses and repeat after me "We are the core developers and we are > MEAN!" > > It's a well know fact that we put functions in unistd.h which are not > actually exported by cygwin just to tantalize and confuse people. > What other earthly reason would we have for dangling this tempting > fruit in front of people, if not to frustrate them? > > Bwahahaha. --meanmeanmean Attempting translation: cgf_mean -> en_gb ... Translation not possible! Gist comprehended... Will you make the necessary adjustments to cygwin.din/version.h, or should I submit a patch? Max. -- 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/
Re: linker can't find getsubopt()
At 09:32 2003-01-19, Christopher Faylor wrote: On Sun, Jan 19, 2003 at 04:49:04PM -, Max Bowsher wrote: >It appears getsubopt is in newlib, and so present in Cygwin's >, but not exported from cygwin1.dll > >One of Cygwin's core developers will need to tell us whether this is >accidental or on purpose. Oh, it's on purpose. Believe me. Caused someone some discomfort? Then our evil plan is succeeding. Core developers! Raise your glasses and repeat after me "We are the core developers and we are MEAN!" It's a well know fact that we put functions in unistd.h which are not actually exported by cygwin just to tantalize and confuse people. What other earthly reason would we have for dangling this tempting fruit in front of people, if not to frustrate them? Bwahahaha. cgf I'm on to you, Chaotica. Captain Proton -- 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/
Re: linker can't find getsubopt()
On Sun, Jan 19, 2003 at 04:49:04PM -, Max Bowsher wrote: >It appears getsubopt is in newlib, and so present in Cygwin's >, but not exported from cygwin1.dll > >One of Cygwin's core developers will need to tell us whether this is >accidental or on purpose. Oh, it's on purpose. Believe me. Caused someone some discomfort? Then our evil plan is succeeding. Core developers! Raise your glasses and repeat after me "We are the core developers and we are MEAN!" It's a well know fact that we put functions in unistd.h which are not actually exported by cygwin just to tantalize and confuse people. What other earthly reason would we have for dangling this tempting fruit in front of people, if not to frustrate them? Bwahahaha. cgf -- Please use the resources at cygwin.com rather than sending personal email. Special for spam email harvesters: send email to [EMAIL PROTECTED] and be permanently blocked from mailing lists at sources.redhat.com -- 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/
Re: linker can't find getsubopt()
It appears getsubopt is in newlib, and so present in Cygwin's , but not exported from cygwin1.dll One of Cygwin's core developers will need to tell us whether this is accidental or on purpose. Max. -- 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/
linker can't find getsubopt()
Hi,
I try to compile this simple program on cygwin:
#include
#include
#include
int main()
{
getsubopt(0,0,0);
return 0;
}
gcc has no problem with the program, but when linking starts, the linker can't find
a reference to getsubopt.
I don't care about the program working or not, I just want to make it compile, as it
will solve
several problems porting a Linux program to CYGWIN.
Any ideas?
Maor Avni
--
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/
