summaryrefslogtreecommitdiff
path: root/meta/recipes-devtools
Commit message (Collapse)AuthorAgeFilesLines
* dpkg: Fix preinst executionRichard Purdie2011-12-082-2/+49
| | | | | | | Add a patch to fix exeuction of pre/post install scripts. See the patch header for more details. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* subversion: update 1.7.0 to 1.7.2 and force libtool recreationKlaus Kurzmann2011-12-072-3/+4
| | | | | | | | | | | | | * subversion-1.7.* had libtool-2.4, oe-core now has 2.4.2 and it was failing: x86_64-linux-libtool: Version mismatch error. This is libtool 2.4.2, but the x86_64-linux-libtool: definition of this LT_INIT comes from libtool 2.4. x86_64-linux-libtool: You should recreate aclocal.m4 with macros from libtool 2.4.2 x86_64-linux-libtool: and run autoconf again. Signed-off-by: Klaus Kurzmann <mok@fluxnetz.de> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Backport patch from trunk to fix ICE seen on armv7 with mesa-xlibKhem Raj2011-12-062-1/+36
| | | | | | | This patch is a backport of http://patchwork.ozlabs.org/patch/110517/ Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* openjade-native_1.3.2.bb: remove CONFIGUREOPTS as vardep for do_configureMatthew McClintock2011-12-051-0/+5
| | | | | | | | | This variable was being expanded immediately and pulling in paths to the variable dependecies which causes it's sstate-cache to never be reused Signed-off-by: Matthew McClintock <msm@freescale.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dpkg-native: Fix perl pathRichard Purdie2011-12-021-1/+2
| | | | | | | The path to the native perl was incorrect leading to rootfs failures. This patch corrects that problem. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ubootchart: update to svn R12Saul Wold2011-12-021-1/+1
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* libtool: Upgrade from 2.4 -> 2.4.2Nitin A Kamble2011-12-0115-208/+168
| | | | | | | | | | | | | Rebased patches to the newer source code and deleted resolve-sysroot.patch since its already applied upstream merged libtool-2.4.2.inc & libtool.inc files replaced PR with ${INC_PR}.0 Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: fix for .debug files QA warningsNitin A Kamble2011-12-014-3/+5
| | | | | | | | | | | | | | | | | | THis commit fixes these QA warnings for binutils recipe WARNING: For recipe binutils, the following files/directories were installed but not shipped in any package: WARNING: /usr/arm-oe-linux-gnueabi/bin/.debug WARNING: /usr/arm-oe-linux-gnueabi/bin/.debug/strip WARNING: /usr/arm-oe-linux-gnueabi/bin/.debug/objcopy WARNING: /usr/arm-oe-linux-gnueabi/bin/.debug/objdump WARNING: /usr/arm-oe-linux-gnueabi/bin/.debug/ld WARNING: /usr/arm-oe-linux-gnueabi/bin/.debug/nm WARNING: /usr/arm-oe-linux-gnueabi/bin/.debug/as WARNING: /usr/arm-oe-linux-gnueabi/bin/.debug/ranlib WARNING: /usr/arm-oe-linux-gnueabi/bin/.debug/ld.bfd WARNING: /usr/arm-oe-linux-gnueabi/bin/.debug/ar Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gnu-config: Only apply path transformations in the non-native/non-nativesdk caseRichard Purdie2011-12-012-2/+2
| | | | | | | | | The BUILD_ARCH != TARGET_ARCH check isn't a safe one to detect native builds and doesn't cover the nativesdk case. This converts the recipe to use PN instead which is more accurate and ensures the correct entries making it into the correct packages. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* make: expand MAKEFLAGS before we re-exec after rebuilding makefiles.Dexuan Cui2011-12-012-1/+42
| | | | | | | | | This patch was got from the upstream cvs repo of make to fix the bug of make-3.82: http://savannah.gnu.org/bugs/?30723 RP: Tweaked patch status to Backport Signed-off-by: Dexuan Cui <dexuan.cui@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* squashfs-tools: fix PR, those should start with 'r'Martin Jansa2011-11-301-1/+1
| | | | | Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Fix multiarch DISTRO_FEATUREJulian Pidancet2011-11-302-7/+11
| | | | | | | | | | | | Make get_gcc_multiarch_setting more elegant. Use a dictionnary to store the config options and replace bb.data.getVar with d.getVar. Remove i686 from the architecture list because it doesn't seem to be a valid TARGET_ARCH any more in OE. Configure gdb (gdb and gdb-cross) with --enable-64-bit-bfd if multiarch DISTRO_FEATURE is present Signed-off-by: Julian Pidancet <julian.pidancet@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perl: bump PR for gdbm SOVERSION changeKoen Kooi2011-11-301-1/+1
| | | | | Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* autoconf: Extend to provide nativesdk recipeWenzong Fan2011-11-301-3/+6
| | | | | | | | | | | | | | As the same reason with automake, extend autoconf to provide nativesdk recipe too. This patch was only used for autoconf that running on target: * path_prog_fixes.patch: replace '@PERL@' with '@bindir@/env perl' It's unavailable for autoconf-native and autoconf-nativesdk, so exclude it for those two recipes. Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* automake: Extend to provide nativesdk recipeWenzong Fan2011-11-302-2/+3
| | | | | | | | | We will provide autotools nativesdk in meta-tookchain for reconfigure any autotools supported projects, as a part of the plan we should extend their recipes first. Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* m4: Extend to provide nativesdk recipeWenzong Fan2011-11-302-2/+6
| | | | | | | | | | We need to provide autoconf-natviesdk in meta-toolchain, the m4-nativesdk is required by it. Both extend the m4 recipes for GPLv2 and GPLv3. Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gnu-config: Extend to provide nativesdk recipeWenzong Fan2011-11-301-2/+2
| | | | | | | | We need to provide autoconf-natviesdk in meta-toolchain, the gnu-config-nativesdk is required by it. Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* PR Bump for OpenSSL 1.0Saul Wold2011-11-304-4/+4
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* binutils: upgrade from 2.21.1a to 2.22Nitin A Kamble2011-11-2918-577/+542
| | | | | | | | | And rebase the patches to the newer source code This patch is upstream hence deleting it from the recipe. binutils/110-arm-eabi-conf.patch Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
* intltool: remove XML::Parser checkSaul Wold2011-11-292-3/+37
| | | | | | | | | | | | | | | | | | | | | | Add Patch to disable the XML::Parser check in the target intltool.m4, this check will find the host (not native) XML::Parser if it's installed possibly causing Host contamination, but will also fail configuration if XML::Parser is not installed on the host. Since we know that XML::Parser is installed on the image, we don't really need this check, so comment it out. From RP in mail thread: > If the recipe needs perl for > some other reason than intltool, it needs perlnative but it if only > needs perl for intltool, we shouldn't need the dependency. The .m4 macro > checks are well intended but don't fit the way we use perl. I really > don't want to end up in a position where intltool automatically means we > have to add perlnative as a dependency and we've previously seen many > problems related to that. Signed-off-by: Saul Wold <sgw@linux.intel.com>
* rpm_5.4.0.bb: Build rpm without xzMatthew McClintock2011-11-291-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes the following issue: Log data follows: | NOTE: Creating RPM package for perf-dbg | NOTE: Creating RPM package for perf | NOTE: Creating EMPTY RPM Package for kernel | NOTE: Creating EMPTY RPM Package for kernel-3.0.9-00348-gec4b357 | NOTE: Creating RPM package for kernel-image-3.0.9-00348-gec4b357 | NOTE: Creating RPM package for kernel-dev | NOTE: Creating RPM package for kernel-vmlinux | NOTE: Not creating empty RPM package for kernel-misc | NOTE: Creating RPM package for kernel-devicetree | NOTE: Creating RPM package for kernel-module-libcrc32c | NOTE: Creating RPM package for kernel-module-crc-itu-t | NOTE: Creating RPM package for kernel-module-sctp | NOTE: Creating RPM package for kernel-module-pcbc | NOTE: Creating RPM package for kernel-module-crc32c | NOTE: Creating RPM package for kernel-module-binfmt-misc | NOTE: Creating RPM package for kernel-module-nfsd | NOTE: Creating RPM package for kernel-module-exportfs | NOTE: Creating RPM package for kernel-module-msdos | NOTE: Creating RPM package for kernel-module-nls-utf8 | NOTE: Creating RPM package for kernel-module-udf | NOTE: Creating RPM package for kernel-module-isofs | NOTE: Creating RPM package for kernel-module-usbhid | NOTE: Creating RPM package for kernel-module-scsi-wait-scan | NOTE: Creating EMPTY RPM Package for kernel-modules | /local/home/mattsm/git/fsl-local-sdk/build_p4080ds_release/tmp/sysroots/x86_64-linux/usr/bin/rpmbuild.real: error while loading shared libraries: liblzma.so.5: cannot open shared object file: No such file or directory | ERROR: Function 'BUILDSPEC' failed (see /local/home/mattsm/git/fsl-local-sdk/build_p4080ds_release/tmp/work/p4080ds-fsl-linux/linux-qoriq-sdk-3.0.6-r2/temp/log.do_package_write_rpm.18943 for further information) Signed-off-by: Matthew McClintock <msm@freescale.com>
* Introduce multiarch DISTRO_FEATUREJulian Pidancet2011-11-294-3/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch introduces a distro feature which enables gcc to produce both 32bit and 64bit code, and enables binutils to operate on both 32bit and 64bit binaries. It differs from multilib toolchains in that it does not require to compile a version of the libc for each architecture variant. However, the code produced for the secondary architecture will not be linkable against the libc. v2: - Renamed the feature name from "biarch" to "multiarch". The GCC installation manual claims that the mips-linux can be made a tri-arch compiler (http://gcc.gnu.org/install/configure.html) - For x86_64, the compiler is made bi-arch by default, so nothing has to be done in particular. - I analyzed the gcc/config.gcc from GCC sources and added in this patch all the architectures that could be made biarch with the version of gcc currently used in OE, which are powerpc, and sparc, in addition to x86. mips and s390 will probably be supported in future versions of gcc. For x86 and sparc, only the --enable-targets=all option is valid to make this work (this option doesn't have any other side effects than making the compiler bi-arch). For powerpc, I used the --enable-targets=powerpc64 option (although 'all' also works). Note: - Untested on powerpc and sparc. But I believe it works the same as with x86. - gcc in meta-toolchain is also made multiarch. Signed-off-by: Julian Pidancet <julian.pidancet@gmail.com>
* opkg-utils: handle 6 digit UID fields properlyKoen Kooi2011-11-292-1/+29
| | | | Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
* python-native: Fix gcc compiler detecting logicKhem Raj2011-11-292-12/+12
| | | | | | | | | | | | | | | | | | | We have a patch unixccompiler.patch where we try to throw away everything except first element of CC string but this does not work if gcc is prepended with something e.g. CC="ccache gcc" then the logic fails and it ends up in some modules failing on you silently (_sqlite3) in my case. The fix here is to drop basename so we keep the whole string as it is and then the detection function searches for gcc string in the whole CC. This works in both cases one the original intent of the patch and the second described above. One place where it will fail is if someone has non-gcc compiler installed in some subdir which has gcc in it e.g. /usr/gcc/fakecc but for OE this should never happen. Ideally the the detection logic should have tried to execute gcc and then parsed --version output or something. Signed-off-by: Khem Raj <raj.khem@gmail.com>
* libjson: add 0.9Koen Kooi2011-11-291-0/+14
| | | | Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
* gcc-package-target.inc: add the symbol link /lib/cppDexuan Cui2011-11-242-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | When I was trying self-hosted-image, eglibc's do_install failed in the target: ERROR: cannot stat bootparam_prot.h: the cause is: rpcgen doesn't work properly: rpcgen can't exec /lib/cpp since it doesn't exist. According to http://tldp.org/LDP/Linux-Filesystem-Hierarchy/html/lib.html: "if a C preprocessor is installed, /lib/cpp must be a reference to it, for historical reasons. The usual placement of this binary is /usr/bin/cpp". Typical distros, like Ubuntu, openSuSE, Fedora and RHEL, all comply with the rule. Actually in meta/recipes-devtools/gcc/gcc-package-target.inc, we do try to package ${base_libdir}/cpp: FILES_cpp = "\ ${bindir}/${TARGET_PREFIX}cpp \ ${base_libdir}/cpp \ ${libexecdir}/gcc/${TARGET_SYS}/${BINV}/cc1" But unluckily we didn't create a symbol link in do_install. This patch adds the symbol link. Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
* rpm: Flush old logs by change the DB_CONFIGMei Lei2011-11-242-2/+15
| | | | | | | | Fixes [YOCTO #1174] Rpm logs will grow indefinitely, so change the config to flush those old logs. Signed-off-by: Mei Lei <lei.mei@intel.com>
* dosfstools: add Upstream-Status to patchesScott Garman2011-11-247-0/+44
| | | | Signed-off-by: Scott Garman <scott.a.garman@intel.com>
* libtool: Avoid relinking when cross compiling, its pointlessRichard Purdie2011-11-243-2/+105
| | | | | | | | | | | | | | | | | | There is no point in having "executable" binaries in the .libs directory linked with different rpaths to the target which could concivably be run on the build system when cross compiling. This patch removes the extra rpaths ($compile_rpath) so that the output from the "link" stage can be used on the target. We can then avoid having to "relink" during the install stage. This saves some build time (do_install is over 2 minutes faster for pulseaudio). This patch also removes an annoying "seems to be moved" warning which is totally bogus in the sysroot case. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* apt: Fix locale header and hardcoded libname issuesRichard Purdie2011-11-236-10/+104
| | | | | | | | | | | apt wasn't building on modern libc/compiler combinations due to missing header includes. The libcpp version was also being hardcoded, this patch generates it dynamically to work on different host systems which no longer have this. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-4.6: Fix gcc ICE on qt4-x11-free/armv7-aKhem Raj2011-11-212-4/+68
| | | | | | | | Backport fix for PR 47551 fixes the ICE seen on armv7-a/qt4-x11-free Bump up SRCREV past gcc 4.6.2 release Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtool-cross: Unbreak and actually use more of itRichard Purdie2011-11-211-11/+15
| | | | | | | | | | | | We should be using libtool-cross for cross compiling but were not. This patch sets datadir so libtoolize ends up containing correct paths. It then installs libtoolize. The path ltmain.sh was installed to was incorrect and this is fixed. We also now install all the libtool m4 macros and config files. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* btrfs-tools: update to the latest git commitNitin A Kamble2011-11-1726-4644/+16
| | | | | | Remove all the upstreamed and not needed patches. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
* python-gst: upgrade from 0.10.21 to 0.10.22Nitin A Kamble2011-11-171-3/+3
| | | | | Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tcl: upgrade from 8.5.10 to 8.5.11Nitin A Kamble2011-11-171-2/+2
| | | | | Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* update-alternatives: Various fixesRichard Purdie2011-11-163-5/+13
| | | | | | | | | | | dpkg-native's update-alternatives is broken for offline work so don't install it. Also list update-alternatives in the multiprovider whitelist to avoid unwanted multiple provider warnings when multiple package backends are enabled. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-4.6: fix toolchain build for SH4Michael Brown2011-11-161-0/+2
| | | | | | | | | | | | | | | | Signed-off-by: Michael Brown <Michael_E_Brown@dell.com> Port patch from base openembedded. Since 4.6 already has fixes for config.gcc, the fix only requires a one line change to gcc-cross4.inc. The patch was imported from the OpenEmbedded git server (git://git.openembedded.org/openembedded) as of commit id 3aa8afe97e9cf1340feb9c4442a6ed88b7e32c96. gcc-4.5: Fix toolchain builds for SH4/SH3 Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gnu-config: Create 2011111 releaseSaul Wold2011-11-161-0/+41
| | | | | | | | | Use a yoctoproject.org based tarball since gnu-config is required very early on in the native build process, we do not want to rely on git, which can cause a circular dependency issue. Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gnu-config: update to git HEADSaul Wold2011-11-162-85/+75
| | | | | | | | | Licence has update timestamp and Copyright year. This change needs a coresponding change to ASSUME_PROVIDED to add git-native Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* file: update to 5.09Saul Wold2011-11-162-5/+25
| | | | | Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* subversion: add 1.7.0 with native support and negative D_P for nowMartin Jansa2011-11-152-0/+52
| | | | | | | | | | | | | | | | | | | | | | | | | * intentionaly with negative D_P, bitbake fetcher should be improved to detect old checkout with newer subversion available or vice versa and do svn upgrade automaticaly or show better error, but subversion as client for target or -native for distributions which explicitly say they want 1.7 (with PREFERRED_VERSION) can be available already from oe-core. * be aware that checkouts from 1.7.0 are not compatible with older subversion clients (ie when builder populating distro PREMIRROR is using 1.7.0 all builders need to have also 1.7.0) * and also 1.7.0 client needs to call svn upgrade in checkout first in order to use it (so if PREMIRROR has tarball from 1.6.x it won't work on client using 1.7.0 unless fetcher2 is improved to detect this and call svn upgrade) * tested on SHR distribution http://wiki.shr-project.org/trac/wiki/Building%20SHR#subversion1.7inshr-chroot * only missing part is to add subversion-native dependency, so that native subversion is built, before building ie elementary (because EFL are using svnversion from configure.ac to detect source revision and .svn dir needs to be from compatible version). * read http://subversion.apache.org/docs/release-notes/1.7.html Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* dpkg/update-alternatives: Fix dpkg version of update-alternatives to be usableRichard Purdie2011-11-155-70/+57
| | | | | | | | | | | | | | | The version of dpkg the updates-alternatives-dpkg recipe pointed at no longer used a perl script but a compiled binary. This meant the "all" architecture field was invalid, as as the sed operation during do_patch. All things considered the separate recipe was pretty pointless. This patch moves update-alternatives back to being built as part of the dpkg recipe. It also moves various functionalty to the .inc file which it belongs and fixes building and packaging of the dpkg perl modules. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* syslinux: fix the SRC_URI by using the 4.xx directoryJan Luebbe2011-11-141-2/+2
| | | | | | | | This path should be valid for a longer time, as only the current release stays in main directory. Signed-off-by: Jan Luebbe <jluebbe@debian.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* opkg: Ensure we use the uname/gname fields when extracting tarballsRichard Purdie2011-11-142-1/+90
| | | | | | | | | | When extracting packages onto the target system in particular, we really want to ensure the name fields in the tarball are used over and above the numerical uid/gid values. This patch adds this functionality to opkg and ensures package upgrades work correctly permission wise. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rootfs_rpm.bbclass: Enable pre and post install scriptsMark Hatle2011-11-112-1/+161
| | | | | | | | | | | | | | | | | | [YOCTO #1755] We change the want the RPM rootfs install works to install pre and post install scripts. The new method uses a script helper that is invoked by RPM outside of the normal chroot. The wrapper is dynamically generated prior to the install starting. It will check the return code of the script. If the script fails, it will store a copy to be executed on the first system boot. This is similar to the previous mechanism. In addition, a line of debug was added to the scripts as written by package_rpm to list which package and which script for later debugging, if necessary. Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
* python: bump PRTom Zanussi2011-11-101-1/+1
| | | | | | | Commit 23d2eaf9 ('skip setup.py 'import check' when cross-compiling') neglected bumping the PR, this adds it. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
* Convert to use direct access to the data store (instead of bb.data.*Var*())Richard Purdie2011-11-1014-23/+23
| | | | | | | | | | | | | | | This is the result of running the following over the metadata: sed \ -e 's:bb.data.\(setVar([^,()]*,[^,()]*\), *\([^ )]*\) *):\2.\1):g' \ -e 's:bb.data.\(setVarFlag([^,()]*,[^,()]*,[^,()]*\), *\([^) ]*\) *):\2.\1):g' \ -e 's:bb.data.\(getVar([^,()]*\), *\([^(), ]*\) *,\([^)]*\)):\2.\1,\3):g' \ -e 's:bb.data.\(getVarFlag([^,()]*,[^,()]*\), *\([^(), ]*\) *,\([^)]*\)):\2.\1,\3):g' \ -e 's:bb.data.\(getVarFlag([^,()]*,[^,()]*\), *\([^() ]*\) *):\2.\1):g' \ -e 's:bb.data.\(getVar([^,()]*\), *\([^) ]*\) *):\2.\1):g' \ -i `grep -ril bb.data *` Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Allow use of dash as /bin/shRichard Purdie2011-11-102-2/+13
| | | | | | | | | | | | | | | | | | | | | We've had the check for dash as /bin/sh for a long time. Dash has been around long enough now that most major issues have been identified and fixed from build perspective. This patch fixes a bashism in the openjade-native recipe. It also adjusts libtool so that the header at the script is used and not the value of $SHELL. This is because many Makefiles change $SHELL so dash can get used to execute what is otherwise configured as a bash shell script. Since we don't need to execute scripts this way on any system I'm aware of us building upon, the simplest fix is just to remove $SHELL. With these two changes the dash check can be removed and we can allow builds with dash as /bin/sh Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> [Note: I know I need to add the description of the libtool change above into the prefix.patch]
* qemu: Ensure an internal qemugl script uses bash as it has bashismsRichard Purdie2011-11-106-6/+6
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python: skip setup.py 'import check' when cross-compilingTom Zanussi2011-11-082-0/+32
| | | | | | | | | | | | | | | | | | | | | | | | | build_extension() in setup.py, as part of the build process, does an 'import check' on the built extension. The import check in turn dlopen()'s the shared library associated with the extension, which isn't something that makes sense if that library was cross-compiled for a different architecture. This was noticed with an x86_64 target that was compiled with avx support, because it caused 'illegal instruction' exceptions: | /bin/sh: line 1: 14575 Illegal instruction ... -E ./setup.py -q build For other target architectures, it doesn't necessarily cause illegal instruction exceptions, but still fails. For example, on arm, the failure pathway causes this warning: *** WARNING: renaming "cmath" since importing it failed: .../cmath.so: wrong ELF class: ELFCLASS32 This patch to setup.py and the associated recipe changes allow the whole 'import check' logic to be skipped when cross-compiling. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
generated by cgit v1.2.3 (git 2.46.0) at 2024-11-03 12:34:08 +0000