public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: <lloyd.wood@yahoo.co.uk>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>,
		"jon.turney@dronecode.org.uk" <jon.turney@dronecode.org.uk>
Subject: Piping on 64-bit Cygwin was Re: [ANNOUNCEMENT] llvm 3.7.1-2
Date: Tue, 21 Jun 2016 07:48:00 -0000	[thread overview]
Message-ID: <1341561944.11163115.1466484828091.JavaMail.yahoo@mail.yahoo.com> (raw)
In-Reply-To: <6ecc2a84-449f-01f1-0ef7-440e97a9b850@dronecode.org.uk>

Yes, it's the same piping problem of three years ago.

At the time the Geomview community wondered if this was
the shape of things to come for piping and IPC in general,
and if Geomview would need fixing for all platforms.
But since 32-bit and 64-bit Cygwin differed, and OpenGL
didn't work on 64-bit Cygwin either, making 32-bit the
obvious choice to use, masterful inaction was the
result. Wait and see how 64-bit Cygwin shakes out...


Three years on, 64-bit Cygwin is still the outlier;
piping works everywhere else, 32- and 64-bit. It would
be good to have 64-bit Cygwin work with Geomview and
its modules, particularly since 32-bit OpenGL seems less
than reliable (as also shown by the weird things seen
on Raspbian on the Pi).


It would also be good if Geomview was in the Cygwin
installer, as compiling it is not easy for many; it's
already a Debian package.


But I don't personally have the technical piping or
Cygwin-specific knowledge to troubleshoot this one,
other than providing and maintaining the installation
hints at


http://sat-net.com/L.Wood/software/SaVi/building-under-Windows/

thanks

Lloyd Wood
http://savi.sf.net/
(that screenshot comes from 32-bit Cygwin, btw.) 


----- Original Message -----
From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin@cygwin.com
Cc: lloyd.wood@yahoo.co.uk
Sent: Monday, 20 June 2016, 22:58
Subject: Re: [ANNOUNCEMENT] llvm 3.7.1-2

On 10/06/2016 02:18, lloyd.wood@yahoo.co.uk wrote:
> Thanks, picking up 3.7.1-2 from the mirrors.kernel.org site (as it's
> not mirrored everywhere yet) resolved the 32-bit OpenGL crashing
> issues with SaVi and Geomview that I reported in May; texturemapping
> is back.

You're welcome.

> (I've no idea how 64-bit OpenGL is doing, as unique Cygwin piping
> issues there prevent SaVi and Geomview from communicating.)

I guess this is the same 'piping problem' I asked for more details on 
back in [1]?

Can you please provide more information?

[1] https://cygwin.com/ml/cygwin/2013-07/msg00675.html


-- 
Jon Turney
Volunteer Cygwin/X X Server maintainer

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

  reply	other threads:[~2016-06-21  4:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1989991589.1040675.1465521483978.JavaMail.yahoo.ref@mail.yahoo.com>
2016-06-10  1:55 ` lloyd.wood
2016-06-10  2:58   ` Yaakov Selkowitz
2016-06-21  1:44   ` Jon Turney
2016-06-21  7:48     ` lloyd.wood [this message]
2016-06-21 22:19       ` Piping on 64-bit Cygwin was " Warren Young
2016-06-21 22:55         ` Piping on 64-bit Cygwin, STC found Warren Young
2016-06-21 23:00           ` Warren Young
2016-06-22  3:59           ` Andrey Repin
2016-06-22 12:40             ` Warren Young
     [not found] <953793912.12352673.1466549681179.JavaMail.yahoo.ref@mail.yahoo.com>
2016-06-21 23:12 ` Piping on 64-bit Cygwin was Re: [ANNOUNCEMENT] llvm 3.7.1-2 lloyd.wood
2016-06-22  1:35   ` Warren Young
2016-06-22 11:46   ` lloyd.wood
2016-06-22 15:30     ` Marco Atzeri
2016-06-22 16:02       ` Warren Young
2016-06-22 17:17         ` Corinna Vinschen
2016-06-22 18:06           ` Warren Young
2016-06-22 18:40             ` Corinna Vinschen
2016-06-24  7:57               ` cyg Simple
2016-06-24 22:56                 ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1341561944.11163115.1466484828091.JavaMail.yahoo@mail.yahoo.com \
    --to=lloyd.wood@yahoo.co.uk \
    --cc=cygwin@cygwin.com \
    --cc=jon.turney@dronecode.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).