So perhaps what you need to do is uninstall the dpi100 font package?
Just to confirm - I removed the 100dpi fonts, and now my display is back
to what it was before the recent major X update.
Unfortunately, Cygwin thinks other installs are dependent on the the
100dpi fonts, so on any update I'll
James Ferguson wrote:
So perhaps what you need to do is uninstall the dpi100 font package?
Just to confirm - I removed the 100dpi fonts, and now my display is back
to what it was before the recent major X update.
Unfortunately, Cygwin thinks other installs are dependent on the the
100dpi
James Ferguson wrote:
But anyway, when my Emacs fails, it does not trigger the breakpoint. My
xterm gave me a BadAlloc, but the Solaris patch fixed that.
My instructions were really aimed at investigating the XkbSetNamedIndicator
problem, and the report that installing the Solaris patches
If you use my pre-built binary you only need to have the cygwin source
package installed and cygwin prep'ed, you don't need all of it's build
dependencies as well.
Jon, the probem is that xorg-server-1.5.3-4/build/hw/xwin/.libs does
not exist because of the build failure I sent you
If you're building emacs yourself, you might try to ./configure it
--without-xim to see if that makes a difference, or if it just fails
in a different place.
That worked - Thank you... Now I can run Emacs (from the non-production
Solaris machine I'm allowed to patch).
Now I'm just trying to
James Ferguson wrote:
If you're building emacs yourself, you might try to ./configure it
--without-xim to see if that makes a difference, or if it just fails
in a different place.
That worked - Thank you... Now I can run Emacs (from the non-production
Solaris machine I'm allowed to patch).
TOY Richard wrote:
Jon
First problem is something to do with permissions.
[EMAIL PROTECTED] /usr/src
$ cygport xorg-server-1.5.3-4.cygport prep compile
[...]
Compiling xorg-server-1.5.3-4
autoreconf-2.63: Entering directory `.'
autoreconf-2.63: configure.ac: not using Gettext
What is the failure mode for running emacs on an unpatched Solaris?
Same before and after the patch (the almost immediate BadAtom error).
However, before the patch, when I ran an xterm it displayed, but the
first keystroke made it crash with BadAlloc. After the patch, xterm
appears to run
James Ferguson wrote:
What is the failure mode for running emacs on an unpatched Solaris?
Same before and after the patch (the almost immediate BadAtom error).
Are you sure that the stack trace points back to XCreateIC() in an emacs built
--without-xim run on an unpatched Solaris?
Some confusion...
Are you sure that the stack trace points back to XCreateIC() in an
emacs built --without-xim run on an unpatched Solaris?
No - built --without-xim, on a patched Solaris, it doesn't crash any
more _at all_, my only problem is fonts. I'll try getting rid of the
100dpi fonts.
Hi
We get all the same issues described in [1].
Furthermore, installing the Solaris patch mentioned in [2] made *NO*
difference (we are using Solaris 9).
Some applications half work e.g. xclearcase does not crash but
keyboard inputs into some dialogue boxes are ignored.
Other appications e.g.
@cygwin.com
Subject: RE: X11 apps failing after upgrade
Hi
We get all the same issues described in [1].
Furthermore, installing the Solaris patch mentioned in [2] made *NO*
difference (we are using Solaris 9).
Some applications half work e.g. xclearcase does not crash but
keyboard inputs into some
Richard Toy wrote:
Hi
We get all the same issues described in [1].
Furthermore, installing the Solaris patch mentioned in [2] made *NO*
difference (we are using Solaris 9).
:-(
Any suggestions as to how to progress this issue further?
If you are willing to do some further investigation,
Jon TURNEY wrote:
If you are willing to do some further investigation, it would be a great
help if you could:
* build the X server from source with debugging enabled
(no, don't run away! the autotoolized modular server is much easier to
work with the monolithic imaked monstrosity)
Thanks for the build, because I couldn't get the build to work. I
double checked I'd installed everything (Cygwin installer needs command
line option!). Something to do with autoconf I think:
checking build system type... config.sub: missing argument
Try `config.sub --help' for more
All help gratefully received! I haven't found this problem through
searches, apologies if I've been searching for the wrong terms.
In my first update in a few months I picked up the major upgrade to the
X server. XWin -version now reports 1.5.3.0. After having the problems
below I did a full
James Ferguson wrote:
My client machine is Solaris. Everything worked fine before the update.
I'm running the installed startxwin.bat startup (with xterm REM'd out).
I can display xclock fine. xterm appears up, but as soon as I hit a key
it crashes with:
$ xterm
xterm: warning, error
17 matches
Mail list logo
