You might be able to get away w/ simply including the lvm-specific kernel
headers in your package, as long as the lower level asm stuff that it uses
haven't changed their interface in 2.6. OTOH, it also might introduce
subtle bugs. Maybe you're better off build-dep'ing.
Sigh. I should probably
On Wed, Nov 19, 2003 at 03:33:53PM +0100, Christoph Hellwig wrote:
> On Wed, Nov 19, 2003 at 02:18:34PM +, Patrick Caulfield wrote:
> > The only solution I can think of is for the lvm10 package to build-depend on
> > (eg) kernel-source-2.4.19, then in the build script untar the header
> > files
On Wed, Nov 19, 2003 at 02:18:34PM +, Patrick Caulfield wrote:
> The only solution I can think of is for the lvm10 package to build-depend on
> (eg) kernel-source-2.4.19, then in the build script untar the header
> files, make the arch symlink (ugh) and compile against that.
>
> Does anyone el
LVM1 includes kernel headers in its build - yeah, I know, but it does interface
(rather too) tightly into the kernel.
The problem now is that the linux-kernel-headers package has Linux 2.6 files in
it rather than 2.4 and LVM(1) is not supported in 2.6. so it doesn't build.
This isn't a new probl
4 matches
Mail list logo
