Bug#684788: emacs24-lucid: segfaults on startup

2013-05-29 Thread Kevin Ryde
I suspect this may have to do with -Wl,-znocombreloc. If I change the debian/rules to LDFLAGS = $(shell dpkg-buildflags --get LDFLAGS) -Wl,-znocombreloc then the emacs24-lucid package works. The emacs configure checks for and adds -Wl,-znocombreloc to LDFLAGS. But the way the build_cmd

Bug#684788: emacs24-lucid: segfaults on startup

2013-04-25 Thread Kevin Ryde
This bug happens for me too with 24.3+1-1. (Though emacs23-lucid is ok.) gdb suggests that the superclass field in emacsFrameClassRec is some wild pointer value, not the intended widgetClassRec, causing XtInitializeWidgetClass() to crash when it follows to the superclass. The superclass field

Bug#676424: Bug#454778: emacsen-common: load-path order vs debian-run-directories

2012-12-06 Thread Kevin Ryde
Rob Browning r...@defaultvalue.org writes: # The version-specific site-lisp dir, say emacs/21.1/site-lisp, needs # to be in share/FLAVOR so that as we upgrade from 21.1 to 21.2, # etc., add-on package bits don't get left behind. Hmm. I suppose if an add-on is removed

Bug#676424: Bug#454778: emacsen-common: load-path order vs debian-run-directories

2012-12-03 Thread Kevin Ryde
Rob Browning r...@defaultvalue.org writes: investigate our load-path handling more carefully, perhaps even more so, given that Emacs has changed its behavior over the past couple of major releases -- but I also think that it's probably not something that we should attempt right now, this

Bug#676424: Bug#454778: emacsen-common: load-path order vs debian-run-directories

2012-12-01 Thread Kevin Ryde
Rob Browning r...@defaultvalue.org writes: It's not the list spine I'm trying to copy, but the string objects Ah, I see. Yes that might be prudent, though the flavor-dir one coming in is a fresh concat. I suppose one argument for keeping the symlink is the possibility that Emacs or add-on

Bug#676424: Bug#454778: emacsen-common: load-path order vs debian-run-directories

2012-11-30 Thread Kevin Ryde
Rob Browning r...@defaultvalue.org writes: (let* ((paths (mapcar copy-sequence dirs)) ; Ensure we have unique objects. In debian-run-directories? I suspect its rest makes dirs a fresh list anyway. Incidentally, one thing I never understood was why load-path has entries for both

Bug#676424: emacsen-common: debian-startup puts items before /usr/local directories in load-path, violating policy

2012-06-10 Thread Kevin Ryde
Hendrik Tews hend...@askra.de writes: (Yes, Coq and Proof General should not use the same Emacs feature name for different packages. Oh, I see they're not really different, just the coq one is smaller and maybe older. For the debian packages I'd suggest proofgeneral could supercede the coq

Bug#676424: emacsen-common: debian-startup puts items before /usr/local directories in load-path, violating policy

2012-06-06 Thread Kevin Ryde
Hendrik Tews hend...@askra.de writes: (setq load-path (append add-on-package-paths old-load-path)) This was recently (recently!) noted in bug 117564. I made a report a time after too, missing the earlier one, as bug 454778. This makes the requirement in the Debian Emacs policy

Bug#582410: (Fwd) Bug#582410: libgtk2-perl: FTBFS on mips: Failed test 'callbacks encountered'

2010-07-22 Thread Kevin Ryde
muppet sc...@asofyet.org writes: This behavior implies that there are cases in which the cell renderer is never being asked to draw itself. In some of my own tests I wait for map-event before checking certain callbacks and settings, because a window manager can delay map and expose for an

Bug#300146: guile-1.6: FTBFS (amd64/gcc-4.0): array type has incomplete element type

2006-01-13 Thread Kevin Ryde
Andreas Jochens [EMAIL PROTECTED] writes: - extern const scm_lt_dlsymlist lt_preloaded_symbols[]; + extern const scm_lt_dlsymlist *lt_preloaded_symbols; As noted under bug 326527, this is incorrect. It happens to work because the first entry in the array is NULL, but the thing to do to