Hi; Am Montag, 21. Juli 2014, 21:18:09 schrieb Andrew: > 21.07.2014 18:01, kp kirchdoerfer пишет: > > Hi Andrew; > > > > I've tried today to build a new kernel version for i486 while still > > keeping > > the bcmrpi toolchain at the older kernel version. > > > > Your patch from 06.01.2014 > > 8948daef0d8c6e535ac17a06b16f276ff5bfd6e6 > > with the log message > > > > toolcain: kernel version is defined into makefile > > > > made me believe this should be doable. > > But it somewhat fails. > > > > I don't know a proper solution, but the symptom is that buildtool.cfg uses > > KVER from make/toolchain/* and then tries to download all files with KVER > > in their names (Bering-KVER.config*), even if the version is different - > > hard to desrcibe - maybe you try just yourself , you'll quickly see what > > happens and what goes wrong. > > > > kp > > Right, it uses version from KVER variable in makefile for corresponding > arch. It works OK (I changed version in > make/toolchain/x86_64-unknown-linux-uclibc.mk for test): > > NiTr0 LEAF # ./buildtool.pl -f -t x86_64-unknown-linux-uclibc source linux > make the list of required source packages: linux [0.K.] > > source/package: linux > ------------------------ > downloading: buildtool.cfg from server localrepo type filesymlnk [0.K.] > downloading: buildtool.mk from server localrepo type filesymlnk [0.K.] > downloading: wireless-regdb-2013.11.27.tar.bz2 from server localrepo > type filesymlnk [0.K.] > downloading: kernel_bcmrpi-3.11.5.patch from server localrepo type > filesymlnk > download failed: file > /var/testpoint/LEAF/repo/linux/kernel_bcmrpi-3.11.5.patch does not exist > > you might find useful information in log/buildtoollog > > > NiTr0 LEAF # ./buildtool.pl -f source linux > make the list of required source packages: linux [0.K.] > > source/package: linux > ------------------------ > downloading: buildtool.cfg from server localrepo type filesymlnk [0.K.] > downloading: buildtool.mk from server localrepo type filesymlnk [0.K.] > downloading: wireless-regdb-2013.11.27.tar.bz2 from server localrepo > type filesymlnk [0.K.] > downloading: kernel_bcmrpi-3.10.43.patch from server localrepo type > filesymlnk [0.K.] > downloading: 620-sched_esfq.patch from server localrepo type filesymlnk > [0.K.] > downloading: Bering-3.10.43.config from server localrepo type filesymlnk > [0.K.] > downloading: Bering-3.10.43.config-geode.patch from server localrepo > type filesymlnk [0.K.] > downloading: Bering-3.10.43.config-x86_64.patch from server localrepo > type filesymlnk [0.K.] > downloading: r6040_no_state_flood.patch from server localrepo type > filesymlnk [0.K.] > downloading: 621-sched_act_connmark.patch from server localrepo type > filesymlnk [0.K.] > downloading: linux-3.10.tar.xz from server localrepo type filesymlnk [0.K.] > downloading: Bering-3.10.43.config-versatile.patch from server localrepo > type filesymlnk [0.K.] > downloading: Bering-3.10.43.config-i686.patch from server localrepo type > filesymlnk [0.K.] > downloading: Bering-3.10.43.config-i486.patch from server localrepo type > filesymlnk [0.K.] > downloading: bitreverse.patch from server localrepo type filesymlnk [0.K.] > downloading: patch-3.10.43.xz from server localrepo type filesymlnk [0.K.] > downloading: Bering-3.10.43.config-bcmrpi.patch from server localrepo > type filesymlnk [0.K.] > downloading: kernel-mkmakefile.patch from server localrepo type > filesymlnk [0.K.] > calling 'make source' for linux [0.K.] > > For kernel configs we can even use KBRANCH variable (major.minor > version) for easy kernel update.
But it stops here to build the kernel for the given toolchain. So if we have a 3.10.49 toolchain for i486 and a 3.10.43 toolchain for x86_64 it will try to download Bering-3.10.43.config* and Bering-3.10.49.config* instead Bering-3.10.49.config-i686.patch Bering-3.10.49.config-i486.patch Bering-3.10.49.config-geode.patch and Bering-3.10.43.config-x86_64.patch only. We can workaround, but this will clutter repo/linux with lots of (unused) configs. Any chance this can be improved? kp ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
