It is possible for the git repository to have commits on branches
that are ahead of the SRCREVs for those branches. Since the
kern tools will simply checkout and build, we can end up building
a different kernel than what is expected.
It is up to the recipe to ensure that the branches are at the
correct commits. To do this, we simply check the current machine
branch against the SRCREV and if they don't match we move the
existing branch and do a checkout at the desired commit.
Note: This probably needs to be disabled with AUTOREV.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
This change allows the IMAGE_OVERHEAD_FACTOR (default to 1.2) to
adjust dynamicly how much space to add for each image, thus there
is 20% overhead space by default.
Signed-off-by: Saul Wold <Saul.Wold@intel.com>
The Linux man-pages project documents the Linux kernel and C library interfaces that are employed by user programs
Signed-off-by: Xiaofeng Yan <xiaofeng.yan@windriver.com>
It was possible for bitbake-runtime to be run against a semi-installed
python-native resulting in tracebacks with ImportError's.
To prevent this we stash the initial PATH in the BBConfiguration when bitbake
is started and then set this in the env when launching bitbake-runtask through
subprocesses Popen() call.
Signed-off-by: Joshua Lock <josh@linux.intel.com>
By defining the perf package in the shared kernel class bitbake will be able to
find the package provider even when the preferred kernel doesn't build perf,
preventing dependency resolution failures.
Signed-off-by: Joshua Lock <josh@linux.intel.com>
libzypp failed due to GCC "internal compiler error: segmentation fault" error on
MIPS target. The cause is about boost tribool type usage. If having assignement
within conditional check as below:
if ( (a = b) )
...
<a is a tribool type, b is a normal bool type>
then gcc4.3.3 throws internal error. Then the workaround is to move assignement
out of the conditional check.
However I didn't find same case from web.
We can come back to recheck this issue after upgrading to gcc4.5.0 for MIPS. If
this issue is still there, we'll need more analysis to decide whether to report
to gcc upstream or to libzypp upstream.
This fixes [BUGID #277]
Signed-off-by: Kevin Tian <kevin.tian@intel.com>
we use /usr/lib for x86-64 target, but sat-solver will use /usr/lib64 if 64bit
target arch is detected. This finally causes libzypp failed to find libsatsolver.a.
use "-DLIB=lib" to explicitly enforce the requirement
fix [BUGID #286]
Signed-off-by: Kevin Tian <kevin.tian@intel.com>
Add a new method, try_premirror, to the Fetch object which checks to see
whether the file needs to be fetched from a premirror.
Override this in the Git fetcher to only require a pre-mirror fetch when the
clone directory does not exist.
Fixes [BUGID 290]
Signed-off-by: Joshua Lock <josh@linux.intel.com>
"-Bsymbolic-functions" flag makes ld to bind the global function symbol of shared library at compiling time, thus reduce the runtime relocation cost.
However, this flag in binutil 2.20 cause QT4 mips building failure, which is "final link failed: Bad value" error in libQtWebKit.so linking stage. If downgrad to binutil 2.19, this error disappears.
so before binutil new release is out, it is better to disable this flag for QT4 mips.
Fix [BUGID #271]
Signed-off-by: Yu Ke <ke.yu@intel.com>
Rather than trying to determine things through guess-work use the newly
exported variables to determine where the native binaries reside and
whether we are running in a build directory or not.
Signed-off-by: Joshua Lock <josh@linux.intel.com>
Export the location of the native sysroot for use in the scripts to
determine the location of native binaries.
Also add a POKY_DISTRO_VERSION to the external toolchain environment as a
method of determining if we're running under a build directory or not
i.e. not if the variable is empty
Signed-off-by: Joshua Lock <josh@linux.intel.com>
The unfs server requires either rpcbind or portmap to be installed and
running to start so check for their presence in the script.
Signed-off-by: Joshua Lock <josh@linux.intel.com>
Updating the SRCREVs for the recent port of bug fixes for all boards
and the integration of qemux86-64 config and connector changes.
Now that the qemux86-64 changes are in tree, we can drop them from
the linux-wrs recipe.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
there're two RRECOMMENDS_task-poky-tools-profile both using direct assignment,
which makes 'perf' overriden by "kernel-module-oprofile"
Fix [BUGID #97]
Signed-off-by: Kevin Tian <kevin.tian@intel.com>
When setting localpath in the SRC_URI parameters the basename should be set
explicitly as the localpath() method is not called.
Fixes [BUGID #81]
Signed-off-by: Joshua Lock <josh@linux.intel.com>
These patches were mistakenly moved into meta/recipes-graphics/clutter
during the metadata reorg. This moves them back where they belong.
Signed-off-by: Scott Garman <scott.a.garman@intel.com>
In order to resolve a host-contamination problem, we re-work the way that
autoconf and friends are invoked during the compilation of RPM.
This has a side effect of fixing another bug where RPM was being renamed
HOST_ARCH-HOST_OS-rpm. So we remove the "fixes" for that behavior as well.
Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
