Re: 2.6.16.19 + gcc-4.1.1

>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


Jan Engelhardt
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: 2.6.16.19 + gcc-4.1.1
    • From: Alistair John Strachan <[email protected]>

• References:
  • 2.6.16.19 + gcc-4.1.1
    • From: Russell Whitaker <[email protected]>
  • Re: 2.6.16.19 + gcc-4.1.1
    • From: "Avuton Olrich" <[email protected]>
  • Re: 2.6.16.19 + gcc-4.1.1
    • From: Brice Goglin <[email protected]>

• Prev by Date: Re: [RFC/PATCH 1/2] in-kernel sockets API
• Next by Date: Re: bad command responsiveness Proliant DL 585
• Previous by thread: Re: 2.6.16.19 + gcc-4.1.1
• Next by thread: Re: 2.6.16.19 + gcc-4.1.1
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]