date:20151109

Re: [yocto] [prelink-cross][PATCH 1/1] rtld.c: LD_PRELOAD bugfix

2015-11-09 Thread Mark Hatle

On 11/7/15 5:24 AM, Maninder Singh wrote:
> Hi,
> Ping

I'd gotten a msg after this to hold off and wait for an update.  Is this the
updated version of the fix?

--Mark

>> This patch do following things:-
>> 1.   Fixes bug of adding preloaded libs in search scope of dependent 
>>  libraries which results in search scope of few symbols becomes 
>>  same for executable and library, so conflict doesn't occur for 
>>  those symbols and hence resulted in less number of conflicts.
>> 2.   Reduce code redundancy.
>> 3.   Buffer Overflow fix.
>>
>> Signed-off-by: Maninder Singh 
>> Signed-off-by: Vaneet Narang 
>> Reviewed-by: Doha Hwang 
>> ---
>> trunk/src/rtld/rtld.c |   27 ---
>> 1 files changed, 16 insertions(+), 11 deletions(-)
>>
>> diff --git a/trunk/src/rtld/rtld.c b/trunk/src/rtld/rtld.c
>> index 50461b6..8af5052 100644
>> --- a/trunk/src/rtld/rtld.c
>> +++ b/trunk/src/rtld/rtld.c
>> @@ -606,7 +606,7 @@ load_dsos (DSO *dso, int host_paths)
>> {
>>   struct dso_list *dso_list, *dso_list_tail, *cur_dso_ent, *new_dso_ent;
>>   struct stat64 st;
>> -  int total_preload = 0;
>> +  int total_preload = 0, temp_total_preload = 0;
>>   char * libname[MAX_PRELOADED_LIBS] = {NULL};
>>
>>   /* Assume it's static unless we find DT_NEEDED entries */
>> @@ -632,19 +632,19 @@ load_dsos (DSO *dso, int host_paths)
>>
>>   if(dso->ehdr.e_type == ET_EXEC && ld_preload) {
>>   char *next_lib =  ld_preload;
>> -  libname[total_preload] = ld_preload;
>> -  total_preload++;
>> -  next_lib=strchr(ld_preload,':');
>> -  while(next_lib!=NULL){
>> -  *next_lib = '\0';
>> -  next_lib++;
>> -  libname[total_preload] = next_lib;
>> -  total_preload++;
>> -  next_lib=strchr(next_lib,':');
>> -  }
>> +  while(*next_lib != '\0' && (total_preload < MAX_PRELOADED_LIBS)){
>> +libname[total_preload++] = next_lib;
>> +next_lib=strchrnul(next_lib,':');
>> +if(*next_lib == '\0')
>> +  break;
>> +*next_lib = '\0';
>> +next_lib++;
>> + }
>> +temp_total_preload = total_preload;
>>   }
>>   else {
>>   total_preload = 0;
>> +  temp_total_preload = 0;
>>   }
>>   while (cur_dso_ent != NULL)
>> {
>> @@ -666,6 +666,11 @@ load_dsos (DSO *dso, int host_paths)
>>  {
>>int ndx, maxndx;
>>maxndx = data->d_size / cur_dso->shdr[cur_dso->dynamic].sh_entsize;
>> +  if(!(cur_dso->ehdr.e_type == ET_EXEC))
>> +total_preload = 0;
>> +  else
>> +total_preload = temp_total_preload;
>> +
>>for (ndx = 0; ndx < maxndx + total_preload; ++ndx)
>>  {
>>
>> -- 
>> 1.7.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] binutils failing in FIDO branch

2015-11-09 Thread Martin Townsend

Hi,

binutils is failing to compile.  I'm using tip of fido branch.  Error
message is:

|
/home/martint/yocto/build/am43-devboard-aquila/bia-tmp-glibc/work/cortexa9hf-vfp-neon-oe-linux-gnueabi/binutils/2.24-r0/binutils-2.24/libiberty/fibheap.c:
In function 'fibheap_replace_key_data':
|
/home/martint/yocto/build/am43-devboard-aquila/bia-tmp-glibc/work/cortexa9hf-vfp-neon-oe-linux-gnueabi/binutils/2.24-r0/binutils-2.24/libiberty/fibheap.c:38:24:
error: 'LONG_MIN' undeclared (first use in this function)
|  #define FIBHEAPKEY_MIN LONG_MIN

I've tracked it down to the fact that libiberty is the only component that
doesn't define HAVE_LIMITS in config.h, so I assume this part of the
configure is failing for some reason.

Anyone else seen this, or have an idea on how to fix this?

Cheers,
Martin.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 04/10][AUH] buildhistory.py: Don't modify BB_ENV_EXTRAWHITE before init.

2015-11-09 Thread Aníbal Limón

Move code for add BUILDHISTORY_DIR to __init__ method because
it fails when import in early step.

Signed-off-by: Aníbal Limón 
---
 buildhistory.py | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/buildhistory.py b/buildhistory.py
index 1732f23..6eca6e1 100644
--- a/buildhistory.py
+++ b/buildhistory.py
@@ -30,11 +30,10 @@ from errors import *
 from bitbake import *
 from git import Git
 
-os.environ['BB_ENV_EXTRAWHITE'] = os.environ['BB_ENV_EXTRAWHITE'] + \
-" BUILDHISTORY_DIR"
-
 class BuildHistory(object):
 def __init__(self, bb, pn, workdir):
+os.environ['BB_ENV_EXTRAWHITE'] = os.environ['BB_ENV_EXTRAWHITE'] + \
+" BUILDHISTORY_DIR"
 self.bb = bb
 self.pn = pn
 self.workdir = workdir
-- 
2.1.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 01/10][AUH] upgradehelper.py: Add step for build gcc-runtime at init.

2015-11-09 Thread Aníbal Limón

When try to upgrade a recipe the first recipe in the list
takes too much time because gcc-runtime build is needed.

So add previous step to build gcc-runtime for every machine.

Signed-off-by: Aníbal Limón 
---
 upgradehelper.py | 5 +
 1 file changed, 5 insertions(+)

diff --git a/upgradehelper.py b/upgradehelper.py
index b5a8abd..bb19b65 100755
--- a/upgradehelper.py
+++ b/upgradehelper.py
@@ -467,6 +467,11 @@ class Updater(object):
 W("No recipes attempted, not sending status mail!")
 
 def run(self, package_list=None):
+I(" Building gcc runtimes ...")
+for machine in self.machines:
+I("  building gcc runtime for %s" % machine)
+self.bb.complete("gcc-runtime", machine)
+
 pkgs_to_upgrade = self._get_packages_to_upgrade(package_list)
 
 total_pkgs = len(pkgs_to_upgrade)
-- 
2.1.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 00/10][AUH] Improvements and small fixes.

2015-11-09 Thread Aníbal Limón

Aníbal Limón (10):
  upgradehelper.py: Add step for build gcc-runtime at init.
  upgradehelper.py: Fix bug when buildhistory isn't enabled
  recipe.py: Improvements and refactor of fetch method.
  buildhistory.py: Don't modify BB_ENV_EXTRAWHITE before init.
  upgradehelper.py: Add sanity test for ensure that git is configured.
  buildhistory.py: Add missing warning import. git.py: Fix
last_commit method.
  upgradehelper.py: Improve work directory structure
  upgradehelper.py: Add support for do recipe upgrades based on builddep
  upgradehelper.py: Add support for preserve statistics into work
directory.
  requirements.txt: Add file for now only with GitPython

 buildhistory.py  |   8 +--
 git.py   |   2 +-
 recipe.py|  58 +++
 requirements.txt |   1 +
 upgradehelper.py | 170 +--
 5 files changed, 168 insertions(+), 71 deletions(-)
 create mode 100644 requirements.txt

-- 
2.1.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 10/10][AUH] requirements.txt: Add file for now only with GitPython

2015-11-09 Thread Aníbal Limón

Signed-off-by: Aníbal Limón 
---
 requirements.txt | 1 +
 1 file changed, 1 insertion(+)
 create mode 100644 requirements.txt

diff --git a/requirements.txt b/requirements.txt
new file mode 100644
index 000..64b1ada
--- /dev/null
+++ b/requirements.txt
@@ -0,0 +1 @@
+GitPython
-- 
2.1.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 08/10][AUH] upgradehelper.py: Add support for do recipe upgrades based on builddep

2015-11-09 Thread Aníbal Limón

Signed-off-by: Aníbal Limón 
---
 upgradehelper.py | 114 +--
 1 file changed, 86 insertions(+), 28 deletions(-)

diff --git a/upgradehelper.py b/upgradehelper.py
index aeb9cf1..a08833e 100755
--- a/upgradehelper.py
+++ b/upgradehelper.py
@@ -91,7 +91,6 @@ def parse_cmdline():
 def get_build_dir():
 return os.getenv('BUILDDIR')
 
-
 def parse_config_file(config_file):
 settings = dict()
 maintainer_override = dict()
@@ -435,26 +434,6 @@ class Updater(object):
 I(" %s: %s" % (self.pn, e.stdout))
 raise e
 
-def _order_list(self, package_list):
-try:
-self.bb.dependency_graph(' '.join(p[0] for p in package_list))
-except Error as e:
-multiple_providers = False
-for l in e.stdout.split('\n'):
-if l.find("ERROR: Multiple .bb files are due to be built which 
each provide") == 0:
-multiple_providers = True
-
-if not multiple_providers:
-raise e
-
-dep_file = os.path.join(get_build_dir(), "pn-buildlist")
-ordered_list = []
-with open(dep_file) as deps:
-for d in deps:
-ordered_list.extend(p for p in package_list if p[0] == 
d.strip())
-
-return ordered_list
-
 def send_status_mail(self):
 if "status_recipients" not in settings:
 E("Could not send status email, no recipients set!")
@@ -471,16 +450,100 @@ class Updater(object):
 else:
 W("No recipes attempted, not sending status mail!")
 
+
+def _order_pkgs_to_upgrade(self, pkgs_to_upgrade):
+def _get_pn_dep_dic(pn_list, dependency_file): 
+import re
+
+pn_dep_dic = {}
+
+with open(dependency_file) as dep:
+data = dep.read()
+dep.close()
+
+for line in data.split('\n'):
+m = re.search('^"(.*)" -> "(.*)"$', line)
+if not m:
+continue
+
+pn = m.group(1)
+pn_dep = m.group(2)
+if pn == pn_dep:
+continue
+
+if pn in pn_list:
+if pn_dep in pn_list:
+if pn in pn_dep_dic.keys():
+pn_dep_dic[pn].append(pn_dep)
+else:
+pn_dep_dic[pn] = [pn_dep]
+elif not pn in pn_dep_dic.keys():
+pn_dep_dic[pn] = []
+
+return pn_dep_dic
+
+def _dep_resolve(graph, node, resolved, seen):
+seen.append(node)
+
+for edge in graph[node]:
+if edge not in resolved:
+if edge in seen:
+raise RuntimeError("Packages %s and %s have " \
+"a circular dependency." \
+% (node, edge))
+_dep_resolve(graph, edge, resolved, seen)
+
+resolved.append(node)
+
+
+pn_list = []
+for pn, new_ver, maintainer in pkgs_to_upgrade:
+pn_list.append(pn)
+
+try:
+   self.bb.dependency_graph(' '.join(pn_list))
+except Error as e:
+multiple_providers = False
+for l in e.stdout.split('\n'):
+if l.find("ERROR: Multiple .bb files are due to be built which 
each provide") == 0:
+multiple_providers = True
+if not multiple_providers:
+raise e
+
+dependency_file = os.path.join(get_build_dir(), "pn-depends.dot")
+
+pkgs_to_upgrade_ordered = []
+pn_list_ordered = []
+
+pn_dep_dic = _get_pn_dep_dic(pn_list, dependency_file)
+if pn_dep_dic:
+root = "__root_node__"
+pn_dep_dic[root] = pn_dep_dic.keys()
+_dep_resolve(pn_dep_dic, root, pn_list_ordered, [])
+pn_list_ordered.remove(root)
+
+for pn_ordered in pn_list_ordered:
+for pn, new_ver, maintainer in pkgs_to_upgrade:
+if pn == pn_ordered: 
+pkgs_to_upgrade_ordered.append([pn, new_ver, maintainer])
+
+return pkgs_to_upgrade_ordered
+
 def run(self, package_list=None):
 I(" Building gcc runtimes ...")
 for machine in self.machines:
 I("  building gcc runtime for %s" % machine)
 self.bb.complete("gcc-runtime", machine)
 
-pkgs_to_upgrade = self._get_packages_to_upgrade(package_list)
-
+pkgs_to_upgrade = self._order_pkgs_to_upgrade(
+self._get_packages_to_upgrade(package_list))
 total_pkgs = len(pkgs_to_upgrade)
 
+I(" ### The list of recipes to be upgraded #")
+for p, v, m in pkgs_to_upgrade:
+

[yocto] [PATCH 07/10][AUH] upgradehelper.py: Improve work directory structure

2015-11-09 Thread Aníbal Limón

Add work directory with datetime suffix to preserve recipe upgrades.

Create tree folders all, succeed and failed,
all - Contains all the recipes work
succeed - Contains a symlinks to the recipes that successful
  upgrade
failed  - Contains a symlinks to the recipes that fail
  upgrade

This helps to navigate over patches that have a successful upgrade.

Signed-off-by: Aníbal Limón 
---
 upgradehelper.py | 24 +---
 1 file changed, 17 insertions(+), 7 deletions(-)

diff --git a/upgradehelper.py b/upgradehelper.py
index ae40fb1..aeb9cf1 100755
--- a/upgradehelper.py
+++ b/upgradehelper.py
@@ -132,9 +132,16 @@ class Updater(object):
 if not os.path.exists(self.uh_dir):
 os.mkdir(self.uh_dir)
 
-self.uh_work_dir = os.path.join(self.uh_dir, "work")
-if not os.path.exists(self.uh_work_dir):
-os.mkdir(self.uh_work_dir)
+self.uh_work_dir = os.path.join(self.uh_dir, "work-%s" % \
+datetime.now().strftime("%Y%m%d%H%M"))
+os.mkdir(self.uh_work_dir)
+
+self.uh_recipes_all_dir = os.path.join(self.uh_work_dir, "all")
+os.mkdir(self.uh_recipes_all_dir)
+self.uh_recipes_succeed_dir = os.path.join(self.uh_work_dir, "succeed")
+os.mkdir(self.uh_recipes_succeed_dir)
+self.uh_recipes_failed_dir = os.path.join(self.uh_work_dir, "failed")
+os.mkdir(self.uh_recipes_failed_dir)
 
 self.bb = Bitbake(get_build_dir())
 self.git = None
@@ -223,10 +230,7 @@ class Updater(object):
 self.env = self._get_env(self.pn)
 
 def _create_workdir(self):
-self.workdir = os.path.join(self.uh_work_dir, self.pn)
-
-if os.path.exists(self.workdir):
-shutil.rmtree(self.workdir)
+self.workdir = os.path.join(self.uh_recipes_all_dir, self.pn)
 os.mkdir(self.workdir)
 
 def _detect_repo(self):
@@ -490,6 +494,9 @@ class Updater(object):
 I(" %s: %s" % (self.pn, msg))
 step()
 
+os.symlink(self.workdir, os.path.join( \
+self.uh_recipes_succeed_dir, self.pn))
+
 I(" %s: Upgrade SUCCESSFUL! Please test!" % self.pn)
 except Exception as e:
 if isinstance(e, UpgradeNotNeededError):
@@ -511,6 +518,9 @@ class Updater(object):
 
 error = e
 
+os.symlink(self.workdir, os.path.join( \
+self.uh_recipes_failed_dir, self.pn))
+
 self._commit_changes()
 
 self.pkg_upgrade_handler(error)
-- 
2.1.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 02/10][AUH] upgradehelper.py: Fix bug when buildhistory isn't enabled

2015-11-09 Thread Aníbal Limón

Don't use buildhistory object if buildhistory_enabled is False
because cause undefined variable error.

Signed-off-by: Aníbal Limón 
---
 upgradehelper.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/upgradehelper.py b/upgradehelper.py
index bb19b65..9b321f6 100755
--- a/upgradehelper.py
+++ b/upgradehelper.py
@@ -310,7 +310,7 @@ class Updater(object):
 for machine in self.machines:
 I(" %s: compiling for %s ..." % (self.pn, machine))
 self.recipe.compile(machine)
-if self.buildhistory is not None:
+if self.buildhistory_enabled == True:
 self.buildhistory.add()
 
 def _buildhistory_diff(self):
-- 
2.1.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 06/10][AUH] buildhistory.py: Add missing warning import. git.py: Fix last_commit method.

2015-11-09 Thread Aníbal Limón

Signed-off-by: Aníbal Limón 
---
 buildhistory.py | 3 ++-
 git.py  | 2 +-
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/buildhistory.py b/buildhistory.py
index 6eca6e1..2e442d2 100644
--- a/buildhistory.py
+++ b/buildhistory.py
@@ -20,8 +20,9 @@
 
 import os
 import logging as log
-from logging import info as I
 from logging import debug as D
+from logging import info as I
+from logging import warning as W
 from logging import error as E
 from logging import critical as C
 import sys
diff --git a/git.py b/git.py
index 3eebac3..9661364 100644
--- a/git.py
+++ b/git.py
@@ -88,7 +88,7 @@ class Git(object):
 return self._cmd("clean -fd")
 
 def last_commit(self, branch_name):
-return self._cmd("log --pretty=format:\"%H\" -1" + branch_name)
+return self._cmd("log --pretty=format:\"%H\" -1 " + branch_name)
 
 def ls_remote(self, repo_url=None, options=None, refs=None):
 cmd = "ls-remote"
-- 
2.1.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 03/10][AUH] recipe.py: Improvements and refactor of fetch method.

2015-11-09 Thread Aníbal Limón

Make more clear fetch method changing recursive manner to
loop and split logic into try fetch and suffix change.

Now when fails only retry changing recipe suffix when recipe
isn't git based because does not make sense suffixes in SCM's.

Signed-off-by: Aníbal Limón 
---
 recipe.py | 58 +-
 1 file changed, 33 insertions(+), 25 deletions(-)

diff --git a/recipe.py b/recipe.py
index 6fd8f24..0e8799f 100644
--- a/recipe.py
+++ b/recipe.py
@@ -55,7 +55,6 @@ class Recipe(object):
 "tar.gz", "tgz", "zip", "tar.bz2", "tar.xz", "tar.lz4", "bz2",
 "lz4", "orig.tar.gz", "src.tar.gz", "src.rpm", "src.tgz",
 "svnr\d+.tar.bz2", "stable.tar.gz", "src.rpm"]
-self.suffix_index = 0
 self.old_env = None
 
 self.commit_msg = self.env['PN'] + ": upgrade to " + self.new_ver + 
"\n\n"
@@ -540,33 +539,42 @@ class Recipe(object):
 self.bb.unpack(self.env['PN'])
 
 def fetch(self):
-try:
-self.bb.fetch(self.env['PN'])
-except Error as e:
-machine, failed_recipes = self._get_failed_recipes(e.stdout)
-if not self.env['PN'] in failed_recipes:
-raise Error("unknown error occured during fetch")
-
-fetch_log = failed_recipes[self.env['PN']][1]
-if self.suffix_index < len(self.suffixes) and 
self._is_uri_failure(fetch_log):
-I(" Trying new SRC_URI suffix: %s ..." % 
self.suffixes[self.suffix_index])
-self._change_source_suffix(self.suffixes[self.suffix_index])
-self.suffix_index += 1
-self.fetch()
-
-if not self._is_uri_failure(fetch_log):
-if not self.checksums_changed:
+from gitrecipe import GitRecipe
+
+def _try_fetch():
+try:
+self.bb.fetch(self.env['PN'])
+return
+except Error as e:
+machine, failed_recipes = self._get_failed_recipes(e.stdout)
+if not self.env['PN'] in failed_recipes:
+raise Error("Unknown error occured during fetch",
+stdout = e.stdout, stderr = e.stderr)
+
+fetch_log = failed_recipes[self.env['PN']][1]
+
+if not self._is_uri_failure(fetch_log) and not \
+self.checksums_changed:
 self._change_recipe_checksums(fetch_log)
-return
-else:
-raise FetchError()
+self.checksums_changed = True
+return True
 
-if self.recipes_renamed and not self.checksums_changed:
-raise Error("fetch succeeded without changing checksums")
+return False
+
+succeed = _try_fetch()
+if succeed is False and not isinstance(self, GitRecipe):
+for sfx in self.suffixes:
+I(" Trying new SRC_URI suffix: %s ..." % sfx)
+self._change_source_suffix(sfx)
+
+succeed = _try_fetch()
+if succeed is True:
+break
 
-elif self.suffix_index == len(self.suffixes):
-# Every suffix tried without success
-raise FetchError()
+if succeed is False:
+raise Error("Can't built a valid SRC_URI")
+elif self.recipes_renamed and not self.checksums_changed:
+raise Error("Fetch succeeded without changing checksums")
 
 def cleanall(self):
 self.bb.cleanall(self.env['PN'])
-- 
2.1.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] binutils failing in FIDO branch

2015-11-09 Thread Paul Eggleton

What I think Martin hasn't mentioned here (but did on IRC) is this is binutils 
for the target machine, not host/cross. I would assume it's somehow related to 
the target being built for. Martin, can you provide any details on that which 
might help others to reproduce the issue?

Cheers,
Paul

On Monday 09 November 2015 12:15:40 Khem Raj wrote:
> No it should be well supported. So now I wonder why no one else sees it
> 
> > On Nov 9, 2015, at 11:22 AM, Martin Townsend 
> > wrote:
> > 
> > Hi,
> > 
> > I'm running Ubuntu 14.04 LTS.
> > 
> > Could this be the problem?
> > 
> > Cheers,
> > Martin.
> > 
> > 
> > On Mon, Nov 9, 2015 at 5:56 PM, Khem Raj  > > wrote:> 
> > On Mon, Nov 9, 2015 at 4:36 AM, Martin Townsend > wrote:
> > > Hi,
> > > 
> > > binutils is failing to compile.  I'm using tip of fido branch.  Error
> > > message is:
> > > 
> > > 
> > > /home/martint/yocto/build/am43-devboard-aquila/bia-tmp-glibc/work/cortex
> > > a9hf-vfp-neon-oe-linux-gnueabi/binutils/2.24-r0/binutils-2.24/libiberty/
> > > fibheap.c: In function 'fibheap_replace_key_data':
> > > 
> > > /home/martint/yocto/build/am43-devboard-aquila/bia-tmp-glibc/work/cortex
> > > a9hf-vfp-neon-oe-linux-gnueabi/binutils/2.24-r0/binutils-2.24/libiberty/
> > > fibheap.c:38:24: error: 'LONG_MIN' undeclared (first use in this
> > > function)
> > > 
> > > |  #define FIBHEAPKEY_MIN LONG_MIN
> > > 
> > > I've tracked it down to the fact that libiberty is the only component
> > > that
> > > doesn't define HAVE_LIMITS in config.h, so I assume this part of the
> > > configure is failing for some reason.
> > > 
> > > Anyone else seen this, or have an idea on how to fix this?
> > 
> > whats your host distro ?
> > 
> > > Cheers,
> > > Martin.
> > > 
> > > 
> > > 
> > > 
> > > 
> > > --
> > > ___
> > > yocto mailing list
> > > yocto@yoctoproject.org 
> > > https://lists.yoctoproject.org/listinfo/yocto
> > > 

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 09/10][AUH] upgradehelper.py: Add support for preserve statistics into work directory.

2015-11-09 Thread Aníbal Limón

Signed-off-by: Aníbal Limón 
---
 upgradehelper.py | 11 ++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/upgradehelper.py b/upgradehelper.py
index a08833e..4f33d2f 100755
--- a/upgradehelper.py
+++ b/upgradehelper.py
@@ -591,7 +591,16 @@ class Updater(object):
 self.statistics.update(self.pn, self.new_ver, self.maintainer, 
error)
 
 if (attempted_pkgs > 1):
-I("%s" % self.statistics.pkg_stats())
+statistics_summary = self.statistics.pkg_stats() + \
+self.statistics.maintainer_stats()
+
+statistics_file = os.path.join(self.uh_work_dir,
+"statistics_summary")
+with open(statistics_file, "w+") as f:
+f.write(statistics_summary)
+
+I("%s" % statistics_summary)
+
 if self.send_email:
 self.send_status_mail()
 
-- 
2.1.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [yocto-announce] [ANNOUNCEMENT] Yocto Project 1.7.3 (fido 12.0.3) Released

2015-11-09 Thread Robert Yang



I think that the codename is not fido for 1.7 ?

// Robert

On 11/10/2015 03:45 AM, Flanagan, Elizabeth wrote:

Hello,

The latest release of the Yocto Project 1.7.3 (dizzy-12.0.3) is now available
for download at:

http://downloads.yoctoproject.org/releases/yocto/yocto-1.7.3/poky-dizzy-12.0.3.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-1.7.3/poky-dizzy-12.0.3.tar.bz2

A gpg signed version of these release notes is available at:

http://downloads.yoctoproject.org/releases/yocto/yocto-1.7.3/RELEASENOTES

Full pass test report is available at:

https://wiki.yoctoproject.org/wiki/Ww41_-_2015-10-08_-_Full_Pass_1.7.3.rc1

Thanks go out to everyone for all their hard work during this release!

Sincerely,

Elizabeth Flanagan
Yocto Project
Build and Release

-
yocto-1.7.3 Errata

Release Name:  eclipse-poky-kepler-12.0.3
Branch: kepler/dizzy
Tag: luna/dizzy-12.0.3
Hash:  cf60ac293629fc8ecd6c4eb3709a6f334b499d0c
md5: e7eca889b7a6efffa815581fee50b657  eclipse-poky-kepler-dizzy-12.0.3.tar.bz2
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-1.7.3/eclipse-poky-kepler-dizzy-12.0.3.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-1.7.3/eclipse-poky-kepler-dizzy-12.0.3.tar.bz2

Release Name:  eclipse-poky-luna-12.0.3
Branch: luna/dizzy
Tag: luna/dizzy-12.0.3
Hash: 45aa5c77523bdf051d548fff4305382942db2ebb
md5: ebcf90e66bae33519387f299ca0c908a  eclipse-poky-luna-dizzy-12.0.3.tar.bz2
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-1.7.3/eclipse-poky-luna-dizzy-12.0.3.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-1.7.3/eclipse-poky-luna-dizzy-12.0.3.tar.bz2

Release Name:  meta-qt3-12.0.3
Branch: dizzy
Tag: dizzy-12.0.3
Hash:  3016129d90b7ac8517a5227d819f10ad417b5b45
md5: 77f5c7cb8b3523862086dd9e6271b79d  meta-qt3-dizzy-12.0.3.tar.bz2
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-1.7.3/meta-qt3-dizzy-12.0.3.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-1.7.3/meta-qt3-dizzy-12.0.3.tar.bz2

Release Name:  poky-12.0.3
Branch: dizzy
Tag: dizzy-12.0.3
Hash:  b38454c2e3a7a58f5397bb16d59e2b0aa71c4a94
md5: 7d3196798cb5e78e6b7f89e03edcf9e7  poky-dizzy-12.0.3.tar.bz2
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-1.7.3/poky-dizzy-12.0.3.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-1.7.3/poky-dizzy-12.0.3.tar.bz2

---
Security Fixes
---
bind: CVE-2015-1349 CVE-2015-4620 CVE-2015-5722
icu: CVE-2014-8146-CVE-2014-8147
gnutls: CVE-2015-3308
qemu-slirp: CVE-2014-3640
qemu-vnc: CVE-2014-7815
qemu: CVE-2014-7840
bind9.9.5: CVE-2015-5477
libxml2: Security Advisory - libxml2 - CVE-2015-1819
rpm: Fix CVE-2013-6435
rpm: Fix CVE-2014-8118
dbus: CVE-2015-0245: prevent forged ActivationFailure
unzip: fix four CVE defects
unzip: Security Advisory -CVE-2014-9636 and CVE-2015-1315
gpgme: fix CVE-2014-3564
glibc: CVE-2015-1781: resolv/nss_dns/dns-host.c buffer overflow
qemu: fix CVE-2015-3456
ppp: Security Advisory - CVE-2015-3310
libsndfile: Security Advisory - libsndfile - CVE-2014-9496

---
Fixes
---
build-appliance-image: Update to dizzy head revision
poky.conf: Bump version for 1.7.3 dizzy release
sstate: run recipe-provided hooks outside of ${B}
oprofileui: Use inherit gettext
rootfs.py: show intercept script output in log.do_rootfs
postinst_intercept: allow to pass variables with spaces
rootfs.py: Allow to override postinst-intercepts location
base.bbclass: Note when including pn with INCOMPATIBLE_LICENSES
autotools.bbclass: mkdir ${B} -> mkdir -p ${B}
perf: mkdir ${B} -> mkdir -p ${B}
bitbake: prserv/serv: Improve exit handling
bitbake: bitbake: cooker: properly fix bitbake.lock handling
bitbake: runqueue: Add message to explain the problem if diffsigs
multiple tasks don't exist
oeqa/selftest: fix test_incremental_image_generation for changes in log output
qemurunner: Improves checking for server and target IPs on qemus parameters
oeqa/utils/qemurunner: fix logging
oeqa/QemuRunner: don't use bb for logging
license.bbclass: fix unexpected operator for LICENSE values with space
license_class: fix license.manifest shows LICENSE field differently to recipe
connman-conf: fix SRC_URI_append
sstate: Use SSTATE_DIR for FILESPATH
gnome: move introspection options to gnomebase
tzdata, tzcode-native: drop older versions 2014h, 2015b
grub-efi: Add backslash lost from previous commit
grub-efi: Use the backport patch from grub
license_class: Fix choose_lic_set into incompatible license
dpkg: Fix tarfix.patch
dpkg: Fix for Fedora22 and new versions of tar
oeqa/bbtests: Fix to ensure DL_DIR is set
oeqa/bbtests: Fix race over DL_DIR and SSTATE_DIR
subversion: Fix subversion-native on Fedora22
subversion: Add -P to CPPFLAGS
cross-localedef-native: Use older C standards for older code
grub: Backport const qualifier fix for gcc-5
binutils: fix native builds when host has gcc5
ncurses: fix native builds when host has gcc5
unzip: drop 12-cve-2014-9636-test-compr-eb.patch
linux-firmware:

Re: [yocto] [yocto-announce] [ANNOUNCEMENT] Yocto Project 1.7.3 (fido 12.0.3) Released

2015-11-09 Thread akuster



On 11/09/2015 05:42 PM, Robert Yang wrote:
> 
> I think that the codename is not fido for 1.7 ?

its Dizzy.

- armin
> 
> // Robert
> 
> On 11/10/2015 03:45 AM, Flanagan, Elizabeth wrote:
>> Hello,
>>
>> The latest release of the Yocto Project 1.7.3 (dizzy-12.0.3) is now
>> available
>> for download at:
>>
>> http://downloads.yoctoproject.org/releases/yocto/yocto-1.7.3/poky-dizzy-12.0.3.tar.bz2
>>
>> http://mirrors.kernel.org/yocto/yocto/yocto-1.7.3/poky-dizzy-12.0.3.tar.bz2
>>
>>
>> A gpg signed version of these release notes is available at:
>>
>> http://downloads.yoctoproject.org/releases/yocto/yocto-1.7.3/RELEASENOTES
>>
>> Full pass test report is available at:
>>
>> https://wiki.yoctoproject.org/wiki/Ww41_-_2015-10-08_-_Full_Pass_1.7.3.rc1
>>
>>
>> Thanks go out to everyone for all their hard work during this release!
>>
>> Sincerely,
>>
>> Elizabeth Flanagan
>> Yocto Project
>> Build and Release
>>
>> -
>> yocto-1.7.3 Errata
>>
>> Release Name:  eclipse-poky-kepler-12.0.3
>> Branch: kepler/dizzy
>> Tag: luna/dizzy-12.0.3
>> Hash:  cf60ac293629fc8ecd6c4eb3709a6f334b499d0c
>> md5: e7eca889b7a6efffa815581fee50b657 
>> eclipse-poky-kepler-dizzy-12.0.3.tar.bz2
>> Download Locations:
>> http://downloads.yoctoproject.org/releases/yocto/yocto-1.7.3/eclipse-poky-kepler-dizzy-12.0.3.tar.bz2
>>
>> http://mirrors.kernel.org/yocto/yocto/yocto-1.7.3/eclipse-poky-kepler-dizzy-12.0.3.tar.bz2
>>
>>
>> Release Name:  eclipse-poky-luna-12.0.3
>> Branch: luna/dizzy
>> Tag: luna/dizzy-12.0.3
>> Hash: 45aa5c77523bdf051d548fff4305382942db2ebb
>> md5: ebcf90e66bae33519387f299ca0c908a 
>> eclipse-poky-luna-dizzy-12.0.3.tar.bz2
>> Download Locations:
>> http://downloads.yoctoproject.org/releases/yocto/yocto-1.7.3/eclipse-poky-luna-dizzy-12.0.3.tar.bz2
>>
>> http://mirrors.kernel.org/yocto/yocto/yocto-1.7.3/eclipse-poky-luna-dizzy-12.0.3.tar.bz2
>>
>>
>> Release Name:  meta-qt3-12.0.3
>> Branch: dizzy
>> Tag: dizzy-12.0.3
>> Hash:  3016129d90b7ac8517a5227d819f10ad417b5b45
>> md5: 77f5c7cb8b3523862086dd9e6271b79d  meta-qt3-dizzy-12.0.3.tar.bz2
>> Download Locations:
>> http://downloads.yoctoproject.org/releases/yocto/yocto-1.7.3/meta-qt3-dizzy-12.0.3.tar.bz2
>>
>> http://mirrors.kernel.org/yocto/yocto/yocto-1.7.3/meta-qt3-dizzy-12.0.3.tar.bz2
>>
>>
>> Release Name:  poky-12.0.3
>> Branch: dizzy
>> Tag: dizzy-12.0.3
>> Hash:  b38454c2e3a7a58f5397bb16d59e2b0aa71c4a94
>> md5: 7d3196798cb5e78e6b7f89e03edcf9e7  poky-dizzy-12.0.3.tar.bz2
>> Download Locations:
>> http://downloads.yoctoproject.org/releases/yocto/yocto-1.7.3/poky-dizzy-12.0.3.tar.bz2
>>
>> http://mirrors.kernel.org/yocto/yocto/yocto-1.7.3/poky-dizzy-12.0.3.tar.bz2
>>
>>
>> ---
>> Security Fixes
>> ---
>> bind: CVE-2015-1349 CVE-2015-4620 CVE-2015-5722
>> icu: CVE-2014-8146-CVE-2014-8147
>> gnutls: CVE-2015-3308
>> qemu-slirp: CVE-2014-3640
>> qemu-vnc: CVE-2014-7815
>> qemu: CVE-2014-7840
>> bind9.9.5: CVE-2015-5477
>> libxml2: Security Advisory - libxml2 - CVE-2015-1819
>> rpm: Fix CVE-2013-6435
>> rpm: Fix CVE-2014-8118
>> dbus: CVE-2015-0245: prevent forged ActivationFailure
>> unzip: fix four CVE defects
>> unzip: Security Advisory -CVE-2014-9636 and CVE-2015-1315
>> gpgme: fix CVE-2014-3564
>> glibc: CVE-2015-1781: resolv/nss_dns/dns-host.c buffer overflow
>> qemu: fix CVE-2015-3456
>> ppp: Security Advisory - CVE-2015-3310
>> libsndfile: Security Advisory - libsndfile - CVE-2014-9496
>>
>> ---
>> Fixes
>> ---
>> build-appliance-image: Update to dizzy head revision
>> poky.conf: Bump version for 1.7.3 dizzy release
>> sstate: run recipe-provided hooks outside of ${B}
>> oprofileui: Use inherit gettext
>> rootfs.py: show intercept script output in log.do_rootfs
>> postinst_intercept: allow to pass variables with spaces
>> rootfs.py: Allow to override postinst-intercepts location
>> base.bbclass: Note when including pn with INCOMPATIBLE_LICENSES
>> autotools.bbclass: mkdir ${B} -> mkdir -p ${B}
>> perf: mkdir ${B} -> mkdir -p ${B}
>> bitbake: prserv/serv: Improve exit handling
>> bitbake: bitbake: cooker: properly fix bitbake.lock handling
>> bitbake: runqueue: Add message to explain the problem if diffsigs
>> multiple tasks don't exist
>> oeqa/selftest: fix test_incremental_image_generation for changes in
>> log output
>> qemurunner: Improves checking for server and target IPs on qemus
>> parameters
>> oeqa/utils/qemurunner: fix logging
>> oeqa/QemuRunner: don't use bb for logging
>> license.bbclass: fix unexpected operator for LICENSE values with space
>> license_class: fix license.manifest shows LICENSE field differently to
>> recipe
>> connman-conf: fix SRC_URI_append
>> sstate: Use SSTATE_DIR for FILESPATH
>> gnome: move introspection options to gnomebase
>> tzdata, tzcode-native: drop older versions 2014h, 2015b
>> grub-efi: Add backslash lost from previous commit
>> grub-efi: Use the backport patch from grub
>> license_class: Fix choose_lic_set into incompatible license
>> dpkg: Fix tarfix.patch
>> dpkg: Fix for

Re: [yocto] Python pip

2015-11-09 Thread Alejandro Hernandez




On 05/11/15 08:25, Gary Thomas wrote:

On 2015-11-05 07:14, Paul Eggleton wrote:

Hi Gary,

On Thursday 05 November 2015 05:39:21 Gary Thomas wrote:

Just curious, does anyone know why OE-core has python3-pip
but python-pip is relegated to meta-oe?


I think it has to do with pip being supplied as part of the standard 
python 3

distribution from 3.4 onwards. I think for simplicity's sake it might be
argued that python-pip could be in the same place though.
Yes, in fact, python3-pip was included on oe-core after the upgrade to 
python3.4 since it's now a requirement, I agree, we probably should 
include python-pip on oe-core too


Thanks, I'll consider sending a patch set for that.

Sadly, at this point, both packages can't be installed at the
same time as they both call the result "/usr/bin/pip".  Maybe
in keeping with the python/python3 naming, the python3 version
should be installed as pip3?


python3-pip recipe had to be created to avoid an issue with the default 
pip installation by python3.4, its now handled by distutils3, if its 
only a matter of changing the binary name afterwards from pip to pip3 I 
see no problem doing this, I am hoping this solves it, but just 
mentioning that we already had some issues with this, because of the 
"defaults" python3 expects


--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Python pip

2015-11-09 Thread Gary Thomas


On 2015-11-09 09:11, Alejandro Hernandez wrote:



On 05/11/15 08:25, Gary Thomas wrote:

On 2015-11-05 07:14, Paul Eggleton wrote:

Hi Gary,

On Thursday 05 November 2015 05:39:21 Gary Thomas wrote:

Just curious, does anyone know why OE-core has python3-pip
but python-pip is relegated to meta-oe?


I think it has to do with pip being supplied as part of the standard python 3
distribution from 3.4 onwards. I think for simplicity's sake it might be
argued that python-pip could be in the same place though.

Yes, in fact, python3-pip was included on oe-core after the upgrade to 
python3.4 since it's now a requirement, I agree, we probably should include 
python-pip on oe-core too


Thanks, I'll consider sending a patch set for that.

Sadly, at this point, both packages can't be installed at the
same time as they both call the result "/usr/bin/pip".  Maybe
in keeping with the python/python3 naming, the python3 version
should be installed as pip3?


python3-pip recipe had to be created to avoid an issue with the default pip 
installation by python3.4, its now handled by distutils3, if its only a matter 
of changing the binary
name afterwards from pip to pip3 I see no problem doing this, I am hoping this solves it, 
but just mentioning that we already had some issues with this, because of the 
"defaults"
python3 expects


In that case, we could rename the Python2 pip as pip2.  I think
they really need different names as they will be installing
packages into very different locations Python2 vs Python3.

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] binutils failing in FIDO branch

2015-11-09 Thread Khem Raj

On Mon, Nov 9, 2015 at 4:36 AM, Martin Townsend  wrote:
> Hi,
>
> binutils is failing to compile.  I'm using tip of fido branch.  Error
> message is:
>
> |
> /home/martint/yocto/build/am43-devboard-aquila/bia-tmp-glibc/work/cortexa9hf-vfp-neon-oe-linux-gnueabi/binutils/2.24-r0/binutils-2.24/libiberty/fibheap.c:
> In function 'fibheap_replace_key_data':
> |
> /home/martint/yocto/build/am43-devboard-aquila/bia-tmp-glibc/work/cortexa9hf-vfp-neon-oe-linux-gnueabi/binutils/2.24-r0/binutils-2.24/libiberty/fibheap.c:38:24:
> error: 'LONG_MIN' undeclared (first use in this function)
> |  #define FIBHEAPKEY_MIN LONG_MIN
>
> I've tracked it down to the fact that libiberty is the only component that
> doesn't define HAVE_LIMITS in config.h, so I assume this part of the
> configure is failing for some reason.
>
> Anyone else seen this, or have an idea on how to fix this?

whats your host distro ?

>
> Cheers,
> Martin.
>
>
>
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Python pip

2015-11-09 Thread Paul Eggleton

On Monday 09 November 2015 10:11:30 Alejandro Hernandez wrote:
> On 05/11/15 08:25, Gary Thomas wrote:
> > On 2015-11-05 07:14, Paul Eggleton wrote:
> >> Hi Gary,
> >> 
> >> On Thursday 05 November 2015 05:39:21 Gary Thomas wrote:
> >>> Just curious, does anyone know why OE-core has python3-pip
> >>> but python-pip is relegated to meta-oe?
> >> 
> >> I think it has to do with pip being supplied as part of the standard
> >> python 3
> >> distribution from 3.4 onwards. I think for simplicity's sake it might be
> >> argued that python-pip could be in the same place though.
> 
> Yes, in fact, python3-pip was included on oe-core after the upgrade to
> python3.4 since it's now a requirement, I agree, we probably should
> include python-pip on oe-core too
> 
> > Thanks, I'll consider sending a patch set for that.
> > 
> > Sadly, at this point, both packages can't be installed at the
> > same time as they both call the result "/usr/bin/pip".  Maybe
> > in keeping with the python/python3 naming, the python3 version
> > should be installed as pip3?
> 
> python3-pip recipe had to be created to avoid an issue with the default
> pip installation by python3.4, its now handled by distutils3, if its
> only a matter of changing the binary name afterwards from pip to pip3 I
> see no problem doing this, I am hoping this solves it, but just
> mentioning that we already had some issues with this, because of the
> "defaults" python3 expects

My question would be would renaming it to "pip3" be consistent with how this 
situation is handled on mainstream distributions?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Python pip

2015-11-09 Thread Alejandro Hernandez




On 09/11/15 10:17, Paul Eggleton wrote:

On Monday 09 November 2015 10:11:30 Alejandro Hernandez wrote:

On 05/11/15 08:25, Gary Thomas wrote:

On 2015-11-05 07:14, Paul Eggleton wrote:

Hi Gary,

On Thursday 05 November 2015 05:39:21 Gary Thomas wrote:

Just curious, does anyone know why OE-core has python3-pip
but python-pip is relegated to meta-oe?

I think it has to do with pip being supplied as part of the standard
python 3
distribution from 3.4 onwards. I think for simplicity's sake it might be
argued that python-pip could be in the same place though.

Yes, in fact, python3-pip was included on oe-core after the upgrade to
python3.4 since it's now a requirement, I agree, we probably should
include python-pip on oe-core too


Thanks, I'll consider sending a patch set for that.

Sadly, at this point, both packages can't be installed at the
same time as they both call the result "/usr/bin/pip".  Maybe
in keeping with the python/python3 naming, the python3 version
should be installed as pip3?

python3-pip recipe had to be created to avoid an issue with the default
pip installation by python3.4, its now handled by distutils3, if its
only a matter of changing the binary name afterwards from pip to pip3 I
see no problem doing this, I am hoping this solves it, but just
mentioning that we already had some issues with this, because of the
"defaults" python3 expects

My question would be would renaming it to "pip3" be consistent with how this
situation is handled on mainstream distributions?

Cheers,
Paul
Apparently... yes, at least it looks like it on Ubuntu-based distros, 
they use pip -> pip2 and also another binary for pip3.

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] binutils failing in FIDO branch

2015-11-09 Thread Martin Townsend

Hi,

I'm running Ubuntu 14.04 LTS.

Could this be the problem?

Cheers,
Martin.


On Mon, Nov 9, 2015 at 5:56 PM, Khem Raj  wrote:

> On Mon, Nov 9, 2015 at 4:36 AM, Martin Townsend 
> wrote:
> > Hi,
> >
> > binutils is failing to compile.  I'm using tip of fido branch.  Error
> > message is:
> >
> > |
> >
> /home/martint/yocto/build/am43-devboard-aquila/bia-tmp-glibc/work/cortexa9hf-vfp-neon-oe-linux-gnueabi/binutils/2.24-r0/binutils-2.24/libiberty/fibheap.c:
> > In function 'fibheap_replace_key_data':
> > |
> >
> /home/martint/yocto/build/am43-devboard-aquila/bia-tmp-glibc/work/cortexa9hf-vfp-neon-oe-linux-gnueabi/binutils/2.24-r0/binutils-2.24/libiberty/fibheap.c:38:24:
> > error: 'LONG_MIN' undeclared (first use in this function)
> > |  #define FIBHEAPKEY_MIN LONG_MIN
> >
> > I've tracked it down to the fact that libiberty is the only component
> that
> > doesn't define HAVE_LIMITS in config.h, so I assume this part of the
> > configure is failing for some reason.
> >
> > Anyone else seen this, or have an idea on how to fix this?
>
> whats your host distro ?
>
> >
> > Cheers,
> > Martin.
> >
> >
> >
> >
> >
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> >
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [ANNOUNCEMENT] Yocto Project 1.7.3 (fido 12.0.3) Released

2015-11-09 Thread Flanagan, Elizabeth

Hello,

The latest release of the Yocto Project 1.7.3 (dizzy-12.0.3) is now available
for download at:

http://downloads.yoctoproject.org/releases/yocto/yocto-1.7.3/poky-dizzy-12.0.3.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-1.7.3/poky-dizzy-12.0.3.tar.bz2

A gpg signed version of these release notes is available at:

http://downloads.yoctoproject.org/releases/yocto/yocto-1.7.3/RELEASENOTES

Full pass test report is available at:

https://wiki.yoctoproject.org/wiki/Ww41_-_2015-10-08_-_Full_Pass_1.7.3.rc1

Thanks go out to everyone for all their hard work during this release!

Sincerely,

Elizabeth Flanagan
Yocto Project
Build and Release

-
yocto-1.7.3 Errata

Release Name:  eclipse-poky-kepler-12.0.3
Branch: kepler/dizzy
Tag: luna/dizzy-12.0.3
Hash:  cf60ac293629fc8ecd6c4eb3709a6f334b499d0c
md5: e7eca889b7a6efffa815581fee50b657  eclipse-poky-kepler-dizzy-12.0.3.tar.bz2
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-1.7.3/eclipse-poky-kepler-dizzy-12.0.3.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-1.7.3/eclipse-poky-kepler-dizzy-12.0.3.tar.bz2

Release Name:  eclipse-poky-luna-12.0.3
Branch: luna/dizzy
Tag: luna/dizzy-12.0.3
Hash: 45aa5c77523bdf051d548fff4305382942db2ebb
md5: ebcf90e66bae33519387f299ca0c908a  eclipse-poky-luna-dizzy-12.0.3.tar.bz2
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-1.7.3/eclipse-poky-luna-dizzy-12.0.3.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-1.7.3/eclipse-poky-luna-dizzy-12.0.3.tar.bz2

Release Name:  meta-qt3-12.0.3
Branch: dizzy
Tag: dizzy-12.0.3
Hash:  3016129d90b7ac8517a5227d819f10ad417b5b45
md5: 77f5c7cb8b3523862086dd9e6271b79d  meta-qt3-dizzy-12.0.3.tar.bz2
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-1.7.3/meta-qt3-dizzy-12.0.3.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-1.7.3/meta-qt3-dizzy-12.0.3.tar.bz2

Release Name:  poky-12.0.3
Branch: dizzy
Tag: dizzy-12.0.3
Hash:  b38454c2e3a7a58f5397bb16d59e2b0aa71c4a94
md5: 7d3196798cb5e78e6b7f89e03edcf9e7  poky-dizzy-12.0.3.tar.bz2
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-1.7.3/poky-dizzy-12.0.3.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-1.7.3/poky-dizzy-12.0.3.tar.bz2

---
Security Fixes
---
bind: CVE-2015-1349 CVE-2015-4620 CVE-2015-5722
icu: CVE-2014-8146-CVE-2014-8147
gnutls: CVE-2015-3308
qemu-slirp: CVE-2014-3640
qemu-vnc: CVE-2014-7815
qemu: CVE-2014-7840
bind9.9.5: CVE-2015-5477
libxml2: Security Advisory - libxml2 - CVE-2015-1819
rpm: Fix CVE-2013-6435
rpm: Fix CVE-2014-8118
dbus: CVE-2015-0245: prevent forged ActivationFailure
unzip: fix four CVE defects
unzip: Security Advisory -CVE-2014-9636 and CVE-2015-1315
gpgme: fix CVE-2014-3564
glibc: CVE-2015-1781: resolv/nss_dns/dns-host.c buffer overflow
qemu: fix CVE-2015-3456
ppp: Security Advisory - CVE-2015-3310
libsndfile: Security Advisory - libsndfile - CVE-2014-9496

---
Fixes
---
build-appliance-image: Update to dizzy head revision
poky.conf: Bump version for 1.7.3 dizzy release
sstate: run recipe-provided hooks outside of ${B}
oprofileui: Use inherit gettext
rootfs.py: show intercept script output in log.do_rootfs
postinst_intercept: allow to pass variables with spaces
rootfs.py: Allow to override postinst-intercepts location
base.bbclass: Note when including pn with INCOMPATIBLE_LICENSES
autotools.bbclass: mkdir ${B} -> mkdir -p ${B}
perf: mkdir ${B} -> mkdir -p ${B}
bitbake: prserv/serv: Improve exit handling
bitbake: bitbake: cooker: properly fix bitbake.lock handling
bitbake: runqueue: Add message to explain the problem if diffsigs
multiple tasks don't exist
oeqa/selftest: fix test_incremental_image_generation for changes in log output
qemurunner: Improves checking for server and target IPs on qemus parameters
oeqa/utils/qemurunner: fix logging
oeqa/QemuRunner: don't use bb for logging
license.bbclass: fix unexpected operator for LICENSE values with space
license_class: fix license.manifest shows LICENSE field differently to recipe
connman-conf: fix SRC_URI_append
sstate: Use SSTATE_DIR for FILESPATH
gnome: move introspection options to gnomebase
tzdata, tzcode-native: drop older versions 2014h, 2015b
grub-efi: Add backslash lost from previous commit
grub-efi: Use the backport patch from grub
license_class: Fix choose_lic_set into incompatible license
dpkg: Fix tarfix.patch
dpkg: Fix for Fedora22 and new versions of tar
oeqa/bbtests: Fix to ensure DL_DIR is set
oeqa/bbtests: Fix race over DL_DIR and SSTATE_DIR
subversion: Fix subversion-native on Fedora22
subversion: Add -P to CPPFLAGS
cross-localedef-native: Use older C standards for older code
grub: Backport const qualifier fix for gcc-5
binutils: fix native builds when host has gcc5
ncurses: fix native builds when host has gcc5
unzip: drop 12-cve-2014-9636-test-compr-eb.patch
linux-firmware: Package Marvell pci8897 and usb8897 firmware
test-dependencies.sh: strip only .bb suffix
mesa: update

Re: [yocto] LTP tests

2015-11-09 Thread Yi Zhao


Hi Raghavendra,

There is a wiki page for LTP results: 
https://wiki.yoctoproject.org/wiki/LTP_result

You could check it as a reference.

Thanks,
Yi


在 2015年11月09日 19:55, Raghavendra Kakarla 写道:


Hi All,


I built the ltp_20150119 in the yocto build system.


But  while running the test cases, some tests are failed.


I am attaching the document for that failed test cases to this mail.



Please confirm me these test cases are failed due to the yocto rfs 
or kernel.



Thanks in advance.


Regards,

Raghavendra K.





-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] binutils failing in FIDO branch

2015-11-09 Thread Martin Townsend

Hi,

My issue is particular to my distro, I tried changing to poky and all was
well.  The reason for our own distro was to migrate from Arago which we
were using.  So I copied Arago into a separate distro and then started
morphing it into something more akin to Poky over time.  Alas I left the
following line in the distro conf, one which should have removed :(

# Enable basic stack and buffer overflow protections
TARGET_CPPFLAGS += "-fstack-protector -D_FORTIFY_SOURCE=1"

After commenting this out binutils for the target builds fine.  I'm
guesssing that for libiberty CPPFLAGS propogates into configure or makefile
in the binutils recipe which then fails one of it's config checks and
because of this fails to set HAVE_LIMITS and a few others no doubt.

Many apologies for leading you on a wild goose chase, I don't know if there
is anything you can do so others don't fall foul of this.  Is setting
TARGET_CPPFLAGS or TARGET_CFLAGS for that matter useful in configuration
files??  If so, maybe making sure they are reverted for building binutils??

Thanks for all the help and maybe it's time we moved over to Poky :)

Cheers,
Martin.




On Mon, Nov 9, 2015 at 10:07 PM, Paul Eggleton <
paul.eggle...@linux.intel.com> wrote:

> What I think Martin hasn't mentioned here (but did on IRC) is this is
> binutils
> for the target machine, not host/cross. I would assume it's somehow
> related to
> the target being built for. Martin, can you provide any details on that
> which
> might help others to reproduce the issue?
>
> Cheers,
> Paul
>
> On Monday 09 November 2015 12:15:40 Khem Raj wrote:
> > No it should be well supported. So now I wonder why no one else sees it
> >
> > > On Nov 9, 2015, at 11:22 AM, Martin Townsend 
> > > wrote:
> > >
> > > Hi,
> > >
> > > I'm running Ubuntu 14.04 LTS.
> > >
> > > Could this be the problem?
> > >
> > > Cheers,
> > > Martin.
> > >
> > >
> > > On Mon, Nov 9, 2015 at 5:56 PM, Khem Raj  > > > wrote:>
> > > On Mon, Nov 9, 2015 at 4:36 AM, Martin Townsend <
> mtownsend1...@gmail.com
> > wrote:
> > > > Hi,
> > > >
> > > > binutils is failing to compile.  I'm using tip of fido branch.  Error
> > > > message is:
> > > >
> > > >
> > > >
> /home/martint/yocto/build/am43-devboard-aquila/bia-tmp-glibc/work/cortex
> > > >
> a9hf-vfp-neon-oe-linux-gnueabi/binutils/2.24-r0/binutils-2.24/libiberty/
> > > > fibheap.c: In function 'fibheap_replace_key_data':
> > > >
> > > >
> /home/martint/yocto/build/am43-devboard-aquila/bia-tmp-glibc/work/cortex
> > > >
> a9hf-vfp-neon-oe-linux-gnueabi/binutils/2.24-r0/binutils-2.24/libiberty/
> > > > fibheap.c:38:24: error: 'LONG_MIN' undeclared (first use in this
> > > > function)
> > > >
> > > > |  #define FIBHEAPKEY_MIN LONG_MIN
> > > >
> > > > I've tracked it down to the fact that libiberty is the only component
> > > > that
> > > > doesn't define HAVE_LIMITS in config.h, so I assume this part of the
> > > > configure is failing for some reason.
> > > >
> > > > Anyone else seen this, or have an idea on how to fix this?
> > >
> > > whats your host distro ?
> > >
> > > > Cheers,
> > > > Martin.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > ___
> > > > yocto mailing list
> > > > yocto@yoctoproject.org 
> > > > https://lists.yoctoproject.org/listinfo/yocto
> > > > 
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] binutils failing in FIDO branch

2015-11-09 Thread Paul Eggleton

On Monday 09 November 2015 22:32:59 Martin Townsend wrote:
> My issue is particular to my distro, I tried changing to poky and all was
> well.  The reason for our own distro was to migrate from Arago which we
> were using.  So I copied Arago into a separate distro and then started
> morphing it into something more akin to Poky over time.  Alas I left the
> following line in the distro conf, one which should have removed :(
> 
> # Enable basic stack and buffer overflow protections
> TARGET_CPPFLAGS += "-fstack-protector -D_FORTIFY_SOURCE=1"
> 
> After commenting this out binutils for the target builds fine.  I'm
> guesssing that for libiberty CPPFLAGS propogates into configure or makefile
> in the binutils recipe which then fails one of it's config checks and
> because of this fails to set HAVE_LIMITS and a few others no doubt.
> 
> Many apologies for leading you on a wild goose chase, I don't know if there
> is anything you can do so others don't fall foul of this.  Is setting
> TARGET_CPPFLAGS or TARGET_CFLAGS for that matter useful in configuration
> files??  If so, maybe making sure they are reverted for building binutils??

I'm assuming you could do something like:

TARGET_CPPFLAGS += "${MY_EXTRAFLAGS}"
MY_EXTRAFLAGS = "-fstack-protector -D_FORTIFY_SOURCE=1"
MY_EXTRAFLAGS_pn-binutils = ""

FYI we do have meta/conf/distro/include/security_flags.inc to apply these two 
flags, but interestingly there's no mention of binutils in there.

> Thanks for all the help and maybe it's time we moved over to Poky :)

Well, there's nothing forcing you to use poky - it's a reference distribution; 
the assumption is usually that you'll want to change something at the 
distribution level at which point you've effectively created your own distro.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH 05/10][AUH] upgradehelper.py: Add sanity test for ensure that git is configured.

2015-11-09 Thread Aníbal Limón

[YOCTO #8390]

Signed-off-by: Aníbal Limón 
---
 upgradehelper.py | 16 +++-
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/upgradehelper.py b/upgradehelper.py
index 9b321f6..ae40fb1 100755
--- a/upgradehelper.py
+++ b/upgradehelper.py
@@ -28,6 +28,7 @@
 
 import argparse
 import os
+from subprocess import call
 import logging as log
 from logging import debug as D
 from logging import info as I
@@ -734,17 +735,22 @@ if __name__ == "__main__":
 global settings
 global maintainer_override
 
+if not os.getenv('BUILDDIR', False):
+E(" You must source oe-init-build-env before running this script!\n")
+exit(1)
+
+devnull = open(os.devnull, 'wb');
+if call(["git", "config", "user.name"], stdout=devnull, stderr=devnull) or 
\
+call(["git", "config", "user.email"], stdout=devnull, stderr=devnull):
+E(" Git isn't configure please configure user name and email\n")
+exit(1)
+
 signal.signal(signal.SIGINT, close_child_processes)
 
 debug_levels = [log.CRITICAL, log.ERROR, log.WARNING, log.INFO, log.DEBUG]
 args = parse_cmdline()
 log.basicConfig(format='%(levelname)s:%(message)s',
 level=debug_levels[args.debug_level - 1])
-
-if not os.getenv('BUILDDIR', False):
-E(" You must source oe-init-build-env before running this script!\n")
-exit(1)
-
 settings, maintainer_override = parse_config_file(args.config_file)
 
 if args.recipe == "all":
-- 
2.1.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Add SUSE 42.1 "Leap" to SANITY_TESTED_DISTROS

2015-11-09 Thread Jan-Simon Moeller

I forgot the "\n" at the end ... please use the attached version.


Am Montag, 9. November 2015, 23:40:07 schrieb Jan-Simon Moeller:
> Hi !
> 
> Here is a patch to add "Leap" to the tested distros. I ran a couple of
> builds since the update and all is normal. Please consider for
> inclusion.
> 
> Best,
> Jan-Simon Möller
> ---
> commit f729ca343849d2e0692caf18ba1789da408ceba3
> Author: Jan-Simon Möller 
> Date:   Mon Nov 9 23:36:41 2015 +0100
> 
> Add SUSE Leap (SUSE-LINUX-42.1) to SANITY_TESTED_DIST
> 
> Signed-off-by: Jan-Simon Möller 
> ---
>  meta-yocto/conf/distro/poky.conf | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/meta-yocto/conf/distro/poky.conf b/meta-yoct
> index 2c99da8..06209fc 100644
> --- a/meta-yocto/conf/distro/poky.conf
> +++ b/meta-yocto/conf/distro/poky.conf
> @@ -84,6 +84,7 @@ SANITY_TESTED_DISTROS ?= " \
>  Debian-7.* \n \
>  Debian-8.* \n \
>  openSUSE-project-13.2 \n \
> +SUSE-LINUX-42.1
>  "
> 
>  # Default hash policy for distro
>From 989c063a26f794ec0ef95afdc4896e8ee30450f4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan-Simon=20M=C3=B6ller?= 
Date: Mon, 9 Nov 2015 23:36:41 +0100
Subject: [PATCH] Add SUSE Leap (SUSE-LINUX-42.1) to SANITY_TESTED_DISTROS.
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Signed-off-by: Jan-Simon Möller 
---
 meta-yocto/conf/distro/poky.conf | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta-yocto/conf/distro/poky.conf b/meta-yocto/conf/distro/poky.conf
index 2c99da8..1477b4b 100644
--- a/meta-yocto/conf/distro/poky.conf
+++ b/meta-yocto/conf/distro/poky.conf
@@ -84,6 +84,7 @@ SANITY_TESTED_DISTROS ?= " \
 Debian-7.* \n \
 Debian-8.* \n \
 openSUSE-project-13.2 \n \
+SUSE-LINUX-42.1 \n \
 "
 
 # Default hash policy for distro
-- 
2.6.2

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Add SUSE 42.1 "Leap" to SANITY_TESTED_DISTROS

2015-11-09 Thread Jan-Simon Moeller

Hi !

Here is a patch to add "Leap" to the tested distros. I ran a couple of 
builds since the update and all is normal. Please consider for 
inclusion.

Best,
Jan-Simon Möller
---
commit f729ca343849d2e0692caf18ba1789da408ceba3
Author: Jan-Simon Möller 
Date:   Mon Nov 9 23:36:41 2015 +0100

Add SUSE Leap (SUSE-LINUX-42.1) to SANITY_TESTED_DIST

Signed-off-by: Jan-Simon Möller 
---
 meta-yocto/conf/distro/poky.conf | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta-yocto/conf/distro/poky.conf b/meta-yoct
index 2c99da8..06209fc 100644
--- a/meta-yocto/conf/distro/poky.conf
+++ b/meta-yocto/conf/distro/poky.conf
@@ -84,6 +84,7 @@ SANITY_TESTED_DISTROS ?= " \
 Debian-7.* \n \
 Debian-8.* \n \
 openSUSE-project-13.2 \n \
+SUSE-LINUX-42.1
 "
 
 # Default hash policy for distro
>From f729ca343849d2e0692caf18ba1789da408ceba3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan-Simon=20M=C3=B6ller?= 
Date: Mon, 9 Nov 2015 23:36:41 +0100
Subject: [PATCH] Add SUSE Leap (SUSE-LINUX-42.1) to SANITY_TESTED_DISTROS.
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Signed-off-by: Jan-Simon Möller 
---
 meta-yocto/conf/distro/poky.conf | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta-yocto/conf/distro/poky.conf b/meta-yocto/conf/distro/poky.conf
index 2c99da8..06209fc 100644
--- a/meta-yocto/conf/distro/poky.conf
+++ b/meta-yocto/conf/distro/poky.conf
@@ -84,6 +84,7 @@ SANITY_TESTED_DISTROS ?= " \
 Debian-7.* \n \
 Debian-8.* \n \
 openSUSE-project-13.2 \n \
+SUSE-LINUX-42.1
 "
 
 # Default hash policy for distro
-- 
2.6.2

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] LTP tests

2015-11-09 Thread Raghavendra Kakarla

Hi All,


I built the ltp_20150119 in the yocto build system.


But  while running the test cases, some tests are failed.


I am attaching the document for that failed test cases to this mail.


Please confirm me these test cases are failed due to the yocto rfs or kernel.


Thanks in advance.


Regards,

Raghavendra K.


LTP_RUN_LOG
Description: LTP_RUN_LOG
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [prelink-cross][PATCH 1/1] rtld.c: LD_PRELOAD bugfix

2015-11-09 Thread Maninder Singh

Hello,

>On 11/7/15 5:24 AM, Maninder Singh wrote:
>> Hi,
>> Ping
>
>I'd gotten a msg after this to hold off and wait for an update.  Is this the
>updated version of the fix?
>
>--Mark

Yes, we send message for update a fix for LD_PRELOAD implemntation in prelink:-
https://lists.yoctoproject.org/pipermail/yocto/2015-September/026431.html
 (LD_PRELOAD implemntation patch, which is merged with prelink_cross project)

and this below patch fixes  bug in LD_PRELOAD patch (yes this is updated 
version of fix).

>>> This patch do following things:-
>>> 1.  Fixes bug of adding preloaded libs in search scope of dependent 
>>> libraries which results in search scope of few symbols becomes 
>>> same for executable and library, so conflict doesn't occur for 
>>> those symbols and hence resulted in less number of conflicts.
>>> 2.  Reduce code redundancy.
>>> 3.  Buffer Overflow fix.
>>>
>>> Signed-off-by: Maninder Singh 
>>> Signed-off-by: Vaneet Narang 
>>> Reviewed-by: Doha Hwang 
>>> ---
>>> trunk/src/rtld/rtld.c |   27 ---
>>> 1 files changed, 16 insertions(+), 11 deletions(-)
>>>
>>> diff --git a/trunk/src/rtld/rtld.c b/trunk/src/rtld/rtld.c
>>> index 50461b6..8af5052 100644
>>> --- a/trunk/src/rtld/rtld.c
>>> +++ b/trunk/src/rtld/rtld.c
>>> @@ -606,7 +606,7 @@ load_dsos (DSO *dso, int host_paths)
>>> {
>>>   struct dso_list *dso_list, *dso_list_tail, *cur_dso_ent, *new_dso_ent;
>>>   struct stat64 st;
>>> -  int total_preload = 0;
>>> +  int total_preload = 0, temp_total_preload = 0;
>>>   char * libname[MAX_PRELOADED_LIBS] = {NULL};
>>>
>>>   /* Assume it's static unless we find DT_NEEDED entries */
>>> @@ -632,19 +632,19 @@ load_dsos (DSO *dso, int host_paths)
>>>
>>>   if(dso->ehdr.e_type == ET_EXEC && ld_preload) {
>>>   char *next_lib =  ld_preload;
>>> -  libname[total_preload] = ld_preload;
>>> -  total_preload++;
>>> -  next_lib=strchr(ld_preload,':');
>>> -  while(next_lib!=NULL){
>>> - *next_lib = '\0';
>>> - next_lib++;
>>> - libname[total_preload] = next_lib;
>>> - total_preload++;
>>> - next_lib=strchr(next_lib,':');
>>> -  }
>>> +  while(*next_lib != '\0' && (total_preload < MAX_PRELOADED_LIBS)){
>>> +libname[total_preload++] = next_lib;
>>> +next_lib=strchrnul(next_lib,':');
>>> +if(*next_lib == '\0')
>>> +  break;
>>> +*next_lib = '\0';
>>> +next_lib++;
>>> + }
>>> +temp_total_preload = total_preload;
>>>   }
>>>   else {
>>>   total_preload = 0;
>>> +  temp_total_preload = 0;
>>>   }
>>>   while (cur_dso_ent != NULL)
>>> {
>>> @@ -666,6 +666,11 @@ load_dsos (DSO *dso, int host_paths)
>>> {
>>>   int ndx, maxndx;
>>>   maxndx = data->d_size / cur_dso->shdr[cur_dso->dynamic].sh_entsize;
>>> +  if(!(cur_dso->ehdr.e_type == ET_EXEC))
>>> +total_preload = 0;
>>> +  else
>>> +total_preload = temp_total_preload;
>>> +
>>>   for (ndx = 0; ndx < maxndx + total_preload; ++ndx)
>>> {
>>>
>>> -- 
>>> 1.7.1

This patch is a fix to a bug of below commit (addition of new --ld-preload 
option):-
http://git.yoctoproject.org/cgit/cgit.cgi/prelink-cross/commit/?h=cross_prelink=3199ee4ebfc37288391e169825b75fa80c6136a3
and applicable after this commit


Thanks,
Maninder Singh
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [prelink-cross][PATCH 1/1] rtld.c: LD_PRELOAD bugfix

[yocto] binutils failing in FIDO branch

[yocto] [PATCH 04/10][AUH] buildhistory.py: Don't modify BB_ENV_EXTRAWHITE before init.

[yocto] [PATCH 01/10][AUH] upgradehelper.py: Add step for build gcc-runtime at init.

[yocto] [PATCH 00/10][AUH] Improvements and small fixes.

[yocto] [PATCH 10/10][AUH] requirements.txt: Add file for now only with GitPython

[yocto] [PATCH 08/10][AUH] upgradehelper.py: Add support for do recipe upgrades based on builddep

[yocto] [PATCH 07/10][AUH] upgradehelper.py: Improve work directory structure

[yocto] [PATCH 02/10][AUH] upgradehelper.py: Fix bug when buildhistory isn't enabled

[yocto] [PATCH 06/10][AUH] buildhistory.py: Add missing warning import. git.py: Fix last_commit method.

[yocto] [PATCH 03/10][AUH] recipe.py: Improvements and refactor of fetch method.

Re: [yocto] binutils failing in FIDO branch

[yocto] [PATCH 09/10][AUH] upgradehelper.py: Add support for preserve statistics into work directory.

Re: [yocto] [yocto-announce] [ANNOUNCEMENT] Yocto Project 1.7.3 (fido 12.0.3) Released

Re: [yocto] [yocto-announce] [ANNOUNCEMENT] Yocto Project 1.7.3 (fido 12.0.3) Released

Re: [yocto] Python pip

Re: [yocto] Python pip

Re: [yocto] binutils failing in FIDO branch

Re: [yocto] Python pip

Re: [yocto] Python pip

Re: [yocto] binutils failing in FIDO branch

[yocto] [ANNOUNCEMENT] Yocto Project 1.7.3 (fido 12.0.3) Released

Re: [yocto] LTP tests

Re: [yocto] binutils failing in FIDO branch

Re: [yocto] binutils failing in FIDO branch

[yocto] [PATCH 05/10][AUH] upgradehelper.py: Add sanity test for ensure that git is configured.

Re: [yocto] Add SUSE 42.1 "Leap" to SANITY_TESTED_DISTROS

[yocto] Add SUSE 42.1 "Leap" to SANITY_TESTED_DISTROS

[yocto] LTP tests

Re: [yocto] [prelink-cross][PATCH 1/1] rtld.c: LD_PRELOAD bugfix

30 matches

Site Navigation

Mail list logo

Footer information