Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 14 Dec 2000 14:48:11 +0100
From:      Christoph Kukulies <kuku@gilberto.physik.RWTH-Aachen.DE>
To:        freebsd-isdn@freebsd.org
Subject:   Re: GRRRRRRRRR COMPILER ERRORS
Message-ID:  <20001214144811.A28018@gil.physik.rwth-aachen.de>

next in thread | raw e-mail | index | archive | help
On Thu, Dec 14, 2000 at 02:26:30PM -0800, Boris wrote:
> Hello Christoph,
> 
> Thursday, December 14, 2000, 12:38:27 AM, you wrote:
> 
> CK> On Wed, Dec 13, 2000 at 09:07:09PM -0800, Boris wrote:
>> Hello freebsd-isdn,
> >> 
> >>   I really DISLIKE the ISDN-DRIVER for *BSD!
> 
> CK> Why?
> 
> Last time i lost a lot of data while recompiling a fresh 4.2 kernel
> from cvs repository. I made make world (worked), i applied the i4b
> patch to the kernel, recompiled the kernel -> stop error, i restarted
> my server and nothing worked anymore because of no new kernel. I lost
> a week for reinstalling and reconfiguring my freebsd machine only
> because the i4b driver makes me crazy and nothing works.

When you are playing with fire or knocking away the ground under your feet
you cannot blame i4b for this. I myself am using i4b on the server 
which I upgrade now and then. Presentently I'm using 4.2 (RELEASE though)
(which I installed from a CD I burned from the iso-image from ftp.freebsd.org,
btw.)

Anyway, it happened to me last week that I was crazy enough to
cvsup -current into that important server I'm using for
i4b and I was off the net for two or three days (fortunately over the
weekend and I had a parallel access which was still working).
Interestingly enough that the problem I had was compiling a kernel
and it was the mutex.h code that was currently being worked on
that made kernel compilation break in the i4b area.

Being aware of the dangers when doing this I don't complain loudly
or blame i4b. That's unfair if not foolish.

> 
> This you can see is from a fresh installed 4.2 release box after
> updating with cvs. My current version is as following:
> 
> uname -a

My box (and I built a special kernel with i4b):
FreeBSD isdn-kukulies.dialup.rwth-aachen.de 4.2-RELEASE FreeBSD 4.2-RELEASE #2: Mon Dec 11 10:59:51 CET 2000     kuku@isdn-kukulies.dialup.rwth-aachen.de:/usr/src/sys/compile/MONKAVMIFB  i386

> 
> FreeBSD bastion.localhost 4.2-STABLE FreeBSD 4.2-STABLE #1: Tue Dec 12 19:03:586
> 
> Try it yourself! update your sources via cvs and try to get the i4b up
> and running, i wish you a lot of fun -(

Maybe you update (cvsup once more and the problem is gone).

> 
> >> 
> >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c: In function `avma1pp_attach_avma1pp':
> >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:628: warning: implicit declaration of funct
> >> ion `DELAY'
> >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c: In function `avma1pp_hscx_intr':
> >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:866: warning: implicit declaration of funct
> >> ion `IF_HANDOFF'
> >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c: In function `avma1pp_bchannel_setup':
> >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: warning: implicit declaration of func
> >> tion `mtx_init'
> >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: structure has no member named `ifq_mt
> >> x'
> >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: `MTX_DEF' undeclared (first use in th
> >> is function)
> >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: (Each undeclared identifier is report
> >> ed only once
> >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1121: for each function it appears in.)
> >> ../../i4b/layer1/ifpi/i4b_ifpi_pci.c:1136: structure has no member named `ifq_mt
> >> x'
> >> *** Error code 1
> >> 
> >> Any comments? Itīs nearly impossible to compile a new kernel with this
> >> driver!!!!!!!!!!!!!!!!!!!
> 
> CK> Shht. Don't shout. You don't say which version of FreeBSD you are using.
> 
> >>
> 
> currently 4.2 stable #1, downloaded latest sources from cvs yesterday
> via cvsup.

Do you want me send you a 4.2-RELEASE CD so you can get on your feet again?

--
Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isdn" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001214144811.A28018>