I'm just wondering what happened to the kernel-sourcecode RPMs.
I know that the source code can be found in the kernel-SRPMS package, but I really appreciated having a package to installed the source code where it was expected to be (/usr/src/kernel) and am a little lost as to why the package seems to have been removed.
Rodd
On Wed, 22 Sep 2004 22:22:55 +1000, Rodd Clarkson rodd@clarkson.id.au wrote:
I'm just wondering what happened to the kernel-sourcecode RPMs.
I know that the source code can be found in the kernel-SRPMS package, but I really appreciated having a package to installed the source code where it was expected to be (/usr/src/kernel) and am a little lost as to why the package seems to have been removed.
Rodd
I'm with you, I think its stupid not to have the source patched to the current kernel on hand. I used it all the time to find bugs. I hope that common sense will prevail and the kernel-source rpm returns
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wednesday 22 September 2004 13:33, Mark Bradbury wrote:
On Wed, 22 Sep 2004 22:22:55 +1000, Rodd Clarkson rodd@clarkson.id.au
wrote:
I'm just wondering what happened to the kernel-sourcecode RPMs.
I know that the source code can be found in the kernel-SRPMS package, but I really appreciated having a package to installed the source code where it was expected to be (/usr/src/kernel) and am a little lost as to why the package seems to have been removed.
Rodd
I'm with you, I think its stupid not to have the source patched to the current kernel on hand. I used it all the time to find bugs. I hope that common sense will prevail and the kernel-source rpm returns
There is now a SRPM for the kernel sources, eg,
http://ftp.belnet.be/linux/fedora/linux/core/development/i386/SRPMS/kernel-2...
However, I tried to patch the kernel using this and retired baffled from the field. I ended up having to patch a vanilla 2.6.8 kernel from kernel.org :-( I used to be able to patch the redhat sources just fine by hand from a kernel-source RPM, so I also agree things have gone backwards. I suggested before someone knock up a howto or some document describing the new system and how to emulate the old behaviours but AFAIK it is not in existence.
- -Andy
- -- http://www.addintelligence.co.uk -- we design custom hardware and software for your products
On Wed, Sep 22, 2004 at 05:36:01PM +0100, Andy Green wrote:
There is now a SRPM for the kernel sources, eg,
http://ftp.belnet.be/linux/fedora/linux/core/development/i386/SRPMS/kernel-2...
It always was. Nothing changed here from the first distribution which used an rpm packaging.
However, I tried to patch the kernel using this and retired baffled from the field.
How did you try to do that? A correct way, if you really need patched sources and not just data in /lib/modules/$(uname -r)/build which most likely you are really after, is to install that src.rpm with 'rpm -i ...' followed by 'rpmbuild -bp kernel.spec' in your SPECS directory. You will end up with properly patched sources in your BUILD.
This was already discussed on this list a few times including explanations how not to use a 'root' account for this.
Michal
On Wed, 2004-09-22 at 18:36, Andy Green wrote:
There is now a SRPM for the kernel sources, eg,
http://ftp.belnet.be/linux/fedora/linux/core/development/i386/SRPMS/kernel-2...
However, I tried to patch the kernel using this and retired baffled from the field. I ended up having to patch a vanilla 2.6.8 kernel from kernel.org :-( I used to be able to patch the redhat sources just fine by hand from a kernel-source RPM, so I also agree things have gone backwards. I suggested before someone knock up a howto or some document describing the new system and how to emulate the old behaviours but AFAIK it is not in existence.
rpm -i kernel-2.6.8-1.541.src.rpm rpmbuild -bp --target noarch /usr/src/redhat/SPECS/kernel-2.6.spec
and the sourcecode will end up in /usr/src/redhat/BUILD
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wednesday 22 September 2004 17:56, Arjan van de Ven wrote:
rpm -i kernel-2.6.8-1.541.src.rpm rpmbuild -bp --target noarch /usr/src/redhat/SPECS/kernel-2.6.spec
and the sourcecode will end up in /usr/src/redhat/BUILD
So this is pretty much an emulation of the old kernel-source RPM? Cool! Going to give it a try tonight.
Thanks.
- -Andy
- -- http://www.addintelligence.co.uk -- we design custom hardware and software for your products
Hi
How is it possible to build the Nvidia driver agaist the kernel.src? It fails for mee.
Is the Nvidia driver the only way to test the option "RenderAccel" "on" funktion in Xorg?
Why is the kernel-sourcecode left out?
/Bjorn
ons, 22 09 2004 kl. 18:56 +0200, skrev Arjan van de Ven:
On Wed, 2004-09-22 at 18:36, Andy Green wrote:
There is now a SRPM for the kernel sources, eg,
http://ftp.belnet.be/linux/fedora/linux/core/development/i386/SRPMS/kernel-2...
However, I tried to patch the kernel using this and retired baffled from the field. I ended up having to patch a vanilla 2.6.8 kernel from kernel.org :-( I used to be able to patch the redhat sources just fine by hand from a kernel-source RPM, so I also agree things have gone backwards. I suggested before someone knock up a howto or some document describing the new system and how to emulate the old behaviours but AFAIK it is not in existence.
rpm -i kernel-2.6.8-1.541.src.rpm rpmbuild -bp --target noarch /usr/src/redhat/SPECS/kernel-2.6.spec
and the sourcecode will end up in /usr/src/redhat/BUILD
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-test-list
On Wed, Sep 22, 2004 at 09:29:23PM +0200, Bjorn Andersen wrote:
Hi
How is it possible to build the Nvidia driver agaist the kernel.src?
No.
Nor can you build it against kernel-sourcecode for that matter.
You can only build against the headers in /lib/modules/`uname `r/build, just like it was the case ever since RHL 7.0. (except that now the cheat of using another location no longer works)
Why is the kernel-sourcecode left out?
because it is redundant and mostly pointless. We don't ship openoffice-source code either, right?
On Wed, 22 Sep 2004, Arjan van de Ven wrote:
On Wed, Sep 22, 2004 at 09:29:23PM +0200, Bjorn Andersen wrote:
Hi
How is it possible to build the Nvidia driver agaist the kernel.src?
No.
Nor can you build it against kernel-sourcecode for that matter.
You can only build against the headers in /lib/modules/`uname `r/build, just like it was the case ever since RHL 7.0. (except that now the cheat of using another location no longer works)
Note, this assumes you are building driver for the machine you are running on. If your building drivers for multiple kernels, building them using the include directory in a configured kernel source tree instead of having to actually have each of the kernels installed is much better. I have built various build tools to support doing this for kernel modules in a completely automated way. So when we update the kernels in our one-off wonder distribution we just turn the crank and out pops module rpms for all of our modules for each of the kernels in the distribution.
Why is the kernel-sourcecode left out?
because it is redundant and mostly pointless. We don't ship openoffice-source code either, right?
Actually, its quite usefull in the case above. I can get to the same place with a SRPM, but I have to go through a few extra steps. What was nice about the kernel-source rpm was that it contained the "patched" version of the sources with various default redhat configs in the config directory. Use rpm2cpio to plop this down where you want, copy in the proper config (or your own), and point your module sources at this kernel source tree, and your done.
Cheers...james
On Thu, 23 Sep 2004 07:54:52 -0400 (EDT), James Olin Oden joden@lee.k12.nc.us wrote:
On Wed, 22 Sep 2004, Arjan van de Ven wrote:
On Wed, Sep 22, 2004 at 09:29:23PM +0200, Bjorn Andersen wrote:
Hi
How is it possible to build the Nvidia driver agaist the kernel.src?
No.
Nor can you build it against kernel-sourcecode for that matter.
You can only build against the headers in /lib/modules/`uname `r/build, just like it was the case ever since RHL 7.0. (except that now the cheat of using another location no longer works)
Note, this assumes you are building driver for the machine you are running on. If your building drivers for multiple kernels, building them using the include directory in a configured kernel source tree instead of having to actually have each of the kernels installed is much better. I have built various build tools to support doing this for kernel modules in a completely automated way. So when we update the kernels in our one-off wonder distribution we just turn the crank and out pops module rpms for all of our modules for each of the kernels in the distribution.
Why is the kernel-sourcecode left out?
because it is redundant and mostly pointless. We don't ship openoffice-source code either, right?
Actually, its quite usefull in the case above. I can get to the same place with a SRPM, but I have to go through a few extra steps. What was nice about the kernel-source rpm was that it contained the "patched" version of the sources with various default redhat configs in the config directory. Use rpm2cpio to plop this down where you want, copy in the proper config (or your own), and point your module sources at this kernel source tree, and your done.
Cheers...james
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-test-list
I agree, There has been instuctions on making a kernel source tree on this list for a while but none that I have seen that makes a kernel-source-noarch-rpm ,The instructions seem to say how easy it is to build a tree in /usr/src/redhat/BUILD . So if that is the case why not have ia sorce rpm 'as we did before' as a download?
my 2cents
On Wed, Sep 22, 2004 at 09:31:55PM +0200, Arjan van de Ven wrote:
On Wed, Sep 22, 2004 at 09:29:23PM +0200, Bjorn Andersen wrote:
How is it possible to build the Nvidia driver agaist the kernel.src?
No.
Nor can you build it against kernel-sourcecode for that matter.
I wonder how I provide such packages for two years now ... (discussed on fedora-devel two months ago)
You can only build against the headers in /lib/modules/`uname `r/build, just like it was the case ever since RHL 7.0. (except that now the cheat of using another location no longer works)
Why is the kernel-sourcecode left out?
because it is redundant and mostly pointless. We don't ship openoffice-source code either, right?
Hm, one of the posters wanted to patch his kernel, another to configure it.
There aren't really that many patches for openoffice, nor is the configuration space of openoffice or any other package near that big as the kernel's. Obviously the use of the kernel sources and openoffice sources is quite different, and so is the need for it.
then it would be great to have an redhat kernel-patchset, so one can patch an vanilla kernel.org source to the same state as the redhat/fedora kernel.rpm.
lars
On Thu, 2004-09-23 at 12:28, Lars wrote:
then it would be great to have an redhat kernel-patchset, so one can patch an vanilla kernel.org source to the same state as the redhat/fedora kernel.rpm.
That's pretty much what the kernel SRPM is: it contains the vanilla kernel tarball (the version of which is what is used to set the RPM version number) and the applied patches. Unpack it and have a look!
Cheers, Per