Hi,
[EMAIL PROTECTED] wrote:
>
> Hello to the list,
> Compiling the new kernel we found that the drivers for
>
> 6pack
> yam
> bpqether
>
> cause the kernel compile to fail
By intention. This way they will get fixed *apropriately*.
I could also fix them, but I�d need the hardware to test it or
somebody reliable for remote-diagnostics. However, it�s very much
easier for the developers of these drivers to fix the interface than
for me.
> make all-recursive
> make[1]: Entering directory `/usr/src/ax25-apps-kjd-1-0.0.4'
> Making all in ax25ipd
> make[2]: Entering directory `/usr/src/ax25-apps-kjd-1-0.0.4/ax25ipd'
> make[2]: Nothing to be done for `all'.
> make[2]: Leaving directory `/usr/src/ax25-apps-kjd-1-0.0.4/ax25ipd'
> Making all in ax25rtd
> make[2]: Entering directory `/usr/src/ax25-apps-kjd-1-0.0.4/ax25rtd'
> make[2]: Nothing to be done for `all'.
> make[2]: Leaving directory `/usr/src/ax25-apps-kjd-1-0.0.4/ax25rtd'
> Making all in call
> make[2]: Entering directory `/usr/src/ax25-apps-kjd-1-0.0.4/call'
> /bin/sh ../libtool --mode=link gcc -g -O2 -Wall -o call call.o menu.o
> crc.o yapp.o dostime.o -lax25
> gcc -g -O2 -Wall -o call call.o menu.o crc.o yapp.o dostime.o -lax25
> call.o: In function `statline':
Obviously the linker wasn�t told to link against the ncurses library.
This is either a problem with the configure script or with your system.
I suspect the latter one since the original packages must have the same
problem and nobody else complained. Add -lncurses to the command line
and it will probably work.
> Nevertheless, call seems to have some problems with the new AX.25 stack.
> Every time I want to connect to someone using a command like call radio
> MYCALL the call program comes up with
>
> Trying...
> connect: No route to host
You have to set a route using axparms or via the ax25 routing deamon.
This not really a bug, I will change this behaviour of call, but there
are other things to do which have priority.
> But setting an option for either serial or parallel or MIDI connected PTT
> circuit failed. It seems that sethdlc is broken, too.
I suspect that you still had the parport and serial device drivers
loaded
or some hardware problem. If not please investigate and send patches.
> sethdlc -i -d bcsf0
>
> failed on both computers.
> I am not sure if this is a fault of sethdlc or the driver.
Perhaps you could be more specific here.
-- Jens
