From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750939AbWFNRGZ (ORCPT ); Wed, 14 Jun 2006 13:06:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750936AbWFNRGZ (ORCPT ); Wed, 14 Jun 2006 13:06:25 -0400 Received: from smtp.nildram.co.uk ([195.112.4.54]:42504 "EHLO smtp.nildram.co.uk") by vger.kernel.org with ESMTP id S1750707AbWFNRGZ (ORCPT ); Wed, 14 Jun 2006 13:06:25 -0400 From: Alistair John Strachan To: Jan Engelhardt Subject: Re: 2.6.16.19 + gcc-4.1.1 Date: Wed, 14 Jun 2006 18:06:25 +0100 User-Agent: KMail/1.9.3 Cc: Brice Goglin , Avuton Olrich , Russell Whitaker , linux-kernel@vger.kernel.org References: <448F8C53.5010406@ens-lyon.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200606141806.25124.s0348365@sms.ed.ac.uk> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday 14 June 2006 10:33, Jan Engelhardt wrote: > >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. > > You can _still_ build bzImage and modules separately. > > The _default_ kernel Makefile target though reads (sth. like) > > all: bzImage modules Maybe for consistency with other packages, the default "make install" should imply modules_install too. I know you can hack around this with /sbin/installkernel (on at least x86 and x86_64), but it's counterintuitive. I guess the reason is that 'install' has always meant "just the bzImage please", and sometimes it's valid to install only a bzImage without reinstalling modules. However, it just leads to problems such at the original poster's. -- Cheers, Alistair. Third year Computer Science undergraduate. 1F2 55 South Clerk Street, Edinburgh, UK.