[kbuild-devel] Re: Announce: Kernel Build for 2.5, Release 2.0 is available
On Sun, 14 Apr 2002 23:23:16 +1000, Keith Owens <[EMAIL PROTECTED]> wrote: >Updates for kbuild 2.5 at >http://sourceforge.net/project/showfiles.php?group_id=18813 >kbuild-2.5-i386-2.5.8-pre3-1.bz2 i386-2.5.8-pre3-1 was missing this bit, against i386-2.5.8-pre3-1. Apply this patch or use kbuild-2.5-i386-2.5.8-pre3-2.bz2. diff -urN 2.5.8-pre3-kbuild-2.5/arch/i386/kernel/Makefile.in 2.5.8-pre3-kbuild-2.5-save/arch/i386/kernel/Makefile.in --- 2.5.8-pre3-kbuild-2.5/arch/i386/kernel/Makefile.in Tue Apr 16 11:09:25 2002 +++ 2.5.8-pre3-kbuild-2.5-save/arch/i386/kernel/Makefile.in Sun Apr 14 11:45:28 +2002 @@ -27,5 +27,11 @@ # uses_asm_offsets(entry.o) +# "Unterminated character constants", due to mismatched ' in comments +extra_aflags(entry.o -traditional) extra_aflags(head.o -traditional) extra_aflags(trampoline.o -traditional) + +extra_cflags(acpi.o $(fixme_acpi_includes)) +extra_cflags(pci-irq.o $(fixme_acpi_includes)) +extra_cflags(setup.o $(fixme_acpi_includes)) ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
[kbuild-devel] Re: Announce: Kernel Build for 2.5, Release 2.0 is available
Updates for kbuild 2.5 at http://sourceforge.net/project/showfiles.php?group_id=18813 I made the mistake of use the sourceforge fast release system. Turns out it creates new releases for each file so there are multiple 'Release 2.0' headings. Ignore that, they are all part of Release 2.0. kbuild-2.5-core-5.bz2. Changes from core-4 to core-5. Split config immediately after make *config instead of as a side effect of the next target. Cleaner rules, fewer special cases. Add include/sound on include list. New command 'select_elsewhere()'. A complete kludge to work around the crc32.o problem in 2.5 kernels. Selection of CONFIG_CRC32 should really be done in CML but CML1 cannot cope, so add a kbuild kludge to overcome the incomplete CML data. Fix a bug where cached timestamps prevented the detection of some config changes. kbuild-2.5-common-2.4.18-4.bz2. Changes from common-2.4.18-3 to common-2.4.18-4. DocBook tweaks. Add dummy dep rule for people who forget that make dep is not required. New - support for 2.5 kernels, starting with 2.5.8-pre3. i386 only for now, ia64 to follow. kbuild-2.5-common-2.5.8-pre3-1.bz2. Built from scratch, there was too much divergence between 2.4.18 and 2.5.8-pre3 Makefiles. The result was cross checked against Peter Samuelson's patch for 2.5.6pre1, for which much thanks. kbuild-2.5-i386-2.5.8-pre3-1.bz2 Mainly from i386-2.4.18-1, with updates for i386-2.5.8-pre3. TODO: Add config help to common-2.5.8-pre3-1. I could not decide where to put the config help in 2.5 so I left it until -2. Sync common-2.4.19-pre* with common-2.4.18-. Will be done when next 2.4.19-pre* kernel comes out. Add 2.4.18-ia64-020410 support. Already supports 2.4.18-ia64-020226. Add 2.5.8-pre3-ia64-020411 support. Wait for other arch maintainers to roll patches against kernel 2.5. Create Release 2.1 with the latest version of each kernel and arch branch. See how stable release 2.1 is then contact Linus. ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
[kbuild-devel] Re: Announce: Kernel Build for 2.5, Release 2.0 is available
New core and common code for kbuild 2.5 is available in http://sourceforge.net/project/showfiles.php?group_id=18813&release_id=83065 Changes from core-3 to core-4. GNUism removal. WISH is exposed in case your wish binary is not in /usr/bin/wish. awk changed to $(AWK) throughout. PP_variables added to expose headers and compiler flags that might be different on on non-Linux build platforms. Force the use of KBUILD_SHELL instead of relying on a working build platform shell. Drop back to getopt if getopt_long is not available on the build platform, in which case only the single character command flags are available. Documentation updates. *** kbuild 2.5-core-4 runs on Solaris using gcc, gmake, gawk. *** Would any brave (or foolhardy) person like to run kbuild 2.5 under Cygwin or other build platforms? Changes from common-2.4.18-2 to common-2.4.18-3. Yet more aic7xxx problems :( Documentation updates. Correct fencepost error in scripts/tkparse. Changes from common-2.4.19-pre6-1 to common-2.4.19-pre6-2. As for common-2.4.18-2 -> 3. ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
[kbuild-devel] Re: Announce: Kernel Build for 2.5, Release 2.0 is available
On 09 Apr 2002 12:00:55 -0700, Thomas Duffy <[EMAIL PROTECTED]> wrote: >Ok, with core-3, now kbuild 2.5 v2.0 works on sparc64. There was one >typo in one sparc64 Makefile.in from 1.12. Attached is the patch to fix >this. > >Also attached is the full kbuild 2.0 patch for sparc64 2.4.18 tree. Thanks Tom. Uploaded as http://prdownloads.sourceforge.net/kbuild/kbuild-2.5-sparc64-2.4.18-1.bz2 I will get 2.5.8-pre2 working and upload that then wait for a couple of days to see if any other arch maintainers have kbuild 2.5 patches. Then it will be time for Release 2.1 which will be a candidate to go to Linus. ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
[kbuild-devel] Re: Announce: Kernel Build for 2.5, Release 2.0 is available
New core, common and ia64 code for kbuild 2.5 is available in http://sourceforge.net/project/showfiles.php?group_id=18813&release_id=83065 Changes from core-2 to core-3. Ensure that database records are aligned. Do not assume that keys are aligned (all the world is not a 386). Changes from common-2.4.18-1 to common-2.4.18-2. Minor changes to common code to suit ia64. New, ia64-020226-2.4.18-1. core-3 works on ia64, it should work on other architectures that have alignment requirements such as sparc. Other architecture maintainers can use core-3 and common-2.4.18-2 as a starting point for porting this release of kbuild 2.5 to their architecture. The existing arch patches from Release 1.12 are a good starting point, ia64 was almost unchanged from Release 1.12 to 2.0. I have not tested any of the kbuild 2.5 code on big endian machines. It should work as is but it would be nice to have it confirmed. ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
[kbuild-devel] Re: Announce: Kernel Build for 2.5, Release 2.0 is available
New core code for kbuild 2.5 is available in http://prdownloads.sourceforge.net/kbuild/kbuild-2.5-core-2.bz2 Backout core-1 then apply this patch. Changes from core-1. Do not set KBUILD_OBJECT for objects that are linked into multiple conglomerates, there is no unambiguous KBUILD_OBJECT value for such objects. These objects will not be able to use module or boot parameters in the forthcoming merge of module and boot parameter handling. Create object directory before copying .prepend/.append files. Fixes Richard Chan's bug report. make foo/bar.[si] works again. Fixes Roman Zippel bug report. Correctly standardize relative names. Fixes Roman Zippel "touch include/linux/mm.h" does nothing bug. Only affected builds in common source and object mode. Update timestamps on files generated by make as they are used. This removes some spurious rebuilds. Changes to the underlying database layout to reduce the mmap footprint. This speeds up kbuild 2.5 on smaller machines. ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
[kbuild-devel] Re: Announce: Kernel Build for 2.5, Release 2.0 is available
Hi, On Mon, 8 Apr 2002, Keith Owens wrote: > >"touch include/linux/mm.h" doesn't cause a recompile of any object. > > I have found a bug that is probably causing your problem. Can you > confirm that you are using a common source and object directory, i.e. > no separate object tree? Yes, so far I only tested this. bye, Roman ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
[kbuild-devel] Re: Announce: Kernel Build for 2.5, Release 2.0 is available
On Sun, 07 Apr 2002 16:18:12 +0200, Roman Zippel <[EMAIL PROTECTED]> wrote: >"touch include/linux/mm.h" doesn't cause a recompile of any object. I have found a bug that is probably causing your problem. Can you confirm that you are using a common source and object directory, i.e. no separate object tree? ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
Re: [kbuild-devel] Re: Announce: Kernel Build for 2.5, Release 2.0 is available
Keith Owens wrote: >It takes time to do all the analysis to work out what has changed and >what has been affected. You might know that you only changed one file >but kernel build and make don't know that until they have checked >everything. Changing one file or specifying a command override might >affect one file or it might affect the entire kernel. > >If you know that you have only changed one source file and you have not >altered the Makefiles or the dependency chain in any way, then it >_might_ be safe to just rebuild that one file, use NO_MAKEFILE_GEN=1. >Otherwise let kbuild work out what has been affected. > Humans/Hackers are really really REALLY good at making assumptions and using assumptions that are outdated, thus leading to mistakes. Some/many hackers like to live in there own little world and not worry about the effect they might have on other developers. Using a dependency maintenance tool (such as Make, Cook, ...) to automate the build is the _ONLY_ safe way to be sure the build is correct. This assumes that the build system itself is 100% correct :) Regards, Brendan Simon. ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
[kbuild-devel] Re: Announce: Kernel Build for 2.5, Release 2.0 is available
Hi, Keith Owens wrote: > It takes time to do all the analysis to work out what has changed and > what has been affected. You might know that you only changed one file > but kernel build and make don't know that until they have checked > everything. Changing one file or specifying a command override might > affect one file or it might affect the entire kernel. Doing that analysis once is fine. After that it should know what it has to check if I only want foo/bar.o recompiled and that shouldn't take that long. > Otherwise let kbuild work out what has been affected. That's the problem with kernel hackers, they want to know what's going on. :) bye, Roman ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
[kbuild-devel] Re: Announce: Kernel Build for 2.5, Release 2.0 is available
On Sun, 07 Apr 2002 16:51:36 +0200, Roman Zippel <[EMAIL PROTECTED]> wrote: >Keith Owens wrote: >> make NO_MAKEFILE_GEN=1 foo/bar.o. Very low overhead for quick and >> dirty testing of changes, but if you want an accurate kernel build, you >> have to take the overhead. kbuild 2.4 overhead for a full build when >> only minor changes have been made is even worse. > >I don't want a kernel build, I just want a single object file to be >rebuilt?! >I can understand that it takes longer, when I change a Makefile or the >config, but why has the Makefile to be rebuilt, when only a source file >changed? It takes time to do all the analysis to work out what has changed and what has been affected. You might know that you only changed one file but kernel build and make don't know that until they have checked everything. Changing one file or specifying a command override might affect one file or it might affect the entire kernel. If you know that you have only changed one source file and you have not altered the Makefiles or the dependency chain in any way, then it _might_ be safe to just rebuild that one file, use NO_MAKEFILE_GEN=1. Otherwise let kbuild work out what has been affected. ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
[kbuild-devel] Re: Announce: Kernel Build for 2.5, Release 2.0 is available
Hi, Keith Owens wrote: > >These 14 seconds (or 37 seconds on my machine) are always needed > >whatever I try, e.g. "make foo/bar.o" also needs that time. > > make NO_MAKEFILE_GEN=1 foo/bar.o. Very low overhead for quick and > dirty testing of changes, but if you want an accurate kernel build, you > have to take the overhead. kbuild 2.4 overhead for a full build when > only minor changes have been made is even worse. I don't want a kernel build, I just want a single object file to be rebuilt?! I can understand that it takes longer, when I change a Makefile or the config, but why has the Makefile to be rebuilt, when only a source file changed? bye, Roman ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
[kbuild-devel] Re: Announce: Kernel Build for 2.5, Release 2.0 is available
On Sun, 07 Apr 2002 16:18:12 +0200, Roman Zippel <[EMAIL PROTECTED]> wrote: >Keith Owens wrote: > >> kbuild 2.5: >> make -j8 oldconfig installable 8:51 (no make dep needed :) >> make -j8 oldconfig installable :14 (second run, no changes) > >These 14 seconds (or 37 seconds on my machine) are always needed >whatever I try, e.g. "make foo/bar.o" also needs that time. make NO_MAKEFILE_GEN=1 foo/bar.o. Very low overhead for quick and dirty testing of changes, but if you want an accurate kernel build, you have to take the overhead. kbuild 2.4 overhead for a full build when only minor changes have been made is even worse. >Some other problems: >"make foo/bar.[si]" doesn't work anymore. Hmm, that was working, I will investigate. >"touch include/linux/mm.h" doesn't cause a recompile of any object. I have found some cases where the timestamps are not tracked correctly so changes to dependencies are not always detected. Fixed in build-2.5-core-2, out tomorrow. ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
[kbuild-devel] Re: Announce: Kernel Build for 2.5, Release 2.0 is available
Hi, Keith Owens wrote: > kbuild 2.5: > make -j8 oldconfig installable 8:51 (no make dep needed :) > make -j8 oldconfig installable :14 (second run, no changes) These 14 seconds (or 37 seconds on my machine) are always needed whatever I try, e.g. "make foo/bar.o" also needs that time. Some other problems: "make foo/bar.[si]" doesn't work anymore. "touch include/linux/mm.h" doesn't cause a recompile of any object. bye, Roman ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
[kbuild-devel] Re: Announce: Kernel Build for 2.5, Release 2.0 is available
2.4.19-pre6 i386 patches are now available for kbuild 2.5. Instructions at the start of each patch. Kai, could you verify that the ISDN selection works as expected, both old and new ISDN code? http://sourceforge.net/project/showfiles.php?group_id=18813&release_id=83065 kbuild-2.5-core-1.bz2 (unchanged) kbuild-2.5-common-2.4.19-pre6-1.bz2(new) kbuild-2.5-i386-2.4.19-pre6-1.bz2 (new) ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
[kbuild-devel] Re: Announce: Kernel Build for 2.5, Release 2.0 is available
On Sat, 6 Apr 2002 17:35:39 +0100, Russell King <[EMAIL PROTECTED]> wrote: >On Sat, Apr 06, 2002 at 12:03:15PM +1000, Keith Owens wrote: >> The timings above were for exactly the same .config on the same build >> machine, > >Can you provide details of this machine? It was in the original message. http://marc.theaimsgroup.com/?l=linux-kernel&m=101800612931031&w=2 ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
[kbuild-devel] Re: Announce: Kernel Build for 2.5, Release 2.0 is available
[Sebastian Heidl] > > It's signed. Just pipe it through gpg with Keiths public key. [Mike Fedyk] > Signed means that there is a checksum at the bottom that you can > verify with gpg/pgp to see if the message was tampered with, but the > text itself it still in ascii and not encoded. Not that it matters (he did send out a reprint) but the message *was* merely signed. The base64-looking encoding is merely a way to make sure that MTAs and other software don't screw with tabs, line breaks, etc., which would make the signature look invalid. > This looks encrypted to me. It doesn't look encrypted to gpg. Pipe the message to it, you'll see. Peter ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
[kbuild-devel] Re: Announce: Kernel Build for 2.5, Release 2.0 is available
On Sat, Apr 06, 2002 at 12:03:15PM +1000, Keith Owens wrote: > Just to avoid any confusion. kbuild 2.4 is the existing kernel build > system, as used in Marcelo's and Linus's kernels. kbuild 2.5 is the > complete rewrite of the kernel build system. So that means that you have a system which does more, is more accurate, and is faster than the system we currently use. Right? Rock on. Has anyone integrated the kbuild stuff into a BK tree, so I could pull from it and play with it? If not, I might have a go at it and make a bk://kbuild.bkbits.net project. -- --- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
[kbuild-devel] Re: Announce: Kernel Build for 2.5, Release 2.0 is available
On Sat, Apr 06, 2002 at 12:03:15PM +1000, Keith Owens wrote: > The timings above were for exactly the same .config on the same build > machine, Can you provide details of this machine? -- Russell King ([EMAIL PROTECTED])The developer of ARM Linux http://www.arm.linux.org.uk/personal/aboutme.html ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
[kbuild-devel] Re: Announce: Kernel Build for 2.5, Release 2.0 is available
Thanks to Peter Samuelson and Tom Duffy, 2.4.18 i386 patches are now available for kbuild 2.5. Instructions at the start of each patch. http://sourceforge.net/project/showfiles.php?group_id=18813&release_id=83065 kbuild-2.5-core-1.bz2 (unchanged) kbuild-2.5-common-2.4.18-1.bz2 (new) kbuild-2.5-i386-2.4.18-1.bz2 (new) ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
[kbuild-devel] Re: Announce: Kernel Build for 2.5, Release 2.0 is available
On Fri, 05 Apr 2002 21:26:08 +1000, Keith Owens <[EMAIL PROTECTED]> wrote: >kbuild 2.4: > make oldconfig0:07 > make dep 0:37 (make -j dep is unsafe on some architectures) > make -j8 bzImage modules 14:16 > Total15:00 > make -j8 bzImage modules 2:10 (second run, no changes, spurious rebuilds) > >kbuild 2.5: > make -j8 oldconfig installable 8:51 (no make dep needed :) > make -j8 oldconfig installable :14 (second run, no changes) Just to avoid any confusion. kbuild 2.4 is the existing kernel build system, as used in Marcelo's and Linus's kernels. kbuild 2.5 is the complete rewrite of the kernel build system. Although it says 2.5, kbuild 2.5 will run on 2.4 kernels, it was developed on 2.4. The timings above were for exactly the same .config on the same build machine, building a 2.4.16 kernel, using the existing and new kernel build system. Compared to the existing build system, kbuild 2.5 is much more robust (I found several bugs in the 2.4 rules while developing kbuild 2.5), provides more facilities, has debugging information, is more accurate (2.5 tracks everything, 2.4 only managed about 80% tracking accuracy) and still manages to run 30% faster than the existing build system. Although kbuild 2.5 will run on 2.4 kernels, I have no plans to send all of kbuild 2.5 to Marcelo. Changing the kernel build on a stable kernel is a bad idea. I will be sending some kbuild 2.4 bug fixes to Marcelo but not the rest of kbuild 2.5. I am now working on kbuild 2.5 patches for 2.4.18, 2.4.19-pre6, 2.5.7 and 2.5.8-pre1 as well as for other architectures, see http://sourceforge.net/projects/kbuild for updates. ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
[kbuild-devel] Re: Announce: Kernel Build for 2.5, Release 2.0 is available
On Fri, Apr 05, 2002 at 01:23:24PM +0200, Sebastian Heidl wrote: > On Fri, Apr 05, 2002 at 01:09:14PM +0200, Pavel Machek wrote: > > Hi! > > > > Nice, but what about decrypted version? > It's signed. Just pipe it through gpg with Keiths public key. Signed means that there is a checksum at the bottom that you can verify with gpg/pgp to see if the message was tampered with, but the text itself it still in ascii and not encoded. This looks encrypted to me. Mike ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
[kbuild-devel] Re: Announce: Kernel Build for 2.5, Release 2.0 is available
On Fri, Apr 05, 2002 at 01:09:14PM +0200, Pavel Machek wrote: > Hi! > > Nice, but what about decrypted version? It's signed. Just pipe it through gpg with Keiths public key. ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
[kbuild-devel] Re: Announce: Kernel Build for 2.5, Release 2.0 is available
Hi! Nice, but what about decrypted version? > -BEGIN PGP MESSAGE- > Version: GnuPG v1.0.4 (GNU/Linux) > Comment: Exmh version 2.1.1 10/15/1999 > > owGNVk2PG0UQzYcQWUsWivIHKocku5J3bG/2I+tsEsiSBJPdECUBkWN7psfueGZ6 > 1N2zXgdxQAgJCQ4cOSGuCHELd5AQF04IDvkDHCCIn4B41TNjeyOCiLTRbk9X1atX > r6r6s+bJ4ydOf/LRy1sXnkR/HP/pmXulE6R2GGysb2wG8jAd7Xzz4XRXZ05mbvXB > NJc9cvLQtfNEqOwyhSNhrHRXCrsqbKhUs9Fs3JOJFFbSWtAhHdNYmkwmNChUElGs > TX2wFmzQ8rg8xu8rpCyJA6ESMUhk0GyMnMt77bbVhQkl7IYyyCQCG/1Ihs62S9N2 > i+6KcCyGksqDVfhqUaQnWaJF1GyYOZqA0QVBQA91QeNMT2gyEo7cSE7JiimJgS4c > AXVlY4kv09tWGhrIiTDSe3gwYqRZposslCl4YeScGBzRgGPNs6JQR7JF6uKlTRJD > UGYdjteD7iZc9R0VHKU8QIhQ4G+4AaihOsAXwRfiIoGbNBdGWZ3N3CBas5EbeaB0 > YWvIwBXBKpIh4xoYkYUjyrXCH7HRac09hySnGaFP6a5w4UiWWWg4NiRMOFIORBeG > ccBraWppohJUUxJzpTKfdAZFUCwnzUYkphbpAp0Yw86pVHKcocykEa6E5yTQ5wsR > 0yJxKk+QznNRq0wjFcfScEIVfGektB54JZIUhgGQCAXtGl3kAQhrX0uuJCorDldL > s/Pple3trbWN9e7admdte/PS+cmVtWYjhLg5DpIBmFQ4xSR7KcwKWrPLcp7V1gPY > HYlsKBM97PFfRHRHTloUC+tAYqiNrBSAomZjy1zsCWOmtB++o6c+ewj6QEUqG5YV > hYtUphpXUpHnMqJIOOFBsKOgilIXDJokFrLNE8XlgH8fdLliSmWRzCX+y9xKi1WU > 6sw7WF6kevEaGnXG89y21BVM/sV4Lo5Fg1glqBHRg5EsIfmKE3JKlLTeDcAKaKkS > VosGkJ5XJntkgmtrRj1DUHr2jqa1G5vLUMUqnImUL2M0RbOmbTbe8rrmOkC9TPcC > Z1aiu1iflSxbiy1ct3bNHvv2DR0pAwq0QT5+eCWphloxFbwmorLjaul0g+4aJ6TT > ZuP1Io6nF2xFCfuPDPrd2LYdFLb9nigipVs8W99v76OROOMAvTYSFtglMKgsTIpI > RiVFXAT8WI1uS1UGfyUENKv/yOhTroFRQ214XEhjtIH2RzIcMxcQtuOxVqONMdyi > 8hY3xpyOdaoB2WoYcneIpIrIPFRcoaEdf5sYKKUMIOcdAeB99LYUET41G4VlFMLv > Fl/gcgp6RLgymJIEP1Pvl7/CMqdlm+jJ2ZW6WM0GV8tP1IUeA80v6CdfnuvK3ZZQ > raHlNBqkiNhseB3eurvnVXT99t6Kz3THOqOz4dWdIRaLu8pHN4skqac3Jk4Wq2Gr > BAoyfUMjhwqy9RuQ9YbU1+mQ7qJNVAE19Pt9Wt7F+hSRtCv06lans//G4xZtbHY6 > dF0PdapyKLJ7a0D3Xttv0f3d+/1WGXZr9TAu6zAvUI+bIkWRSCdRCWppiTq9ztbs > A9p0yZ9d3ELafLL6iA+R/e/QrxUxjLNST0dG8srMxeqjSzR43E958aY6KpDgUne9 > 193kGw+0EwlHqP51N3qdzn+a0lqv20FBJQBHZIqshbFWq7iFVi1MteZ8ngxkIeeN > 3hHns7yJ1wdGDL8o6FJvo0vL8FpTgLUl0ULUW/kf1tTrrr8Inwez0y51sdOudMKH > +yx3EYaFHy6LLyHoRFjFA0lT2SEsNjQdpoDjX2dt1mo2LnbO1SvFz695saGlOxj/ > fgmL6SpeMbAvV/RIHPjdG2O4Nxtcy1KUGI/+3LcoFl+5684y3D6MvssPeKVg+WGu > RUenwpH1hyhoE4GP/q3B44s3J3fz7v4ez7ryfRP5FLUZs6T4C0bhdtDFI403Dbbf > AARPfTFsKTl/Oeb5xHklwj8YKp93tKtmwwIS5st7Fkd3GZPMKysEZzHmsl/tDLte > 7v6t05pR4Wy1+L0zTyCYKFtZ43Gjy5yfewJ8fO3kS8f5mVw/o0+fOPP5sS+6vzz8 > 8fKzb88Nbpz64Eb/1z9/vnjq5LEvn/ww/vvpme+ffvrum3/9dvXW5a++1jf/AQ== > =BQTO > -END PGP MESSAGE- > > - > 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/ -- Casualities in World Trade Center: ~3k dead inside the building, cryptography in U.S.A. and free speech in Czech Republic. ___ kbuild-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/kbuild-devel
