On Tuesday 09 December 2003 09:46, John L. Fjellstad wrote:
> Yeah, I figured that out after looking at the dependency list of
> the kernel-packages. I'm wondering though if using gcc3.3 would
> have any impact (since everything else on the stable system would
> have the programs compiled with gcc
Colin Watson wrote:
> The kernel doesn't use the libc, so I expect that this is a red herring.
> (I don't know the real answer, though.)
Yeah, I figured that out after looking at the dependency list of the
kernel-packages. I'm wondering though if using gcc3.3 would have any
impact (since everyth
On Thu, Dec 04, 2003 at 04:29:51PM +0100, John L. Fjellstad wrote:
> My server runs Debian stable, while my workstation runs Debian testing.
> Since the server is a slower machine, I would like to create the kernel
> package on my workstation and install the deb package on my server.
> Is this poss
On Monday 08 December 2003 00:59, Bill Goudie wrote:
> The unresolved symbols still exist -- depmod is run with "-q"
> from /etc/init.d/modutils. This suppresses the error warnings.
Well, what I did was run this from the command line:
# depmod -a
Even this:
# depmod -a -e
And it doesn't complai
On Sun, Dec 07, 2003 at 05:37:16PM -0600, Bill Goudie wrote:
> On Sun, Dec 07, 2003 at 11:28:41PM +0100, Magnus von Koeller wrote:
> > On Sunday 07 December 2003 23:11, Bill Goudie wrote:
> > > The upshot of all this is that modules with unresolved symbols
> > > require functions which were exclude
On Sun, Dec 07, 2003 at 11:28:41PM +0100, Magnus von Koeller wrote:
> On Sunday 07 December 2003 23:11, Bill Goudie wrote:
> > The upshot of all this is that modules with unresolved symbols
> > require functions which were excluded from both the kernel and any
> > other installed modules for that k
On Sunday 07 December 2003 23:11, Bill Goudie wrote:
> The upshot of all this is that modules with unresolved symbols
> require functions which were excluded from both the kernel and any
> other installed modules for that kernel version. If for some
> reason you built this module but don't need it
On Sun, Dec 07, 2003 at 01:46:09AM +0100, John L. Fjellstad wrote:
> Magnus von Koeller wrote:
> > I mean, after all, you can still boot to the old kernel with LinuxOLD,
> > can't you? Or is your machine that uptime-critical?
>
> No, I'm just worried because I have unplugged everything on it (moni
On Sunday 07 December 2003 19:28, Roberto Sanchez wrote:
> Do you mean to install the kernel and ignore the unresolved symbol
> errors? Then try booting the new kernel to see if it actually
> works?
That's what I did in your exact situation and it worked out just fine.
I'm not getting any errors
Magnus von Koeller wrote:
On Sunday 07 December 2003 18:06, Roberto Sanchez wrote:
I'm a little late in the thread, but I think I am having the same
problem. Last night I compiled a vanilla 2.4.23 kernel on my Sid
workstation to then install it on my Woody server. Before doing
the compile, I mov
On Sunday 07 December 2003 18:06, Roberto Sanchez wrote:
> I'm a little late in the thread, but I think I am having the same
> problem. Last night I compiled a vanilla 2.4.23 kernel on my Sid
> workstation to then install it on my Woody server. Before doing
> the compile, I moved my /usr/bin/gcc
John L. Fjellstad wrote:
Magnus von Koeller wrote:
I mean, after all, you can still boot to the old kernel with LinuxOLD,
can't you? Or is your machine that uptime-critical?
No, I'm just worried because I have unplugged everything on it (monitor,
keyboard etc). So the only way I will find out s
On Sunday 07 December 2003 01:46, John L. Fjellstad wrote:
> No, I'm just worried because I have unplugged everything on it
> (monitor, keyboard etc). So the only way I will find out something
> is wrong is if it doesn't come up after a couple of minutes (and
> then I have to spend some time pluggi
Magnus von Koeller wrote:
> I mean, after all, you can still boot to the old kernel with LinuxOLD,
> can't you? Or is your machine that uptime-critical?
No, I'm just worried because I have unplugged everything on it (monitor,
keyboard etc). So the only way I will find out something is wrong is if
On Saturday 06 December 2003 02:05, John L. Fjellstad wrote:
> The reason I got worried was because it's the first time I tried to
> kompile the kernel on a different system than the one I was going
> to install it on.
Well, I'm telling you - I was just as worried as you were. I mean, I
was insta
Hugo Vanwoerkom wrote:
> When you install the modules deb you will get unresolved symbols because
> the running kernel is not the same. Goes away when you boot with the new
> kernel.
But that doesn't make sense, because then I would see the same kind of
behaviour (depmod complaining about missing
Magnus von Koeller wrote:
On Thursday 04 December 2003 16:29, John L. Fjellstad wrote:
When I tried, I got several unresolved symbols when installing the
deb package during the /sbin/depmod -a stage. I'm guessing because
testing uses libc6 2.3.2, while stable uses libc6 2.2.5.
Hey, finally some
On Thursday 04 December 2003 16:29, John L. Fjellstad wrote:
> When I tried, I got several unresolved symbols when installing the
> deb package during the /sbin/depmod -a stage. I'm guessing because
> testing uses libc6 2.3.2, while stable uses libc6 2.2.5.
Hey, finally someone with the same prob
18 matches
Mail list logo
