editor poll

Timothy H. Legant tim at catseye.net
Sat Oct 29 16:56:52 PDT 2005

Richard Nyberg <rnyberg at xxxxxxxxxxxxx> writes:

> The lack of complaints about the non working emacs in pkgsrc piqued my
> curiosity. Am I the sole emacs heretic amongst vi users? or do you use
> something even more esoteric? While I do use vi occasionally, I do
> all my programming (and even mail) in emacs.

Nope, you're not the only one, and not the only one who is (was)
frustrated.  I have spent countless hours over the last couple of
months trying to figure out what the problem was.  I've stared at core
dumps that made no sense and tried numerous variations on the build
process, all to no avail.  I end up with an Emacs that works just fine
in a vty or an xterm (with -nw), but segfaults when run as a native X

The clue, it turns out, is the comment in the NetBSD section of the
pkgsrc Makefile, Makefile.common to be precise.  Emacs and an ld newer
than 2.13.<something> do not get along.  You need an additional link
flag to make it happy.

A patch is attached.  This is probably not the right way to solve this
from a pure pkgsrc point of view; it would be best to determine the ld
version from in the Makefile and do the right thing rather than
littering the Makefile with special cases for various operating
systems.  However, I'm new to pkgsrc and have been frustrated for some
time now at not having a working Emacs, so this is my quick-and-dirty

Now to install pkgdiff and start figuring out how to do this right...

Tim Legant
tim at xxxxxxxxxxx

Index: Makefile.common
RCS file: /cvsroot/pkgsrc/editors/emacs/Makefile.common,v
retrieving revision 1.3
diff -u -r1.3 Makefile.common
--- Makefile.common	14 Oct 2005 08:59:50 -0000	1.3
+++ Makefile.common	29 Oct 2005 23:47:19 -0000
@@ -40,6 +40,10 @@
 LDFLAGS+=	-Wl,-z,nocombreloc
+.if ${OPSYS} == "DragonFly"
+LDFLAGS+=	-Wl,-z,nocombreloc
 .if ${OPSYS} == "Darwin"
 PLIST_SUBST+=	FNS_EL="@comment "

More information about the Users mailing list