I am in the middle of rebuilding Cygwin/XFree86 for Cygwin 1.5.4.
I wanted to check with others about the list of packages that should be
updated for the Cygwin 1.5.4 rebuild. Currently, I am thinking that the
following packages need to be updated:
1) XFree86-bin
2) XFree86-fsrv
3)
Harold L Hunt II [EMAIL PROTECTED]:
Perhaps Test99/4.3.0-9 fixes your problem?
Nope. I did an update today, and the AltGr button still misbehaves.
I ran xev and pressed and released AltGr. Here's the result:
KeyPress event, serial 17, synthetic NO, window 0x101,
root 0x3a, subw 0x0,
Alexander Gottwald wrote:
On Tue, 16 Sep 2003, Harold L Hunt II wrote:
I am in the middle of rebuilding Cygwin/XFree86 for Cygwin 1.5.4.
I wanted to check with others about the list of packages that should be
updated for the Cygwin 1.5.4 rebuild. Currently, I am thinking that the
following
You don't have any of the Windows PowerToys installed, do you?
Harold
Steinar Bang wrote:
Harold L Hunt II [EMAIL PROTECTED]:
Perhaps Test99/4.3.0-9 fixes your problem?
Nope. I did an update today, and the AltGr button still misbehaves.
I ran xev and pressed and released AltGr. Here's the
On Tue, 16 Sep 2003, Harold L Hunt II wrote:
XFree86-lib doesn't actually have any libraries or binaries in it:
The name fooled me to believe that it contains libraries.
I would leave it as it is now. Only 4.2 programs are still linked
with the old dll and every program which was
Yamin Bismilla wrote:
I've been reading the thread: Re: xdvi: SIGSEGV in XtInitialize
Is this the same problem I am having.
Yes.
Using the 1.5 cygwin and X is the problem. If it is, is there a
workaround?
Wait until Harold recompiles XFree for 1.5.x (I believe he is doing that
now), or
Hi
I'm using almost the default startxwin.bat with the following:
start XWin -emulate3buttons
run xterm -ls -sl 1000 -sb -rightbar -ms red -fg yellow -bg black -e
/usr/bin/bash
Funnily enough, the xterm I get did NOT run bash as a login shell (the -ls
option), as my ~/.bash_profile hasn't been
This is because you are actually using two shells. The first is what is run
by xterm and honors the -ls. The second is run from the first and does not.
What should work is putting a -l after the bash you are running as the
command (ie. run xterm -ls -sl 1000 -sb -rightbar -ms red -fg yellow -bg
I am new in Xfree86 , I use many Xwin windows with the comman xwin :XX
-query hostname . It works fine but the window gets a permanent nam
Xfree86 PORTNUM is there a way to change this to display something
meaningful such as the host name for example .
Thank You
On Tue, 16 Sep 2003, amr roushi wrote:
I am new in Xfree86 , I use many Xwin windows with the comman xwin :XX
-query hostname . It works fine but the window gets a permanent nam
Xfree86 PORTNUM is there a way to change this to display something
meaningful such as the host name for example
To anyone that has entered bugs in XFree86'd Bugzilla (especially
Alexander Gottwald), please add my email address as a CC in each of your
open bugs. I can check the status of these bugs and make sure that
someone commits them.
Harold
Harold L Hunt II [EMAIL PROTECTED]:
You don't have any of the Windows PowerToys installed, do you?
Not intentially.
Can they be installed during a service pack upgrade? Can they be
remotely installed by helpful IT support people? Is there a way to
find out if I have them installed?
And do
Nicholas,
I was wondering how fontconfig and freetype2 were coming along?
I have used the following two suggestions in my build for Cygwin 1.5.4:
Ditch -DNO_ALLOCA and replace with -DINCLUDE_ALLOCA_H for
AllocateLocalDefines.
Ditch -DUSE_XWCHAR_STRING -DUSE_XMBTOWC and use -DHAS_WCHAR_H
I've recently been motivated to tinker a bit with compiling XWin.exe on my
own. After reading through the Obtaining the Source Code and Native
Compiling sections of the Contributor's Guide, I'm left with the following
question ...
Do I rally need to download and build all of XFree86? Can't I
Brian Ford writes:
Sorry to be so tearse. Let me explain.
The Xt library has not yet been compiled under Cygwin 1.5.x. Until it is,
it is unsafe for use by apps compiled under 1.5.x. This is a side effect
of the 64 bit implementation method choice.
Does that help, or is it still to
I don't believe this is X-specific, but it may be, hence the
cross-post...
I recently upgraded my Cygwin install (to get a new version of the
XFree86-xserv package). I went ahead and let it upgrade everything to
the latest packages. All in all, it seems to have gone well, but I have
one strange
The following packages have been updated in the Cygwin distribution:
*** XFree86-bin-4.3.0-3
*** XFree86-fsrv-4.3.0-2
*** XFree86-nest-4.3.0-2
*** XFree86-prog-4.3.0-5
*** XFree86-prt-4.3.0-2
*** XFree86-vfb-4.3.0-2
*** XFree86-xserv-4.3.0-10
Changes
===
1) General - Recompile all libraries
Ralf Habacker sent some patches on 2003/09/05 that I am working on
getting committed to the XFree86 CVS tree. Those two patches are here:
http://cygwin.com/ml/cygwin-xfree/2003-09/msg00092.html
http://cygwin.com/ml/cygwin-xfree/2003-09/msg00090.html
I have opened Bug 698 in XFree86's Bugzilla
18 matches
Mail list logo