Am Sonntag, 7. November 2010, 16:19:58 schrieb davidMbrooke:
> Hi,
>
> I have just run a full rebuild and buildall.sh failed on "kmodules":
>
> calling buildpacket for kmodules
> Generating package moddb-geode
> cp: cannot stat
> `/home/leaf/src/bering-uclibc4/buildtool/staging/lib/modules/2.6.35.8-geode
> /net/pptp.ko': No such file or directory Copying
> file
> /home/leaf/src/bering-uclibc4/buildtool/staging/lib/modules/2.6.35.8-geode
> /net/pptp.ko failed. No such file or directory at ./buildpacket.pl line 461
> main::system_exec('cp
> -r /home/leaf/src/bering-uclibc4/buildtool/staging/lib/mod...', 'Copying
> file /home/leaf/src/bering-uclibc4/buildtool/staging/...') called
> at ./buildpacket.pl line 565
> main::copyBinariesToPackageStaging('HASH(0x2a5a4c8)',
> '/home/leaf/src/bering-uclibc4/buildtool/staging') called
> at ./buildpacket.pl line 1215
>
>
> dMb
Try again again after you've run buildclean accel-pptp and build accel-pptp.
I guess we have had a misunderstanding about what to do with modules like pptp
from accel-pptp. I think they should not provided in the package (accel-pptp)
in this case, but with the modules tarball. Andrew put it into moddb
(kmodules).
This way moddb may grow too much in the long run, and we start to make things
complicated due to (unnecessary) dependencies. Unnecessary cause the whole
build process fails if accel-pptp is not (re)builded, but it's basically a
special, which can be build later or neverever, if the module is just in the
tarball and not in moddb.
kp
------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a
Billion" shares his insights and actions to help propel your
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
_______________________________________________
leaf-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
