Summary: | mjc-sources cannot emerge correctly | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | gaplo <gaplo> |
Component: | [OLD] Core system | Assignee: | Michael Cohen (RETIRED) <mjc> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | styx |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
gaplo
2002-06-18 13:27:25 UTC
Could you be a little more precise? What's the actual error? Are there rejects, or is the patching failing altogether? after I emerge mjc-sources, there are two directories created, one is storing those gentoo-patches, another is mjc-kernel(actually, I forgot what exactly name it is) directory. However, I found that the mjc-kernel directory is storing the original stock kernel 2.4.18, no patches has been applied. I have to manually get into the gentoo-patches directory and use the command "addpatches ../gentoo-sources ../mjc-kernel" to apply the patches. I do think there may be some error in the ebuild file, it should change into the gentoo-patches directory before and run the addpatches command, but the ebuild file seems running the addpatches at the parent directory of gentoo-patches, and fail to apply the patches since it cannot find those patches which are not located at the current directory. I'm aware of this. I've not had a chance to look at it yet, but I will. If you can figure out why it isn't running correctly please let me know =) I noticed some errors. 1. in the ebuild file mjc-sources-2.4.19_pre10.ebuild: - line 46: should be similar to this "addpatches default linux-${KV} gentoo-patches" 2. addpatches script seems can only run in the directory that contain the patches Oops. |