Brendan,

Thanks for your reply.

Unfortunately I seem to get the same error with 4.03-pre-2 as well.

Michael

> -----Original Message-----
> From: Brendan Pratt [SMTP:[EMAIL PROTECTED]]
> Sent: 12 October 1999 10:29
> To:   michael.dj.cox; linuxtapelist
> Subject:      Re: ftape 4.02 won't compile
> 
> Hi,
> 
> ----- Original Message -----
> From: <[EMAIL PROTECTED]>
> 
> > I'm trying to get my Colorado Jumo 120 to work on my Suse 6.2 linux
> > installation (Kernel 2.2.10) but with not much joy.
> >
> > Firstly I understand that that kernel version comes with support for
> ftape
> > 4.02 built-in but I can only find the ftape.o module and not
> > ftape-internal.o or zftape.o etc. I can't find them anywhere on the
> > distribution.
> >
> > Hence I can't install the modules as instructed in the ftape
> documentation.
> >
> > My next step was to download the source for ftape 4.02, amend MCONFIG
> and
> > try to build the modules.
> >
> > But..it doesn't compile with gcc 2.7.2.3..but fails with:
> >
> > fdc-io.c: In function 'fdc_interrupt_wait':
> > fdc-io.c:433: structure has no member named 'timeout'
> > fdc-io.c:454: structure has no member named 'timeout'
> >
> > In the code the structure in question is pointed to by a variable
> 'current'
> > but I can't establish the type of this structure but its something to do
> > with signals.
> 
> I had the same problem, and was advised to grab the latest 'unstable'
> version
> of it, which compiled fine without any errors.
> 
> YMMV, but give it a go anyhow.
> 
> 
> --
>  Current Net Legislation will slow us down and cost us more!
> Tell you Local Federal Member NOW it will hurt your business
>  For more info visit http://www.efa.org.au/Campaigns/99.html
> --
> 
> C u laitr
> -------------------------------------------------------------------------
> Brendan Pratt         Overflow Internet Services
>                       Mobile : +61-418-746657
>                       Phone  : +61-7-55-463-832
>         E-Mail : [EMAIL PROTECTED]
> -------------------------------------------------------------------------
> 

Reply via email to