Re: Unresolved symbols when building kernel modules with make-kpkg, worked fine before
I didn't touch the Makefile, but temporarily repointed the gcc symlink
to gcc-3.2 and everything was happy (lm-sensors is working again).
After compiling the modules I changed the symlink back to gcc-3.3.
Maybe gcc could use an /etc/alternatives entry :^)
On Thu, Jun 05, 2003 at 03:44:01PM -0300, Theo Cabrerizo Diem wrote:
> Hi Ross,
> I don't know ... =) ... I only changed CC but a module (can't remmember
> if was i2c, lm-sensors or mppe) still used gcc ... so I changed HOSTCC
> too ...
> I was building a 2.4.20 kernel with xfs, preempt, freeswan and mppe in a
> Debian unstable.
> and yes .. seems to work all patches together ;o)
> On Thu, 2003-06-05 at 14:44, Ross Boylan wrote:
> > 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 !...
> > >
> > > Maybe this isn't the best solution available, but worked to me ;o)
> > >
> > I thought redefining CC was sufficient. What's HOSTCC, and who uses
> > it?
> > P.S. Trimming the distribution list.
> To UNSUBSCRIBE, email to firstname.lastname@example.org
> with a subject of "unsubscribe". Trouble? Contact email@example.com
Bob Nielsen, N7XY firstname.lastname@example.org
Bainbridge Island, WA http://www.n7xy.net
IOTA NA-065, USI WA-028S