This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: coreutils-6.11-1 in release-2 area
On Thu, May 22, 2008 at 10:28:32PM +0200, Corinna Vinschen wrote:
>On May 22 15:56, Christopher Faylor wrote:
>> On Thu, May 22, 2008 at 09:28:19PM +0200, Corinna Vinschen wrote:
>> >On May 22 13:56, Corinna Vinschen wrote:
>> >> While we're talking about coreutils, it would be a good idea to use the
>> >> latest Cygwin from CVS when testing coreutils further(*). cp baild out
>> >> on me because it used a NULL pathname in calls to futimesat, which I'd
>> >> consider a bug in coreutils, but the Linux man page gives away that this
>> >> is a GLIBC extension. I fixed that in CVS so futimesat can now do its
>> >> job (hopefully) correctly withe NULL pathname as well.
>> >> [...]
>> >> (*) I guess I have to upload yet another 1.7 version before I'm really
>> >> off on vacation...
>> >
>> >FYI, I've uploaded a 1.7.0-15 to release-2 which fixes this as well as a
>> >related internal error in Cygwin which was caused by getting an EFAULT
>> >due to the NULL pathname. It also contains your strchr patch and the
>> >setfacl changes discussed on the main list.
>>
>> It will also contain my removal of the strchr from cygwin's string.h
>> which should have the effect of causing cygwin to use gcc's built-in
>> version of strchr.
>
>Oh, surprise! I thought Cygwin would use Eric's version now.
It will export it but, in my testing, it won't use it. But that's no
different than any other program which uses strchr() and specifies the
right -O optimization level.
strchr() and strlen() are among a group of functions that gcc inlines
automatically when you compile a file with optimization.
cgf