HI, I always thought that it was -j"number of cores +1" Yannick.
-----Message d'origine----- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Jon Smirl Envoyé : vendredi 13 juin 2008 01:29 À : Marc Kleine-Budde Cc : [EMAIL PROTECTED]; [email protected] Objet : Re: [ptxdist] [OSELAS.Phytec] OSELAS.Toolchain-1.1.1 and bintuils2.18 On 6/12/08, Marc Kleine-Budde <[EMAIL PROTECTED]> wrote: > Jon Smirl wrote: > >> >> If you don't do enything, you will end up with "-j<number of cores> x > 2" > >> >> If you don't want to build a programm in parallel, edit the > >> >> corresponding makefile, look for the compile rule and change > >> >> "$(PARALLELMFLAGS)" into "$(PARALLELMFLAGS_BROKEN)". (See attached > patch) > >> >> > >> >> > >> >> > make[3]: Entering directory > >> >> > `/home/OSELAS.Toolchain-1.1.1/build-target/glibc-2.5/csu' > >> >> > make[3]: warning: -jN forced in submake: disabling jobserver mode. > >> > >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > >> > >> Why do we have these warnings here? Have you set some kind of > >> PARALLELMFLAGS manually? > > > > I have PARALLELMFLAGS=-j5 exported to my environment. I asked earlier > > if that was the right way to do it. If I don't export it nothing > > builds in parallel. > > > Sure? Please unset PARALLELMFLAGS, don't export it. PTXdist does take > care of it. Please show me the output (in a clean shell, w/o > PARALLELMFLAGS) of "ptxdist print PARALLELMFLAGS" and "cat /proc/cpuinfo" Unsetting PARALLELMFLAGS from the environment is doing parallel builds now. I put that into my environment a long time ago (maybe two years ago) when it wasn't doing very good parallel builds. I see that just setting it to NULL like I did previously causes a single threaded build. The parallel build now looks to be a lot more parallel that it used to be. I'll pull it out of my environment. > > It is also possible that ptxdist is picking the flag up from something > > else that is installed on my system. > > Maybe, or some "unusual environment" :) > > >> >> > checking for library containing gethostbyname... none required > >> >> > checking for library containing socketpair... none required > >> >> > checking for library containing waddstr... no > >> >> > checking for library containing tgetent... no > >> >> > configure: error: no termcap library found > > >> >> Okay - it says "no termcap" library found, that means "I cannot find > any > >> >> library that contains termcap stuff". In other words, it will work > >> >> perfectly with libncurses. > > > [..] > > > >> what is your default compiler? "gcc -v" ouput please. Please uninstall > >> the lib32ncurses5-dev, start a toolchain buld and send me the file > >> "build-cross/gdb-6.6/config.log" after cross-gdb breaks. > > > > I can't get this to reproduce today which is confusing, I was able to > > reproduce it twice yesterday. This is probably a packaging problem in > > ubuntu. Maybe the 64b ncurses dev didn't make a symlink that the 32b > > package fixed. > > > which symlink? Check out the ncurses 64b dev package there are over 100 things in there. Something isn't quite right, probably a missing termcap symlink. I hit this on a clean Hardy install. My box the I upgraded from Edgy to Hardy didn't hit it. I should have saved the logs. If I hit it again I will save them. If you recognize which configure script it was running when it died, just look at the script and see what it was checking for. Most likely it was just looking for the presence of a file that was missing. > > > > Yesterday I uninstalled/reinstalled lib32ncurses5-dev and it > > reproduced twice. I did reboot overnight. > > > > [EMAIL PROTECTED]:/home/OSELAS.Toolchain-1.1.1$ gcc -v > > Using built-in specs. > > Target: x86_64-linux-gnu > > Configured with: ../src/configure -v > > --enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr > > --enable-shared --with-system-zlib --libexecdir=/usr/lib > > --without-included-gettext --enable-threads=posix --enable-nls > > --with-gxx-include-dir=/usr/include/c++/4.2 --program-suffix=-4.2 > > --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc > > --enable-mpfr --enable-checking=release --build=x86_64-linux-gnu > > --host=x86_64-linux-gnu --target=x86_64-linux-gnu > > Thread model: posix > > gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7) > > > at least this is a 64 bit compiler, so it should not pick up 32 bit > libs. You cannot intermix 64 bit code with 32 bit libraries. > > So I consider the libncurses problem solved. > > regards, Marc > > > -- > Marc Kleine-Budde Phone: +49-231-2826-924 > Pengutronix - Linux Solutions for Science and Industry > Vertretung West/Dortmund http://www.pengutronix.de > > > -- Jon Smirl [EMAIL PROTECTED] -- ptxdist mailing list [email protected] -- ptxdist mailing list [email protected]
