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 <sven.luther@wanadoo.fr> 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.
>
> The kernel Makefile overrides the environment variables CC and
> HOSTCC, or else the MAKEFLAGS over ride would not have been needed.
That said, the MAKEFLAGS is not listed as environment variable in the
make-kpkg man page, while the following are :
ENVIRONMENT VARIABLES
The following variables (documented above) affect make-kpkg:
DEBIAN_REVISION_MANDATORY APPEND_TO_VERSION VERSION_H_OK
PATCH_THE_KERNEL NO_UNPATCH_BY_DEFAULT KPKG_ARCH CROSS_COMPILE
KPKG_SUBARCH ARCH_IN_NAME INITRD SOURCE_CLEAN_HOOK MODULE_LOC
Is there a reason for that ?
Furthermore, it would be nice if you could add a :
MAKEFLAGS := "CC=gcc-3.2"
line to your /etc/kernel-pkg.conf, like it is possible with at least
some other environment variables (ROOT_CMD and PATCH_THE_KERNEL seem to
work).
But then, maybe there are technical problems with this that i am not
aware of.
Friendly,
Sven Luther
Reply to: