Age | Commit message (Collapse) | Author | Files |
|
* no need for DONT_CHECK_KERNELSIZE
* clean up the affected files
* check happens only if KERNEL_IMAGE_MAXSIZE is set
|
|
STAGING_DIR_HOST is "" when using native bbclass:
native.bbclass:STAGING_DIR_HOST = ""
But in autotools.bbclass there is:
sed -i -e s:${STAGING_DIR_HOST}::g $i
which result in the following code in run.autotools_prepackage_lamangler
sed -i -e s:::g $i
which makes libxml2-native fail like this:
| sed: -e expression #1, char 0: no previous regular expression
I discussed it on IRC:
Feb 11 17:41:29 <RP> GNUtoo: We should only be doing that is STAGING_DIR_HOST isn't empty I guess
So I made a temporary fix which only workarround,because some issues persist:
Feb 11 17:41:02 <pb_> RP: heh, I wonder whether paths with colons in would be considered valid :-}
Signed-off-by: Denis 'Gnutoo' Carikli <GNUtoo@no-log.org>
|
|
* config.vapi is per-app and can be considered as part of the autotools stuff
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
|
|
There is no point in telling users to move TMPDIR "back" to its current location :-}
|
|
We need to add ${S}/${KERNEL_OUTPUT} with package_stagefile_shell to
avoid playing more complex games with the install line. We should
also use package_stagefile_shell on the modules tarball as that will
not otherwise be reproduced.
|
|
${SYSROOT_DESTDIR} ends on a / but there is also a / after the variable
and a slash as the first character of the next variable.
This patch removes the / that is explicitly added so in the generated
code we get // instead of the even sillier looking (and probably more
confusing) ///
Signed-off-by: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>
|
|
Accidently tagged another file to this commit, sorry
This reverts commit b977bbd442f3d00c884b68c1307bd9b14fb96446.
|
|
${SYSROOT_DESTDIR} ends on a / but there is also a / after the variable
and a slash as the first character of the next variable.
This patch removes the / that is explicitly added so in the generated
code we get // instead of the even sillier looking (and probably more confusing) ///
Signed-off-by: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>
|
|
This file was not updated when DISTRO_PR was introduced.
Result of it was that packages were not properly added to the packaged staging package
(due to faulty filenames being generated).
This patch adds ${DISTRO_PR} to the filenames involved
Signed-off-by: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>
|
|
* use += instead of =
this appends new file paths to include instead of replacing the
current definition
Signed-off-by: Rolf Leggewie <oe-devel@rolf.leggewie.biz>
Acked-by: Graeme Gregory <dp@xora.org.uk>
Acked-by: Martin Jansa <Martin.Jansa@gmail.com>
Acked-by: Michael 'Mickey' Lauer <mickey@vanille-media.de>
|
|
When using base_contains() to check for a string in a variable for a,
if the variable is not defined an exception occurs. By checking the
existance of the variable and returning false if it isn't there,
a value can be checked for a variable regardless of whether or not it
is defined.
Signed-off-by: Brian Pomerantz <bapper@mvista.com>
Signed-off-by: Chris Larson <clarson@mvista.com>
Acked-by: Khem Raj <raj.khem@gmail.com>
Acked-by: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
Signed-off-by: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
|
|
from packaged staging"
This reverts commit 61acb940a7436a43d0894284d25e8d106f461c23.
This patch is not as robust as I thought, will reassess the issue at hand later
Signed-off-by: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>
|
|
packaged staging
kernel.bbclass do_deploy has:
install -m 0644 ${KERNEL_OUTPUT} ${DEPLOY_DIR_IMAGE}/${KERNEL_IMAGE_BASE_NAME}.bin
which expands to
install -m 0644 arch/arm/boot/uImage .../deploy/glibc/images/beagleboard/uImage-2.6.29-r51-beagleboard.bin
but in packaged staging arch/arm/boot/uImage does not exist so we get the error:
install: cannot stat `arch/arm/boot/uImage': No such file or directory
This patch only installs uImage if not using packaged staging
Signed-off-by: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>
|
|
Signed-off-by: Denys Dmytriyenko <denis@denix.org>
Acked-by: Khem Raj <raj.khem@gmail.com>
Acked-by: Frans meulenbroeks <fransmeulenbroeks@gmail.com>
|
|
-native and -sdk cases as well
|
|
|
|
New checksums system needs a name= in the SRC_URI name, so add a default
one for gnome.
|
|
to package we don't read potentially stale pkgdata from staging.
This is basically the commit 27b9bc946eeb3faa7b10d92689ab527af42727bd that got
lost when merging poky stuff into the repo. The behavior is much like
what we already have with package_ipk.
Signed-off-by: Ricardo Salveti de Araujo <ricardo.salveti@openbossa.org>
|
|
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.
|
|
comprehensible
Signed-off-by: Chris Larson <clarson@mvista.com>
|
|
Signed-off-by: Chris Larson <clarson@mvista.com>
|
|
Signed-off-by: Chris Larson <clarson@mvista.com>
|
|
* Apply the same change as c0a3e91845fad1cdda723bdcf962de8bc01f8a2d for
x86 path
* A check was missed in the x86 path of the stage method.
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
* With 2.6.33-rc2-00252-ge9e5521 on my host I noticed that
"cat /proc/sys/vm/mmap_min_addr" returns now
"cat: /proc/sys/vm/mmap_min_addr: Operation not permitted"
Its probably becuse of
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=0e1a6ef2dea88101b056b6d9984f3325c5efced3
But I'm not sure if checking CAP_SYS_RAWIO even for reading this value
is intentional or just bug which should be fixed in kernel.
This patch makes bitbake ignore reading error. Possible QEmu failure is not
handled yet.
Acked-by: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
|
|
Without that patch uicmoc3-native fails to build.
|
|
This optional bbclass implements per-subpackage debug packages. Among other
things, this makes it much easier to automate creation of debug images (where
you have the debug files for all installed packages).
Signed-off-by: Chris Larson <clarson@mvista.com>
|
|
|
|
The Makefile's generated by Qt are using this variable and the
assignment of STRIP = $(OE_QMAKE_STRIP) will be overturned by
this export. One option would be to set STRIP = $OE_QMAKE_STRIP
in the bb file but this would break striping in package.bbclass.
With the unset STRIP we are able to generate proper -dbg packages
for Qt and other qmake based utilities.
|
|
Acked-By: Michael 'Mickey' Lauer <mlauer@vanille-media.de>
Acked-by: Koen Kooi <koen@openembedded.org>
|
|
* The LGPL and Commercial edition are actually the same tarball.
* If someone sees the need he can take qt qt4-recipes and specify
-commercial in the compilation.
|
|
insane.bbclass
* Without it the insance check will fail due to key miss exception.
Signed-off-by: Guo Hongruan <camelguo@gmail.com>
|
|
there is choice between gzip and lzma for the initramfs.cpio - in patchwork there are pending patches for lzo compressor, so we add lzo too - patch is only concerning initramfs images
|
|
|
|
* include/asm link was killed in
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=f7f16b7799ed68654850ab340ef812895aebcf4c
* utsrelease.h was moved in
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=273b281fa22c293963ee3e6eec418f5dda2dbc83
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Acked-by: Khem Raj <raj.khem@gmail.com>
|
|
When Java things are build for more then one architecture strange things
happen:
- first architecture builds fine
- next architectures fails to build
Thats due to lack of JAR files as they were built as PACKAGE_ARCH="all"
but staged as PACKAGE_ARCH="TARGET_ARCH" so BitBake do not build them
again but Java classes are unable to find them.
Solution is to stage JAR files to non-ARCH directory. I used
staging/java for it and build tested with stable/2009 and
org.openembedded.dev branches.
Signed-off-by: Marcin Juszkiewicz <marcin@buglabs.net>
|
|
|
|
* this fixes the uninitalize message in CMakeCache.txt
|
|
|
|
This reverts commit 38361a2cd9b962daccf5af7c85d54245e3711f9e.
Unfortunately the fix need to be done in the specific recipes.
Filtering .so at this stage breaks packaging for other plugins.
|
|
This closes bug 5339. Thx to Pb for fix.
Signed-off-by: Kristoffer Ericson
|
|
|
|
RP says: In theory the recipes themselves should be patched to stop this nonesense getting in there in the first place
but that is appropriate for pkgconfig.bbclass
|
|
Added the chicken-cross recipe and a chicken class for translating
architectures to the Chicken nomenclature.
Signed-off-by: Mario Domenech Goulart <mario@ossystems.com.br>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
* Move do_deploy after do_package in kernel.bbclass as RP said
* Move devicetree_image before do_deploy in linux.inc, because
it creates dependency loop if its between after do_package
and before do_deploy.
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
* Turn striping functionality into functions and call in the appropriate place
* Removing various races and ordering issues
* Should mean kernel modules are correctly stripped (and stripping can be disabled)
* Addresses bug 1182
* kernel module stripping applied to ${PKGD} (the correct place)
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|