openembedded-core.git/meta/recipes-devtools, branch dora

gcc-4.8: backport fix for ICE when building opus

2014-08-11T11:06:43+00:00

* backported from 4.8.2, so daisy isn't affected

Signed-off-by: Martin Jansa 
Signed-off-by: Richard Purdie

binutils: Fix building nativesdk binutils with gcc 4.9

2014-07-27T07:37:38+00:00

Patches explain the issue in detail but this is exposed
with gcc 4.9 in binutils 2.23.2

(From OE-Core rev: fc5c467b680fc5aef4b0f689e6988e17a9322ae0)

(From OE-Core rev: 4dfb8847ebf8aab90ad8888933468e2899c96998)

(From OE-Core rev: af347d3298e15552d502d5b2ce497bbda9705bc7)

Signed-off-by: Khem Raj 
Signed-off-by: Richard Purdie

opkg: putting the service files into PN

2014-07-08T15:15:21+00:00

(From OE-Core rev: f0ec7f81c1951211f049c342fd6bd1cad424564a)

[YOCTO #6392]

Signed-off-by: Roy Li 
Signed-off-by: Saul Wold 
Signed-off-by: Richard Purdie 
Signed-off-by: Chen Qi 
Signed-off-by: Richard Purdie

populate-extfs.sh: fix to handle special file names correctly

2014-07-08T15:09:10+00:00

`debugfs' treats spaces and "" specially. So when we are dealing with
file names, great care should be taken to make sure that `debugfs'
recognizes file names correctly.

The basic solution here is:
1. Use quotation marks to handle spaces correctly.
2. Replace "xxx" with ""xxx"" so that debugfs knows that the quotation
   marks are parts of the file name.

[YOCTO #6503]

Signed-off-by: Chen Qi 
Signed-off-by: Richard Purdie

libtool-cross/native: Force usage of bash due to sstate inconsistencies

2014-07-03T13:55:42+00:00

Scenario:
a) libtool script is built on system with bash as /bin/sh
b) machine B installs sstate from build a)
c) machine B has dash as /bin/sh

In this scenario, the script fails to work properly since its expecting
/bin/sh to have bash like syntax and it no longer does have it.

This patch forces the configure process to use /bin/bash, not /bin/sh
and hence allows the scripts to work correctly when used from sstate.

(From OE-Core rev: 24d5b449e5f4d91119f0d8e13c457618811aadfc)

Signed-off-by: Richard Purdie

e2fsprogs: Fix populate-extfs.sh

2014-06-30T15:27:28+00:00

Fix the use of command dirname on ubuntu 12.04.
dirname does not accept space in file name.

Signed-off-by: Stéphane Cerveau 
Signed-off-by: Richard Purdie

prelink: Fix SRC_URI

2014-06-24T10:06:28+00:00

The SHA we use it actually on cross_prelink branch
if you do not use yocto source mirrors then the fetch
for prelink on dora fails due to missing branch in SRC_URI

Signed-off-by: Khem Raj 
Signed-off-by: Richard Purdie

populate-extfs.sh: keep file timestamps

2014-06-24T10:05:26+00:00

Fix populate-extfs.sh to keep file timestamps while generating the
ext file systems.

[YOCTO #6348]

Signed-off-by: Chen Qi

rpm: Fix rpm -V usage

2014-06-24T10:05:26+00:00

[YOCTO #6309]

It appears a logic issue has caused rpm -V to no longer
verify the files on the filesystem match what was installed.

(From OE-Core master rev: 117862cd0eebf6887c2ea6cc353432caee2653aa)

Signed-off-by: Mark Hatle 
Signed-off-by: Richard Purdie 
Signed-off-by: Robert Yang

populate-extfs.sh: error out if debugfs encounters some error

2014-06-24T09:57:32+00:00

Previously, even if we encounter some error when populating the
ext filesystem, we don't error out and the rootfs process still
succeeds.

However, what's really expected is that the populate-extfs.sh script
should error out if something wrong happens when using `debugfs' to
generate the ext filesystem. For example, if there's not enough block
in the filesystem, and allocating a block for some file fails, the
failure should not be ignored. Otherwise, we will have a successful
build but a corrupted filesystem.

The debugfs returns 0 as long as the command is valid. That is, even
if the command fails, the debugfs still returns 0. That's really a
pain here. That's why this patch checks the error output to see whether
there's any error logged.

Signed-off-by: Chen Qi 
Signed-off-by: Richard Purdie