Bug#196293: installation-reports: trying debian-installer (2003-06-04)

2003-06-06 Thread Henning Meier-Geinitz
On Thu, Jun 05, 2003 at 11:35:02PM +0200, Henning Meier-Geinitz wrote: > Package: installation-reports > Version: unavailable; reported 2003-06-05 > Severity: normal > > INSTALL REPORT [...] I had another try. > I need the rtl8139 kernel module That's what the automatic detection says. But it

Bug#196293: installation-reports: trying debian-installer (2003-06-04)

2003-06-06 Thread Henning Meier-Geinitz
On Thu, Jun 05, 2003 at 11:35:02PM +0200, Henning Meier-Geinitz wrote: > Package: installation-reports > Version: unavailable; reported 2003-06-05 > Severity: normal > > INSTALL REPORT [...] I had another try. > I need the rtl8139 kernel module That's what the automatic detection says. But it

Bug#196293: installation-reports: trying debian-installer (2003-06-04)

2003-06-06 Thread Henning Meier-Geinitz
Package: installation-reports Version: unavailable; reported 2003-06-05 Severity: normal INSTALL REPORT Debian-installer-version: sarge-i386-businesscard.iso from gluck (2003-06-04) uname -a: Linux (none) 2.4.20-1-386 #3 Sat Mar 22 12:11:40 EST 2003 i686 unknown Date: 2003-06-05 18:00 Method: Boo

Re: Unresolved symbols when building kernel modules with make-kpkg, worked fine before

2003-06-06 Thread Bob Nielsen
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

Re: Unresolved symbols when building kernel modules withmake-kpkg, worked fine before

2003-06-06 Thread Theo Cabrerizo Diem
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

Re: Unresolved symbols when building kernel modules with make-kpkg, worked fine before

2003-06-06 Thread Ross Boylan
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

Re: Unresolved symbols when building kernel modules with make-kpkg, worked fine before

2003-06-06 Thread Sven Luther
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

Re: Unresolved symbols when building kernel modules withmake-kpkg, worked fine before

2003-06-06 Thread Theo Cabrerizo Diem
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) []'s On Wed, 2003-06-04 at 20:57, Ross Boylan wrote: > On Wed,