Re: Unresolved symbols when building kernel modules with make-kpkg, worked fine before
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.
manoj
--
"I prefer to think that God is not dead, just drunk." John Huston
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Reply to: