The following packages have been uploaded to the Cygwin distribution:
* libglib2.0_0-2.46.2-3
* libglib2.0-devel-2.46.2-3
* libglib2.0-doc-2.46.2-3
GLib is the low-level core library that forms the basis for projects
such as GTK+ and GNOME. It provides data structure handling for C,
portability
The following packages have been uploaded to the Cygwin distribution:
* shared-mime-info-1.6-3
* shared-mime-info-devel-1.6-3
This package contains the core database of common types and the
update-mime-database command used to extend it.
This release adds a perpetual postinstall script in place
The following packages have been uploaded to the Cygwin distribution:
* desktop-file-utils-0.22-2
desktop-file-utils contains a few command line utilities for working
with desktop entries.
This release adds a perpetual postinstall script in place of individual
postinstall commands in each pack
The following packages have been uploaded to the Cygwin distribution:
* xdg-utils-1.1.1-2
Xdg-utils is a set of command line tools that assist applications with a
variety of desktop integration tasks. About half of the tools focus on
tasks commonly required during the installation of a desktop
On 2016-03-12 13:14, sdbeni...@runbox.com wrote:
At first I thought it could be a bug with SDL, but to make sure, I created a
very simple reproduction
of the issue using only the iconv libraray, and a simple main() function. This
"test" fails
on every machine on which I have ran it, in both 32-
On 12.03.2016 14:29, Corinna Vinschen wrote:
I do now. Basically it's setvbuf screwing up the internal flags in the
FILE structure. I took the liberty to update newlib's setvbuf to the
OpenBSD version locally and I'm going to apply my patches to newlib
soon. I'll provide a new 2.5.0 test relea
On 12.03.2016 14:29, Corinna Vinschen wrote:
On Mar 12 20:39, Corinna Vinschen wrote:
On Mar 11 16:05, Kaz Kylheku wrote:
> We can reproduce the problem with just file streams using
> a much simpler program:
>
> #include
>
> int main(void)
> {
> FILE *out = fopen("file", "w+");
> setvbuf(ou
Hi Cygwin friends and users,
I released a new Cygwin TEST version 2.5.0-0.6.
Refresh with the following bugfixes:
- Fix bug in setvbuf resulting in overwriting data in line buffered IO
when writing after reading.
Addresses: https://cygwin.com/ml/cygwin/2016-03/msg00180.html
- Fix typo in c
On Mar 12 20:39, Corinna Vinschen wrote:
> On Mar 11 16:05, Kaz Kylheku wrote:
> > We can reproduce the problem with just file streams using
> > a much simpler program:
> >
> > #include
> >
> > int main(void)
> > {
> > FILE *out = fopen("file", "w+");
> > setvbuf(out, (char *) NULL, _IOLBF,
On Mar 11 22:38, darkdragon wrote:
> Some file paths were not correctly escaped. Fix attached
> ("ssh-copy-id.patch").
Thanks, since we're using the verbatim upstream OpenSSH sources,
I sent the patch upstream. Hopefully they apply it.
Corinna
--
Corinna Vinschen Please, sen
On Mar 11 16:05, Kaz Kylheku wrote:
> We can reproduce the problem with just file streams using
> a much simpler program:
>
> #include
>
> int main(void)
> {
> FILE *out = fopen("file", "w+");
> setvbuf(out, (char *) NULL, _IOLBF, 0);
> getc(out);
> clearerr(out);
> fseek(out, 0, SEEK_
Hello,
I'm writing because I'm encountering a strange bug in cygwin's distributed
x86_64-w64-mingw32 libraries. Specifically a problem with win-iconv.
-=System Info=-
OS(s): Windows 7 Professional, Windows 10 Professional Edition
Package(s): mingw64-{i686,x86_64}-win-iconv version: 0.0.6-2
Cygwin
On Mar 12 09:38, Kaz Kylheku wrote:
> On 11.03.2016 22:27, Marco Atzeri wrote:
> >On 12/03/2016 00:10, David Stacey wrote:
> >>On 11/03/16 14:23, Girish Joglekar wrote:
> >>>I have cleaned up the test example based on X-Windows/Motif which
> >>>crashes
> >>>on 64-bit cygwin cygwin/X but runs on the
On 11.03.2016 22:27, Marco Atzeri wrote:
On 12/03/2016 00:10, David Stacey wrote:
On 11/03/16 14:23, Girish Joglekar wrote:
I have cleaned up the test example based on X-Windows/Motif which
crashes
on 64-bit cygwin cygwin/X but runs on the 32-bit version. The only
warnings are of the type 'var
> Could be an accidental regression in my cygwin-specific patches betweenthe
> two versions. But I don't normally use or test on text-mounts, so
> I'll need confirmation that you are indeed experiencing the problem only
>
For what it's worth, I recently had the similar issues with Cygwin tar
on t
hey cygwin
http://buanajaya-alkesindo.com/havent.php?cross=c1d2853nhbm
Best Regards
zyskowski
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/m
16 matches
Mail list logo
