Re: Problems with ELF Emacs
Dag-Erling Smorgrav d...@flood.ping.uio.no wrote: Peter Jeremy peter.jer...@auss2.alcatel.com.au writes: I'm running -current from a couple of weeks ago. I recently re-compiled XFree86 to ELF - which works, and re-compiled emacs-19.34b - which won't work with X11, though it does work inside an Xterm. I run an Elf build of Emacs 19.34b daily on a completely Elf, very up-to-date 4.0-CURRENT box with Elf XFree86 3.3.3.1. No trouble at all. I've worked out that emacs is looping in xterm.c:x_make_frame_visible. It is apparently waiting for an input event indicating the the window has been mapped. It expects to get informed of this when a signal (presumably SIGIO) invokes XTread_socket() via input_available_signal(). The only problem is that input_available_signal() never seems to get called. (I haven't been able to track down where F_ASYNC is being set/cleared yet). I'll try another make world next week and see if that helps. Looking into this, I've found a few anomolies: 1) Trying to use the new aout X11 shared libraries reports an undefined ___error. My old shared libraries are OK. I suspect this isn't a major issue. 2) Running an ELF emacs inside gdb, when I set a breakpoint on sigaction, the breakpoint is never hit. Setting a breakpoint on signal and then stepping shows that sigaction (actually _sigaction) is executed - though at a radically different address to the breakpoint. Can one of the ELF experts explain this please. (Not having breakpoints behave as expected is very off-putting). Peter To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Problems with ELF Emacs
Peter Jeremy peter.jer...@auss2.alcatel.com.au writes: I'm running -current from a couple of weeks ago. I recently re-compiled XFree86 to ELF - which works, and re-compiled emacs-19.34b - which won't work with X11, though it does work inside an Xterm. My old aout emacs still works (with old aout libraries - the re-compiled aout libraries seem to be missing a symbol). I run an Elf build of Emacs 19.34b daily on a completely Elf, very up-to-date 4.0-CURRENT box with Elf XFree86 3.3.3.1. No trouble at all. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Problems with ELF Emacs
%I'm running -current from a couple of weeks ago. I recently re-compiled %XFree86 to ELF - which works, and re-compiled emacs-19.34b - which won't %work with X11, though it does work inside an Xterm. My old aout emacs %still works (with old aout libraries - the re-compiled aout libraries %seem to be missing a symbol). % %When running as an X11 client, emacs opens the window and then nothing %happens. Looking at a ktrace, it seems to be continuously sending %GetInputFocus commands to the X-server, which are being correctly %replied to (as far as I can tell). % %I haven't bumped into this problem with any other X clients. % %Has anyone else seen this, or have any ideas? Yes, and no. It happens for me only with an ssh1 forwarded xterm, with whatever the most recent emacs2 is. Checked, and fails with emacs19. Elf emacs works fine on a local xterm. Xemacs works fine. Everything else does too. At that point, I started exporting filesystems. Russell %Peter % % %To Unsubscribe: send mail to majord...@freebsd.org %with unsubscribe freebsd-current in the body of the message % To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
