Re: gcc bug? Openoffice port impossibel to compile on 4.8

2003-05-29 Thread Dimitry Andric
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2003-05-28 at 14:12:34 Dag-Erling Smorgrav wrote: have you tried -traditional? gcc 3.1 release notes: The -traditional C compiler option has been deprecated and will be removed in GCC 3.3. (It remains possible to preprocess non-C code with

Re: mbuf reference? (and missing man page)

2003-05-29 Thread Yar Tikhiy
On Fri, May 23, 2003 at 09:53:48PM +0200, Simon L. Nielsen wrote: On 2003.05.23 15:42:36 +, Bosko Milekic wrote: On May 23, 2003 07:07 pm, Michael R. Wayne wrote: Missing man page: 4.8 releasse - man netstat has a reference to mbuf(9) but man mbuf says: No manual entry for

Re: gcc bug? Openoffice port impossibel to compile on 4.8

2003-05-29 Thread Wes Peters
On Wednesday 28 May 2003 05:12 am, Dag-Erling Smorgrav wrote: Wes Peters [EMAIL PROTECTED] writes: GCC 3.2 is broken by design. It insists, amongst other stupidities, on type-checking arguments using old style declarations like: int foo(bar) char *bar; {} rendering

Re: gcc problem/openoffice failure

2003-05-29 Thread Narvi
On Tue, 27 May 2003, Don Lewis wrote: On 27 May, Julian Elischer wrote: For the last month (more actually)(and after completely rebuilding my system and all the ports on it) I have not been able to compile the openoffice port due to gcc failures. (I have posted the message earlier

pcic setup / wi0 timeout

2003-05-29 Thread Dirk-Willem van Gulik
On two (seemingly) identical machines - one works, one fails Kernel: FreeBSD 5.0-RELEASE #0: Tue May 6 01:04:09 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/WLEIDEN.6316 cvsup as of that day. Machine 1: pcic0: Ricoh RL5C475 PCI-CardBus Bridge mem

Who configures the pci/pcmcia bridge

2003-05-29 Thread Dirk-Willem van Gulik
Even when the BIOS is instructed to assign an IRQ - boot -v shows FreeBSD 5.0-RELEASE #0: Mon Apr 28 11:24:06 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/WLEIDEN.93264 ... bios32: Found BIOS32 Service Directory header at 0xc00fdb00 bios32: Entry = 0xf5f23 (c00f5f23) Rev = 0 Len = 1

Re: pcic setup / wi0 timeout

2003-05-29 Thread Dirk-Willem van Gulik
On Wed, 28 May 2003, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Dirk-Willem van Gulik [EMAIL PROTECTED] writes: : pcic0: Ricoh RL5C475 PCI-CardBus Bridge at device 18.0 on pci0 : pcic0: PCI Memory allocated: 0x8800 : pcic0: No PCI interrupt routed,

Re: pcic setup / wi0 timeout

2003-05-29 Thread M. Warner Losh
In message: [EMAIL PROTECTED] Dirk-Willem van Gulik [EMAIL PROTECTED] writes: : In message: [EMAIL PROTECTED] : Dirk-Willem van Gulik [EMAIL PROTECTED] writes: : : pcic0: Ricoh RL5C475 PCI-CardBus Bridge at device 18.0 on pci0 : : pcic0: PCI Memory allocated:

Re: pcic setup / wi0 timeout

2003-05-29 Thread Dirk-Willem van Gulik
On Wed, 28 May 2003, M. Warner Losh wrote: It depends. Really old machines routed interrupts to all PCI slots and assigned devices found there an interrupt. Newer old machines expect the PCI bridge driver of the OS to cope. And I take it that if I start mucking myself by poke-ing a value

Re: pcic setup / wi0 timeout

2003-05-29 Thread M. Warner Losh
OK. You might have a little better luck with 5.1-BETA, or you might not. However, you might try http://people.freebsd.org/~msmith/pir.c as root and tell me if it finds a $PIR table. The boot verbose says no, but I can't recall if 5.0-RELEASE printed it or not (I think it does). The Pentium

Re: pcic setup / wi0 timeout

2003-05-29 Thread Dirk-Willem van Gulik
On Wed, 28 May 2003, M. Warner Losh wrote: OK. You might have a little better luck with 5.1-BETA, or you might ok; cvsuping to -HEAD. Did not see any 5_1 tags. not. However, you might try http://people.freebsd.org/~msmith/pir.c as root and tell me if it finds a $PIR table. The boot

Re: pcic setup / wi0 timeout

2003-05-29 Thread M. Warner Losh
In message: [EMAIL PROTECTED] Dirk-Willem van Gulik [EMAIL PROTECTED] writes: : Aye - it seems to think that no intpin is connected perhaps : : Actually, I take it back. 5.1 won't help, but might make it easier to : diagnose. : : Thanks for the help sofar - I'll report if 5.1

should pw(8) accept spaces/tabs in passwords?

2003-05-29 Thread Alexey Neyman
Hello, I was just asked why the passwd(1) utility allows to set up a password containing spaces and tabs, and the adduser(8) script does not: the password is stripped of anything past a space or a tab. E.g., my password turns into my. It turned out that it's pw(8) utility that does such

Re: should pw(8) accept spaces/tabs in passwords?

2003-05-29 Thread Alexey Neyman
On Thursday 29 May 2003 08:25, Alexey Neyman wrote: attached patch makes it behave consistently with passwd(1). Seems that attachments are stripped somewhere on the way; resend inline. Index: pw_user.c === RCS file:

Problem adding new disk to existing installation (FreeBSD 4.8)

2003-05-29 Thread Joel V
Hello all. My problem seemed to be a little too weird and uncommon to post at freebsd-questions. Background information: P4 2.4 / Intel D845PESV / 512 DDR333 / 120GB WD primary master / 60GB WD secondary master I've succesfully installed FreeBSD 4.8 on primary master. However, when I try to

Re: should pw(8) accept spaces/tabs in passwords?

2003-05-29 Thread Terry Lambert
Alexey Neyman wrote: On Thursday 29 May 2003 08:25, Alexey Neyman wrote: attached patch makes it behave consistently with passwd(1). Seems that attachments are stripped somewhere on the way; resend inline. It's probably because your attachment re-specified the MIME version. Looking at the

Re: Problem adding new disk to existing installation (FreeBSD 4.8)

2003-05-29 Thread Terry Lambert
Joel V wrote: DEBUG: MakeDev: Unknown major/minor for devtype - I changed the ata100 cable. I checked the disk with WD's Data Lifeguard. The disk also worked fine in a Win2k workstation. All the BIOS settings are on auto. Someone suggested on doing cd /dev/ ./MAKEDEV all, but this didn't

Re: gcc bug? Openoffice port impossibel to compile on 4.8

2003-05-29 Thread Wes Peters
On Wednesday 28 May 2003 04:11 pm, Bruce M Simpson wrote: I remember having to convert all my Lattice C code to use ANSI style declarations after upgrading to SAS/C on the Amiga. However, we're dealing with something a bit more stable in terms of code base, anyway. Having to commit a whole