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-
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 tha
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
> executa
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-timesta
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
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
6 matches
Mail list logo
