Hello Warner,
Hello everybody,
If you are looking for confirmation that the workaround for the ex/libc
related world breakage works then here it is: I have just finished
upgrading this way and did not have any problems.
Actually, there is an even simpler way: If you already have started a
I have some troubleshootings with -current.
A program that previously worked (-current of November) with -pthread now
fails with an abort and a " in free(): error: recursive call" warning.
I think that there may be some errors in my program and
I'd like to know what was recently modified in
On Wed, Jan 03, 2001 at 05:54:26PM +0100, Nicolas Souchu wrote:
A program that previously worked (-current of November) with -pthread now
fails with an abort and a " in free(): error: recursive call" warning.
FWIW, WindowMaker 0.62.1 also crashes like this ocassionally (usually
when I open a
On Wed, Jan 03, 2001 at 05:54:26PM +0100, Nicolas Souchu wrote:
A program that previously worked (-current of November) with -pthread now
fails with an abort and a " in free(): error: recursive call" warning.
I need a copy of this program (source form) to test with.
--
-- David ([EMAIL
I just completed a 'make world' from sources at midnight PST. I made
a static vi before starting.
I had problems trying to make libc. I got lots of complaints about
'tqh_last' not being members of a structure. But, world completed OK.
Must have been something on my system or something I did.
The merging of our bits into GCC 2.95.3(RC#1) took a little longer than I
suspected. I've got to head to an appointment, so the world will be broken
for a little while.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Sat, Dec 30, 2000 at 03:13:24AM +1000, Andrew Kenneth Milton wrote:
Is there a nice way to stop vga_pci from attaching to my video card, or
to allow another driver to attach to it after vga_pci has done its thing?
At the moment I'm removing all traces of vga_pci from the Makefile in
my
:The merging of our bits into GCC 2.95.3(RC#1) took a little longer than I
:suspected. I've got to head to an appointment, so the world will be broken
:for a little while.
:
( sky starts to fall as David O takes a coffee break at the local
starbucks, remarking merrily to other patrons
On Wed, Jan 03, 2001 at 10:35:48AM -0800, Matt Dillon wrote:
:The merging of our bits into GCC 2.95.3(RC#1) took a little longer than I
:suspected. I've got to head to an appointment, so the world will be broken
:for a little while.
:
( sky starts to fall as David O takes a coffee
On Wed, Jan 03, 2001 at 10:26:30AM -0800, David O'Brien wrote:
The merging of our bits into GCC 2.95.3(RC#1) took a little longer than I
suspected. I've got to head to an appointment, so the world will be broken
for a little while.
World should be buildable again. Quite sorry for the longer
I was mostly trying to push the locks down so that they weren't held during
attach and remove. I was using them to protect mostly the kthread state flag
in the softc, as well as other variables in the softc.
Comments?
It seems to me that having a single thread per-softc gives you this
It seems to me that having a single thread per-softc gives you this
protection without requiring any locks. Other than having to aquire
Giant at thread starup (as most code below us is not thread safe yet),
I don't see any other locking requirements.
I take that back. In pccbb_detach, you need
Dear all...
Recent -CURRENT make buildkernel target died with this message:
=== uscanner
cc -O -pipe -g -D_KERNEL -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
-Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I.
URL:http://current.jp.FreeBSD.org/build/i386/LINT/5.0-CURRENT-20010104-JPSNAP.bad
According to this logfile, 'cy' (Cyclades serial), 'ar' (Arnet
SYNC/570i), 'sr' (RISCom/N2) and 'meteor' (Matrox meteor) requires
COMPAT_OLDPCI support which is removed a few weeks before.
Can we temporary
On Thu, 4 Jan 2001, Makoto MATSUSHITA wrote:
URL:http://current.jp.FreeBSD.org/build/i386/LINT/5.0-CURRENT-20010104-JPSNAP.bad
According to this logfile, 'cy' (Cyclades serial), 'ar' (Arnet
SYNC/570i), 'sr' (RISCom/N2) and 'meteor' (Matrox meteor) requires
COMPAT_OLDPCI support which is
URL:http://current.jp.FreeBSD.org/build/i386/LINT/5.0-CURRENT-20010104-JPSNAP.bad
According to this logfile, 'cy' (Cyclades serial), 'ar' (Arnet
SYNC/570i), 'sr' (RISCom/N2) and 'meteor' (Matrox meteor) requires
COMPAT_OLDPCI support which is removed a few weeks before.
Can we
16 matches
Mail list logo
