| Age | Commit message (Collapse) | Author | Files |
|---|
|
Libtool in some packages (e.g. curl) tries to relink libraries during
installation stage. If the Icecc environment isn't set in the do_install
such relinking fails. Fix this by adding do_install_prepend to
icecc.bbclass with set_icecc_env() call.
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
|
|
The installation of toolchains in /cross/ has changed a bit, resulting
in failures of icecc.bbclass to find necessary files (libstdc++.so, g++, etc.)
Fix that by pointing the class file to libstdc++ in staging and corrent name
of target g++.
Also correct the name of kernel toolchain tarball.
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
|
|
QEMU 0.9.x is obsolete this days and with all modifications made for
QEMU 0.10.x in OE, versions 0.9.x are unusable anyway. 0.10.3 was
introduced 10 month ago, so a good transition time was also given.
Now it's time to just kill it.
Also remove cvs and svn versions since those are 0.9.x leftovers and
QEMU moved to git long ago.
Also remove gcc3 checks since that are not relevant for QEMU 0.10+.
Also remove from icecc blacklist, since QEMU builds fine with it and
the reason for blacklisting was GCC 3.
Signed-off-by: Roman I Khimov <khimov@altell.ru>
Acked-by: Tom Rini <tom_rini@mentor.com>
Acked-by: Koen Kooi <koen@openembedded.org>
Acked-by: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
|
|
icecc-blacklisted packages currently built not only without icecc environment
set but also without any parallel options enabled. The original intention was
not to kill the build machine, I guess, since having a good icecc cluster it's
easy to set '-j16' or '-j32' or whatever else which could do so. However as
the toolchain packages are blacklisted for icecc they're becoming a
bottleneck in the build process, while they can be built with local-machine
parallelism.
So, in order to solve it, introducing ICECC_FALLBACK_PARALLEL option. It's
simply used as PARALLEL_MAKE for icecc-blacklisted packages.
|
|
Building things with icecc and BB_NUMBER_THREADS more then 1 you could see
a lot of messages:
ERROR: no cross compiler built yet?
before gcc-cross would be properly built. There is technically nothing wrong,
cross compiler is not there yet and it's not needed when bitbake does
fetch-unpack-patch and other things to prepare package build. But it makes
people uncomfortable.
We can safely kill this messages.
|
|
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
Signed-off-by: Koen Kooi <koen@openembedded.org>
|
|
|
|
Disable icecc to pass compiling
|
|
compiler while building glibc from scratch.
|
|
* compiled from scratch cooking fso-image successfully so I can say it
works for me (tm).
* must bitbake icecc-create-env first.
|
|
|
|
package is not to use the icecc scheduler.
In this way you don't end up with -jX to be handled by a single cpu/machine
Remove glibc and add glibc-intermediate in the list of packages not use the icecc scheduler
|
|
|
|
Remove debug messages
|
|
dependancy problem
|
|
Handles native/cross cross-kernel and target compile jobs
Accepts user supplied package and class exclusion lists
|
|
|
|
single charachter
[2] will get us the 2nd charachter of the first line. This
is not what we wanted. We want the version number which is the
'2nd' column of the first line.
|
|
For icecream we need to package a tar.bz2 containing our
used toolchain. It must contain a gcc, g++ and cc1 and cc1plus
and a spec file (if it is not built-in). Optionally it contains
host libc.so and libfd.so (which we do not package). Simplify the
code creating the tar.bz2 and make it work with any version of
gcc/glibc/uclibc (untested).
|
|
os.path.join to create paths
|
|
native or cross package
|
|
|
|
INHERIT += " icecc " in your local.conf to use icecream for
distributed builds. Once a toolchain is built we build a tar.gz out
of it and it will automatically get distributed on the build farm.
There are still problemes to be resolved but this class is good enough
for now
BKrev: 42b9db561cfYQxk9iw6rR1nFxOggQQ
|
