________________________________________ De : Wolfgang Denk [[email protected]] Date d'envoi : vendredi 20 août 2010 13:44 À : Marie Reine SARAZIN Objet : Re: RE : RE : RE : RE : How can I build agin the toolchain ? (ELDK)
Dear Marie, In message <ee97821c81277e459bea5c6384c6f2410107a0e5f...@srvexch01.sodielec.local> you wrote: > Dear Wolfgang, > > Thanks for fast replying ! > Actually, I tried to clone the tarballs git repository but it stops... : > # git clone http://git.denx.de/eldk/tarballs.git > /home/alberix/Documents/git_eldk/tarballs Cloning over HTTP is extremely slow. Try if you can use git protocol instead. > The other ones work very well. I let it for a very long time and tried a > few times but it always stops. I guess it does not stop, it just takes so long . The repository is huge - some 2 GB. It might be more efficient just to download the snapshot you are interested in (see the "snapshot" links at http://git.denx.de/?p=eldk/tarballs.git;a=summary (right column). ________________________________________ De : Wolfgang Denk [[email protected]] Date d'envoi : mercredi 25 août 2010 08:42 À : Marie Reine SARAZIN Objet : Re: RE : RE : RE : RE : RE : How can I build agin the toolchain ? (ELDK) Dear Marie Reine SARAZIN, is there a reason for not keeping the ELDK mailing list on Cc: ? Usually this is preferred, as others who run into the same problems can find the solutions later in the mailing list archives... In message <ee97821c81277e459bea5c6384c6f2410107a0e5f...@srvexch01.sodielec.local> you wrote: > > Right, cloning the tarballs git repository took a very long time but finally > achieved. As mentioned before, a download of the relevant snapshop should be _much_ faster. > As it is written in your link : > http://www.denx.de/wiki/view/DULG/ELDKRebuilding > "For build.sh to work correctly, the script must be invoked from the build > environment after a successful build using the ELDK_BUILD script." > So I started a build using ELDK_BUILD. But I'm afraid it takes a really too > long time (it started 4 hours and a half ago and it's arrived at the step > eldt.5...) Thisis normal. Even if run nativley on a fast machine the complete build of ELDK can take some 15...40 hours, depending on speed of CPU, disk drivers / RAID system, and how many architectures you are building for. > I cannot use kvm... This is not needed when using the "chrot" approach. > I installed ELKD 4.2 on my computer. I am trying to install a wifi driver for > my embedded linux (kernel 2.32) on a powerpc chipset (> ppc6). > I have an error when I am building the driver from the supplier. There is no > fix avalaible for the driver but there is one for gcc4.2.2 as it is a know > bug. > I just have to delete some lines in two files .c (gcc/expr.c and > gcc/dojump.c). And so rebuilding it and use the bin in my existing ELDK > environment. I think it should be much easier to modify the driver source such that it does not trigger this specific compiler bug. Which bug is this, btw? > Can I do it properly without building using the ELDK_BUILD script ? If yes, > how...? You can of course try running the commands manually, step by step. But it's a tediuos and time consuming procedure, and most likely you will have to do it more than once as you make mistakes on the way and have to restart. It is probably easier to use the build script than doing things manually. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [email protected] The inappropriate cannot be beautiful. - Frank Lloyd Wright _The Future of Architecture_ (1953) -------------------------------------------------------------------------------------------- Dear Wolfgang, Sorry, I just forgot to keep the ELDK mailing list on Cc. Above are the last messages, for everyone. I said it is an know bug, but almost actually. I refer to bug 37014. I got the same error but not exactly at the same line. I got the error at the line 8718 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37014 [4.2/4.3/4.4 Regression] internal compiler error: in expand_expr_real_1, at expr.c:8760 The patch fixing this bug deletes some lines around the line 8718, so I hope it will work. The driver is not ath9k but has the same global aim. I let the ELDK_BUILD script running and I got an error at step trg.76. Building boa package step trg.76 at 15:15 Installing boa-0.94.14-0.10.rc21.fc9.noarch.rpm package parse file : install failed for boa-0.94.14-0.10.rc21.fc9 package + exit 1 + rm -fr /tmp/pkg.978 I precise that I didn't modify any file of the one I downloaded. But it's not a problem anymore for me as I found an other idea. I decided running again ELDK_BUILD, after having replaced the gcc package in tarballs with the modifications from the patch and after having deleted the lines after crosstool line in cpkgs.lst and the lines after gcc line in tpkgs.lst (I am lucky that crosstool is number 4 over 17 in cpkgs.lst and gcc is number 10 over 153 in tpkgs.lst). Building is running since 26 hours and I'm arrived at step trg.2 (the longer one I think). I'll let you know the result. Best Regards Marie _______________________________________________ eldk mailing list [email protected] http://lists.denx.de/mailman/listinfo/eldk
