On Fri, 2011-02-04 at 07:54 +1100, ads...@genis-x.com wrote: > Hi David, > > Can do I'll run a diff over the logs and report the results. > I gather that not everything is up in git yet (contrib pacakges?) > > When I issue a ./buildtool.pl build > > So far there don't seem to exist > nttcp > haserl > pwcrypt > hdparm > patch > etherwake > netkit-telnet > upnpbridg > libpopt > .... I stopped here as I mainly wanted keepalived and it requires libpopt, > is there an ETA on a full commit to git?
If CVS comes back online in a day or two we may stick with that for 4.0 and make the move to git later. Then again, it doesn't seem that hard to learn the basics of git (I had never used it until yesterday) so a move may not be all that disruptive, and we still have some bugs to fix for 4.0. I suspect the problem with the packages you list above is that they were being referenced from the bering-uclibc directory in CVS, not bering-uclibc4 (because they had not changed since 3.x). Only bering-uclibc4 has been copied to git. dMb > all that same kind of error > downloading: buildtool.cfg from server leaf-sourceforge type gitweb > wget failed: > /home/leaf/leaf/bering-uclibc4/buildtool/source/pwcrypt/buildtool.cfg could > not be found > > Cheers > Adam > > -----Original Message----- > From: davidMbrooke [mailto:dmb.leaf-de...@ntlworld.com] > Sent: Thursday, 3 February 2011 11:52 PM > To: ads...@genis-x.com > Cc: leaf-devel@lists.sourceforge.net > Subject: RE: [leaf-devel] Buildtool with cvs down etc > > On Thu, 2011-02-03 at 16:39 +1100, ads...@genis-x.com wrote: > > Hi David, > > > > Thanks for your response etc, > > I had no luck second time around on Ubuntu, seems there is a bug in > > buildtool on Ubuntu 10 x64. (I was never able to get builtool to work > > correctly on debian either with the earlier release of Bering). > > > > I just run up a quick Fedora 14 x64 box, and ran buildtool, no issues > > at all. > > This will get my by for now, but would still like to be able to stick > > to my favourite flavour of nix ;) > > > > If there is anything/info I can help with to make it work on Ubuntu > > happy to help. > > > > Thanks again. > > Ad > > Hi Ad, > > Glad to hear you got things working so quickly. I have added a warning about > the problem to the "Preparing the Build Environment" Chapter of the 4.x > Developer Guide wiki. > > If you get chance to compare the buildtoollog files from the successful / > failed environments that may highlight the issue, or perhaps you could > compare the logs from 32-bit and 64-bit Ubuntu 10. > > dMb > > > > > -----Original Message----- > > From: davidMbrooke [mailto:dmb.leaf-de...@ntlworld.com] > > Sent: Thursday, 3 February 2011 10:10 AM > > To: ads...@genis-x.com > > Cc: leaf-devel@lists.sourceforge.net > > Subject: RE: [leaf-devel] Buildtool with cvs down etc > > > > On Thu, 2011-02-03 at 08:37 +1100, ads...@genis-x.com wrote: > > > Hi, > > > > > > I was under the impression the new bering didn't have the old issues > > > of being tied to a certain gcc. > > > > Bering-uClibc 4.x is much less fussy about GCC versions than before, > > although GCC 3 probably won't work anymore. GCC 4.4.3 should be fine. > > I am using GCC 4.5.1 now but I used 4.4.x until a few weeks ago. > > > > > I'm running Ubuntu-10.04.1 with latest apt-get upgrade > > > > > > gcc --version > > > > > > gcc (Ubuntu 4.4.3-4ubuntu5) 4.4.3 > > > Copyright (C) 2009 Free Software Foundation, Inc. > > > This is free software; see the source for copying conditions. There > > > is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A > > > PARTICULAR > > PURPOSE. > > > > > > I noticed at the start of the uclibc build the command not found > > > errors? Is this expected? > > > > I have these same errors in buildtoollog (with a successful build) so > > they seem to be harmless. > > > > > MKDIR include/config > > > /bin/sh: > > > /home/leaf/leaf/bering-uclibc4/buildtool/staging/bin/i486-pc-linux-u > > > cl > > > ibc-gc > > > c: not found > > > make[2]: > > > /home/leaf/leaf/bering-uclibc4/buildtool/staging/bin/i486-pc-linux-u > > > cl > > > ibc-gc > > > c: Command not found > > > make[2]: > > > /home/leaf/leaf/bering-uclibc4/buildtool/staging/bin/i486-pc-linux-u > > > cl > > > ibc-gc > > > c: Command not found > > > gcc -DCURSES_LOC="<curses.h>" -DLOCALE -MM *.c > .depend 2>/dev/null > || > > : > > > /bin/sh: > > > /home/leaf/leaf/bering-uclibc4/buildtool/staging/bin/i486-pc-linux-u > > > cl > > > ibc-gc > > > c: not found > > > make[2]: > > > /home/leaf/leaf/bering-uclibc4/buildtool/staging/bin/i486-pc-linux-u > > > cl > > > ibc-gc > > > c: Command not found > > > make[2]: > > > /home/leaf/leaf/bering-uclibc4/buildtool/staging/bin/i486-pc-linux-u > > > cl > > > ibc-gc > > > c: Command not found > > > gcc -DCURSES_LOC="<curses.h>" -DLOCALE -c conf.c -o conf.o > > > gcc -DCURSES_LOC="<curses.h>" -DLOCALE -c kxgettext.c -o kxgettext.o > > > cat zconf.tab.c_shipped > zconf.tab.c cat lex.zconf.c_shipped > > > > lex.zconf.c cat zconf.hash.c_shipped > zconf.hash.c > > > gcc -DCURSES_LOC="<curses.h>" -DLOCALE -I. -c zconf.tab.c -o > zconf.tab.o > > > gcc -DCURSES_LOC="<curses.h>" -DLOCALE conf.o zconf.tab.o -o conf > > > # > > > # configuration written to .config > > > # > > > make[1]: Leaving directory > > > > `/home/leaf/leaf/bering-uclibc4/buildtool/source/buildenv/uClibc-0.9.30.3' > > > make -j1 -C > > > /home/leaf/leaf/bering-uclibc4/buildtool/source/buildenv/uClibc-0.9.30.3 > \ > > > PREFIX=/home/leaf/leaf/bering-uclibc4/buildtool/staging/ \ > > > CROSS_COMPILER_PREFIX="" \ > > > DEVEL_PREFIX=/ CC=gcc \ > > > RUNTIME_PREFIX=/ \ > > > pregen install_dev; > > > > I get different output in the log around where you get the fatal error. > > I get: > > > > AR cr lib/libpthread.a > > STRIP -x -R .note -R .comment lib/libpthread.a > > LD ld-uClibc-0.9.30.3.so > > AR cr libc/libc_so.a > > STRIP -x -R .note -R .comment libc/libc_so.a > > make[2]: `lib/ld-uClibc.so' is up to date. > > LD libuClibc-0.9.30.3.so > > LD libdl-0.9.30.3.so > > > > so it is definitely behaving differently on your system. > > > > All I can suggest is that you re-run the git clone and try again with > > a clean download, and if that has the same problem check for any other > > errors in the log. > > > > Andrew is much more of an expert on the buildenv than I am, so he may > > have some other suggestions. > > > > Does anybody else have a successful build on 64-bit Ubuntu 10? > > > > dMb > > > > > > > > -----Original Message----- > > > From: davidMbrooke [mailto:dmb.leaf-de...@ntlworld.com] > > > Sent: Thursday, 3 February 2011 7:57 AM > > > To: leaf-devel > > > Subject: Re: [leaf-devel] Buildtool with cvs down etc > > > > > > On Wed, 2011-02-02 at 20:13 +1100, ads...@genis-x.com wrote: > > > > I should have added, > > > > Base machine is Ubuntu 2.6.32-24-server #43-Ubuntu SMP Thu Sep 16 > > > > 16:05:42 UTC 2010 x86_64 GNU/Linux > > > > > > > > -----Original Message----- > > > > From: ads...@genis-x.com [mailto:ads...@genis-x.com] > > > > Sent: Wednesday, 2 February 2011 5:16 PM > > > > To: leaf-devel@lists.sourceforge.net > > > > Subject: Re: [leaf-devel] Buildtool with cvs down etc > > > > > > > > Hey guys, > > > > > > > > I git clone'd the lastest buildtool and hit a snag. > > > > > > > > > > > > downloading: .config from server leaf4-sourceforge type gitweb > > > > [0.K.] > > > > downloading: 50_all_gcc44_no_ssp_tls_uclibc.patch from server > > > > leaf4-sourceforge type gitweb [0.K.] > > > > downloading: uClibc-0.9.30.3.tar.bz2 from server uclibc.org type > > > > http [0.K.] calling 'make source' for buildenv make source failed > > > > for > > > > /home/leaf/leaf/bering-uclibc4/buildtool/source/buildenv/buildtool > > > > .m k , please have a look at the logfile log/buildtoollog at > > > > buildtool/Make/Source.pm line 398. > > > > > > > > The log > > > > CC libc/misc/elf/dl-iterate-phdr.os > > > > CC libc/misc/internals/__uClibc_main.os > > > > CC libc/inet/rpc/rpc_thread.os > > > > CC libc/stdlib/atexit.os > > > > AR cr lib/libc.a > > > > STRIP -x -R .note -R .comment lib/libc.a > > > > AR cr lib/uclibc_nonshared.a > > > > STRIP -x -R .note -R .comment lib/uclibc_nonshared.a > > > > AR cr libc/libc_so.a > > > > STRIP -x -R .note -R .comment libc/libc_so.a > > > > LD libuClibc-0.9.30.3.so > > > > libc/libc_so.a(lldiv.os): In function `imaxdiv': > > > > lldiv.c:(.text.lldiv+0x32): undefined reference to `__divdi3' > > > > lldiv.c:(.text.lldiv+0x4e): undefined reference to `__moddi3' > > > > collect2: ld returned 1 exit status > > > > make[1]: *** [lib/libc.so] Error 1 > > > > make[1]: Leaving directory > > > > > > `/home/leaf/leaf/bering-uclibc4/buildtool/source/buildenv/uClibc-0.9.30.3' > > > > make: *** > > > > [/home/leaf/leaf/bering-uclibc4/buildtool/source/buildenv/uClibc-0 > > > > .9 > > > > .3 > > > > 0.3/.c > > > > onfigured] Error 2 > > > > make: Leaving directory > > > > `/home/leaf/leaf/bering-uclibc4/buildtool/source/buildenv' > > > > > > > > Not sure if I've missed something in the config > > > > > > > > Any ideas? > > > > > > > > Cheers > > > > Ad > > > > > > Hi Ad, > > > > > > A git clone of the latest buildtool works OK for me, on Fedora 14 > > > (2.6.35.10-74.fc14.x86_64). > > > > > > Which version of GCC do you have? > > > > > > davidMbrooke > > > > > > > > > > > ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
