Bill Davidsen schrieb: > Alexy Khrabrov wrote: >> The 2.6 build system compiles only those modules whose config >> changed. However, the install still installs all modules. >> >> Is there a way to entice make modules_install to install only those >> new modules we've actually just changed/built? > > Out of curiosity, why? I've noticed this, but the copy runs so fast I > never really thought about it as an issue. Not here. On the 933 MHz P3 machine I use for driver development, "make modules_install" takes so much time that I always copy my modules by hand instead after recompiling them. -- Tilman Schmidt E-Mail: [email protected] Bonn, Germany Diese Nachricht besteht zu 100% aus wiederverwerteten Bits. Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
Attachment:
signature.asc
Description: OpenPGP digital signature
- References:
- installing only the newly (re)built modules
- From: "Alexy Khrabrov" <[email protected]>
- Re: installing only the newly (re)built modules
- From: Bill Davidsen <[email protected]>
- installing only the newly (re)built modules
- Prev by Date: Re: 2.6.20-rc4: known unfixed regressions (v3)
- Next by Date: Re: [linux-usb-devel] 2.6.20-rc4: null pointer deref in khubd
- Previous by thread: Re: installing only the newly (re)built modules
- Next by thread: Re: [PATCH 1/2] reimplement flush_workqueue()
- Index(es):
 |