Re: LZS (STAC) compression in i4b?
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
Curent kernel fails compiling
As of 3:53AM 3/26/99 PST -Current Kernel compiling, it fails at: loading kernel lpt.o: In function `lpt_request_ppbus': lpt.o(.text+0x1c): undefined reference to `ppb_request_bus' lpt.o: In function `lpt_release_ppbus': lpt.o(.text+0x3c): undefined reference to `ppb_release_bus' lpt.o: In function `lptread': lpt.o(.text+0x6b6): undefined reference to `ppb_1284_negociate' lpt.o(.text+0x6f0): undefined reference to `ppb_1284_read' lpt.o(.text+0x726): undefined reference to `ppb_1284_terminate' lpt.o: In function `lptwrite': lpt.o(.text+0x7bb): undefined reference to `ppb_write' ioconf.o(.data+0x664): undefined reference to `lptdriver' *** Error code 1 Stop. Any ideas? Cheers, Vince - vi...@mcestate.com - vi...@gaianet.net __ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[] To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Curent kernel fails compiling
It seems Vincent Poy wrote: Sounds an awfull lot like you are using the old lpt driver which is no longer present in -current. Look in GENERIC | LINT to see how parallel port are handled nowadays As of 3:53AM 3/26/99 PST -Current Kernel compiling, it fails at: loading kernel lpt.o: In function `lpt_request_ppbus': lpt.o(.text+0x1c): undefined reference to `ppb_request_bus' lpt.o: In function `lpt_release_ppbus': lpt.o(.text+0x3c): undefined reference to `ppb_release_bus' lpt.o: In function `lptread': lpt.o(.text+0x6b6): undefined reference to `ppb_1284_negociate' lpt.o(.text+0x6f0): undefined reference to `ppb_1284_read' lpt.o(.text+0x726): undefined reference to `ppb_1284_terminate' lpt.o: In function `lptwrite': lpt.o(.text+0x7bb): undefined reference to `ppb_write' ioconf.o(.data+0x664): undefined reference to `lptdriver' *** Error code 1 Stop. Any ideas? Cheers, Vince - vi...@mcestate.com - vi...@gaianet.net __ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[] To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Curent kernel fails compiling
On Fri, 26 Mar 1999, Soren Schmidt wrote: It seems Vincent Poy wrote: Sounds an awfull lot like you are using the old lpt driver which is no longer present in -current. Look in GENERIC | LINT to see how parallel port are handled nowadays I'm using the GENERIC config file as of 3/16/99 as the base and the same problem still exists... Let me try again... Cheers, Vince - vi...@mcestate.com - vi...@gaianet.net __ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[] As of 3:53AM 3/26/99 PST -Current Kernel compiling, it fails at: loading kernel lpt.o: In function `lpt_request_ppbus': lpt.o(.text+0x1c): undefined reference to `ppb_request_bus' lpt.o: In function `lpt_release_ppbus': lpt.o(.text+0x3c): undefined reference to `ppb_release_bus' lpt.o: In function `lptread': lpt.o(.text+0x6b6): undefined reference to `ppb_1284_negociate' lpt.o(.text+0x6f0): undefined reference to `ppb_1284_read' lpt.o(.text+0x726): undefined reference to `ppb_1284_terminate' lpt.o: In function `lptwrite': lpt.o(.text+0x7bb): undefined reference to `ppb_write' ioconf.o(.data+0x664): undefined reference to `lptdriver' *** Error code 1 Stop. Any ideas? Cheers, Vince - vi...@mcestate.com - vi...@gaianet.net __ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[] To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message -S?ren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
natd broke my make world (990326)
It's more than one days that natd modifications break my make world... Anyone, other than me, has verified it ? (4.0-CURRENT) === sbin/natd cc -nostdinc -O -pipe -Wall -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sbin/natd/natd.c cc -nostdinc -O -pipe -Wall -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sbin/natd/icmp.c gzip -cn /usr/src/sbin/natd/natd.8 natd.8.gz /usr/src/sbin/natd/natd.c:795: conflicting types for `Quit' /usr/src/sbin/natd/natd.h:20: previous declaration of `Quit' /usr/src/sbin/natd/natd.c: In function `Quit': /usr/src/sbin/natd/natd.c:796: warning: passing arg 1 of `Warn' discards `const' from pointer target type /usr/src/sbin/natd/natd.c: At top level: /usr/src/sbin/natd/natd.c:801: conflicting types for `Warn' /usr/src/sbin/natd/natd.h:21: previous declaration of `Warn' *** Error code 1 1 error *** Error code 2 Best Regards, Gianmarco Giovannelli , Unix expert since yesterday http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Spontaneous reboots
Brian Feldman wrote: It could. Ahem... are you absolutely certain there are no messages in /var/log/messages that happen before the reboot? Completely certain, there was nothing in /var/log/all either (which as the name suggests, all syslog messages are written to). -- Ben Smithurst b...@scientia.demon.co.uk send a blank message to ben+...@scientia.demon.co.uk for PGP key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
What to make of the script /usr/src/tools/LibraryReport/LibraryReport.tcl?
Hello, Sorry for posting to two lists...not sure where this should go. I saw an email where someone mentioned this script... how do I make out what this script is telling me and even though this script says a library is stale, does this mean I can remove it??? Also I read someones post about the motherboard not getting enough power and causing things to run slow...how do I check if I fall into this catagory? and if I do fall into it, how do I remedy it? Thanks Michael Mercer mmer...@ipass.net To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
usb modems and usb soundcards??
Since my USB keyboard and mouse are working like a charm , I am looking around for a USB modem and sound card 8) Tnks! Amancio To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
