[ANNOUNCEMENT] mesa 17.2.2-1

[Yaakov Selkowitz]

The following packages have been uploaded to the Cygwin distribution:

* dri-drivers-17.2.2-1
* libglapi0-17.2.2-1
* libGL1-17.2.2-1
* libGL-devel-17.2.2-1
* libOSMesa8-17.2.2-1
* libOSMesa-devel-17.2.2-1
* libEGL1-17.2.2-1
* libEGL-devel-17.2.2-1
* libGLESv2_2-17.2.2-1
* libGLESv2-devel-17.2.2-1
* windowsdriproto-17.2.2-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:

https://www.mesa3d.org/relnotes/17.2.0.html
https://www.mesa3d.org/relnotes/17.2.1.html
https://www.mesa3d.org/relnotes/17.2.2.html

This release also includes a backport of integrated S3TC support, now that 
the relevant patent has expired.  As a consequence, libtxc_dxtn is no 
longer required.

libEGL1 now requires libxcb-dri2_0 to avoid needing to maintain a patch to 
avoid the dependency.

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

[Yaakov Selkowitz]

The following packages have been uploaded to the Cygwin distribution:

* dri-drivers-17.2.2-1
* libglapi0-17.2.2-1
* libGL1-17.2.2-1
* libGL-devel-17.2.2-1
* libOSMesa8-17.2.2-1
* libOSMesa-devel-17.2.2-1
* libEGL1-17.2.2-1
* libEGL-devel-17.2.2-1
* libGLESv2_2-17.2.2-1
* libGLESv2-devel-17.2.2-1
* windowsdriproto-17.2.2-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:

https://www.mesa3d.org/relnotes/17.2.0.html
https://www.mesa3d.org/relnotes/17.2.1.html
https://www.mesa3d.org/relnotes/17.2.2.html

This release also includes a backport of integrated S3TC support, now that 
the relevant patent has expired.  As a consequence, libtxc_dxtn is no 
longer required.

libEGL1 now requires libxcb-dri2_0 to avoid needing to maintain a patch to 
avoid the dependency.

--
Yaakov

[ANNOUNCEMENT] libxcb 1.12-2

[Yaakov Selkowitz]

The following packages have been uploaded to the Cygwin distribution:

* libxcb1-1.12-2
* libxcb-devel-1.12-2
* libxcb-doc-1.12-2
* libxcb-composite0-1.12-2
* libxcb-composite-devel-1.12-2
* libxcb-damage0-1.12-2
* libxcb-damage-devel-1.12-2
* libxcb-dpms0-1.12-2
* libxcb-dpms-devel-1.12-2
* libxcb-dri2_0-1.12-2
* libxcb-dri2-devel-1.12-2
* libxcb-glx0-1.12-2
* libxcb-glx-devel-1.12-2
* libxcb-randr0-1.12-2
* libxcb-randr-devel-1.12-2
* libxcb-record0-1.12-2
* libxcb-record-devel-1.12-2
* libxcb-render0-1.12-2
* libxcb-render-devel-1.12-2
* libxcb-res0-1.12-2
* libxcb-res-devel-1.12-2
* libxcb-screensaver0-1.12-2
* libxcb-screensaver-devel-1.12-2
* libxcb-shape0-1.12-2
* libxcb-shape-devel-1.12-2
* libxcb-shm0-1.12-2
* libxcb-shm-devel-1.12-2
* libxcb-sync1-1.12-2
* libxcb-sync-devel-1.12-2
* libxcb-xfixes0-1.12-2
* libxcb-xfixes-devel-1.12-2
* libxcb-xinerama0-1.12-2
* libxcb-xinerama-devel-1.12-2
* libxcb-xinput0-1.12-2
* libxcb-xinput-devel-1.12-2
* libxcb-xkb1-1.12-2
* libxcb-xkb-devel-1.12-2
* libxcb-xtest0-1.12-2
* libxcb-xtest-devel-1.12-2
* libxcb-present0-1.12-2
* libxcb-present-devel-1.12-2

libxcb provides an interface to the X Window System protocol, which 
replaces the current Xlib interface. Xlib can also use XCB as a transport 
layer, allowing software to make requests and receive responses with both, 
which eases porting to XCB. However, client programs, libraries, and 
toolkits will gain the most benefit from a native XCB port.

This release enables xcb-dri2.  Not because DRI2 is supported on Cygwin 
(it's not), but having the library avoids the need for an unwieldy (and 
ever-changing) patch to Mesa's libEGL to build without it.

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

libxcb 1.12-2

[Yaakov Selkowitz]

The following packages have been uploaded to the Cygwin distribution:

* libxcb1-1.12-2
* libxcb-devel-1.12-2
* libxcb-doc-1.12-2
* libxcb-composite0-1.12-2
* libxcb-composite-devel-1.12-2
* libxcb-damage0-1.12-2
* libxcb-damage-devel-1.12-2
* libxcb-dpms0-1.12-2
* libxcb-dpms-devel-1.12-2
* libxcb-dri2_0-1.12-2
* libxcb-dri2-devel-1.12-2
* libxcb-glx0-1.12-2
* libxcb-glx-devel-1.12-2
* libxcb-randr0-1.12-2
* libxcb-randr-devel-1.12-2
* libxcb-record0-1.12-2
* libxcb-record-devel-1.12-2
* libxcb-render0-1.12-2
* libxcb-render-devel-1.12-2
* libxcb-res0-1.12-2
* libxcb-res-devel-1.12-2
* libxcb-screensaver0-1.12-2
* libxcb-screensaver-devel-1.12-2
* libxcb-shape0-1.12-2
* libxcb-shape-devel-1.12-2
* libxcb-shm0-1.12-2
* libxcb-shm-devel-1.12-2
* libxcb-sync1-1.12-2
* libxcb-sync-devel-1.12-2
* libxcb-xfixes0-1.12-2
* libxcb-xfixes-devel-1.12-2
* libxcb-xinerama0-1.12-2
* libxcb-xinerama-devel-1.12-2
* libxcb-xinput0-1.12-2
* libxcb-xinput-devel-1.12-2
* libxcb-xkb1-1.12-2
* libxcb-xkb-devel-1.12-2
* libxcb-xtest0-1.12-2
* libxcb-xtest-devel-1.12-2
* libxcb-present0-1.12-2
* libxcb-present-devel-1.12-2

libxcb provides an interface to the X Window System protocol, which 
replaces the current Xlib interface. Xlib can also use XCB as a transport 
layer, allowing software to make requests and receive responses with both, 
which eases porting to XCB. However, client programs, libraries, and 
toolkits will gain the most benefit from a native XCB port.

This release enables xcb-dri2.  Not because DRI2 is supported on Cygwin 
(it's not), but having the library avoids the need for an unwieldy (and 
ever-changing) patch to Mesa's libEGL to build without it.

--
Yaakov

Re: bash pipe race condition

[Kaz Kylheku]

On 03.10.2017 05:56, cyg Simple wrote:

On 10/2/2017 9:06 PM, Matthew McGIllis wrote:

If I use the same code from bash I get:

$ ./input.exe | ./simple.exe
line1
<—— Hangs indefinitely until you kill it or ctrl-c

Some how if input has a delay between its line output then things will 
get hung, if you remove the sleep from the input things work, add the 
sleep in it fails.



input.exe is generate from input.vb using: vbc input.vb

[ ... ]


It is a known issue of the PTY emulation between a Cygwin runtime and a
Windows runtime enabled app.  It just cannot be fixed.  You're even
lucky that it works in the Windows command shell.


Lucky? Are VB console apps known to have unreliable piping when
used from the Windows command processor?


Either convert
simple.vb to simple.c and use Cygwin's gcc to build it or create a
Windows runtime version of input.exe.


Isn't that what "input.exe is generate[d] from input.vb using: vbc 
input.vb"

is referring to?


--
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: Segmentation fault with binutils 2.28.1

[叶雨飞]

Guys,

If someone could show me some instructions on how to build and release
binutils for CYGWIN, I'm happy to do it this week.

Cheers.

--
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: Segmentation fault with binutils 2.28.1

[Steven Penny]

On Tue, 3 Oct 2017 14:37:04, Marco Atzeri wrote:

you wrote nothing at all. So it is difficult to understand what is your exact
issue


I wrote it 4 times:

- http://cygwin.com/ml/cygwin/2017-09/msg00229.html
- http://cygwin.com/ml/cygwin/2017-09/msg00289.html
- http://cygwin.com/ml/cygwin/2017-10/msg00021.html
- http://github.com/Martchus/tageditor/issues/23#issuecomment-331757730

Here though, let me write it 5 now:

   $ cat z.cpp
   #include 
   main() {
 std::cout << "cout test\n";
   }

   $ x86_64-w64-mingw32-g++ -static -o z z.cpp

   $ ./z
   Segmentation fault


as in the past you blamed the compiler.


Yes, I discovered new information, so I modified the email subject to reflect
that. Would you rather me continue to blame the complier, or try to help
diagnose the problem?


Error report should be clear and complete;


Example above is MCVE http://stackoverflow.com/help/mcve


only links to other place are not enough.


See above - also notice carefully that example was included in my previous post
as well


I saw the comment from Martchus
"Note that when I had been using mingw-w64-binutils 2.28 (before recent 
update to 2.29) I didn't encounter this issue. I never tried 2.28.1."


So it does not seem an issue specif of 2.28


No one but you has said that 2.28 has a problem. What Martchus actually said
was:

- 2.28   working
- 2.28.1 never tried
- 2.29   working


Have you built it ?


No


Or are you only asking Jon to dedicate his time ?


Hm. Last I checked I have already made at least 10 posts on this issue:

- http://cygwin.com/ml/cygwin/2017-09/msg00195.html
- http://cygwin.com/ml/cygwin/2017-09/msg00218.html
- http://cygwin.com/ml/cygwin/2017-09/msg00229.html
- http://cygwin.com/ml/cygwin/2017-09/msg00247.html
- http://cygwin.com/ml/cygwin/2017-09/msg00248.html
- http://cygwin.com/ml/cygwin/2017-09/msg00282.html
- http://cygwin.com/ml/cygwin/2017-09/msg00289.html
- http://cygwin.com/ml/cygwin/2017-09/msg00294.html
- http://cygwin.com/ml/cygwin/2017-10/msg00021.html
- http://cygwin.com/ml/cygwin/2017-10/msg00025.html

Maybe your sense of time is distorted.


Last time I had issue with cygwin binutils 2.25, I built the 2.28.90
and I verified that was solving the issue I saw.
I was not just expecting Jon to debug it alone.


Good for you, but I dont have to build anything to verify the issue - I narrowed
the problem to a single package, and tested with "Test" and "Current" versions.
"Current" works - "Test" fails.

So we could patch "Test", but since a newer version is already available (2.29),
the sane thing to do would be to just upload a newer test version and probably
bypass the problem altogether. If you want to waste your time making a build in
this case that is your business, but dont put that bad advice off on me when I
have already diagnosed the problem.


--
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: [PATCH cygport] Add a command to make a test release

[Achim Gratz]

Andrew Schulman writes:
> Cygport needs a way to specify which versions are prev, curr, and test in
> cygport files. David Rothenberger and I each proposed a method [1,2]. It
> doesn't matter much to me which method is picked, but it's definitely a
> missing feature.

My latest iteration on the original patch by David:

http://repo.or.cz/cygport/rpm-style.git/commitdiff/b169fec0a4a14e79a1d07bd0df300ef1f43b92a0


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

Re: [PATCH cygport 1/2] Rename DEPEND to BUILD_DEPENDS

[Andrew Schulman]

> Somewhat clearer as to it's purposes, and pluralized for consistency with
> REQUIRES.

Yes! Thank you!

[PATCH cygport 1/2] Rename DEPEND to BUILD_DEPENDS

[Jon Turney]

Somewhat clearer as to it's purposes, and pluralized for consistency with
REQUIRES.

Still support the previous name for backwards compatibility
---
 lib/check_funcs.cygpart | 17 -
 1 file changed, 12 insertions(+), 5 deletions(-)

diff --git a/lib/check_funcs.cygpart b/lib/check_funcs.cygpart
index 93f3e12..08b1be3 100644
--- a/lib/check_funcs.cygpart
+++ b/lib/check_funcs.cygpart
@@ -543,9 +543,9 @@ check_vala_module() {
return ${ret};
 }
 
-#f* Information/DEPEND
+#f* Information/BUILD_DEPENDS
 #  SYNOPSIS
-#  DEPEND="ATOM [ATOM] ..."
+#  BUILD_DEPENDS="ATOM [ATOM] ..."
 #  DESCRIPTION
 #  A list of build-time (not runtime) dependencies to be checked before calling
 #  src_compile.  Each ATOM can be in one of the following forms:
@@ -565,6 +565,8 @@ check_vala_module() {
 #  * tex(foo.ext): TeX modules
 #  * vala(foo-1.0): Vala bindings
 #  * foo: A Cygwin package (check skipped on non-Cygwin build systems)
+#
+# DEPEND is an obsolete synonym for BUILD_DEPENDS.
 #
 __check_depends() {
local atom failed_atoms;
@@ -574,14 +576,19 @@ __check_depends() {
error "Compiling this package requires $(cross_compiling && 
echo -n ${CHOST}' ')binutils and gcc"
fi
 
-   if ! defined DEPEND
+   if ! defined BUILD_DEPENDS
then
-   return 0;
+   if defined DEPEND
+   then
+   BUILD_DEPENDS=${DEPEND}
+   else
+   return 0;
+   fi
fi
 
__deparenthesize() { echo "$@" | sed -e 's|[a-z]*(\([^)]*\))|\1|' ; }
 
-   for atom in ${DEPEND}
+   for atom in ${BUILD_DEPENDS}
do
case ${atom} in
girepository\(*)
-- 
2.14.2

[PATCH cygport 0/2] Better handling of build depends

[Jon Turney]

Jon Turney (2):
  Rename DEPEND to BUILD_DEPENDS
  Pass BUILD_DEPENDS through to .hint for source package as
build-depends:

 lib/check_funcs.cygpart | 17 -
 lib/pkg_pkg.cygpart |  5 +
 2 files changed, 17 insertions(+), 5 deletions(-)

-- 
2.14.2

[PATCH cygport 2/2] Pass BUILD_DEPENDS through to .hint for source package as build-depends:

[Jon Turney]

Converting a dependency atom to a package name with full generality requires
a database of all the pathnames contained in all packages, so we don't even
try to do that here.

In the fullness of time, calm may have the information needed to perform
that task, at which time it can start emitting build-depends: lines for
source packages into setup.ini.
---
 lib/pkg_pkg.cygpart | 5 +
 1 file changed, 5 insertions(+)

diff --git a/lib/pkg_pkg.cygpart b/lib/pkg_pkg.cygpart
index cfc0770..b3aeb32 100644
--- a/lib/pkg_pkg.cygpart
+++ b/lib/pkg_pkg.cygpart
@@ -717,6 +717,10 @@ _EOF
then
cat >> 
${distdir}/${PN}/${distsubdir}/${pkg_name[${n}]}-${PVR}.hint <<-_EOF
 external-source: ${PN}
+_EOF
+   else
+   cat >> 
${distdir}/${PN}/${distsubdir}/${pkg_name[${n}]}-${PVR}.hint <<-_EOF
+build-depends: ${BUILD_DEPENDS}
 _EOF
fi
if defined ${pkg_message_var}
@@ -818,6 +822,7 @@ _EOF
cat > ${distdir}/${PN}/${PN}-${PVR}.hint <<-_EOF
 category: ${!pkg_category_var:-${CATEGORY}}
 requires:
+build-depends: ${BUILD_DEPENDS}
 sdesc: "${!pkg_summary_var:-${SUMMARY}}"
 ldesc: 
"${!pkg_description_var:-${DESCRIPTION:-${!pkg_summary_var:-${SUMMARY"
 skip:
-- 
2.14.2

[PATCH cygport] Add a command to make a test release

[Jon Turney]

This patch (originally by Achim Gratz) adds a mechanism for generating 
packages marked as 'test' as described in [1].


I'm not committed to any of the details, but I would like to get 
something with this functionality in, so tell me how you'd like it 
implemented and I'll do it...


[1] https://cygwin.com/ml/cygwin-apps/2016-12/msg5.html
From f0e8ed8266da36fcf5ea0b648e91c1be5e793c6b Mon Sep 17 00:00:00 2001
From: Achim Gratz 
Date: Sat, 8 Apr 2017 17:00:34 +0200
Subject: [PATCH cygport] Add a command to make a test release

lib/pkg_pkg.cygpart: inform when creating hint files for a test release.

lib/help.cygport: document command to package test releases.

bin/cygport.in: provide command to package test releases.

v2:
Add test: to all hints
Add to help output

Signed-off-by: Jon Turney 
---
 bin/cygport.in  |  3 +++
 lib/help.cygpart|  1 +
 lib/pkg_pkg.cygpart | 13 +
 3 files changed, 17 insertions(+)

diff --git a/bin/cygport.in b/bin/cygport.in
index 6cf0122..9cf6f46 100644
--- a/bin/cygport.in
+++ b/bin/cygport.in
@@ -599,6 +599,9 @@ do
__show_web;
_status=$?;
;;
+   package-test|pkg-test)
+   TESTRELEASE=cmdline;
+   ;&
package|pkg)
__stage Packaging;
__log_init ${pkglog};
diff --git a/lib/help.cygpart b/lib/help.cygpart
index 460f8f7..54819a9 100644
--- a/lib/help.cygpart
+++ b/lib/help.cygpart
@@ -46,6 +46,7 @@ __show_help() {
  test run the package's test suite, if one exists
  install  install into a DESTDIR, and run 
post-installation steps
  package  create binary and source packages
+ package-test create binary and source packages, marked as test
  upload   upload finished packages to cygwin.com
  announce send an announcement email to cygwin.com
  finish   delete the working directory
diff --git a/lib/pkg_pkg.cygpart b/lib/pkg_pkg.cygpart
index cfc0770..c3b47fe 100644
--- a/lib/pkg_pkg.cygpart
+++ b/lib/pkg_pkg.cygpart
@@ -665,6 +665,14 @@ __pkg_dist() {
 #  libfoo-devel will use libfoo_devel_OBSOLETES.
 #
 
+   pkg_testrelease=${TESTRELEASE+test:};
+   if [ "test:" = "${pkg_testrelease:-none}" ]
+   then
+   inform "Package hint files are prepared for a 
\e[1;31mtest\e[0;0m release\n"
+   else
+   inform "Package hint files are prepared for a 
\e[1;32mcurrent\e[0;0m release\n"
+   fi
+
n=0;
while defined pkg_name[${n}]
do
@@ -712,6 +720,7 @@ category: ${!pkg_category_var:-${CATEGORY}}
 requires: ${pkg_bin_requires} ${!pkg_requires_var}
 sdesc: "${!pkg_summary_var:-${SUMMARY}}"
 ldesc: 
"${!pkg_description_var:-${DESCRIPTION:-${!pkg_summary_var:-${SUMMARY"
+${pkg_testrelease}
 _EOF
if defined distsubdir
then
@@ -751,6 +760,7 @@ ldesc: "The ${obspkg} package is obsolete.  Selecting this 
package for
 installation will cause the ${pkg_name[${n}]} package, which replaces this
 one, to be installed instead."
 ${obssubdir:+external-source: ${PN}}
+${pkg_testrelease}
 _EOF
done
 
@@ -777,6 +787,7 @@ external-source: ${PN}
 sdesc: "Debug info for ${PN}"
 ldesc: "This package contains files necessary for debugging the
 ${PN} package with gdb."
+${pkg_testrelease}
 _EOF
fi
 
@@ -795,6 +806,7 @@ ldesc: "The ${obspkg} package is obsolete.  Selecting this 
package for
 installation will cause the ${PN}-debuginfo package, which replaces this
 one, to be installed instead."
 external-source: ${PN}
+${pkg_testrelease}
 _EOF
done
fi
@@ -820,6 +832,7 @@ category: ${!pkg_category_var:-${CATEGORY}}
 requires:
 sdesc: "${!pkg_summary_var:-${SUMMARY}}"
 ldesc: 
"${!pkg_description_var:-${DESCRIPTION:-${!pkg_summary_var:-${SUMMARY"
+${pkg_testrelease}
 skip:
 _EOF
else
-- 
2.14.2

problem with i686-w64-mingw32-gcc -fstack-protector-all

[Lee]

Maybe I'm just Doing It Wrong, but
  gcc -fstack-protector-all
seems to be working correctly &
  i686-w64-mingw32-gcc -fstack-protector-all
seems to be broken - eg:

$./ssp testtestx
Illegal instruction

printf's that happen before the stack over-write don't show up & no
"*** stack smashing detected ***" msg is printed before the "Illegal
instruction"

STC:

$cat doit
#!/bin/sh
LIB="-lssp"
set -x

cat main-ssp.c
cat func-ssp.c

i686-w64-mingw32-gcc -c -fstack-protector-all   func-ssp.c -o func-ssp.o
i686-w64-mingw32-gcc -c -fstack-protector-all   main-ssp.c -o main-ssp.o
i686-w64-mingw32-gcc -static -o ssp.exe func-ssp.o main-ssp.o $LIB
./ssp.exe testtestx

echo -e '\n\n'

gcc -c -fstack-protector-all   func-ssp.c -o cyg-func-ssp.o
gcc -c -fstack-protector-all   main-ssp.c -o cyg-main-ssp.o
gcc -static -o cyg-ssp.exe cyg-func-ssp.o cyg-main-ssp.o $LIB
./cyg-ssp.exe testtestx


$./doit
+ cat main-ssp.c
/* stack smashing protection
  i686-w64-mingw32-gcc -c -fstack-protector-all -o func-ssp.o func-ssp.c
  i686-w64-mingw32-gcc -c -fstack-protector-all -o main-ssp.o main-ssp.c
  i686-w64-mingw32-gcc -o ssp.exe  main-ssp.o func-ssp.o
  ./ssp testtestx
*** should die ***
 */

#include 
#include 

extern int doit(char *s );

int main(int argc, char *argv[])
{
 int status=0;
 printf("main: argv[1]=%s\n", argv[1] );
 status = doit(argv[1]);
 if ( status != 1 ) printf("OhNoes!! doit returned %d\n", status );
 printf("main: exit\n" );
 return 0;
}

+ cat func-ssp.c
/* stack smashing protection test */

#include 
#include 

extern
int doit(char *s ) {
  char buf[]="12345678";
  int i=0;
  if ( *s != '\0' ) i = 1;  /* return true */
  printf("doit: s=\"%s\"   buf=\"%s\"  i=%d\n", s, buf, i );
  strcpy(buf, s);
/* buffer overflow into return status(int i) if strlen(s) > 8 */
  printf("doit: s=\"%s\"   buf=\"%s\"  i=%d\n", s, buf, i );
  return i;
}

+ i686-w64-mingw32-gcc -c -fstack-protector-all func-ssp.c -o func-ssp.o
+ i686-w64-mingw32-gcc -c -fstack-protector-all main-ssp.c -o main-ssp.o
+ i686-w64-mingw32-gcc -static -o ssp.exe func-ssp.o main-ssp.o -lssp
+ ./ssp.exe testtestx
./doit: line 11:  9128 Illegal instruction ./ssp.exe testtestx
+ echo -e '\n\n'



+ gcc -c -fstack-protector-all func-ssp.c -o cyg-func-ssp.o
+ gcc -c -fstack-protector-all main-ssp.c -o cyg-main-ssp.o
+ gcc -static -o cyg-ssp.exe cyg-func-ssp.o cyg-main-ssp.o -lssp
+ ./cyg-ssp.exe testtestx
main: argv[1]=testtestx
doit: s="testtestx"   buf="12345678"  i=1
doit: s="testtestx"   buf="testtestx"  i=1
*** stack smashing detected ***:  terminated
./doit: line 18:  2336 Illegal instruction (core dumped)
./cyg-ssp.exe testtestx

$

$ gcc --version
gcc (GCC) 6.4.0
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

$ i686-w64-mingw32-gcc --version
i686-w64-mingw32-gcc (GCC) 6.3.0
Copyright (C) 2016 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


Thanks,
Lee

--
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: R-3.4.2-1

[Marco Atzeri]

Versions 3.4.2-1  of
R
libRmath
libRmath-devel

for cygwin are now available:


CHANGES
New upstream release
https://mailman.stat.ethz.ch/pipermail/r-announce/2017/000619.html

DESCRIPTION
R is a language and environment for statistical computing and graphics.

R provides a wide variety of statistical (linear and nonlinear
modelling, classical statistical tests, time-series analysis,
classification, clustering, ...) and graphical techniques, and
is highly extensible.
The S language is often the vehicle of choice for research in
statistical methodology, and R provides an Open Source route
to participation in that activity.

HOMEPAGE
http://www.r-project.org/


Marco Atzeri

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

[ANNOUNCEMENT] Updated: R-3.4.2-1

[Marco Atzeri]

Versions 3.4.2-1  of
R
libRmath
libRmath-devel

for cygwin are now available:


CHANGES
New upstream release
https://mailman.stat.ethz.ch/pipermail/r-announce/2017/000619.html

DESCRIPTION
R is a language and environment for statistical computing and graphics.

R provides a wide variety of statistical (linear and nonlinear
modelling, classical statistical tests, time-series analysis,
classification, clustering, ...) and graphical techniques, and
is highly extensible.
The S language is often the vehicle of choice for research in
statistical methodology, and R provides an Open Source route
to participation in that activity.

HOMEPAGE
http://www.r-project.org/


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

[ITA] multitail

[Andrew Schulman]

I'd like to adopt this from Dr Volker Zell. I've tested the cygport script
with the latest version, 6.4.2, and it works fine, so I have a new package
ready to upload. Andrew

Re: calm: removing test packages override.hint files

[Marco Atzeri]

On 03/10/2017 18:23, Jon Turney wrote:

On 03/10/2017 13:19, Marco Atzeri wrote:

Jon,




I suspect you could work around this (for the moment) by uploading an 
override.hint with the test: line removed, rather than removing the 
override.hint.  You should then be able to remove the override.hint in a 
subsequent upload.


calm has not complained this time


Really, I want to move to using test: labels in the pvr.hint to avoid 
all these edge cases, but we're not there yet...


no problem. It is a border case anyway.

thanks
Marco

Re: calm: removing test packages override.hint files

[Jon Turney]

On 03/10/2017 13:19, Marco Atzeri wrote:

Jon,
It seems calm do not like I remove the test packages and
the override.hint files at the same time

I do not see anything obvious wrong on my instructions

./x86_64/release/GraphicsMagick/-GraphicsMagick-1.3.26-2-src.tar.xz
./x86_64/release/GraphicsMagick/-GraphicsMagick-1.3.26-2.hint
./x86_64/release/GraphicsMagick/-GraphicsMagick-1.3.26-2.tar.xz
./x86_64/release/GraphicsMagick/-override.hint
...


Thanks for pointing this out.

Yeah, this doesn't seem to work as intended.

I suspect you could work around this (for the moment) by uploading an 
override.hint with the test: line removed, rather than removing the 
override.hint.  You should then be able to remove the override.hint in a 
subsequent upload.


Really, I want to move to using test: labels in the pvr.hint to avoid 
all these edge cases, but we're not there yet...

[ANNOUNCEMENT] Updated: fzf v0.12.1-2

[Adam Dinwoodie]

fzf v0.12.1-2 has been uploaded and should be coming soon to a mirror
near you.  This update includes the following packages:

- fzf
- fzf-bash
- fzf-bash-completion
- fzf-fish
- fzf-vim
- fzf-zsh
- fzf-zsh-completion

This update resolves the "bad substitution" error that may be seen if
fzf-bash-completion is installed, with thanks to Gene Pavlovsky.

The Cygwin fzf package is not being actively maintained, as the upstream
fzf project has dropped support for Ruby in favour of Go, and Cygwin
does not currently have Go support.  If you fancy taking over
maintaining the now-abandoned Ruby-based version of fzf, I'd be happy to
point you at the initial work I've done there.

Adam

--
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: fzf v0.12.1-2

[Adam Dinwoodie]

fzf v0.12.1-2 has been uploaded and should be coming soon to a mirror
near you.  This update includes the following packages:

- fzf
- fzf-bash
- fzf-bash-completion
- fzf-fish
- fzf-vim
- fzf-zsh
- fzf-zsh-completion

This update resolves the "bad substitution" error that may be seen if
fzf-bash-completion is installed, with thanks to Gene Pavlovsky.

The Cygwin fzf package is not being actively maintained, as the upstream
fzf project has dropped support for Ruby in favour of Go, and Cygwin
does not currently have Go support.  If you fancy taking over
maintaining the now-abandoned Ruby-based version of fzf, I'd be happy to
point you at the initial work I've done there.

Adam

Re: Dr. Volker Zell's packages

[Marco Atzeri]

On 03/10/2017 17:00, Andrew Schulman wrote:

Unfortunately, we haven't heard from Dr. Volker Zell in quite some time,
and a number of his packages are in need of updates or rebuilds.  I have
marked them ORPHANED in the maintainer list.  ITAs welcome.


I use multitail so I can adopt it if the package is in good shape. I'll
take a look.

Maybe openldap.


Hi Andrew,
openldap-2.4.42 builds fine with the cygwin source packages
but it segfaults during test.

The slapd.1.log suggests the segfault is on the test client and not on 
the server.


Can you try to build just to double check that is not my
computer the problem ?

Regards
Marco

Re: lftp 4.8.0-1

[Andrew Schulman]

> On Thu, Sep 28, 2017 at 10:41 AM, Andy Li  wrote:
> 
> >
> >
> >> Still getting this, but have since paid a bit more attention to the
> >> output,
> >> and I'm seeing:
> >>
> >> assertion "ptr(x.heap_index)==" failed: file
> >> "/home/ASchulma/dev/cygwin/lftp/lftp-4.8.0-1.x86_64/src/lftp-4.8.0/src/xheap.h",
> >> line 127, function: void xheap::remove(xheap::node&) [with T =
> >> Timer]
> >
> >
> > I've just got the same error when running cygport upload in x86.
> > Interestingly, there was no error when I did the same in x86_64.
> > Downgrading lftp to the previous version (4.7.7-1) "fixed" the cygport
> > upload.
> >
> 
> Just noticed that it has been reported upstream and fixed in lftp 4.8.2.
> https://github.com/lavv17/lftp/issues/390
> 
> Andrew: Would you package that soon?

lftp 4.8.1 and 4.8.2 both fail to build. I haven't found the solution yet.
I sent two messages to the lftp list about it, but they didn't post and I
haven't solved that yet either. So no progress there yet.

4.7.8 does fix the problem for me. I tried to upload it as a test release
but I guess I need to submit an override.hint file. Will try again today.


--
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: Dr. Volker Zell's packages

[Andrew Schulman]

> Unfortunately, we haven't heard from Dr. Volker Zell in quite some time,
> and a number of his packages are in need of updates or rebuilds.  I have
> marked them ORPHANED in the maintainer list.  ITAs welcome.

I use multitail so I can adopt it if the package is in good shape. I'll
take a look.

Maybe openldap.

Re: bash pipe race condition

[cyg Simple]

On 10/2/2017 9:06 PM, Matthew McGIllis wrote:

> 
> If I use the same code from bash I get:
> 
> $ ./input.exe | ./simple.exe
> line1
> <—— Hangs indefinitely until you kill it or ctrl-c
> 
> Some how if input has a delay between its line output then things will get 
> hung, if you remove the sleep from the input things work, add the sleep in it 
> fails.
> 
> 
> input.exe is generate from input.vb using: vbc input.vb
> 
>  input.vb file:
> Module input
>   Sub Main()
> Console.Out.WriteLine("line1")
> Threading.Thread.Sleep(2000)
> Console.Out.WriteLine("line2")
>   End Sub
> End Module
> 
> simple.exe is generated from simple.vb using: vbc simple.vb
> 
> simple.vb file:
> Module simple
>   Sub Main()
> Dim line As String
> line = Console.In.ReadLine()
> Do Until line Is Nothing
>   Console.Out.WriteLine(line)
>   line = Console.In.ReadLine()
> Loop
>   End Sub
> End Module
> 
> Microsoft (R) Visual Basic Compiler version 11.0.50938.18408
> 
> The above problem was found when attempting to use cygwin perl using 
> IPC::Open2 to control stdin and stdout of a VB program. So this may not be a 
> bash specific issue but some sort of generic pipe issue in cygwin.

It is a known issue of the PTY emulation between a Cygwin runtime and a
Windows runtime enabled app.  It just cannot be fixed.  You're even
lucky that it works in the Windows command shell.  Either convert
simple.vb to simple.c and use Cygwin's gcc to build it or create a
Windows runtime version of input.exe.

-- 
cyg Simple

--
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: Segmentation fault with binutils 2.28.1

[Marco Atzeri]

On 03/10/2017 13:49, Steven Penny wrote:

On Tue, 3 Oct 2017 07:48:51, Marco Atzeri wrote:

I assume it is one of the reason why the compiler and binutils
you are using are still in test and not current

@ mingw64-x86_64-binutils
version: 2.25.0.1.23f238d-1
[test]
version: 2.28.1.12c1f20d-1

@ mingw64-x86_64-gcc-g++
version: 5.4.0-3
[test]
version: 6.3.0-1


Notice carefully that I did not saying anything about GCC 6.3.0 in this 
thread.


Steven,
you wrote nothing at all.
So it is difficult to understand what is your exact issue as in
the past you blamed the compiler.
Error report should be clear and complete;
only links to other place are not enough.

Also notice that you are incorrectly assuming that I am using GCC 6.3.0. 
The

binutils in question does not work with either 5.4.0 nor 6.3.0.


As you shifted the target from g++ to binutils


I did this because binutils is the problem, not GCC:

- http://cygwin.com/ml/cygwin/2017-09/msg00289.html
- http://github.com/Martchus/tageditor/issues/23


I saw the comment from Martchus
"Note that when I had been using mingw-w64-binutils 2.28 (before recent 
update to 2.29) I didn't encounter this issue. I never tried 2.28.1."


So it does not seem an issue specif of 2.28


do you have evidence that 2.29 will solve the issue ?


It seems that both 2.28 and 2.29 both work, so instead of trying to
troubleshoot we should probably just build a newer version and release 
that as

test:

http://github.com/Martchus/tageditor/issues/23#issuecomment-332686239


Have you built it ? Or are you only asking Jon to dedicate his time ?

Last time I had issue with cygwin binutils 2.25, I built the 2.28.90
and I verified that was solving the issue I saw.
I was not just expecting Jon to debug it alone.

https://cygwin.com/ml/cygwin/2017-07/msg00013.html
https://cygwin.com/ml/cygwin/2017-07/msg00084.html

Regards
Marco


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

calm: removing test packages override.hint files

[Marco Atzeri]

Jon,
It seems calm do not like I remove the test packages and
the override.hint files at the same time

I do not see anything obvious wrong on my instructions

./x86_64/release/GraphicsMagick/-GraphicsMagick-1.3.26-2-src.tar.xz
./x86_64/release/GraphicsMagick/-GraphicsMagick-1.3.26-2.hint
./x86_64/release/GraphicsMagick/-GraphicsMagick-1.3.26-2.tar.xz
./x86_64/release/GraphicsMagick/-override.hint
...


 Forwarded Message 
Subject: calm: cygwin package upload report from sourceware.org for 
Marco Atzeri

Date: Tue, 03 Oct 2017 11:25:11 -
From: cygwin-no-re...@cygwin.com
To: marco.atzeri  gmail.com

ERROR: package 'GraphicsMagick' stability 'test' selects non-existent 
version '1.3.26-2'
ERROR: package 'GraphicsMagick-debuginfo' stability 'test' selects 
non-existent version '1.3.26-2'
ERROR: package 'ImageMagick' stability 'test' selects non-existent 
version '6.9.9.11-2'
ERROR: package 'ImageMagick-debuginfo' stability 'test' selects 
non-existent version '6.9.9.11-2'
ERROR: package 'ImageMagick-doc' stability 'test' selects non-existent 
version '6.9.9.11-2'
ERROR: package 'gdal' stability 'test' selects non-existent version 
'2.2.2-2'
ERROR: package 'gdal-debuginfo' stability 'test' selects non-existent 
version '2.2.2-2'
ERROR: package 'irssi' stability 'test' selects non-existent version 
'1.0.4-2'
ERROR: package 'irssi-debuginfo' stability 'test' selects non-existent 
version '1.0.4-2'
ERROR: package 'irssi-devel' stability 'test' selects non-existent 
version '1.0.4-2'
ERROR: package 'libGraphicsMagick++12' stability 'test' selects 
non-existent version '1.3.26-2'
ERROR: package 'libGraphicsMagick-devel' stability 'test' selects 
non-existent version '1.3.26-2'
ERROR: package 'libGraphicsMagick3' stability 'test' selects 
non-existent version '1.3.26-2'
ERROR: package 'libGraphicsMagickWand2' stability 'test' selects 
non-existent version '1.3.26-2'
ERROR: package 'libMagick-devel' stability 'test' selects non-existent 
version '6.9.9.11-2'
ERROR: package 'libMagickC++6_8' stability 'test' selects non-existent 
version '6.9.9.11-2'
ERROR: package 'libMagickCore6_5' stability 'test' selects non-existent 
version '6.9.9.11-2'
ERROR: package 'libMagickWand6_5' stability 'test' selects non-existent 
version '6.9.9.11-2'
ERROR: package 'libgdal-devel' stability 'test' selects non-existent 
version '2.2.2-2'
ERROR: package 'libgdal20' stability 'test' selects non-existent version 
'2.2.2-2'
ERROR: package 'perl-Graphics-Magick' stability 'test' selects 
non-existent version '1.3.26-2'
ERROR: package 'perl-Image-Magick' stability 'test' selects non-existent 
version '6.9.9.11-2'
ERROR: package 'perl-gdal' stability 'test' selects non-existent version 
'2.2.2-2'
ERROR: package 'python-gdal' stability 'test' selects non-existent 
version '2.2.2-2'

ERROR: error while validating merged x86 packages for Marco Atzeri
ERROR: package 'GraphicsMagick' stability 'test' selects non-existent 
version '1.3.26-2'
ERROR: package 'GraphicsMagick-debuginfo' stability 'test' selects 
non-existent version '1.3.26-2'
ERROR: package 'ImageMagick' stability 'test' selects non-existent 
version '6.9.9.11-2'
ERROR: package 'ImageMagick-debuginfo' stability 'test' selects 
non-existent version '6.9.9.11-2'
ERROR: package 'ImageMagick-doc' stability 'test' selects non-existent 
version '6.9.9.11-2'
ERROR: package 'gdal' stability 'test' selects non-existent version 
'2.2.2-2'
ERROR: package 'gdal-debuginfo' stability 'test' selects non-existent 
version '2.2.2-2'
ERROR: package 'irssi' stability 'test' selects non-existent version 
'1.0.4-2'
ERROR: package 'irssi-debuginfo' stability 'test' selects non-existent 
version '1.0.4-2'
ERROR: package 'irssi-devel' stability 'test' selects non-existent 
version '1.0.4-2'
ERROR: package 'libGraphicsMagick++12' stability 'test' selects 
non-existent version '1.3.26-2'
ERROR: package 'libGraphicsMagick-devel' stability 'test' selects 
non-existent version '1.3.26-2'
ERROR: package 'libGraphicsMagick3' stability 'test' selects 
non-existent version '1.3.26-2'
ERROR: package 'libGraphicsMagickWand2' stability 'test' selects 
non-existent version '1.3.26-2'
ERROR: package 'libMagick-devel' stability 'test' selects non-existent 
version '6.9.9.11-2'
ERROR: package 'libMagickC++6_8' stability 'test' selects non-existent 
version '6.9.9.11-2'
ERROR: package 'libMagickCore6_5' stability 'test' selects non-existent 
version '6.9.9.11-2'
ERROR: package 'libMagickWand6_5' stability 'test' selects non-existent 
version '6.9.9.11-2'
ERROR: package 'libgdal-devel' stability 'test' selects non-existent 
version '2.2.2-2'
ERROR: package 'libgdal20' stability 'test' selects non-existent version 
'2.2.2-2'
ERROR: package 'perl-Graphics-Magick' stability 'test' selects 
non-existent version '1.3.26-2'
ERROR: package 'perl-Image-Magick' stability 'test' selects non-existent 
version '6.9.9.11-2'
ERROR: package 'perl-gdal' stability 'test' selects non-existent version 
'2.2.2-2'
ERROR: 

Re: Segmentation fault with binutils 2.28.1

[Steven Penny]

On Tue, 3 Oct 2017 07:48:51, Marco Atzeri wrote:

I assume it is one of the reason why the compiler and binutils
you are using are still in test and not current

@ mingw64-x86_64-binutils
version: 2.25.0.1.23f238d-1
[test]
version: 2.28.1.12c1f20d-1

@ mingw64-x86_64-gcc-g++
version: 5.4.0-3
[test]
version: 6.3.0-1


Notice carefully that I did not saying anything about GCC 6.3.0 in this thread.
Also notice that you are incorrectly assuming that I am using GCC 6.3.0. The
binutils in question does not work with either 5.4.0 nor 6.3.0.


As you shifted the target from g++ to binutils


I did this because binutils is the problem, not GCC:

- http://cygwin.com/ml/cygwin/2017-09/msg00289.html
- http://github.com/Martchus/tageditor/issues/23


do you have evidence that 2.29 will solve the issue ?


It seems that both 2.28 and 2.29 both work, so instead of trying to
troubleshoot we should probably just build a newer version and release that as
test:

http://github.com/Martchus/tageditor/issues/23#issuecomment-332686239


--
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: [Attn. Maintainers] Perl 5.26.1

[Achim Gratz]

Ken Brown writes:
>> I need to have a look on what the main GNU/Linux distributions are doing
>> with this.
>
> It's the same on Debian:
>
>   https://packages.debian.org/stretch/amd64/texinfo/filelist
>
> I haven't checked any other.

Looks like SuSE splits into texinfo / makeinfo /info paclages, but
otherwise seems to handle these the same.  It does split out
perl-text-Unidecode and externalizes it in the configury, though.

>> WOuld it be possible to cleanly excise those as dependent
>> packages?
>
> I could certainly do that, but I wouldn't want to unless there's a
> GNU/Linux model to follow.  I don't think Cygwin should use special
> packaging that no one else uses.

Certainly not, I am still a bit surprised at that way of installing
things, though.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves