help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GNU NTEmacs and X


From: FRC
Subject: Re: GNU NTEmacs and X
Date: Sun, 3 Aug 2003 13:41:05 +0200

I indeed would like to be able to run un-cygwinized NTEmacs both with X and
no X.
The pb with cygwinized Emacs is for instance that it doesn't deal with NT
paths eg. C:\foo\bar. I can work around that wirh /cygdrive or a /c mount
point, but I'd rather not. I don't want it to pretend to be on *NIX, but
rather to be able to understand *NIX world.
BTW, I got a strange error when trying to build NTEmacs from CVS sources
with cygwin (make bootstrap)
-----------------------------------
gcc -c -I/usr/share/gettext   -Demacs -DHAVE_CONFIG_H -DUSE_LUCID  -I. -I/ho
me/FRC/emacs/src -I/usr/share/gettext -I/usr/X11R6/include -g xterm.c
xterm.c: In function `x_create_toolkit_scroll_bar':
xterm.c:4488: `XtNbeNiceToColormap' undeclared (first use in this function)
xterm.c:4488: (Each undeclared identifier is reported only once
xterm.c:4488: for each function it appears in.)
make[1]: *** [xterm.o] Error 1
make[1]: Leaving directory `/home/FRC/emacs/src'
make: *** [bootstrap] Error 2

-----------------------------------
Googled a bit but didn't find anything. I got almost all latest cygwin
packages (apart from games etc...).

Rookie Q: what's that DOC file used for?

FRC

<jasonr (Jason Rumney) @ f2s.com> a écrit dans le message de
u7k5wgs7p.fsf@jasonrumney.net">news:u7k5wgs7p.fsf@jasonrumney.net...
> Eric Hanchrow <offby1@blarg.net> writes:
>
> > I've had trouble (whose details I forget) sharing byte-compiled Lisp
> > between the NT and Cygwin versions of Emacs.
>
> Were they different versions?  There should be no difference in byte
> format between different platforms. I have successfully shared lisp
> directories between Windows and GNU/Linux installations for years.
> And recently someone fixed the DOC file differences between *nix and
> W32, so the CVS version should be able to share that without problems
> as well.
>




reply via email to

[Prev in Thread] Current Thread [Next in Thread]