On Jun 27, 2006, at 8:58 PM, Ned Ludd wrote:
On Mon, 2006-06-26 at 16:26 -0400, Joshua ChaitinPollak wrote:
Yup:
export KERNELPATH=/usr/src/linux
emerge <modules>
Then I had to re-write the Soekris gpio ebuild for the new 2.6 kernel
drivers. Ugh.
Correct the gpio ebuild is for 2.4.x
What did you have to rewrite exactly?
I'm sure there is a more elegant way to do what I did, but I was in a
rush. I would submit a patch, but as you probably could guess from
the portage/ busybox patch bug you commented on earlier, I'm neither
a portage nor patch expert.
Here is a little step-by-step of what I did, I would be happy to zip
up what I've done and send it to you if it would be helpful.
I created a dev-embedded/gpio-new directory in my portage overlay,
and copied the gpio-1.3.2 ebuild into it, renaming it gpio-
new-1.3.2.ebuild. I did that because I didn't know if it is possible
to differentiate ebuilds based on kernel versions.
In the new ebuild, I updated the homepage and src_uri variables for
the location of the new code (because it is hosted by a different
developer)
I set the S variable because the downloaded tarball extracts to $
{WORKDIR}/gpio-1.3.2+trillian0.01
I moved the MODULE_NAMES and BUILD_PARAMS variables into the pkg_setup
() function (unneeded I'm sure)
Set the BUILD_TARGET variable to be "" instead of "all".
Added a line to pkg_setup():
cp ${FILESDIR}/Makefile ./
created gpio-new/files/Makefile, which is the gpio-1.3.2+trillian0.01
Makefile with the following lines appended to it:
module: default
clean:
rm -f *.ko *.o
--
Joshua ChaitinPollak
Software Engineer
Kiva Systems
--
[email protected] mailing list
