GCC 2.95.2 testing
Hi all,
I've got GCC 2.95.2 working as the base compiler. It is still a little
rough, but I wanted to put it in more hands for testing.
My Alpha is booting from a GENERIC kernel and world built from gcc
2.95.2. This is one compiler bug in building libreadline, but I have a
hack around it.
The i386 doesn't fair as well. GENERIC can only be compiled if `ahc0' is
removed. This is a call to IA-32 ASM experts to find a fix.
I have made two sets of files available:
ftp://relay.nuxi.com/pub/FreeBSD/gcc2952-991004.tar.gz
ftp://relay.nuxi.com/pub/FreeBSD/gcc2952-991004-sidelines.tar.gz
To use ether fetch them and then cd into your version of `/usr/src' and
then untar them.
`gcc2952-991004' will overwrite your current src/gnu/usr.bin/cc/ and
src/gnu/lib/ contents. Using this dist, you can do a full `make world'
and wind up with gcc 2.95.2 as your base compiler and the world built
with it.
`gcc2952-991004-sidelines' will not overwrite any of your existing files.
To build it simply:
cd /usr/src/gnu/usr.bin/cc.gcc2952
make obj
make depend all install
cd /usr/src/gnu/lib
make -f Makefile.gcc2952 obj
make -f Makefile.gcc2952 depend all install
Note that this will replace your existing compiler with gcc 2.95.2. So
YOU MIGHT WANT TO BACKUP YOUR EXISTING EGCS 1.1.2 COMPILER. The files
you'll want to back up are /usr/bin/{cc,c++} /usr/libexec/{cpp,cc1*,f771}
/usr/lib/libg2c* /usr/lib/libgcc* /usr/lib/libstdc++.* /usr/lib/libobjc.*
/usr/include/g++
There is one casualty of the gcc 2.95.2 compiler -- Objective-C support
is currently broken.
Enjoy!
--
-- David([EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: vga driver and signal
Is all this just because some of the new video HW are crappy, ie that they produce snow/flicker/whatever (like in the old CGA days) or is this a genuine problem, as I said above I've never seen any problems on my ATI cards, and my laptop doesn't have this either (neomagic).. Yes, this is a problem if you try to do a blit in the middle of a vertical retrace you will get a small artifact for instance as you move your window you will see have a line or more half drawn and when you stop moving the window the blit completes. What determines the lacking retrace is the delta time of the mouse movement. -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: IPFilter in -current?
From the keyboard of Arjan de Vet: Guido van Rooij ([EMAIL PROTECTED]) is working on it and he recently showed me ipfilter 3.2.2 (I think) working as a loadable module for FreeBSD-current. As soon as it's fully tested he'll commit it. This is very good news! hellmuth -- Hellmuth MichaelisTel +49 40 559747-70 HCS Hanseatischer Computerservice GmbHFax +49 40 559747-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de 22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: GCC 2.95.2 testing
David O'Brien wrote: I've got GCC 2.95.2 working as the base compiler. It is still a little rough, but I wanted to put it in more hands for testing. If it doesn't interfere with my current work, then I'll get to it ASAP. I already have some fixes for the current binutils and egcs WRT to cross-compilation that I like to test on GCC 2.95.2, because building an Alpha world on i386 triggers a bug in egcs. If gcc 2.95.2 doesn't have that bug, then I for one don't have to chase it :-) The i386 doesn't fair as well. GENERIC can only be compiled if `ahc0' is removed. This is a call to IA-32 ASM experts to find a fix. Ok, thanks. It should trigger on my system then... -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking Databases http://www.scc.nl/ The FreeBSD projectmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CTM-deltas generation sptopped ?
On Fri, 5 Nov 1999, Chuck Robey wrote: On Thu, 4 Nov 1999, Peter Jeremy wrote: On 1999-Nov-03 23:58:00 +1100, [EMAIL PROTECTED] wrote: There are no new CTM-deltas on 'ctm.freebsd.org' at least 22 hours. The last e-mail delta I have is cvs-cur.5804, which arrived here at 0808UTC (about 5 hours before your message). I would have expected to receive 5805 (or at least an initial part) about 5 hours ago now, so I suspect something is wrong. I stopped reading the list for a few days (letting my mail pile up) while I handled a panic situation at the University, sorry. I can't traceroute or ping the source of ctm's, and I have mail out to the owner of the system. Now that I'm aware, I will follow this as fast as I can. Replying to my own mail, I want to give an update: the machine that generates ctm has crashed, and the vinum volume doesn't fsck cleanly on startup. It's not a disaster, this can all be fixed, nothing critical *could* have been lost, because I've copies of everything critical right here. The likelihood, tho, is that it'll be a couple days at least until ctm comes back up, because I think I'm going to have to recreate it. Be patient, I'll announce when it gets back up. Oh, yeah, anoncvs is down too, same reasons, same response. Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
OOps broke make world..
I've broken 'make world' because I forgot theat netstat has promiscuous fingers in places it shouldn't 'QUICK FIX:' copy old /usr/src/sys/netgraph/ng_socketvar.h from before I deleted it. then netstat should recompile.. I will fix it as soon as I get to my source tree. julian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: stuck with ~year old current
On Fri, Nov 05, 1999, Lauri Laupmaa wrote: Hi I have -CURRENT from 16 nov 1998 and stuck badly... If I make new kernel, loader says its format's unknown, if I try to make new loader, it says some gcc flag is unknown, if I try to make new gcc it barfs also... From where should I start ? Read all of the -current mailing list starting in 17 November 1998 all the way up to today, and then read /usr/src/UPDATING. -- |Chris Costello [EMAIL PROTECTED] |MOP AND GLOW - Floor wax used by Three Mile Island cleanup team. ` To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Serious locking problem in CURRENT
While changing my Postfix configuration, I stumbled on something weird. One of Postfix's processes (master) runs all the time and keep a exclusive write lock on $spool/pid/master.pid. When one does a reload, postfix-script runs master with the ``-t'' argument which makes master try to get a lock on the pid file. Under 3.3-RELEASE, everything is fine, the lock can't be obtained and Postfix knows it is already running. Under -CURRENT (two days old), the lock IS OBTAINED, meaning Postfix thinks it is not running. 3.3-RELEASE: OK -=-=-=- 402 [22:56] root@sidhe:/etc/postfix# make postfix reload postfix-script: refreshing the Postfix mail system 404 [22:56] root@sidhe:spool/postfix# kdump|tail -20 8359 master RET getrlimit 0 8359 master CALL chdir(0x8057b28) 8359 master NAMI "/var/spool/postfix" 8359 master RET chdir 0 8359 master CALL access(0x805c3e8,0) 8359 master NAMI "pid/master.pid" 8359 master RET access 0 8359 master CALL open(0x805c3e8,0x2,0) 8359 master NAMI "pid/master.pid" 8359 master RET open 7 8359 master CALL fstat(0x7,0xbfbfd300) 8359 master RET fstat 0 8359 master CALL lstat(0x805c3e8,0xbfbfd2a0) 8359 master NAMI "pid/master.pid" 8359 master RET lstat 0 8359 master CALL flock(0x7,0x6) 8359 master RET flock -1 errno 35 Resource temporarily unavailable 8359 master CALL close(0x7) 8359 master RET close 0 8359 master CALL exit(0x1) -=-=-=- 4.0-CURRENT: NOT OK -=-=-=- 331 [22:55] root@keltia:spool/postfix# postfix reload postfix-script: fatal: the Postfix mail system is not running 332 [22:56] root@keltia:spool/postfix# kdump|tail -20 14942 master RET gettimeofday 0 14942 master CALL getrlimit(0x1,0xbfbfd3d0) 14942 master RET getrlimit 0 14942 master CALL chdir(0x80589e8) 14942 master NAMI "/var/spool/postfix" 14942 master RET chdir 0 14942 master CALL access(0x805e248,0) 14942 master NAMI "pid/master.pid" 14942 master RET access 0 14942 master CALL open(0x805e248,0x2,0) 14942 master NAMI "pid/master.pid" 14942 master RET open 7 14942 master CALL fstat(0x7,0xbfbfd324) 14942 master RET fstat 0 14942 master CALL lstat(0x805e248,0xbfbfd2c4) 14942 master NAMI "pid/master.pid" 14942 master RET lstat 0 14942 master CALL flock(0x7,0x6) ? 14942 master RET flock 0? 14942 master CALL exit(0) -=-=-=- I've verified that it has a lock on 3.3-RELEASE but can't on CURRENT since lsof is broken (sigh). 3.3-RELEASE: 405 [22:56] root@sidhe:spool/postfix# lsof pid/master.pid COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME master 7155 root7uW VREG 0,131079 17 18615 pid/master.pid ^^^ Same Postfix versions on both. I even recompiled it on CURRENT. 406 [22:58] root@sidhe:spool/postfix# postconf mail_version mail_version = Snapshot-19990912 333 [22:56] root@keltia:spool/postfix# postconf mail_version mail_version = Snapshot-19990912 -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 4.0-CURRENT #75: Tue Nov 2 21:03:12 CET 1999 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
show stopper for Gcc 2.95.2 conversion
The current show stopper for switching over to GCC 2.95.2 is a problem compiling the `ahc' driver: cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -elf ../../dev/aic7xxx/aic7xxx.c ../../dev/aic7xxx/aic7xxx.c: In function `ahc_download_instr': machine/bus.h:584: Invalid `asm' statement: machine/bus.h:584: fixed or forbidden register 2 (cx) was spilled for class CREG. *** Error code 1 The message is misleading, as the problematic header is /sys/i386/include/bus.h not, /usr/include/machine/bus.h. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ESS 1868 driver, again
I read the last mails regarding problems with their ESS 1868 boards. Well, at least it is partially working for them. I didn't have any luck with the driver for some time now. I couldn't get a single tone. With the old voxware driver, sound worked at least partially (44.1 kHz, 8 Bit, mono), but with the new driver I didn't have any luck at all. Here my configuration: device pcm0at isa? port 0x220 irq 5 drq 1 flags 0x15 and during boot: pcm0: ESS1868 rev 11 at port 0x220-0x22f irq 5 drq 1 flags 0x15 on isa0 If I try to play something, I only get the following error from the driver: sb_dspwr(0xc0) timed out. The old voxware driver: controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 device sbxvi0 at isa? port 0x220 irq 5 drq 5 conflicts device sbmidi0 at isa? port 0x330 device opl0at isa? port 0x388 device mpu0at isa? port 0x330 sb0 at port 0x220 irq 5 drq 1 on isa0 Hmm... Could this be an ESS688 based card (rev 11) snd0: SoundBlaster Pro 3.1 isa_compat: didn't get ports for sbxvi sbxvi0 at port 0x220 irq 5 drq 5 on isa0 isa_compat: didn't get ports for sbxvi snd0: SoundBlaster 16 3.1 WARNING: "snd" is usurping "snd"'s cdevsw[] opl0 at port 0x388 on isa0 snd0: Yamaha OPL3 FM WARNING: "snd" is usurping "snd"'s cdevsw[] Any hints are welcome. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: stuck with ~year old current
Hi, On Fri, 5 Nov 1999, Lauri Laupmaa wrote: ... I have -CURRENT from 16 nov 1998 and stuck badly... If I make new kernel, loader says its format's unknown, if I try to make new loader, it says some gcc flag is unknown, if I try to make new gcc it The flag is probably -fformat-extensions so eliminate it from /usr/share/mk/bsd.kern.mk. Then build linker/kernel/world. The other fortcoming issues should be in /usr/src/UPDATING. If not please tell the solutions to [EMAIL PROTECTED] :-) Bye! Michael Reifenberger Plaut Software GmbH, R/3 Basis To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: show stopper for Gcc 2.95.2 conversion
On Friday, 5 November 1999 at 14:04:15 -0800, David O'Brien wrote: The current show stopper for switching over to GCC 2.95.2 is a problem compiling the `ahc' driver: cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -elf ../../dev/aic7xxx/aic7xxx.c ../../dev/aic7xxx/aic7xxx.c: In function `ahc_download_instr': machine/bus.h:584: Invalid `asm' statement: machine/bus.h:584: fixed or forbidden register 2 (cx) was spilled for class CREG. *** Error code 1 The message is misleading, as the problematic header is /sys/i386/include/bus.h not, /usr/include/machine/bus.h. In the kernel build environment, machine/ points to ../../i386/include. From the point of view of the compiler, the name is correct. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sio working
On Friday, 5 November 1999 at 23:02:52 +0100, D. Rock wrote: Warner Losh wrote: OK. I managed to get sio and ep working on the plane back from FreeBSDCon'99. There are some problems with card eject at the moment, but will be committing things to the tree shortly. Basically, I completely gutted the compatibilty layer and it became much easier. More later after I've had a chance to spend time with my wife and unwind from the drive back. I didn't have any luck using the sio driver with my card. Card info from "pccardc dumpcis": snip card "Intelligent" "PCMCIA FAX+MODEM" # config 0x0f "sio2" ? # config 0x17 "sio2" ? config 0x1f "sio2" ? # config 0x27 "sio2" ? On my Dell Latitude CPi I have: device sio0at isa? port IO_COM1 flags 0x90 irq 4 device sio1at isa? port IO_COM2 irq 3 sio0 really exists; it seems that sio1 shouldn't be there, since I get the message Nov 5 17:15:39 mojave /kernel: devclass_alloc_unit: sio1 already exists, using next available unit number Nov 5 17:15:39 mojave /kernel: sio2 at port 0x2e8-0x2ef irq 5 slot 1 on pccard0 Nov 5 17:15:39 mojave /kernel: sio2: type 16550A Anyway, this configuration works: at least I can use it to dial in to a remote system. I tried many different combinations. I disabled the onboard serial devices in the BIOS and kernel, so config index 0xf could grap io port 0x3f8 with irq 4 but the only thing I get is sio2: configured irq -1071415680 not in bitmap of probed irqs 0 The irq number isn't always the same. It seems to be a pointer. Or junk. Here the remaining relevant lines from my configuration: controller card0 controller pcic0 at isa? irq 10 controller pcic1 at isa? irq 10 ISTR you should put card0 after pcic0 and pcic1. Also, I have no interrupts: device pcic0 at isa? device pcic1 at isa? controller card0 Boot output: pcic-pci0: TI PCI-1131 PCI-CardBus Bridge at device 10.0 on pci0 pcic-pci1: TI PCI-1131 PCI-CardBus Bridge at device 10.1 on pci0 [...] pcic0: VLSI 82C146 at irq 10 on isa0 pccard0: PC Card bus -- kludge version on pcic0 pccard1: PC Card bus -- kludge version on pcic0 I have: Nov 5 17:15:19 mojave /kernel: pcic-pci0: TI PCI-1131 PCI-CardBus Bridge irq 11 at device 3.0 on pci0 Nov 5 17:15:19 mojave /kernel: pcic-pci1: TI PCI-1131 PCI-CardBus Bridge irq 11 at device 3.1 on pci0 ... Nov 5 17:15:19 mojave /kernel: pcic0: VLSI 82C146 on isa0 Nov 5 17:15:19 mojave /kernel: pccard0: PC Card bus -- kludge version on pcic0 Nov 5 17:15:19 mojave /kernel: pccard1: PC Card bus -- kludge version on pcic0 Nov 5 17:15:19 mojave /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x90 on isa0 Nov 5 17:15:19 mojave /kernel: sio0: type 16550A Nov 5 17:15:19 mojave /kernel: sio1: configured irq 3 not in bitmap of probed irqs 0 Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Serious locking problem in CURRENT
According to Ollivier Robert: 3.3-RELEASE: 405 [22:56] root@sidhe:spool/postfix# lsof pid/master.pid COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME master 7155 root7uW VREG 0,131079 17 18615 pid/master.pid ^^^ Apparently the lock is NOT done on FreeBSD 4.0: 202 [0:47] root@keltia:sysutils/lsof# lsof /var/spool/postfix/pid/master.pid COMMAND PID USER FD TYPEDEVICE SIZE/OFF NODE NAME master 242 root7u VREG 13,131080 17 29093 pid/master.pid ^^^ (thanks to David O'Brien for having updated the lsof port). Same Postfix versions on both. I even recompiled it on CURRENT. We have a problem here... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 4.0-CURRENT #75: Tue Nov 2 21:03:12 CET 1999 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
libvgl - status and perspectives
Hi, Today I noticed accidentally that either libvgl is broken, or the demo program does something wrong - the mouse cursor doesn't move. But this brings more general question regarding console graphics library. As it is today, libvgl is almost useless due to very limited set of functions. There were discussions whether to port SVGAlib or GGI. Do you know if someone is working/planning to work on it? Thanks for any info. Andrzej Bialecki // [EMAIL PROTECTED] WebGiro AB, Sweden (http://www.webgiro.com) // --- // -- FreeBSD: The Power to Serve. http://www.freebsd.org // --- Small Embedded FreeBSD: http://www.freebsd.org/~picobsd/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Serious locking problem in CURRENT
(thanks to David O'Brien for having updated the lsof port). More so to Vic Abell [EMAIL PROTECTED] for bending over backwards to deal our changes. I forgot to mention that I've now given him access to my Alpha. So 4.46.1 mostly works on the Alpha now. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
