headers
kbrannen | 7 Mar 2003 20:37

compile failure on 2.4.18 kernel

I have a 2.4.18 kernel (a Suse 8.0 install) that causes ftape 4.04a to fail to 
compile.  Specifically I get:

make[2]: Entering directory `/home/kevin/ftape/ftape-4.04a/ftape/lowlevel'
In file included from ftape-buffer.c:28:
/usr/src/linux/include/linux/malloc.h:4: warning: #warning linux/malloc.h is 
deprecated, use linux/slab.h instead.
In file included from ftape-ctl.c:34:
/usr/src/linux/include/linux/malloc.h:4: warning: #warning linux/malloc.h is 
deprecated, use linux/slab.h instead.
In file included from fdc-io.c:39:
/usr/src/linux/include/linux/malloc.h:4: warning: #warning linux/malloc.h is 
deprecated, use linux/slab.h instead.
make[2]: Leaving directory `/home/kevin/ftape/ftape-4.04a/ftape/lowlevel'
make[2]: Entering directory `/home/kevin/ftape/ftape-4.04a/ftape/lowlevel'
gcc -Wall -Wstrict-prototypes -O2  -fomit-frame-pointer -fno-strength-reduce 
-D__KERNEL__ -I. -I../../include -I/usr/src/linux/include -m486 
-malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=586 -DMODULE 
-DEXPORT_SYMTAB -c ftape_syms.c
In file included from /usr/src/linux/include/linux/fs.h:12,
                  from /usr/src/linux/include/linux/capability.h:17,
                  from /usr/src/linux/include/linux/binfmts.h:5,
                  from /usr/src/linux/include/linux/sched.h:9,
                  from ../../include/linux/ftape.h:35,
                  from ftape_syms.c:32:
/usr/src/linux/include/linux/wait.h: In function `__add_wait_queue_tail':
/usr/src/linux/include/linux/wait.h:220: warning: implicit declaration of 
function `list_add_tail'
In file included from ftape-tracing.h:35,
                  from ftape_syms.c:33:
(Continue reading)

Permalink | Reply | 3 comments |
headers
Bryan Henderson | 7 Mar 2003 23:35
Picon
Favicon

Re: compile failure on 2.4.18 kernel


ftape 4.04a doesn't compile for modern kernels.  You need to get the
current ftape, which is labelled "unstable" or something like that.

-
To unsubscribe from this list: send the line "unsubscribe linux-tape" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 2 comments |
headers
kbrannen | 12 Mar 2003 19:43

Re: compile failure on 2.4.18 kernel

Bryan Henderson wrote:
> 
> 
> 
> ftape 4.04a doesn't compile for modern kernels.  You need to get the
> current ftape, which is labelled "unstable" or something like that.

Still trying on a 2.4.18 kernel.  I went and retrieved the 
ftape-4.x-2002_08_02 tarball, it being the latest in the unstable dir.  I'm 
getting a lot farther, but still have failure.

make[2]: Entering directory `/home/kevin/ftape/ftape-4.x-2002_08_02/'
gcc -Wall -Wstrict-prototypes -O2  -fomit-frame-pointer -fno-strength-reduce 
-D__KERNEL__ -I. -I../../include -I/usr/src/linux/include -DCONFIG_X86 
-mpreferred-stack-boundary=2 -march=i586 -DMODULE    -c -o zftape-rw.o zftape-rw.c
zftape-rw.c: In function `zft_set_flags':
zftape-rw.c:76: `ZFT_Q80_MODE' undeclared (first use in this function)
zftape-rw.c:76: (Each undeclared identifier is reported only once
zftape-rw.c:76: for each function it appears in.)
zftape-rw.c:76: `ZFT_ZIP_MODE' undeclared (first use in this function)
zftape-rw.c:78: warning: unreachable code at beginning of switch statement
make[2]: *** [zftape-rw.o] Error 1
make[2]: Leaving directory `/home/kevin/ftape/ftape-4.x-2002_08_02/ftape/zftape'
make[1]: *** [_modsubdir_zftape] Error 2
make[1]: Leaving directory `/home/kevin/ftape/ftape-4.x-2002_08_02/ftape'
make: *** [all] Error 2

I do NOT have CONFIG_ZFT_OBSOLETE defined in MCONFIG.  I guess I need to make 
sure I'm not using CONFIG_ZFT_COMPRESSOR and CONFIG_ZFT_COMPRESSOR_MODULE? 
Since there are no previous tapes, I don't have to worry about backward
(Continue reading)

Permalink | Reply | 1 comment |
headers
Claus-Justus Heine | 12 Mar 2003 23:36
Picon
Favicon

Re: compile failure on 2.4.18 kernel

Hi Kevin,

kbrannen <at> gte.net wrote:

> Since CONFIG_ZFT_OBSOLETE is not defined, but apparently the _MODULE def 
> is, the compile is failing.  Is the proper thing to do to change MCONFIG 
> so that DCONFIG_ZFT_COMPRESSOR_MODULE and CONFIG_ZFT_COMPRESSOR are 
> always undef?

maybe you should try to first disable ftape support completely in your kernel. 
The ftape distribution uses the "#includenext" preprocessor statements to first 
include its private definitions and then the standard kernel stuff. So some 
FTAPE_... defines in the kernel may interfere with the separate ftape distribution.

Greetings

Claus

--
    Dipl.-Math. Claus-Justus Heine
    Institute for Applied Mathematics              Phone: +49-761-203-5647
    Hermann-Herder-Str. 10                         Fax: +49-761-203-5632
    Freiburg University
    79104 Freiburg / Brsg., Germany

-
To unsubscribe from this list: send the line "unsubscribe linux-tape" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
(Continue reading)

Permalink | Reply | 0 comments |
headers
Andrew Fremantle | 15 Mar 2003 15:14
Picon

Media Compatability question

Okay, can anyone clarify this issue for me?

I've got a Conner TSM1700 tape drive, attached to a 2Mb HSC. The drive has
been hiding in a dark, dry place for the last 5 years or so, I found it
while cleaning and went "hmmmm... I think I can actually use this now that
I've got a proper network and my data is properly organized", so I went and
threw together a 486 and tossed the drive and controller in it. The machine
is running Debian. I'm going to dump to it across the network from my
FreeBSD machine.

FTape is configured and running well on the machine in question, I've got no
problems with it.

My question is regarding media. I've got three Sony "QIC-3020XLF" tapes,
which are labelled as "QIC-3020-MC Preformatted Media". These tapes have
seen almost no usage, but they are at least 5 years old, they've been kept
in the dark and dry, and seem to still be usable. Obviously however, I'm
looking for some newer tapes.

These tapes are, as far as I can tell, QIC-3020/WIDE type tapes. As far as I
can tell "Travan 3" or "TR-3" tapes are just rebranded QIC-3020/WIDE tapes,
but at this web page, Seagate (Connor's owner) does NOT list TR-3 tapes as
compatable with this drive.
http://www.seagate.com/support/kb/tape/spec2000.html Is this purely
marketing, or are there actual technical differences between QIC-3020/WIDE
media and Travan-3 media that would prevent me using Travan-3 media in my
drive? As I'm sure you can imagine, I am interested in using TR-3-EX
cartridges, giving me a 2.2GB capacity per tape.

Additionally, the ftape-faq (I think) includes some rather scathing comments
(Continue reading)

Permalink | Reply | 0 comments |

Gmane