From: Sahara Workshop <workshop@cpt.saharapc.co.za>
To: KML <linux-kernel@vger.kernel.org>
Subject: Problems with 2.5.*'s SCSI headers and cdrtools
Date: 14 Feb 2003 07:48:06 +0200 [thread overview]
Message-ID: <1045201685.5971.78.camel@workshop.saharact.lan> (raw)
[-- Attachment #1: Type: text/plain, Size: 1256 bytes --]
Kernel 2.5.5x (have not tried earlier) and 2.5.60 's scsi/scsi.h do
not have like in 2.4 the 'include <features.h>', or as it may seem
to need an 'include <types.h>', and thus cdrtools for one do not
compile.
The take I get on this from Jorg is that he feels its a problem
kernel side. Comments ?
Attached is a patch that get cdrtools-2.01a2 to compile.
Regards,
--
Martin Schlemmer
Gentoo Linux Developer, Desktop Team
Cape Town, South Africa
- PLEASE NOTE -
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager. Please note that any views or opinions presented
in this email are solely those of the author and do not necessarily
represent those of Sahara Distribution (Pty) Ltd. Finally, while Sahara
Distribution attempts to ensure that all email is virus-free, Sahara
Distribution accepts no liability for any damage caused by any virus
transmitted by this email.
Sahara Distribution (PTY) Ltd
Unit G5-G12, Centurion Business Park, Milnerton, Cape Town, South Africa
Private Bag X180, Halfway House, 1685, South Africa
Scanned and protected by Sistech Viruswall 2.3
[-- Attachment #2: cdrtools-2.01-kernel25-support.patch --]
[-- Type: text/plain, Size: 602 bytes --]
--- cdrtools-2.01/libscg/scsi-linux-sg.c.orig 2003-02-05 21:01:31.000000000 +0200
+++ cdrtools-2.01/libscg/scsi-linux-sg.c 2003-02-05 21:16:33.000000000 +0200
@@ -66,6 +66,11 @@
#if LINUX_VERSION_CODE >= 0x01031a /* <linux/scsi.h> introduced in 1.3.26 */
#if LINUX_VERSION_CODE >= 0x020000 /* <scsi/scsi.h> introduced somewhere. */
/* Need to fine tune the ifdef so we get the transition point right. */
+#if LINUX_VERSION_CODE >= 0x020500 /* 2.5.x breaks things again */
+#define __KERNEL__
+#include <asm/types.h>
+#undef __KERNEL__
+#endif
#include <scsi/scsi.h>
#else
#include <linux/scsi.h>
next reply other threads:[~2003-02-14 5:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 5:48 Sahara Workshop [this message]
2003-02-14 5:58 ` Problems with 2.5.*'s SCSI headers and cdrtools Christoph Hellwig
2003-02-14 6:07 ` Martin Schlemmer
2003-02-14 6:21 ` Christoph Hellwig
2003-02-14 6:27 ` Sahara Workshop
2003-02-14 6:32 ` Christoph Hellwig
2003-02-14 8:48 ` Martin Schlemmer
2003-02-14 6:00 ` Zwane Mwaikambo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1045201685.5971.78.camel@workshop.saharact.lan \
--to=workshop@cpt.saharapc.co.za \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.