Thanks for checking that kp, I guess it's over to the devel's out there to take a look? Anyone up to check/test/fix buildtool?
Cheers Ad -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of KP Kirchdoerfer Sent: Sunday, 29 July 2007 9:25 AM To: leaf-user@lists.sourceforge.net Subject: Re: [leaf-user] Is buildtool busted? Has anyone tried it recently? On Friday 27 July 2007 06:29:09 Adam Niedzwiedzki wrote: > Hi guys, > > I've been pulling my hair out trying to get buildtool to work, I have no > idea where do go from here, but here is what I'm doing. > > I did a fresh install of debian using debian-40r0-i386-netinst.iso Then > just the following as root > apt-get install gcc-3.4 > apt-get install make > apt-get install patch > apt-get install bzip2 > apt-get install libconfig-general-perl > apt-get install cvs > > Then a simple adduser leaf > Login as user leaf via ssh > > Then > cvs -d :pserver:[EMAIL PROTECTED]:/cvsroot/leaf login cvs > -z3 -d :pserver:[EMAIL PROTECTED]:/cvsroot/leaf \ > co src/bering-uclibc/buildtool > > updated /home/leaf/src/bering-uclibc/buildtool/make/MasterInclude.mk > change HOSTCC=gcc-3.4 > > then went > /home/leaf/src/bering-uclibc/buildtool/buildtool.pl build buildenv > > Things hum along nicely until it all goes belly up (I've tried so many > different things it seems to die at this part everytime) I've manually > checked everything in > /home/leaf/src/bering-uclibc/buildtool/source/buildenv (tar -tzvf and tar > -tjvf etc) and all checks out. > > I have attached my buildtool log below > > Anyone have any ideas how to fix this? > > It's like it's not following > /home/leaf/src/bering-uclibc/buildtool/source/buildenv/buildtool.mk at all > it handles binuntils fine then totally skips gcc and goes on with uClibc > it's just doesn't make any sense.. > > Buildtool log file is here http://www.genis-x.net/buildtoollog.zip > > I even rolled a fresh install of debian sarge 3.1 which has default gcc of > 3.3 on it, same error same spot. I'm I totally missing something? Unfortunately it seems you are right. I've tried to run a buildenv within a virtual machine with exactly the same error you see. So this is just a feedback, that it's not your fault. I hope there'll be a solution soon. kp ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ------------------------------------------------------------------------ leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ------------------------------------------------------------------------ leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
