Re: [BProc] a packaging issue in bproc-4.0.0pre5

[<er...@he...>]

On Thu, Jul 08, 2004 at 02:49:59PM -0600, Michal Jaegermann wrote:
> Changes in Makefiles mean that vmadump kernel module is installed
> somewhat indirectly.  An unfortunate side-effect of that is that
> vmadump.h header is no longer installed in /usr/include/sys.
> This prevents compilation of things like cmtools and beoboot as they
> want to see that header.  This is likely harder to notice when
> you have "historical" headers present but hits when you are doing
> that from scratch.
> 
> There are likely various ways to get around that.  I just split
> an 'install' target in vmadump/Makefile into 'install-headers'
> and 'install', which depend on the first, and in the top Makefile
> added to INSTALL_TARGETS something which does
> '$(MAKE) -C vmadump install-headers' and things are fine again.
> 
> BTW - "BuildRequires:" in beboot.spec for beoboot-cm1.9 needs
> both cmtools-devel and bproc-devel as headers from both packages
> are used.
> 
> Another note - a default value for LINUX in various spec files
> should really be /lib/modules/$(uname -r)/build instead of
> /usr/src/linux.  Nowadays you will not find what is needed in
> the later, and similar, locations while data required for building
> external modules for the current kernel should be there under
> /lib/modules/$(uname -r)/build - be that a symlink or an actual
> directory.

Thanks for finding this stuff.  Can make some patches and send them to
me?

- Erik