Date: 26 Oct 1998 18:46:26 -0600 From: Joel Ray Holveck <joelh@gnu.org> To: Chuck Robey <chuckr@mat.net> Cc: "David O'Brien" <obrien@NUXI.com>, Dan Swartzendruber <dswartz@druber.com>, current@FreeBSD.ORG Subject: Re: 3.0 installation problems Message-ID: <86btmyq1b1.fsf@detlev.UUCP> In-Reply-To: Chuck Robey's message of "Sat, 24 Oct 1998 19:04:01 -0400 (EDT)" References: <Pine.BSF.4.05.9810241902150.375-100000@picnic.mat.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> It's not terribly difficult to make it build without X11. A primary
> requirement, however, is to have absolutely NO X11 stuff on your
> machine, because emacs will hunt it down and use X11 if it finds any
> vestiges around.
It's not all that rabid, and can be avoided (see my last paragraph,
below). Emacs's configure relies on a combination of user-specified
paths, xmkmf, X11/Intrinsic.h, and XtMalloc.
If you specify x-includes or x-libraries on the `configure' command
line, then configure takes your word for it. If you don't, then
configure will use xmkmf to find them. If that fails, then it will
look for X11/Intrinsic.h in a list of standard locations, and XtMalloc
in -lXt in a similar list. If locations for both include files and
libraries are found, then Emacs will use X. Otherwise, it won't.
The places checked for X11/Intrinsic.h are:
Your default #include <> path
/usr/{X11,X11R[654]}/include
/usr/include/{X11,X11R[654]}
/usr/local/{X11,X11R[654]}/include
/usr/local/include/{X11,X11R[654]}
/usr/[xX]386/include
/usr/XFree86/include/X11
/usr/include
/usr/{local,unsupported,athena}/include
/usr/local/x11r5/include
/usr/lpp/Xamples/include
/usr/openwin/include
/usr/openwin/share/include
A similar list is used for -lXt.
> If you _have_ any pieces of X11 around, then making emacs ignore it
> is a PITA.
"./configure --without-x" will disable X11 (and its `configure'
checks). You can have X in your default -I and -L paths, and Emacs
will ignore it completely.
Happy hacking,
joelh
--
Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan
Fourth law of programming:
Anything that can go wrong wi
sendmail: segmentation violation - core dumped
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86btmyq1b1.fsf>