I'm attempting to compile Geomview, which depends on Motif, and requires
Xm/Xm.h to compile.
So, installed openmotif 2.34-3 package and source.There's an /etc/X11/mwm so
something must have been installed. But where are the headerfiles (Xm/Xm.h
etc.) hiding? Not in the usual places; configure ca
shouldn't the texinfo package be a dependency that gets pulled in for the
texinfo-tex package?
It doesn't seem to be (on 64-bit cygwin).
thanks
Lloyd Wood
http://www.geomview.org/
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documenta
Today I built geomview-related things on two separate machines running 64-bit
cygwin.
They exhibit different behaviours around fonts. On one, I had
to install a bunch of different TeX stuff (texlive-collection-
fontsrecommended, -basic, -latex) to get geomview documentation
to build. On the other
I'm having trouble with pulling from cvs under 64-bit cygwin.
I have parallel 32-bit and 64-bit cygwin installs on a Win7 Enterprise machine.
Under 32-bit cygwin, I do this all the time:
cvs -z3 -d:ext:lloydw...@savi.cvs.sourceforge.net:/cvsroot/savi co savi-dev
and quite happily; type passw
> > CVS_RSH="ssh"; export CVS_RSH
>
> Good call. I set CVS_RSH in my .bash_profile so long ago I forgot about it.
>
> This probably explains why the OP sees the problem change when moving from
> Cygwin
> 32 to Cygwin 64: he probably doesn't use the same shell startup scripts in
> both cases.
Have there been any changes to OpenGL libraries in 32-bit cygwin in the last
six months?
The opengl application I use (geomview 1.9.5) is now crashing on an uptodate
Cygwin where it worked previously. (Can't compare with previous Cygwin install
- had to replace drive)
It runs without texturema
> It seems still the same problem with dri-drivers
> https://sourceware.org/ml/cygwin/2016-04/msg00283.html
>
> probably caused by LLVM 3.7
Unfortunately, the dri-driver versions available in the installer
depend on LLVM 3.7, so, even though reverting back to LLVM 3.5
is offered when you select
http://www.redhat.com/services/custom/cygwin/support/
OpenGL and drivers are not on the supported list.
I suppose cygwin problems will all be moot once the
Windows 10+Canonical Ubuntu is well-established, but we're not there yet.
https://insights.ubuntu.com/2016/03/30/ubuntu-on-windows-the-ubuntu-
It's odd, the amount of extra support that Cygwin needs.
Okay, OpenGL is broken in 32-bit cygwin, not for the first
time.
I'm unsure if OpenGL is broken in 64-bit cygwin, because
the piping my applications use is broken in 64-bit cygwin -
and only there. Not in any other linux or unix I've run on
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.
(I've no idea how 64-bit OpenGL is doing, as unique Cygwin piping issues there
prev
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-bi
Warren,
this piping problem on 64-bit Cygwin between Geomview and its modules (of which
SaVi is the most used example) is entirely unrelated to OpenGL, and exists when
Geomview is compiled without OpenGL.
Three years ago, 64-bit OpenGL not yet working at all was simply motivation to
see how th
>>I've reproduced this SaVi-can't-talk-with-Geomview-on-64-bit-cygwin problem
>>on multiple installs
> How, exactly? Give me the step-by-step.
Step by step instructions to build Geomview and SaVi are on:
http://sat-net.com/L.Wood/software/SaVi/building-under-Windows/
launch with
geomview -r
> I seem to have stumbled upon the actual STC.
That is not the STC for SaVi and Geomview under 64-bit Cygwin.
The problem for SaVi and Geomview is in INITIALISING any
piping, as previously described. They simply cannot communicate
at all under 64-bit Cygwin, while they can under 32-bit Cygwin.
I'd like to understand Cygwin's installation and
security models better:
- Cygwin's installers aren't signed.
- downloads are from a number of untrusted mirrors
via http/ftp, and packages aren't verified.
Is this correct?
thanks
Lloyd Wood lloyd.w...@yahoo.co.uk http://savi.sf.net/
--
P
Specifically, when I launch Cygwin's setup.exe, I am warned:
"Do you want to allow this app from an unknown publisher to
make changes to your system?"
That code could be anything. I think that means that
if your website gets hacked, and the setup binaries
get replaced, everyone is in trouble. Com
A viewpoint on this whole Windows Ubuntu Frankenstein hybrid vs Cygwin thing:
In comparison with the difficulties trying to build Geomview under 64-bit
Cygwin,
then discovering the piping issues that prevent it working with modules, using
the Windows Ubuntu subsystem to install pre-existing Ubunt
In Cygwin's supplied cvs package:
$ cvs --version
Concurrent Versions System (CVS) 1.11.23 (client/server)
Copyright (C) 2006 Free Software Foundation, Inc.
[..]
This seems to be an older version of cvs, and SourceForge's cvs server won't
always interoperate with it to do e.g. the cvs remo
18 matches
Mail list logo
