[ANNOUNCEMENT] mesa 11.2.1-1

[Yaakov Selkowitz]

The following packages have been uploaded to the Cygwin distribution:

* mesa-11.2.1-1
* dri-drivers-11.2.1-1
* libglapi0-11.2.1-1
* libGL1-11.2.1-1
* libGL-devel-11.2.1-1
* libOSMesa8-11.2.1-1
* libOSMesa-devel-11.2.1-1
* libEGL1-11.2.1-1
* libEGL-devel-11.2.1-1
* libGLESv2_2-11.2.1-1
* libGLESv2-devel-11.2.1-1
* windowsdriproto-11.2.1-1

Mesa is an open-source implementation of the OpenGL, OpenGL ES, and EGL
specifications for rendering interactive 3D graphics.

Complete documentation on OpenGL usage and configuration can be found here:

http://x.cygwin.com/docs/ug/using-glx.html

This is an update to the latest upstream release:

http://mesa3d.org/relnotes/11.2.0.html
http://mesa3d.org/relnotes/11.2.1.html

--
Yaakov

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

mesa 11.2.1-1

[Yaakov Selkowitz]

The following packages have been uploaded to the Cygwin distribution:

* mesa-11.2.1-1
* dri-drivers-11.2.1-1
* libglapi0-11.2.1-1
* libGL1-11.2.1-1
* libGL-devel-11.2.1-1
* libOSMesa8-11.2.1-1
* libOSMesa-devel-11.2.1-1
* libEGL1-11.2.1-1
* libEGL-devel-11.2.1-1
* libGLESv2_2-11.2.1-1
* libGLESv2-devel-11.2.1-1
* windowsdriproto-11.2.1-1

Mesa is an open-source implementation of the OpenGL, OpenGL ES, and EGL
specifications for rendering interactive 3D graphics.

Complete documentation on OpenGL usage and configuration can be found here:

http://x.cygwin.com/docs/ug/using-glx.html

This is an update to the latest upstream release:

http://mesa3d.org/relnotes/11.2.0.html
http://mesa3d.org/relnotes/11.2.1.html

--
Yaakov

Re: Deterministic builds

[Ken Brown]

On 5/5/2016 4:26 PM, Warren Young wrote:

On May 5, 2016, at 11:59 AM, Ken Brown  wrote:


Ismail's suggestion did indeed produce deterministic builds in my setup.  I 
built a large project with about 150 executables, changed a few source files, 
removed the build directory, rebuilt, and found that only the (expected) few 
executables changed.


…and does it do the same on a very different system?  e.g. Try it on both 
64-bit Windows 10 and on 32-bit Windows 7.

Perhaps you don’t need it, but part of the reason for the big push recently for 
reproducible builds is to be able to verify that binaries from a given source 
(e.g. Red Hat’s RPM feed) are in fact buildable from the sources distributed 
from the same source (e.g. Red Hat’s SRPMs).


Yes, that's a much more ambitious goal, and it's not what I was trying 
to do.


Ken

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

Re: Deterministic builds

[Warren Young]

On May 5, 2016, at 11:59 AM, Ken Brown  wrote:
> 
> Ismail's suggestion did indeed produce deterministic builds in my setup.  I 
> built a large project with about 150 executables, changed a few source files, 
> removed the build directory, rebuilt, and found that only the (expected) few 
> executables changed.

…and does it do the same on a very different system?  e.g. Try it on both 
64-bit Windows 10 and on 32-bit Windows 7.

Perhaps you don’t need it, but part of the reason for the big push recently for 
reproducible builds is to be able to verify that binaries from a given source 
(e.g. Red Hat’s RPM feed) are in fact buildable from the sources distributed 
from the same source (e.g. Red Hat’s SRPMs).

The usual motivation for that is security: it’s no good receiving an SRPM with 
a security patch if the binary that yum installs still has the bug.

Therefore, if you get “reproducible” builds on only a single machine, you may 
not have achieved any useful result.
--
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

Re: Deterministic builds

[Ken Brown]

On 5/4/2016 1:39 PM, Ken Brown wrote:

On 5/4/2016 1:21 PM, Ismail Donmez wrote:

You can easily disable this feature:

latte ~ > gcc -Wl,--no-insert-timestamp hello.c
latte ~ > objdump -p a.exe | grep Time/Date
Time/Date   Thu Jan  1 03:31:53 1970
latte ~ > gcc -Wl,--no-insert-timestamp hello.c
latte ~ > objdump -p a.exe | grep Time/Date
Time/Date   Thu Jan  1 03:31:53 1970


Thank you!  That's exactly what I was looking for.


Just for the record, in case anyone else finds this useful, Ismail's 
suggestion did indeed produce deterministic builds in my setup.  I built 
a large project with about 150 executables, changed a few source files, 
removed the build directory, rebuilt, and found that only the (expected) 
few executables changed.


Ken


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

Re: Formatting command line arguments when starting a Cygwin process from a native process

[Erik Soderquist]

On Thu, May 5, 2016 at 11:24 AM, David Allsopp wrote:
>
> I am trying to work out the precise details for character escaping when
> starting a Cygwin process from a native (i.e. non-Cygwin) Windows process.

> For example:
>
>   argv[0] = "foo"
>   argv[1] = "bar baz"
>
> then the resulting command line string should be:
>
>   lpCommandLine = "foo bar\" \"baz"

If I recall correctly, Windows cmd.exe uses the carrot (^) as the
general escape from shell character, so

C:\cygwin64\bin>.\echo.exe -e ^"hello\nworld^"
hello
world

works.

However, I've found Windows's interpretation to be inconsistent, so
often have to play with it to find what the "right combination" is for
a particular instance.

I find echoing the parameters to a temporary text file and then using
the file as input to be more reliable and easier to troubleshoot, and
it breaks apart whether it is Windows cli inconsistencies or receiving
program issues very nicely with the text file content as an
intermediary

-- Erik

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

Formatting command line arguments when starting a Cygwin process from a native process

[David Allsopp]

I am trying to work out the precise details for character escaping when
starting a Cygwin process from a native (i.e. non-Cygwin) Windows process.

I have an array of command line arguments which I want passed verbatim to
the process, as though it were invoked using execv, with no globbing to take
place. I therefore disable globbing by including the noglob option in the
CYGWIN environment variable. My reading of winsup/cygwin/dcrt0.cc suggests
that I should convert argv to a single string to pass to the Windows
CreateProcess API call by protecting any whitespace characters (\t, \r, \n
and space itself) with double quotes. Then the escaped individual argv items
can be concatenated together with a space between each one.

For example:

  argv[0] = "foo"
  argv[1] = "bar baz"

then the resulting command line string should be:

  lpCommandLine = "foo bar\" \"baz"

and if I've interpreted build_argv and quoted correctly in dcrt0.cc, then as
long as allow_glob is 0 (which it is, via the noglob option in the CYGWIN
environment variable) then the Cygwin DLL will correctly reconstruct argv
based on that string returned by the Windows GetCommandLineW call made in
dll_crt0_1.

However, it appears that the single quote character may only be used to
quote strings if globbing is enabled (dcrt0.cc line 321) so how should one
encode the following argv?

  argv[0] = "foo"
  argv[1] = "bar \"baz\""

There doesn't seem to be anything along the lines of the trickery in the
Windows API's CommandLineToArgvW function if globbing is turned off?

Thanks for any pointers to the correct solution!


David


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

[ANNOUNCEMENT] Updated: ImageMagick-6.9.3.10-1

[Marco Atzeri]

New version 6.9.3.10-1 of
   ImageMagick
   ImageMagick-doc
   libMagickCore6_2
   libMagickC++6_6
   libMagickWand6_2
   libMagick-devel
   perl-Image-Magick

have been uploaded for cygwin

CHANGES
Latest 6.9.x upstream release.
This is a security release covering several vulnerabilities

https://www.imagemagick.org/discourse-server/viewtopic.php?f=4=29588

DESCRIPTION
ImageMagick® is a software suite to create, edit, compose, or convert
bitmap images. It can read and write images in a variety of formats
(over 100) including DPX, EXR, GIF, JPEG, JPEG-2000, PDF, PhotoCD,
PNG, Postscript, SVG, and TIFF. Use ImageMagick to resize, flip,
mirror, rotate, distort, shear and transform images, adjust image
colors, apply various special effects, or draw text, lines, polygons,
ellipses and Bézier curves.

HOMEPAGE
http://www.imagemagick.org/


Regards
Marco Atzeri

If you have questions or comments, please send them to the
cygwin mailing list at: cygwin (at) cygwin (dot) com .

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

Updated: ImageMagick-6.9.3.10-1

[Marco Atzeri]

New version 6.9.3.10-1 of
   ImageMagick
   ImageMagick-doc
   libMagickCore6_2
   libMagickC++6_6
   libMagickWand6_2
   libMagick-devel
   perl-Image-Magick

have been uploaded for cygwin

CHANGES
Latest 6.9.x upstream release.
This is a security release covering several vulnerabilities

https://www.imagemagick.org/discourse-server/viewtopic.php?f=4=29588

DESCRIPTION
ImageMagick® is a software suite to create, edit, compose, or convert
bitmap images. It can read and write images in a variety of formats
(over 100) including DPX, EXR, GIF, JPEG, JPEG-2000, PDF, PhotoCD,
PNG, Postscript, SVG, and TIFF. Use ImageMagick to resize, flip,
mirror, rotate, distort, shear and transform images, adjust image
colors, apply various special effects, or draw text, lines, polygons,
ellipses and Bézier curves.

HOMEPAGE
http://www.imagemagick.org/


Regards
Marco Atzeri

If you have questions or comments, please send them to the
cygwin mailing list at: cygwin (at) cygwin (dot) com .