2:37 p.m.
Hello
I tried to use xemacs in a tty, either in Mac or in Linux,
together with LaTeX mode (auctex).
I used xemacs -vanilla -nw
However when I try to turn on LaTeX mode the following error
appeared:
(1) (file-mode-spec/warning) Error in File mode specification: Invalid
argument: Must be string, vector, or font-instance, ((underline)
(highlight) (dim) (blinking) (reverse))
Now this issues was discussed three years ago in
http://comments.gmane.org/gmane.emacs.xemacs.beta/31124
and Steve Turnbull submitted a patch for faces.el
Now this patch seems to have been applied only to 21.5.X and
in fact using 21.5.X (in Linux) everything is fine.
I tried to use face.el from 21.5 in 21.4 but byte compiling
gave me the following error:
While compiling Face-frob-property:
!! Wrong type argument ((listp wed\.))
And it seems that Face-frob-property which causes the
problem with LaTeX and it seems that 21.5.X and 21.4.X are
incompatible concerning faces.el.
So is possible to have a solution for 21.4.X as well?
The other possibility would be to compile 21.5.X for Mac
(using X11).
I have never done this and have two questions:
- The required libraries. Debian has the following
nice command:
apt-get build-dep xemacs21
Does port provide a similar functionality?
- How to generate a pkg? In debian I run
auto-apt run ./configure
make
and then sudo checkinstall
Does port provide a similar functionality?
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
5:07 p.m.
On Tue, Sep 4, 2012 at 9:37 AM, Uwe Brauer <oub(a)mat.ucm.es> wrote:
[...]
The other possibility would be to compile 21.5.X for Mac
(using X11).
I have never done this and have two questions:
- The required libraries. Debian has the following
nice command:
apt-get build-dep xemacs21
Regarding your question about 21.5 on OS X, here are the libraries for
Lion or Mountain Lion for 21.5
/Users/royar/usr/local/bin/xemacs:
/usr/lib/libncurses.5.4.dylib (compatibility version 5.4.0,
current version 5.4.0)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current
version 1.2.5)
/opt/X11/lib/libpng15.15.dylib (compatibility version 27.0.0,
current version 27.0.0)
/opt/X11/lib/libXpm.4.dylib (compatibility version 16.0.0,
current version 16.0.0)
/opt/X11/lib/libXft.2.dylib (compatibility version 6.0.0,
current version 6.1.0)
/opt/X11/lib/libXrender.1.dylib (compatibility version 5.0.0,
current version 5.0.0)
/opt/X11/lib/libXt.6.dylib (compatibility version 7.0.0,
current version 7.0.0)
/opt/X11/lib/libXext.6.dylib (compatibility version 11.0.0,
current version 11.0.0)
/opt/X11/lib/libX11.6.dylib (compatibility version 10.0.0,
current version 10.0.0)
/opt/X11/lib/libSM.6.dylib (compatibility version 7.0.0,
current version 7.1.0)
/opt/X11/lib/libICE.6.dylib (compatibility version 10.0.0,
current version 10.0.0)
/opt/X11/lib/libfontconfig.1.dylib (compatibility version
7.0.0, current version 7.0.0)
/opt/local/lib/libtiff.3.dylib (compatibility version 13.0.0,
current version 13.5.0)
/opt/local/lib/libjpeg.8.dylib (compatibility version 13.0.0,
current version 13.0.0)
/opt/local/lib/libesd.0.dylib (compatibility version 3.0.0,
current version 3.39.0)
/opt/X11/lib/libXaw3d.8.dylib (compatibility version 9.0.0,
current version 9.0.0)
/opt/X11/lib/libXmu.6.dylib (compatibility version 9.0.0,
current version 9.0.0)
/opt/local/lib/libgmp.10.dylib (compatibility version 11.0.0,
current version 11.4.0)
/opt/local/lib/libgdbm.4.dylib (compatibility version 5.0.0,
current version 5.0.0)
/opt/local/lib/libintl.8.dylib (compatibility version 10.0.0,
current version 10.1.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0,
current version 169.3.0)
I think you will need /opt/local/lib/libintl.8.dylib (which I have
from Macports). The other /opt/local/lib graphics libraries are also
probably needed. The esd sound library, the big-num library libgmp,
and libgdbm may not be needed for your configuration. You also need to
have XQuartz installed which is easiest if you get it directly from
macosforge. The /opt/X11/lib files are from the macosforge installed
XQuartz. That is the current version of X11's libraries provided by
Apple as third-party installation. You can also get them from
macports, but I find the macosforge DMG much more convenient.
Does port provide a similar functionality?
1. Install XQuartz
2. Install the most recent XCode for your OS, including the
command-line tools. (needed to install and run macports port)
3. Install macports
4. Issue the command
port selfupdate
(to get the latest port files)
5. Issue the command
port install tiff jpeg gettext
(for the graphics and libintl)
port is likely to install a number of prerequisites including some
that may be needed only to build.
To compile XEmacs, you may need to tell cpp to look in the correct
include directories. I use the following environment variables:
export CPPFLAGS="-I/opt/local/include -I/opt/X11/include
-I/opt/X11/include/freetype2"
export LDFLAGS='-L/usr/lib -lncurses -lz -L/opt/X11/lib -lpng -lXpm
-lXft -lXrender -lXt -lXext -lX11 -lSM -lICE -lfontconfig
-L/opt/local/lib -ltiff -ljpeg -lesd'
Here is my configure command:
./configure --with-mule --with-gcc \
--with-scrollbars=lucid --with-widgets=athena --with-athena=3d
--with-dialogs=athena \
--prefix=${ParentPath} --with-png --with-jpeg --with-tiff \
--with-xim=no --enable-sound=none,esd --disable-xfs \
--with-compiler=gcc --with-pdump \
--disable-kkcc --without-ipv6-cname --without-ldap --without-postgresql \
--x-includes=/opt/X11/include --x-libraries=/opt/X11/lib \
--with-xft=emacs,gauges,tabs --with-union-type --with-bignum=gmp \
--without-error-checking --with-dynamic --enable-dump-in-exec
With Mountain Lion, I had to add
export CC=/usr/bin/gcc so as not to invoke clang
BTW $ParentPath is /Users/royar/usr/local
I hope this helps.
--
Robert Delius Royar
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
3:44 a.m.
Uwe Brauer writes:
Does port provide a similar functionality?
MacPorts 11:12$ port deps xemacs
Full Name: xemacs ＠21.4.22_6
Build Dependencies: xbitmaps
Library Dependencies: libpng, Xaw3d, ncurses, gdbm, jpeg, tiff, compface,
gettext, zlib, xorg-libXaw
Personally I add gmp, openldap, postgresql$VERSION, fontconfig, and
Xft2 to that list of library dependencies.
> - How to generate a pkg? In debian I run [...]
Does port provide a similar functionality?
No. You can copy the Portfile to a new port (xemacs-devel is probably
the best name, see below), remove any patches (since they probably
won't apply to XEmacs 21.5), change the names of the download files,
and remove the checksums. Change the port revision number to 0.
Change the download location to xemacs-21.5.
Do port uninstall xemacs, you'll get "multiple ports claim files"
errors otherwise for a few files like the xemacs binary and etags.
Working around this is possible but more work than I want to explain
at the moment.
Do port install xemacs-devel. If this works, you're good. It may
fail, either immediately (because there are no checksums) or at fetch
stage (ditto). If so, use "for i in rmd160 sha1 md5; do openssl $i
xemacs-$VERSION.tar.gz; done" to get the checksums, and add them to
the portfile. The xemacs tarball is in the Macports download area
(for me that would be /opt/local/var/macports/distfiles/xemacs-devel).
I'll provide checksums in xemacs-$VERSION.checksums starting from the
next release.
For extra points, it's possible to use a VCS to get bleeding-edge
sources, but I've not written such a Portfile, so I can't help with
that offhand. I believe it's possible to have local Portfiles so you
don't need to mess around in the MacPorts tree, but again, I've not
done that so I can't really help.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
11:34 a.m.
New subject: uninstall monitor the installation (was: Problems: tty fonts; latex mode; xemacs -nw; xemacs.21.4.22)
> On Wed, 05 Sep 2012 11:44:35 +0900, "Stephen J.
Turnbull"
> <stephen(a)xemacs.org> wrote:
> - How to generate a pkg? In debian I run [...]
> Does port provide a similar functionality?
No. You can copy the Portfile to a new port
(xemacs-devel is probably the best name, see below),
remove any patches (since they probably won't apply to
XEmacs 21.5), change the names of the download files,
and remove the checksums. Change the port revision
number to 0. Change the download location to
xemacs-21.5.
[snip]
Hm that looks rather complicated. (I am not a MacUser, it is
for a friend).
Could I just run ./configure && make && make install, which
would end xemacs installed in /usr/local.
Would that cause a problem with the official port xemacs?
The problem is that our Makefile does not provide any
*uninstall* option.
In linux there were a couple of installation trackers which
allowed you then to install software, without creating a pkg
(not a very clean way I admit)
I could run make -n install and try to generate a uninstall
command myself.
But I would prefer something more sophisticated.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
1:45 p.m.
New subject: uninstall monitor the installation (was: Problems: tty fonts; latex mode; xemacs -nw; xemacs.21.4.22)
Uwe Brauer writes:
Could I just run ./configure && make && make install,
which
would end xemacs installed in /usr/local.
Sure. If you're going to "borrow" the packages installed by the
MacPorts port, give ./configure the --with-system-packages=$ROOT,
where ROOT is the directory containing {xemacs,mule,site}-packages
directories. Probably it's /opt/local/share/xemacs.
Check that /usr/local/bin is on PATH.
Would that cause a problem with the official port xemacs?
No, unless your MacUser friend put MacPorts in /usr/local. But that
seems very unlikely. And if they did, you can just put XEmacs
somewhere else, for example --prefix=/usr/local/xemacs. This also has
the benefit that if the prefix is used only for that version of
XEmacs, uninstall is just rm -rf /usr/local/xemacs.
If you do this, you need to add /usr/local/xemacs/bin to PATH.
Steve
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
2:39 p.m.
New subject: uninstall monitor the installation (was: Problems: tty fonts; latex mode; xemacs -nw; xemacs.21.4.22)
Before mixing /usr/local with macports, read all the warnings from the
macports wiki. You have to be pretty careful because so many tools
will find the wrong libraries as a result (wrong being the ones not
installed by macports).
On Wed, Sep 5, 2012 at 8:45 AM, Stephen J. Turnbull <stephen(a)xemacs.org> wrote:
Uwe Brauer writes:
> Could I just run ./configure && make && make install, which
> would end xemacs installed in /usr/local.
Sure. If you're going to "borrow" the packages installed by the
MacPorts port, give ./configure the --with-system-packages=$ROOT,
where ROOT is the directory containing {xemacs,mule,site}-packages
directories. Probably it's /opt/local/share/xemacs.
Check that /usr/local/bin is on PATH.
> Would that cause a problem with the official port xemacs?
No, unless your MacUser friend put MacPorts in /usr/local. But that
seems very unlikely. And if they did, you can just put XEmacs
somewhere else, for example --prefix=/usr/local/xemacs. This also has
the benefit that if the prefix is used only for that version of
XEmacs, uninstall is just rm -rf /usr/local/xemacs.
If you do this, you need to add /usr/local/xemacs/bin to PATH.
Steve
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
8:48 p.m.
New subject: uninstall monitor the installation (was: Problems: tty fonts; latex mode; xemacs -nw; xemacs.21.4.22)
Robert Royar writes:
Before mixing /usr/local with macports, read all the warnings from
the
macports wiki. You have to be pretty careful because so many tools
will find the wrong libraries as a result (wrong being the ones not
installed by macports).
True, and I'm sure that's one reason why Uwe wants to make a package
if possible. But it's not a problem for XEmacs, really, because
XEmacs only consumes libraries, it doesn't provide them.
Steve
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
10:32 p.m.
New subject: uninstall monitor the installation (was: Problems: tty fonts; latex mode; xemacs -nw; xemacs.21.4.22)
Sent from my iPod
On 05/09/2012, at 21:48, "Stephen J. Turnbull" <stephen(a)xemacs.org>
wrote:
>
True, and I'm sure that's one reason why Uwe wants to make a package
if possible. But it's not a problem for XEmacs, really, because
XEmacs only consumes libraries, it doesn't provide them.
Steve
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
The other reason is to uninstall it later if needed. Would it be hard
to provide an uninstall option in our makefile(in)?
In my understanding automake provides this. But May be automake does
not run on all unix like platform
Xemacs supports.
Uwe
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
1:38 a.m.
New subject: uninstall monitor the installation (was: Problems: tty fonts; latex mode; xemacs -nw; xemacs.21.4.22)
Uwe Brauer writes:
The other reason is to uninstall it later if needed. Would it be hard
to provide an uninstall option in our makefile(in)?
Yes, it would be hard. First, Makefiles are a terrible way to provide
uninstall. For example, both Emacs and XEmacs provide etags. How do
you know the etags in /usr/bin is yours? Really, you need global
information about other packages. Second, it would require careful
maintenance basically forever.
This is the first of three reasons why almost no large application
provides uninstall in the Makefile. The second is that package
managers do the job *much* better. The third is that
--prefix=/usr/local/this-xemacs-only is easy to do and requires no
uninstall command (rm -rf $prefix works fine).
In my understanding automake provides this.
Maybe it does, but (a) I'm sure it doesn't take into account issues
like multiple packages trying to install the same file, and (b)
XEmacs's build process isn't automake-compatible. I guess it would
take substantial effort to make it so. I think I can contribute more
effectively by doing something else for XEmacs for the foreseeable
future.:-) But as usual, "patches welcome!" ;-)
Steve
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
4248
days inactive
4250
days old
8 comments
3 participants
participants (3)
-
Robert Royar -
Stephen J. Turnbull -
Uwe Brauer