Hi
I want to compile kernel source (kernel-2.6.23.1-42.fc8.i686 ) in my linux fedora
if i compile existing kernel source code of my linux fedora pc . it gives error " No rule to make target "missing -syscalls " stop
Please do provide link to download kernel-2.6.23 tar file .( Not rpm package)
Raj
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
pushparaj muthu a écrit : " No rule to make target "missing -syscalls " stop
Please do provide link to download kernel-2.6.23 tar file .( Not rpm package)
Raj
fc8 is end of life however the vanilla kernel source with historical versions are _always_ available at kernel.org
http://lmgtfy.com/?q=kernel+source that's the first link on the result page....use the force, don't be lazy
Thierry wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
pushparaj muthu a écrit : " No rule to make target "missing -syscalls " stop
Please do provide link to download kernel-2.6.23 tar file .( Not rpm package)
You can get Fedora RPMs using yum, and kernel.org unpatched kernels at kernel.org. Be *very* aware that the Fedora kernel is not the unpatched original, for some kernels that makes a significant difference, for others not. Fedora kernels may have features added which are simply not in the reference kernel.
As to your problem (rather than your question) you may not have the right tool chain installed to do the build.
Raj
fc8 is end of life however the vanilla kernel source with historical versions are _always_ available at kernel.org
http://lmgtfy.com/?q=kernel+source that's the first link on the result page....use the force, don't be lazy -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkmyn4gACgkQLC18tm1XH9b5fwCcCbZyJE9N3a6/inSLDTg3kOSG JnYAoIwoTzAcI+ziZWp4G7BPFhzUA1ZS =bY6Y -----END PGP SIGNATURE-----
Bill Davidsen wrote:
Thierry wrote:
pushparaj muthu a écrit : " No rule to make target "missing -syscalls " stop
Please do provide link to download kernel-2.6.23 tar file .( Not rpm package)
You can get Fedora RPMs using yum, and kernel.org unpatched kernels at kernel.org. Be *very* aware that the Fedora kernel is not the unpatched original, for some kernels that makes a significant difference, for others not. Fedora kernels may have features added which are simply not in the reference kernel.
As to your problem (rather than your question) you may not have the right tool chain installed to do the build.
And as a side note, I just pulled a source rpm off rawhide, for kernel 2.6.29-rc8-git and it would unpack due to "MD5 errors" in the install. Don't know what that's all about, I used rpm2cpio and verified that the cpio data was actually correct.
I guess I'll test on 2.6.29 stock, I really want the new video stuff.
Bill Davidsen wrote:
And as a side note, I just pulled a source rpm off rawhide, for kernel 2.6.29-rc8-git and it would unpack due to "MD5 errors" in the install. Don't know what that's all about,
Rawhide has switched to using SHA256 instead of MD5 everywhere including RPM. Details in the stronger hashes feature at
https://fedoraproject.org/wiki/Releases/11/FeatureList
Rahul
Rahul Sundaram wrote:
Bill Davidsen wrote:
And as a side note, I just pulled a source rpm off rawhide, for kernel 2.6.29-rc8-git and it would unpack due to "MD5 errors" in the install. Don't know what that's all about,
Rawhide has switched to using SHA256 instead of MD5 everywhere including RPM. Details in the stronger hashes feature at
Actually it seems to be signed with a key I don't see, the message is: kernel-2.6.29-0.258.rc8.git2.fc11.src.rpm: RSA sha1 (MD5) (PGP) md5 NOT OK (MISSING KEYS: PGP#d22e77f2)
I assume it's a key only in the FC11 release, which isn't in older systems. A problem for another day, I'm content now that I understand why it fails.
Bill Davidsen wrote:
Rahul Sundaram wrote:
Bill Davidsen wrote:
And as a side note, I just pulled a source rpm off rawhide, for kernel 2.6.29-rc8-git and it would unpack due to "MD5 errors" in the install. Don't know what that's all about,
Rawhide has switched to using SHA256 instead of MD5 everywhere including RPM. Details in the stronger hashes feature at
Actually it seems to be signed with a key I don't see, the message is: kernel-2.6.29-0.258.rc8.git2.fc11.src.rpm: RSA sha1 (MD5) (PGP) md5 NOT OK (MISSING KEYS: PGP#d22e77f2)
I assume it's a key only in the FC11 release, which isn't in older systems. A problem for another day, I'm content now that I understand why it fails.
Yes. Every release has a different key.
Rahul
Rahul Sundaram wrote:
Bill Davidsen wrote:
Rahul Sundaram wrote:
Bill Davidsen wrote:
And as a side note, I just pulled a source rpm off rawhide, for kernel 2.6.29-rc8-git and it would unpack due to "MD5 errors" in the install. Don't know what that's all about,
Rawhide has switched to using SHA256 instead of MD5 everywhere including RPM. Details in the stronger hashes feature at
Actually it seems to be signed with a key I don't see, the message is: kernel-2.6.29-0.258.rc8.git2.fc11.src.rpm: RSA sha1 (MD5) (PGP) md5 NOT OK (MISSING KEYS: PGP#d22e77f2)
I assume it's a key only in the FC11 release, which isn't in older systems. A problem for another day, I'm content now that I understand why it fails.
Yes. Every release has a different key.
Interesting, though, I got that key off the web site for the alpha, and it's in my personal keyring, some time when I want to spend a lot of time on something I probably won't use I'll figure out where that key needs to be, since I don't have a usable FC11 machine (both installed the alpha but when I do the upgrade they hang solid).
Not critical, the newer kernel seems to use my display no better than the old.
On 3/26/2009 12:47 AM, Bill Davidsen wrote:
Rahul Sundaram wrote:
Bill Davidsen wrote:
Rahul Sundaram wrote:
Bill Davidsen wrote:
And as a side note, I just pulled a source rpm off rawhide, for kernel 2.6.29-rc8-git and it would unpack due to "MD5 errors" in the install. Don't know what that's all about,
Rawhide has switched to using SHA256 instead of MD5 everywhere including RPM. Details in the stronger hashes feature at
Actually it seems to be signed with a key I don't see, the message is: kernel-2.6.29-0.258.rc8.git2.fc11.src.rpm: RSA sha1 (MD5) (PGP) md5 NOT OK (MISSING KEYS: PGP#d22e77f2)
I assume it's a key only in the FC11 release, which isn't in older systems. A problem for another day, I'm content now that I understand why it fails.
Yes. Every release has a different key.
Interesting, though, I got that key off the web site for the alpha, and it's in my personal keyring, some time when I want to spend a lot of time on something I probably won't use I'll figure out where that key needs to be, since I don't have a usable FC11 machine (both installed the alpha but when I do the upgrade they hang solid).
Not critical, the newer kernel seems to use my display no better than the old.
The key does not go in your personal keyring. It goes in rpm's keyring.
rpm --import </path_of/name_of_key>
David wrote:
On 3/26/2009 12:47 AM, Bill Davidsen wrote:
Rahul Sundaram wrote:
Bill Davidsen wrote:
Rahul Sundaram wrote:
Bill Davidsen wrote:
And as a side note, I just pulled a source rpm off rawhide, for kernel 2.6.29-rc8-git and it would unpack due to "MD5 errors" in the install. Don't know what that's all about,
Rawhide has switched to using SHA256 instead of MD5 everywhere including RPM. Details in the stronger hashes feature at
Actually it seems to be signed with a key I don't see, the message is: kernel-2.6.29-0.258.rc8.git2.fc11.src.rpm: RSA sha1 (MD5) (PGP) md5 NOT OK (MISSING KEYS: PGP#d22e77f2)
I assume it's a key only in the FC11 release, which isn't in older systems. A problem for another day, I'm content now that I understand why it fails.
Yes. Every release has a different key.
Interesting, though, I got that key off the web site for the alpha, and it's in my personal keyring, some time when I want to spend a lot of time on something I probably won't use I'll figure out where that key needs to be, since I don't have a usable FC11 machine (both installed the alpha but when I do the upgrade they hang solid).
Not critical, the newer kernel seems to use my display no better than the old.
The key does not go in your personal keyring. It goes in rpm's keyring.
rpm --import </path_of/name_of_key>
That gets me back to the original problem I mentioned in news://news.gmane.org:119/gqdcg6$7ss$1@ger.gmane.org
root> rpm -ivh kernel-2.6.29-0.258.rc8.git2.fc11.src.rpm 1:kernel warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root ########################################### [100%] error: unpacking of archive failed on file /usr/src/redhat/SOURCES/Makefile.config;49cb892e: cpio: MD5 sum mismatch
Interesting that I was getting this message before I got the "unknown key" message which I "fixed" wit the rpm import. In any case, the problem returned to what I initially reported, but it still doesn't work.
I'll wait for the FC11 beta next month.
David wrote:
On 3/26/2009 12:47 AM, Bill Davidsen wrote:
Rahul Sundaram wrote:
Bill Davidsen wrote:
Rahul Sundaram wrote:
Bill Davidsen wrote:
And as a side note, I just pulled a source rpm off rawhide, for kernel 2.6.29-rc8-git and it would unpack due to "MD5 errors" in the install. Don't know what that's all about,
Rawhide has switched to using SHA256 instead of MD5 everywhere including RPM. Details in the stronger hashes feature at
Actually it seems to be signed with a key I don't see, the message is: kernel-2.6.29-0.258.rc8.git2.fc11.src.rpm: RSA sha1 (MD5) (PGP) md5 NOT OK (MISSING KEYS: PGP#d22e77f2)
I assume it's a key only in the FC11 release, which isn't in older systems. A problem for another day, I'm content now that I understand why it fails.
Yes. Every release has a different key.
Interesting, though, I got that key off the web site for the alpha, and it's in my personal keyring, some time when I want to spend a lot of time on something I probably won't use I'll figure out where that key needs to be, since I don't have a usable FC11 machine (both installed the alpha but when I do the upgrade they hang solid).
Not critical, the newer kernel seems to use my display no better than the old.
The key does not go in your personal keyring. It goes in rpm's keyring.
rpm --import </path_of/name_of_key>
why not just download 2.26.29-3.fc10 from koji? i'm pretty sure it has the latest modesetting stuff enabled
psmith wrote:
David wrote:
On 3/26/2009 12:47 AM, Bill Davidsen wrote:
Rahul Sundaram wrote:
Bill Davidsen wrote:
Rahul Sundaram wrote:
Bill Davidsen wrote:
> And as a side note, I just pulled a source rpm off rawhide, for > kernel > 2.6.29-rc8-git and it would unpack due to "MD5 errors" in the > install. > Don't know what that's all about, Rawhide has switched to using SHA256 instead of MD5 everywhere including RPM. Details in the stronger hashes feature at
Actually it seems to be signed with a key I don't see, the message is: kernel-2.6.29-0.258.rc8.git2.fc11.src.rpm: RSA sha1 (MD5) (PGP) md5 NOT OK (MISSING KEYS: PGP#d22e77f2)
I assume it's a key only in the FC11 release, which isn't in older systems. A problem for another day, I'm content now that I understand why it fails.
Yes. Every release has a different key.
Interesting, though, I got that key off the web site for the alpha, and it's in my personal keyring, some time when I want to spend a lot of time on something I probably won't use I'll figure out where that key needs to be, since I don't have a usable FC11 machine (both installed the alpha but when I do the upgrade they hang solid).
Not critical, the newer kernel seems to use my display no better than the old.
The key does not go in your personal keyring. It goes in rpm's keyring.
rpm --import </path_of/name_of_key>
why not just download 2.26.29-3.fc10 from koji? i'm pretty sure it has the latest modesetting stuff enabled
Okay, I D/L it, I'll see if it works any better than the kernel.org original.
-
Bill Davidsen -
David Boles -
jon doe -
pushparaj muthu -
Rahul Sundaram -
Thierry