Re: Where is 'getconf' utility?
On 12/24/2010 03:55 PM, Oleksandr Gavenko wrote: > I can not found 'getconf' utility in Cygwin. That's correct. Would you like to help by volunteering to port it? > > I don't know if utility mention in POSIX it must be implemented > in POSIX compliance env. Yes, POSIX requires getconf(1) to exist. Cygwin isn't (quite) POSIX compliant, yet. -- Eric Blake ebl...@redhat.com+1-801-349-2682 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature
Where is 'getconf' utility?
I can not found 'getconf' utility in Cygwin. http://cygwin.com/cgi-bin2/package-grep.cgi?grep=getconf I search that same reported in 2003 and found some article where people have portability issue because utility is missing, like: http://software.intel.com/en-us/blogs/2008/03/05/hacking-threading-building-blocks-into-cygwin-part-2/ 'getconf' utility present in POSIX 2003/2008. I don't know if utility mention in POSIX it must be implemented in POSIX compliance env. Also as state cygwin-ug-net-nochunks.html: Early on in the development process, we made the important design decision that it would not be necessary to strictly adhere to existing UNIX standards like POSIX.1 if it was not possible or if it would significantly diminish the usability of the tools on the Win32 platform. As I understand if it will be exist it must included in 'cygwin' package because this package provide: /usr/include/limits.h ... /usr/lib/libc.a ... etc. and I see 'libc6' for Debian also contain /usr/bin/getconf. In web I found many realisation of this utility (ever with BSD licence from NetBSD). They so simple that I think that no any portability issue occurred. Does it must be included in Cygwin and make it more POSIX compliance? -- Best regards! -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
program_invocation_name
Porting of some programs originally written for glibc over to cygwin
would be easier if cygwin could provide the global variables char*
program_invocation_{short_,}name, set automatically to match argv[0] of
main(), and declared in when strict standards compliance isn't
requested. Is it worth my time to go ahead and submit a patch to add
this? Or is our party line still that as long as you are using
non-portable means, you should just continue to use
readlink("/proc/self/exe") when porting to cygwin?
--
Eric Blake ebl...@redhat.com+1-801-349-2682
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
Re: tar fails to expand simple tar.gz across junction point
On 2:59 PM, Steven Hartland wrote: We're seeing some strange behaviour with tar under cygwin when its start point is a disk mounted under a directory. [snip] uname -a CYGWIN_NT-6.1-WOW64 blade33 1.7.0(0.212/5/3) 2009-09-11 01:25 i686 Cygwin Steven: have U tried a later version? your version of Cygwin seems kind of old; *my* system is old, and i get CYGWIN_NT-6.1-WOW64 freesoft007 1.7.1(0.218/5/3) 2009-12-07 11:48 i686 Cygwin -tanstaafl -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
