mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Meino Christian Cramer <mccramer@s.netic.de>
To: alan@lxorguk.ukuu.org.uk
Cc: mccramer@s.netic.de, linux-kernel@vger.kernel.org
Subject: Re: Problems with 2.4.5ac1[78]
Date: Tue, 26 Jun 2001 18:45:46 +0200	[thread overview]
Message-ID: <20010626184546H.mccramer@s.netic.de> (raw)
In-Reply-To: <E15EuO6-0003dz-00@the-village.bc.nu>
In-Reply-To: <20010626161854G.mccramer@s.netic.de> <E15EuO6-0003dz-00@the-village.bc.nu>

From: Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Problems with 2.4.5ac1[78]
Date: Tue, 26 Jun 2001 16:04:22 +0100 (BST)
Message-ID: <E15EuO6-0003dz-00@the-village.bc.nu>


Thanks a lot, Alan ! :o)

That's it! My build-script only did a make dep _clean_ bzImage modules
modules_install.
With a make distclean before all runs smooth...

  keep hacking on the right site of life ! :-)
  Meino  

> >  I tried to compile linux-2.4.5ac17 with processor type "Athlon"
> >  settings.
> > 
> >  Compilation/Install was successful. But boot produces dozens of
> >  "unresolved symbols" if trying to insmod any of the modules.
> > 
> >  Not one module was insmodded successfully.
> 
> Sounds like your build wasnt clean. Save your .config file and make distclean
> is sometimes needed when changing SMP or CPU types - yes its a bug in the
> config setup really
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


      parent reply	other threads:[~2001-06-26 16:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-26 14:18 Meino Christian Cramer
2001-06-26 15:04 ` Alan Cox
2001-06-26 16:45 ` Meino Christian Cramer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010626184546H.mccramer@s.netic.de \
    --to=mccramer@s.netic.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®