openembedded-core.git/meta/recipes-devtools/installer, branch dylan

adt_installer_internal: fix spelling error

2013-07-29T08:24:54+00:00

s/envrionement/environment/

(From OE-Core master rev: 5ace1d88efc37b70516eeb1a609ea37a657a5ce0)

Signed-off-by: Beth Flanagan 
Signed-off-by: Saul Wold 
Signed-off-by: Richard Purdie

populate_sdk_base.bbclass: use new perm option for find

2013-07-29T08:24:54+00:00

Old way find -perm +mode is no longer supported in newer
versions of find (Fedora 19). Man page says:
-perm +mode
       This  is  no  longer  supported  (and  has been deprecated since
       2005).  Use -perm /mode instead.

[YOCTO #4853]

(From OE-Core master rev: 21b079e01873e2fb4d8674541e8c5818ba73554e)

Signed-off-by: Stefan Stanacar 
Signed-off-by: Saul Wold 
Signed-off-by: Richard Purdie

populate_sdk_base, adt_installer: abort install if path contains spaces

2013-07-29T08:24:25+00:00

Spaces are not handled properly in some parts of oe-core and it's safer
to abort toolchain installation if path contains spaces. Even though
we fix space handling in the toolchain installation script, there are
various other parts in the toolchain (perl scripts, sysroot path passed to
toolchain binaries, shebang lines) that would need special handling. So,
for now, just bail out if path contains spaces.

The checking for spaces in the path is done after expanding relative
paths to absolute and tilde conversion.

[YOCTO #4488]

(From OE-Core master rev: 8c35ba2d3048ce69f74f72cb2676e4bc162cfb63)

Signed-off-by: Laurentiu Palcu 
Signed-off-by: Richard Purdie

adt_installer_internal:add sudo when permission deny on installation directory

2013-07-08T15:28:29+00:00

When the user doesn't have rights to access the installation directory,
the sdk installation will fail, add sudo to fix this.

[YOCTO #4760]

(From OE-Core master rev: 040010d04672c93f18d60308ecf3c26a26ec5fd3)

Signed-off-by: Hongxu Jia 
Signed-off-by: Saul Wold 
Signed-off-by: Richard Purdie

adt_installer_internal:fix perl lib version mismatch

2013-07-08T15:28:29+00:00

When run "autoreconf" in toolchain, there is an error if the host's perl's
version is not the same as the one in the SDK, the error says that the
executable perl mismatches the perl lib's version.

This is because most of the autotools' scripts use the "#!/usr/bin/perl -w"
which is host perl, but the gnu-configize uses "#! /usr/bin/env perl" which
invokes the perl wrapper in the SDK, and the wrapper will set the PERL5LIB to
the SDK which causes the mismatch. We can make all the perl scripts to use the
host perl or the SDK perl to fix this problem.

[YOCTO #4758]

(From OE-Core master rev: 487d1fa7b79e89518494986461c157bace842613)

Signed-off-by: Hongxu Jia 
Signed-off-by: Saul Wold 
Signed-off-by: Richard Purdie

adt_installer_internal: fix perl modules relocated failed on older distributions

2013-07-08T15:28:29+00:00

The perl module for automake has an embedded path in it, this needs
to be relocated.

Older versions of 'file' do not return the "ASCII" text in the output for
a perl module file. Hence, the regex pattern didn't match perl module and
they were not getting relocated at all on older distributions.

1) On CentOS release 6.4, the version of file is 5.04
$ file /usr/lib/perl5/Config_heavy.pl
$ /usr/lib/perl5/Config_heavy.pl: Perl5 module source text

2) On Ubuntu 13.04, the version of file is 5.11
$ file /usr/lib/perl/5.14/Config_heavy.pl
$ /usr/lib/perl/5.14/Config_heavy.pl: C source, ASCII text, with very long lines

[YOCTO #4550]

(From OE-Core master rev: 7cfab2c895bf4daa7716fb7509e367bf74f016e4)

Signed-off-by: Hongxu Jia 
Signed-off-by: Saul Wold 
Signed-off-by: Richard Purdie

adt-installer: do not dereference symlinks when relocating

2013-05-20T15:06:13+00:00

This was already fixed for meta-toolchain.

[YOCTO #4157]

(From OE-Core master rev: 9e9331a4b859c4205c2a0406ab0224ac575e351b)

Signed-off-by: Laurentiu Palcu 
Signed-off-by: Saul Wold 
Signed-off-by: Richard Purdie

adt-installer: remove patches and .pc directories from the shipped tarball

2013-03-09T06:21:57+00:00

The patches and .pc directories should not be shipped since the patches
were already applied. So, remove these 2 directories.

[YOCTO #3983]

Signed-off-by: Laurentiu Palcu 
Signed-off-by: Richard Purdie

recipes: Fix ALLOW_EMPTY with no package specified

2013-03-04T10:08:03+00:00

There are various usages of ALLOW_EMPTY with no packages specified. This
is not recommended syntax, nor is it likely to be supported in the future.
This patch improves the references in OE-Core, either removing them if they're
pointless (e.g. when PACKAGES="") or specifying which package it applies to.

Signed-off-by: Richard Purdie

Split do_packagedata task from do_package

2013-01-25T12:35:48+00:00

Currently, do_rootfs has a dependency on all the do_package output being present
due to its usage of the pkgdata directories. This means that if you run:

bitbake xxxx-image -c rootfs

you end up having to fetch and unpack all the do_package data which is usually
large and inefficient. It also means rm_work has to leave all the do_package
data lying around so rootfs works.

This patch splits the actual creation of the pkgdata directory off into a separate
task, "packagedata" which happens immediately after do_package. We can then remap
the dependencies so this task is depended upon, not do_package. Sstate can then be
programmed not to require do_package at the appropriate times.

Whilst this patch doesn't do so, it opens the possibility of rm_work wiping
out the do_package output from WORKDIR as long as it also removed the do_package
stamp (both normal and setscene variants) and allowing more space savings
with rm_work which has been regularly requested.

Signed-off-by: Richard Purdie