All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Brice Goglin <Brice.Goglin@ens-lyon.org>
Cc: Avuton Olrich <avuton@gmail.com>,
	Russell Whitaker <russ@ashlandhome.net>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.16.19 + gcc-4.1.1
Date: Wed, 14 Jun 2006 06:20:08 +0200	[thread overview]
Message-ID: <20060614042007.GD13255@w.ods.org> (raw)
In-Reply-To: <448F8C53.5010406@ens-lyon.org>

On Wed, Jun 14, 2006 at 12:10:59AM -0400, Brice Goglin wrote:
> Avuton Olrich wrote:
> > On 6/13/06, Russell Whitaker <russ@ashlandhome.net> wrote:
> >> Then, after mrproper, rebuilt with gcc-4.1.1, no other changes.
> >>    compiles ok, installs ok. But, when attempting to load a module, get
> >>    the following message:  version magic '2.6.16.19via K6 gcc-4.1',
> >>    should be '2.6.16.19via 486 gcc-3.3'
> >
> > You may have forgotten to "make modules modules_install"
> 
> Actually, "make modules" does not exist anymore with 2.6. Both built-in
> and modular stuff are built at the same time.
> Only "make modules_install" is still required.

What's this bullshit ?

$ grep ^modules: Makefile
modules: $(vmlinux-dirs) $(if $(KBUILD_BUILTIN),vmlinux)
modules: $(module-dirs)

Avuton is right, you *have* forgotten to make modules.

> Brice

Willy


  reply	other threads:[~2006-06-14  4:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-14  2:23 2.6.16.19 + gcc-4.1.1 Russell Whitaker
2006-06-14  3:49 ` Avuton Olrich
2006-06-14  4:10   ` Brice Goglin
2006-06-14  4:20     ` Willy Tarreau [this message]
2006-06-14  4:27       ` Brice Goglin
2006-06-16 19:43         ` Russell Whitaker
2006-06-14  5:09       ` Russell Whitaker
2006-06-14  9:33     ` Jan Engelhardt
2006-06-14 17:06       ` Alistair John Strachan
2006-06-14  5:24 ` Tino Keitel

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=20060614042007.GD13255@w.ods.org \
    --to=w@1wt.eu \
    --cc=Brice.Goglin@ens-lyon.org \
    --cc=avuton@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=russ@ashlandhome.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.