On Sun, Apr 30, 2000 at 09:50:36PM +0200, Jeroen Hogeveen [EMAIL PROTECTED] wrote:
You can try to edit the libtool file in the kdelibs
directory to set deplibs="$deplibs -lc -lgcc" (around
line number 2600).
This will link the __eh_rtime_match.
I still get a nonworking khtm however.. :
hrm, i'm sad to report that it did not work for me..
let me know if you need output from it, i'll see about sending it to you.
-- jan
On Sun, 30 Apr 2000, Gary Jennejohn wrote:
Here's a simple patch which works for me.
--- /sys/netgraph/ng_base.c Sun Apr 30 11:32:22 2000
+++
"f.johan.beisser" writes:
hrm, i'm sad to report that it did not work for me..
let me know if you need output from it, i'll see about sending it to you.
-- jan
On Sun, 30 Apr 2000, Gary Jennejohn wrote:
Here's a simple patch which works for me.
[patch deleted]
Well, I only have a simple
It was working perfectly about 10 days ago. It stopped working right after
one or two major commits. And also, it's in 5.0-CURRENT, not 4.0
=
| Kenneth Culver | FreeBSD: The best OS around.|
| Unix Systems
On Mon, May 01, 2000 at 10:14:34AM -0400, Kenneth Wayne Culver wrote:
It was working perfectly about 10 days ago. It stopped working right after
one or two major commits. And also, it's in 5.0-CURRENT, not 4.0
I fully agree with this statement ... I am having some of the same weird
things
Ok, more in the sound department: A current src/sys/dev/sound with a
src/sys/dev/sound/pcm/dsp.c from the 22nd does not exhibit the high load
problem. Moving dsp.c to the 24th causes the problem to re-appear. Thus,
I'm prety convinced tha the big commit on the 23rd to dsp.c is the cause
of at
Loader was updated to handle module metadata which was introduced
by recent updates in kernel linker. This is related to a new way of
declaration of module dependencies.
--
Boris Popov
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of
Now I have it recognized with without the irq and I/O space problem because I
had an irq 9 conflict but now I am getting :
wi0: WaveLAN/IEEE 802.11 at port 0x240-0x27f irq 9 slot 0 on pccard0
wi0: Ethernet address: 00:60:1d:03:f4:08
wi0: device timeout
wi0: tx buffer allocation failed
wi0: xmit
Cvsup'ed this morning and built world. All went swimmingly until
reboot. I got this kernel panic:
swapon: adding /dev/da0s2b as swap device
panic: blst_radix_free: freeing free block
The ordering of the swap partions does matter. If /dev/da0s2b is first
in /etc/fstab the panic occurs, if it's
Boris Popov wrote:
Loader was updated to handle module metadata which was introduced
by recent updates in kernel linker. This is related to a new way of
declaration of module dependencies.
Not only that, but once we've settled on a versioning scheme, we will be
using dependency tags
Greetings all..
It seems that there may be a small socket implementation issue
with freebsd 4-Stable. I have been in disscussion with a few people from
the isc bind 9 bug tracking department, and it seems that for the macro
CMSG_NXTHDR to function in freebsd , the macro
wishlist
Not sure if this is a silly question or not, but could the kernel somehow
view a specific dir on a ext2fs disk as the freebsd root and boot a
freebsd system from it? Also being able to access the stuff below the
I think there's a more general need to have a loader variable which
wishlist
Not sure if this is a silly question or not, but could the kernel somehow
view a specific dir on a ext2fs disk as the freebsd root and boot a
freebsd system from it? Also being able to access the stuff below the
I think there's a more general need to have a loader variable
If memory serves me right, Visigoth wrote:
It seems that there may be a small socket implementation issue
with freebsd 4-Stable. I have been in disscussion with a few people from
the isc bind 9 bug tracking department, and it seems that for the macro
CMSG_NXTHDR to function in freebsd
On Fri, 28 Apr 2000, Leif Neland wrote:
Sorry not to have details at hand but anyways:
Current cvsupped today.
I have 2 parallel ports in use.
I have had no problems with kernels dated 2 weeks or older, but since a few
days ago, the system crashes at boot while probing the parallel
What sort of fallback behaviour would you want in case of error here?
Just let chroot() either succeed or fail. It's own "fallback behavior"
in such a case should prove adequate. :)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of
What sort of fallback behaviour would you want in case of error here?
Just let chroot() either succeed or fail. It's own "fallback behavior"
in such a case should prove adequate. :)
Hmm. Failure to chroot == failure to start init?
--
\\ Give a man a fish, and you feed him for a day.
auth b614398f subscribe freebsd-current [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
18 matches
Mail list logo
