Eli Criffield wrote:
Its not a bad idea to have a byte-compiled c code an rpm to distribute it, and some magical way to compile it on rpm -i. I could see that coming in really handy for closed source kernel modules that can't distribute there code due to some NDA somewhere but can't possibly maintain a version for every kernel out there. But if you ask gcc developers to add an easy source hiding byte-compile only way to hide code, i would guess there answer would be, just distribute the source code, and don't use closed source drivers.
I don't see that byte-compiling kernel modules would help anyone: one needs to compile against the correct headers, and preumably any intermediate language would be created using headers on the build system, not on the target, and it's those on the target would be needed. Kernel aside, one still needs development libraries against which to link, unless one's using some kind of VM as Java does. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/ do not reply off-list ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
