Mirror of git.yoctoproject.org/poky https://git.enea.com/cgit/linux/poky.git/atom?h=1.1_M3 2011-07-27T14:45:47+00:00 2011-07-27T14:45:47+00:00 Mark Hatle mark.hatle@windriver.com 2011-07-26T17:57:54+00:00 urn:sha1:5aef1898a5b5e1a91fa5c2ce834b1c69c3df7900 bfd.h conflicts between 32-bit and 64-bit versions. (From OE-Core rev: cd2975f7ad380aaac8c88bc151a2c34a42d4c540) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2011-07-20T14:27:39+00:00 Khem Raj raj.khem@gmail.com 2011-07-18T22:57:23+00:00 urn:sha1:c19d858d019ac8081dd51496cd94225b4d11e788 (From OE-Core rev: 43c72d44337a736fc4b83ce16f7f1ed0d74243dc) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2011-07-13T11:34:29+00:00 Nitin A Kamble nitin.a.kamble@intel.com 2011-07-07T15:44:29+00:00 urn:sha1:ef0d0e105fdbb759f8a98a48fa0026586e663c40 To fix these package qa warnings WARNING: For recipe binutils, the following files were installed but not shipped in any package: WARNING: /usr/bin/ld.bfd WARNING: /usr/bin/elfedit (From OE-Core rev: 2365c6830119f9242aae3450488183ec11fe9c1d) Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2011-07-08T15:39:09+00:00 Nitin A Kamble nitin.a.kamble@intel.com 2011-07-07T00:26:38+00:00 urn:sha1:3f4f5c14ac8088d523c8c884f3dfb5f7ea1e5fdc (From OE-Core rev: 4810404f22d7cf8849dc32da68dd33a156cac407) Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2011-06-30T21:42:04+00:00 Phil Blundell pb@pbcl.net 2011-06-27T15:51:16+00:00 urn:sha1:b78173f176eeff553e2e941bd06ff032daebc7be But ensure that gcc-cross-intermediate always uses ld.bfd since (e)glibc won't build with gold. (From OE-Core rev: 207a9013670560d62c793a66f01e19f4760a71a8) Signed-off-by: Phil Blundell <philb@gnu.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2011-06-22T15:57:34+00:00 Khem Raj raj.khem@gmail.com 2011-06-22T00:58:06+00:00 urn:sha1:3071ceb2bd1a42b28682e0ec851cbea62843e426 (From OE-Core rev: c8dfb7d31ceb3cc92452bda7d4fbf6fd2e248509) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2011-05-25T22:53:47+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2011-05-25T22:51:57+00:00 urn:sha1:5d56586a00350f2ec90a7143182a3f1294fb4c73 Without this, compiler errors such as: configure:33440: i586-poky-linux-gcc -march=i586 --sysroot=/media/build2/builds/rptest/b2/tmp/sysroots/qemux86 -o conftest -D_REENTRANT -Wl,-O1 -Wl,--as-needed conftest.c -lpthread >&5 /media/build2/builds/rptest/b2/tmp/sysroots/x86_64-linux/usr/libexec/i586-poky-linux/gcc/i586-poky-linux/4.6.0/as: /media/build2/builds/rptest/b2/tmp/sysroots/x86_64-linux/usr/bin/i586-poky-linux/../../../usr/lib/libz.so.1: no version information available (required by /media/build2/builds/rptest/b2/tmp/sysroots/x86_64-linux/usr/libexec/i586-poky-linux/gcc/i586-poky-linux/4.6.0/as) /media/build2/builds/rptest/b2/tmp/sysroots/x86_64-linux/usr/libexec/i586-poky-linux/gcc/i586-poky-linux/4.6.0/ld: /media/build2/builds/rptest/b2/tmp/sysroots/x86_64-linux/usr/bin/i586-poky-linux/../../../usr/lib/libz.so.1: no version information available (required by /media/build2/builds/rptest/b2/tmp/sysroots/x86_64-linux/usr/libexec/i586-poky-linux/gcc/i586-poky-linux/4.6.0/ld) can be see. This is due to the compiler being built against the system zlib, before zlib-native is built and in the sysroot. Once that has been built it can confuse the linker depending on the relative library versions. (From OE-Core rev: a04d50a0318cd16d5fb02a625d739e03b94e42b7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2011-05-13T10:02:19+00:00 Nitin A Kamble nitin.a.kamble@intel.com 2011-05-12T21:54:55+00:00 urn:sha1:42d2170f8630ffe4cb9ae8cd8d9e5ca33a808eda python: update upstream-status for patches binutils: update upstream-status for patches gcc 4.5.1 4.6.0: update upstream-status for patches autoconf: update upstream-status for patches automake: update upstream-status for patches bison: update upstream-status for patches distcc: update upstream-status of patches fstests: update upstream-status for patches gdb: update upstream-status of patches intltool: update upstream-status of patches libtool: update upstream status of patches linux-libc-headers: update upstream-status for patches make: update upstream-status for patches perl: update upstream-status for patches python-pycurl: update upstream-status for patches python-pygobject: update upstream status for patches python-pyrex: update upstream-status for patches quilt: update upstream-status of patches tcl: update upstream-status for patches gnu-config: update upstream-status for patches gmp: update upstream-status for patches (From OE-Core rev: a62fa9b213b09bf48c48499d2e3c66a9ee306deb) Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2011-05-11T16:14:26+00:00 Nitin A Kamble nitin.a.kamble@intel.com 2011-05-10T20:07:54+00:00 urn:sha1:2e4518bf18d977e1249ef7e7cd384df66e7b4801 (From OE-Core rev: d7237140554ad076be12edf915d6d15206c9b8c7) Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2011-05-09T13:09:08+00:00 Tom Rini tom_rini@mentor.com 2011-05-04T19:28:25+00:00 urn:sha1:610ba36030b811646cde5f741ef0c8db9af305cb When TARGET_PREFIX and TARGET_SYS didn't match up, the symlinks and update-alternatives weren't working. TARGET_PREFIX is what we use when configuring so it's what we should be using here. This is 79b497edc0ce5d54db564818e59b690d3391d6ce from OE. (From OE-Core rev: 371205d21723ec911a77d5e7c1ef51fb26d854f5) Signed-off-by: Tom Rini <tom_rini@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>