Re: Unresolved symbols when building kernel modules with make-kpkg, worked fine before
On Thu, Jun 05, 2003 at 11:23:49AM -0500, Manoj Srivastava wrote:
> On Thu, 5 Jun 2003 16:59:04 +0200, Sven Luther <firstname.lastname@example.org> said:
> > On Thu, Jun 05, 2003 at 10:43:22AM -0300, Theo Cabrerizo Diem wrote:
> >> Hi,
> >> I'm using unstable (gcc 3.3) and won't build. I've installed
> >> gcc-3.2 package, changed HOSTCC and CC variables in kernel Makefile
> >> to gcc-3.2 and worked fine !...
> > I did that too, too bad that make-kpkg doesn't have a variable were
> > you can specify the gcc to use or something such.
> Why should it? There is a perfectly good way of doing this using
> MAKEFLAGS; without adding to the feeping creaturism that has already
> infected kernel-package.
> It is even documented in the README.
Which README ?
/usr/share/kernel-package$ grep MAKEFLAGS *
/usr/local/src/2.4.21-pre5/linux-2.4.21-pre5$ grep MAKEFLAGS *
There seems to be no mention of it anywhere ?