date:20150921

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

2015-09-21 Thread Maninder Singh

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

Re: [yocto] packageconfig for non-autotooled project

2015-09-21 Thread Taek Hyun Shin

Yes, if you can do it, it is the best.
The necessary pc files are as follows:
egl.pc
glesv1_cm.pc
glesv2.pc
vg.pc

Thanks

Best regards,
Wily Taekhyun Shin

=
Wily Taekhyun Shin
Research Engineer
R Center
Telechips Inc.
Tel : + 82-2-3443-6792(Ext.390)
Fax : + 82-2-6424-7793 
Mobile : + 82-10-4376-5530
E-mail : ths...@telechips.com

-Original Message-
From: Trevor Woerner [mailto:twoer...@gmail.com] 
Sent: Tuesday, September 22, 2015 11:59 AM
To: 신택현 (Taek Hyun Shin); yocto@yoctoproject.org
Subject: Re: [yocto] packageconfig for non-autotooled project

On 09/21/15 22:04, 신택현 (Taek Hyun Shin) wrote:
>
> Create a sunxi-mali_git.bbappend file, to see the pc file of the MESA 
> Project can be used to manually create a .pc file.
>

Thanks for your reply.

I think this is best fixed in the meta-sunxi layer itself, instead of requiring 
users to bbappend this recipe in their layers. I'll be generating a github pull 
request to the maintainers shortly.

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

Re: [yocto] specify compiler version in recipe

2015-09-21 Thread Khem Raj


> On Sep 21, 2015, at 7:47 PM, Trevor Woerner  wrote:
> 
> Hello,
> 
> It looks like I already know the answer to this one... ;-)
> 
> I'm guessing it isn't possible to specify the compiler version in a
> recipe? That's probably way too late in the parse stage?
> 
> There are some vendor Linux kernels for some BSPs that are old enough to
> pre-date the:
> 
>fatal error: linux/compiler-gcc5.h: No such file or directory

back port the needed patch from upstream kernel. No other solution will be 
comprehensive.

> 
> issue. Which means we have to rely on users reading the README and
> updating their conf/local.conf files to include
> 
>GCCVERSION = "4.9%"
> 
> Unfortunately that process is error-prone. It would be great to have
> that occur automatically. In other words: if you want to use the
> community/default/upstream kernel then use the latest compiler (but you
> won't have accelerated graphics). If you want accelerated graphics then
> you have to PREFER an older kernel *and* specify which version of gcc to
> use in your conf/local.conf.
> 
> Can anyone think of a clever trick for this one?
> 
> Are BSP maintainers patching their old kernels to support post-gcc-5.0
> versions?
> 
> Best regards,
>Trevor
> -- 
> ___
> 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] bitbake error

2015-09-21 Thread Paul Eggleton

On Monday 21 September 2015 07:10:00 Gary Thomas wrote:
> When trying to build using latest Poky/Yocto master
> (7b86c771c80d0759c2ca0e57c46c4c966f89c49e) I'm getting this error:
> 
> 
> = Build Configuration:
> BB_VERSION= "1.27.1"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING   = "Ubuntu-15.04"
> TARGET_SYS= "arm-amltd-linux-gnueabi"
> MACHINE   = "teton-p0382"
> DISTRO= "amltd"
> DISTRO_VERSION= "1.8+snapshot-20150921"
> TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard cortexa9"
> TARGET_FPU= "vfp-neon"
> meta  = "master:7b86c771c80d0759c2ca0e57c46c4c966f89c49e"
> 
> ERROR: Error executing a python function in
> /local/poky-cutting-edge/meta/recipes-devtools/quilt/quilt-native_0.64.bb:
> 
> The stack trace of python calls that resulted in this exception/failure was:
> File: 'relocatable_binaries_preprocess', lineno: 6, function: 
> 0002:def relocatable_binaries_preprocess(d):
>   0003:   
> rpath_replace(d.expand('/local/p0382-cutting-edge_2014-11-21/tmp/work/x86_6
> 4-linux/quilt-native/0.64-r0/sysroot-destdir/'), d) 0004:
>   0005:
>   *** 0006:relocatable_binaries_preprocess(d)
>   0007:
> File: 'relocatable_binaries_preprocess', lineno: 3, function:
> relocatable_binaries_preprocess 0001:
>   0002:def relocatable_binaries_preprocess(d):
>   *** 0003:   
> rpath_replace(d.expand('/local/p0382-cutting-edge_2014-11-21/tmp/work/x86_6
> 4-linux/quilt-native/0.64-r0/sysroot-destdir/'), d) 0004:
>   0005:
>   0006:relocatable_binaries_preprocess(d)
>   0007:
> File: 'chrpath.bbclass', lineno: 7, function: rpath_replace
>   0003:
>   0004:for bindir in bindirs:
>   0005:#bb.note ("Processing directory " + bindir)
>   0006:directory = path + "/" + bindir
>   *** 0007:process_dir (path, directory, d)
>   0008:
> File: 'chrpath.bbclass', lineno: 44, function: process_dir
>   0040:perms = None
>   0041:else:
>   0042:# Temporarily make the file writeable so we can
> chrpath it 0043:os.chmod(fpath, perms|stat.S_IRWXU)
>   *** 0044:process_file(cmd, fpath, rootdir, baseprefix, tmpdir,
> d) 0045:
>   0046:if perms:
>   0047:os.chmod(fpath, perms)
>   0048:
> File: 'chrpath.bbclass', lineno: 4, function: process_file_linux
>   0001:def process_file_linux(cmd, fpath, rootdir, baseprefix, tmpdir,
> d): 0002:import subprocess as sub
>   0003:
>   *** 0004:p = sub.Popen([cmd, '-l',
> fpath],stdout=sub.PIPE,stderr=sub.PIPE) 0005:err, out = p.communicate()
>   0006:# If returned succesfully, process stderr for results
>   0007:if p.returncode != 0:
>   0008:return
> File: '/usr/lib/python2.7/subprocess.py', lineno: 710, function: __init__
>   0706:cwd, env, universal_newlines,
>   0707:startupinfo, creationflags,
> shell, to_close, 0708:p2cread, p2cwrite,
>   0709:c2pread, c2pwrite,
>   *** 0710:errread, errwrite)
>   0711:except Exception:
>   0712:# Preserve original exception in case os.close
> raises. 0713:exc_type, exc_value, exc_trace = sys.exc_info()
> 0714:
> File: '/usr/lib/python2.7/subprocess.py', lineno: 1335, function:
> _execute_child 1331:except OSError as e:
>   1332:if e.errno != errno.ECHILD:
>   1333:raise
>   1334:child_exception = pickle.loads(data)
>   *** 1335:raise child_exception
>   1336:
>   1337:
>   1338:def _handle_exitstatus(self, sts,
> _WIFSIGNALED=os.WIFSIGNALED, 1339:_WTERMSIG=os.WTERMSIG,
> _WIFEXITED=os.WIFEXITED, Exception: OSError: [Errno 2] No such file or
> directory
> 
> ERROR: Function failed: relocatable_binaries_preprocess
> ERROR: Logfile of failure stored in:
> /local/p0382-cutting-edge_2014-11-21/tmp/work/x86_64-linux/quilt-native/0.6
> 4-r0/temp/log.do_populate_sysroot.12966 ERROR: Task 11
> (/local/poky-cutting-edge/meta/recipes-devtools/quilt/quilt-native_0.64.bb,
> do_populate_sysroot) failed with exit code '1'
> ===
> ==

[yocto] bitbake error

2015-09-21 Thread Gary Thomas


When trying to build using latest Poky/Yocto master 
(7b86c771c80d0759c2ca0e57c46c4c966f89c49e)
I'm getting this error:

=
Build Configuration:
BB_VERSION= "1.27.1"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-15.04"
TARGET_SYS= "arm-amltd-linux-gnueabi"
MACHINE   = "teton-p0382"
DISTRO    = "amltd"
DISTRO_VERSION= "1.8+snapshot-20150921"
TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard cortexa9"
TARGET_FPU= "vfp-neon"
meta  = "master:7b86c771c80d0759c2ca0e57c46c4c966f89c49e"

ERROR: Error executing a python function in 
/local/poky-cutting-edge/meta/recipes-devtools/quilt/quilt-native_0.64.bb:

The stack trace of python calls that resulted in this exception/failure was:
File: 'relocatable_binaries_preprocess', lineno: 6, function: 
 0002:def relocatable_binaries_preprocess(d):
 0003:
rpath_replace(d.expand('/local/p0382-cutting-edge_2014-11-21/tmp/work/x86_64-linux/quilt-native/0.64-r0/sysroot-destdir/'),
 d)
 0004:
 0005:
 *** 0006:relocatable_binaries_preprocess(d)
 0007:
File: 'relocatable_binaries_preprocess', lineno: 3, function: 
relocatable_binaries_preprocess
 0001:
 0002:def relocatable_binaries_preprocess(d):
 *** 0003:
rpath_replace(d.expand('/local/p0382-cutting-edge_2014-11-21/tmp/work/x86_64-linux/quilt-native/0.64-r0/sysroot-destdir/'),
 d)
 0004:
 0005:
 0006:relocatable_binaries_preprocess(d)
 0007:
File: 'chrpath.bbclass', lineno: 7, function: rpath_replace
 0003:
 0004:for bindir in bindirs:
 0005:#bb.note ("Processing directory " + bindir)
 0006:directory = path + "/" + bindir
 *** 0007:process_dir (path, directory, d)
 0008:
File: 'chrpath.bbclass', lineno: 44, function: process_dir
 0040:perms = None
 0041:else:
 0042:# Temporarily make the file writeable so we can 
chrpath it
 0043:os.chmod(fpath, perms|stat.S_IRWXU)
 *** 0044:process_file(cmd, fpath, rootdir, baseprefix, tmpdir, d)
 0045:
 0046:if perms:
 0047:os.chmod(fpath, perms)
 0048:
File: 'chrpath.bbclass', lineno: 4, function: process_file_linux
 0001:def process_file_linux(cmd, fpath, rootdir, baseprefix, tmpdir, d):
 0002:import subprocess as sub
 0003:
 *** 0004:p = sub.Popen([cmd, '-l', fpath],stdout=sub.PIPE,stderr=sub.PIPE)
 0005:err, out = p.communicate()
 0006:# If returned succesfully, process stderr for results
 0007:if p.returncode != 0:
 0008:return
File: '/usr/lib/python2.7/subprocess.py', lineno: 710, function: __init__
 0706:cwd, env, universal_newlines,
 0707:startupinfo, creationflags, shell, 
to_close,
 0708:p2cread, p2cwrite,
 0709:c2pread, c2pwrite,
 *** 0710:errread, errwrite)
 0711:except Exception:
 0712:# Preserve original exception in case os.close raises.
 0713:exc_type, exc_value, exc_trace = sys.exc_info()
 0714:
File: '/usr/lib/python2.7/subprocess.py', lineno: 1335, function: _execute_child
 1331:except OSError as e:
 1332:if e.errno != errno.ECHILD:
 1333:raise
 1334:child_exception = pickle.loads(data)
 *** 1335:raise child_exception
 1336:
 1337:
 1338:def _handle_exitstatus(self, sts, _WIFSIGNALED=os.WIFSIGNALED,
 1339:_WTERMSIG=os.WTERMSIG, _WIFEXITED=os.WIFEXITED,
Exception: OSError: [Errno 2] No such file or directory

ERROR: Function failed: relocatable_binaries_preprocess
ERROR: Logfile of failure stored in: 
/local/p0382-cutting-edge_2014-11-21/tmp/work/x86_64-linux/quilt-native/0.64-r0/temp/log.do_populate_sysroot.12966
ERROR: Task 11 
(/local/poky-cutting-edge/meta/recipes-devtools/quilt/quilt-native_0.64.bb, 
do_populate_sysroot) failed with exit code '1'
=

Sadly, I don't see enough info in this error trace to really tell me
what file/directory is missing (i.e. what the real problem is)

I tried 'bitbake quilt-native -c cleanstate', but the problem persists.
Note that this is a build in a older tree, one which I've been using 
successfully
(as you can tell) since late 2014.

Interestingly, I can build using the same meta-data on a different build
box!

I get the same error when using a totally fresh tree, so I'm really
perplexed b

Re: [yocto] Dumping sysvinit

2015-09-21 Thread Andy Pont

Hi Mike,

> > Back to plan A then, trying to figure out how to get Busybox init and
> mdev as the defaults in the image.
> 
> Create your own distro, here's an example that uses mdev:
> 
> https://github.com/topic-embedded-products/meta-
> topic/blob/master/conf/distro/tiny.conf

Thanks for pointing me in the direction of this.  I have cloned it and used
it as the basis of my distro, tweaked it a bit and it is starting to behave
how I want.  There are a few anomalies that I haven't managed to figure out
yet...

Despite having VIRTUAL-RUNTIME_initscripts = "" the root file system still
contains /etc/rcX.d directories

On other embedded Linux projects that boot using Busybox init the
/etc/init.d directory contained the individual service start and kill files
e.g. S50-dropbear and K50-dropbear but I can't see how to make Yocto
populate this directory in that form.

Thoughts and guidance from anyone would be much appreciated!

Andy.


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

[yocto] Change in bitbake behaviour?

2015-09-21 Thread Gary Thomas


I just updated to the latest Poky/Yocto master
and I noticed this change in behaviour when I tried to stop
a build:
  Keyboard Interrupt, closing down...

  NOTE: Tasks Summary: Attempted 86 tasks of which 36 didn't need to be rerun 
and all succeeded.
  ERROR: Command execution failed: Stopped build

  Summary: There was 1 ERROR message shown, returning a non-zero exit code.
  Execution was interrupted, returning a non-zero exit code.
  timed out

It took more than a minute between the last two lines at which time
I thought it might be hung.  I left it and then found the "timed out"
line somewhat later.

Is this to be expected?

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

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

Re: [yocto] bitbake error

2015-09-21 Thread Gary Thomas


On 2015-09-21 07:38, Paul Eggleton wrote:

On Monday 21 September 2015 07:10:00 Gary Thomas wrote:

When trying to build using latest Poky/Yocto master
(7b86c771c80d0759c2ca0e57c46c4c966f89c49e) I'm getting this error:


= Build Configuration:
BB_VERSION= "1.27.1"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-15.04"
TARGET_SYS= "arm-amltd-linux-gnueabi"
MACHINE   = "teton-p0382"
DISTRO    = "amltd"
DISTRO_VERSION= "1.8+snapshot-20150921"
TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard cortexa9"
TARGET_FPU= "vfp-neon"
meta  = "master:7b86c771c80d0759c2ca0e57c46c4c966f89c49e"

ERROR: Error executing a python function in
/local/poky-cutting-edge/meta/recipes-devtools/quilt/quilt-native_0.64.bb:

The stack trace of python calls that resulted in this exception/failure was:
File: 'relocatable_binaries_preprocess', lineno: 6, function: 
0002:def relocatable_binaries_preprocess(d):
   0003:
rpath_replace(d.expand('/local/p0382-cutting-edge_2014-11-21/tmp/work/x86_6
4-linux/quilt-native/0.64-r0/sysroot-destdir/'), d) 0004:
   0005:
   *** 0006:relocatable_binaries_preprocess(d)
   0007:
File: 'relocatable_binaries_preprocess', lineno: 3, function:
relocatable_binaries_preprocess 0001:
   0002:def relocatable_binaries_preprocess(d):
   *** 0003:
rpath_replace(d.expand('/local/p0382-cutting-edge_2014-11-21/tmp/work/x86_6
4-linux/quilt-native/0.64-r0/sysroot-destdir/'), d) 0004:
   0005:
   0006:relocatable_binaries_preprocess(d)
   0007:
File: 'chrpath.bbclass', lineno: 7, function: rpath_replace
   0003:
   0004:for bindir in bindirs:
   0005:#bb.note ("Processing directory " + bindir)
   0006:directory = path + "/" + bindir
   *** 0007:process_dir (path, directory, d)
   0008:
File: 'chrpath.bbclass', lineno: 44, function: process_dir
   0040:perms = None
   0041:else:
   0042:# Temporarily make the file writeable so we can
chrpath it 0043:os.chmod(fpath, perms|stat.S_IRWXU)
   *** 0044:process_file(cmd, fpath, rootdir, baseprefix, tmpdir,
d) 0045:
   0046:if perms:
   0047:os.chmod(fpath, perms)
   0048:
File: 'chrpath.bbclass', lineno: 4, function: process_file_linux
   0001:def process_file_linux(cmd, fpath, rootdir, baseprefix, tmpdir,
d): 0002:import subprocess as sub
   0003:
   *** 0004:p = sub.Popen([cmd, '-l',
fpath],stdout=sub.PIPE,stderr=sub.PIPE) 0005:err, out = p.communicate()
   0006:# If returned succesfully, process stderr for results
   0007:if p.returncode != 0:
   0008:return
File: '/usr/lib/python2.7/subprocess.py', lineno: 710, function: __init__
   0706:cwd, env, universal_newlines,
   0707:startupinfo, creationflags,
shell, to_close, 0708:p2cread, p2cwrite,
   0709:c2pread, c2pwrite,
   *** 0710:errread, errwrite)
   0711:except Exception:
   0712:# Preserve original exception in case os.close
raises. 0713:exc_type, exc_value, exc_trace = sys.exc_info()
0714:
File: '/usr/lib/python2.7/subprocess.py', lineno: 1335, function:
_execute_child 1331:except OSError as e:
   1332:if e.errno != errno.ECHILD:
   1333:raise
   1334:child_exception = pickle.loads(data)
   *** 1335:raise child_exception
   1336:
   1337:
   1338:def _handle_exitstatus(self, sts,
_WIFSIGNALED=os.WIFSIGNALED, 1339:_WTERMSIG=os.WTERMSIG,
_WIFEXITED=os.WIFEXITED, Exception: OSError: [Errno 2] No such file or
directory

ERROR: Function failed: relocatable_binaries_preprocess
ERROR: Logfile of failure stored in:
/local/p0382-cutting-edge_2014-11-21/tmp/work/x86_64-linux/quilt-native/0.6
4-r0/temp/log.do_populate_sysroot.12966 ERROR: Task 11
(/local/poky-cutting-edge/meta/recipes-devtools/quilt/quilt-native_0.64.bb,
do_populate_sysroot) failed with exit code '1'
===
==

Sadly, I don't see enough info in this error trace to really tell me
what file/directory is missing (i.e. what the real problem is)

I tried 'bitbake quilt-native -c cleanstate', but the problem persists.
Note that this is a build in a older tree, one which I've been using
successfully (as you can tell) since late 2014.

Interestingly, I can build using the same meta-data on

Re: [yocto] packageconfig for non-autotooled project

2015-09-21 Thread Trevor Woerner

On 09/21/15 22:04, 신택현 (Taek Hyun Shin) wrote:
>
> Create a sunxi-mali_git.bbappend file, to see the pc file of the MESA
> Project can be used to manually create a .pc file.
>

Thanks for your reply.

I think this is best fixed in the meta-sunxi layer itself, instead of
requiring users to bbappend this recipe in their layers. I'll be
generating a github pull request to the maintainers shortly.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] specify compiler version in recipe

2015-09-21 Thread Trevor Woerner

Hello,

It looks like I already know the answer to this one... ;-)

I'm guessing it isn't possible to specify the compiler version in a
recipe? That's probably way too late in the parse stage?

There are some vendor Linux kernels for some BSPs that are old enough to
pre-date the:

fatal error: linux/compiler-gcc5.h: No such file or directory

issue. Which means we have to rely on users reading the README and
updating their conf/local.conf files to include

GCCVERSION = "4.9%"

Unfortunately that process is error-prone. It would be great to have
that occur automatically. In other words: if you want to use the
community/default/upstream kernel then use the latest compiler (but you
won't have accelerated graphics). If you want accelerated graphics then
you have to PREFER an older kernel *and* specify which version of gcc to
use in your conf/local.conf.

Can anyone think of a clever trick for this one?

Are BSP maintainers patching their old kernels to support post-gcc-5.0
versions?

Best regards,
Trevor
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] packageconfig for non-autotooled project

2015-09-21 Thread Taek Hyun Shin

Create a sunxi-mali_git.bbappend file, to see the pc file of the MESA Project 
can be used to manually create a .pc file.

 

sunxi-mali_git.bbappend file

=

FILESEXTRAPATHS_append := ":${THISDIR}/${PN}"

 

SRC_URI += "file://egl.pc"

 

do_install_append() {

install -d ${D}${libdir}/pkgconfig

cp ${WORKDIR}/egl.pc  ${D}${libdir}/pkgconfig

}

=

 

this is my egl.pc file



prefix=/usr

exec_prefix=${prefix}

libdir=/usr/lib

includedir=/usr/include

 

Name: egl

Description: Telechips EGL library

Requires.private: 

Version: 10.1.3

Libs: -L${libdir} -lEGL -lGLESv2 -lMali -lUMP

Libs.private: 

Cflags: -I${includedir}/EGL/ -I${includedir}



 

 

 

Best regards,

Wily Taekhyun Shin

 

=
Wily Taekhyun Shin

Research Engineer
R Center
Telechips Inc.
Tel : + 82-2-3443-6792(Ext.390)

Fax : + 82-2-6424-7793 

Mobile : + 82-10-4376-5530

E-mail : ths...@telechips.com 

 
=



 

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

Re: [yocto] [OE-core] packageconfig for non-autotooled project

2015-09-21 Thread Khem Raj

Look at the patches I have posted for raspberry pi layer
On Sep 21, 2015 7:29 AM, "Trevor Woerner"  wrote:

> Hello,
>
> libepoxy needs its EGL support to have a packageconfig (*.pc) file but
> the EGL I want to use in my project
> (meta-sunxi/recipes-graphics/libgles/sunxi-mali_git.bb, which points to
> gitsm://github.com/linux-sunxi/sunxi-mali.git) isn't autotooled. There
> are a couple ways around this problem, but if there is an example of
> generating a .pc file for a non-autotooled project already, I'd be
> grateful if someone could point me to it :-)
>
> Best regards,
> Trevor
> --
> ___
> Openembedded-core mailing list
> openembedded-c...@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] packageconfig for non-autotooled project

2015-09-21 Thread Trevor Woerner

Hello,

libepoxy needs its EGL support to have a packageconfig (*.pc) file but
the EGL I want to use in my project
(meta-sunxi/recipes-graphics/libgles/sunxi-mali_git.bb, which points to
gitsm://github.com/linux-sunxi/sunxi-mali.git) isn't autotooled. There
are a couple ways around this problem, but if there is an example of
generating a .pc file for a non-autotooled project already, I'd be
grateful if someone could point me to it :-)

Best regards,
Trevor
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] libsoup license

2015-09-21 Thread Dan Winship


On 09/18/2015 04:07 PM, Burton, Ross wrote:

To be honest libsoup isn't very clear

...

Dan: exactly what license is libsoup under?  LGPL v2 precisely, or LGPL
v2 or greater?


I don't know either. :-)

It was initially written at a time when Ximian was explicitly using the 
"v2 only" license on evolution (because reasons), so it's possible that 
libsoup was intended to be v2 only, since it was more-or-less part of 
evolution. But then, Novell relicensed evolution to v2+ later on, so 
presumably, if libsoup actually was v2-only at that point (which it may 
not have been), then surely Novell *intended* to also make libsoup v2+, 
despite not having said so. So... "maybe it used to be v2+" + "probably 
it was intended to have been changed to v2+ later if it wasn't already" 
+ "certainly everything written since 2007 was intended to be v2+" == 
"probably definitely it's v2+ now" ? That's totally how the law works, 
right?


-- Dan

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

Re: [yocto] bitbake error

2015-09-21 Thread Gary Thomas


Sorry for the dups - I forgot to CC the list.

On 2015-09-21 08:35, Paul Eggleton wrote:

On Monday 21 September 2015 07:55:35 Gary Thomas wrote:

On 2015-09-21 07:38, Paul Eggleton wrote:

On Monday 21 September 2015 07:10:00 Gary Thomas wrote:

When trying to build using latest Poky/Yocto master
(7b86c771c80d0759c2ca0e57c46c4c966f89c49e) I'm getting this error:

=
=== = Build Configuration:
BB_VERSION= "1.27.1"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-15.04"
TARGET_SYS= "arm-amltd-linux-gnueabi"
MACHINE   = "teton-p0382"
DISTRO    = "amltd"
DISTRO_VERSION= "1.8+snapshot-20150921"
TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard
cortexa9" TARGET_FPU= "vfp-neon"
meta  = "master:7b86c771c80d0759c2ca0e57c46c4c966f89c49e"

ERROR: Error executing a python function in
/local/poky-cutting-edge/meta/recipes-devtools/quilt/quilt-native_0.64.bb
:

The stack trace of python calls that resulted in this exception/failure
was: File: 'relocatable_binaries_preprocess', lineno: 6, function:
>>
0002:def relocatable_binaries_preprocess(d):
0003:
rpath_replace(d.expand('/local/p0382-cutting-edge_2014-11-21/tmp/work/x86
_6

4-linux/quilt-native/0.64-r0/sysroot-destdir/'), d) 0004:
0005:
*** 0006:relocatable_binaries_preprocess(d)

0007:
File: 'relocatable_binaries_preprocess', lineno: 3, function:

relocatable_binaries_preprocess 0001:
0002:def relocatable_binaries_preprocess(d):
*** 0003:
rpath_replace(d.expand('/local/p0382-cutting-edge_2014-11-21/tmp/work/x86
_6

4-linux/quilt-native/0.64-r0/sysroot-destdir/'), d) 0004:
0005:
0006:relocatable_binaries_preprocess(d)

0007:
File: 'chrpath.bbclass', lineno: 7, function: rpath_replace

0003:
0004:for bindir in bindirs:
0005:#bb.note ("Processing directory " + bindir)
0006:directory = path + "/" + bindir

*** 0007:process_dir (path, directory, d)

0008:
File: 'chrpath.bbclass', lineno: 44, function: process_dir

0040:perms = None
0041:else:
0042:# Temporarily make the file writeable so we
can

chrpath it 0043:os.chmod(fpath, perms|stat.S_IRWXU)

*** 0044:process_file(cmd, fpath, rootdir, baseprefix,
tmpdir,

d) 0045:
0046:if perms:
0047:os.chmod(fpath, perms)

0048:
File: 'chrpath.bbclass', lineno: 4, function: process_file_linux

0001:def process_file_linux(cmd, fpath, rootdir, baseprefix,
tmpdir,

d): 0002:import subprocess as sub

0003:
*** 0004:p = sub.Popen([cmd, '-l',

fpath],stdout=sub.PIPE,stderr=sub.PIPE) 0005:err, out =
p.communicate()

0006:# If returned succesfully, process stderr for results
0007:if p.returncode != 0:
0008:return

File: '/usr/lib/python2.7/subprocess.py', lineno: 710, function: __init__

0706:cwd, env, universal_newlines,
0707:startupinfo, creationflags,

shell, to_close, 0708:p2cread, p2cwrite,

0709:c2pread, c2pwrite,

*** 0710:errread, errwrite)

0711:except Exception:
0712:# Preserve original exception in case os.close

raises. 0713:exc_type, exc_value, exc_trace = sys.exc_info()
0714:
File: '/usr/lib/python2.7/subprocess.py', lineno: 1335, function:

_execute_child 1331:except OSError as e:
1332:if e.errno != errno.ECHILD:
1333:raise
1334:child_exception = pickle.loads(data)

*** 1335:raise child_exception

1336:
1337:
1338:def _handle_exitstatus(self, sts,

_WIFSIGNALED=os.WIFSIGNALED, 1339:_WTERMSIG=os.WTERMSIG,
_WIFEXITED=os.WIFEXITED, Exception: OSError: [Errno 2] No such file or
directory

ERROR: Function failed: relocatable_binaries_preprocess
ERROR: Logfile of failure stored in:
/local/p0382-cutting-edge_2014-11-21/tmp/work/x86_64-linux/quilt-native/0
.6
4-r0/temp/log.do_populate_sysroot.12966 ERROR: Task 11
(/local/poky-cutting-edge/meta/recipes-devtools/quilt/quilt-native_0.64.b
b,
do_populate_sysroot) failed with exit code '1'
=
==
==

Sadly, I don't see enough info in this error trace to really tell me
what file/directory is missing (i.e. what the real problem is)

Re: [yocto] Dumping sysvinit

2015-09-21 Thread Mike Looijmans


On 21-09-15 12:48, Andy Pont wrote:

Hi Mike,


Back to plan A then, trying to figure out how to get Busybox init and

mdev as the defaults in the image.

Create your own distro, here's an example that uses mdev:

https://github.com/topic-embedded-products/meta-
topic/blob/master/conf/distro/tiny.conf


Thanks for pointing me in the direction of this.  I have cloned it and used
it as the basis of my distro, tweaked it a bit and it is starting to behave
how I want.  There are a few anomalies that I haven't managed to figure out
yet...

Despite having VIRTUAL-RUNTIME_initscripts = "" the root file system still
contains /etc/rcX.d directories

On other embedded Linux projects that boot using Busybox init the
/etc/init.d directory contained the individual service start and kill files
e.g. S50-dropbear and K50-dropbear but I can't see how to make Yocto
populate this directory in that form.

Thoughts and guidance from anyone would be much appreciated!


I didn't go as far as attempting to get rid of initscripts as well. I just 
patched the initscripts to remove the things I did not want in a 
do_install_append.


Many recipes will create /etc/rcX.d entries to start/stop things.



Kind regards,

Mike Looijmans
System Expert

TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
Telefax: +31 (0) 499 33 69 70
E-mail: mike.looijm...@topicproducts.com
Website: www.topicproducts.com

Please consider the environment before printing this e-mail





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

Re: [yocto] bitbake error

2015-09-21 Thread Paul Eggleton

On Monday 21 September 2015 07:55:35 Gary Thomas wrote:
> On 2015-09-21 07:38, Paul Eggleton wrote:
> > On Monday 21 September 2015 07:10:00 Gary Thomas wrote:
> >> When trying to build using latest Poky/Yocto master
> >> (7b86c771c80d0759c2ca0e57c46c4c966f89c49e) I'm getting this error:
> >> 
> >> =
> >> === = Build Configuration:
> >> BB_VERSION= "1.27.1"
> >> BUILD_SYS = "x86_64-linux"
> >> NATIVELSBSTRING   = "Ubuntu-15.04"
> >> TARGET_SYS= "arm-amltd-linux-gnueabi"
> >> MACHINE   = "teton-p0382"
> >> DISTRO= "amltd"
> >> DISTRO_VERSION= "1.8+snapshot-20150921"
> >> TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard
> >> cortexa9" TARGET_FPU= "vfp-neon"
> >> meta  = "master:7b86c771c80d0759c2ca0e57c46c4c966f89c49e"
> >> 
> >> ERROR: Error executing a python function in
> >> /local/poky-cutting-edge/meta/recipes-devtools/quilt/quilt-native_0.64.bb
> >> :
> >> 
> >> The stack trace of python calls that resulted in this exception/failure
> >> was: File: 'relocatable_binaries_preprocess', lineno: 6, function:
> >> >> 
> >> 0002:def relocatable_binaries_preprocess(d):
> >>0003:
> >> rpath_replace(d.expand('/local/p0382-cutting-edge_2014-11-21/tmp/work/x86
> >> _6
> >> 
> >> 4-linux/quilt-native/0.64-r0/sysroot-destdir/'), d) 0004:
> >>0005:
> >>*** 0006:relocatable_binaries_preprocess(d)
> >>
> >>0007:
> >> File: 'relocatable_binaries_preprocess', lineno: 3, function:
> >> 
> >> relocatable_binaries_preprocess 0001:
> >>0002:def relocatable_binaries_preprocess(d):
> >>*** 0003:
> >> rpath_replace(d.expand('/local/p0382-cutting-edge_2014-11-21/tmp/work/x86
> >> _6
> >> 
> >> 4-linux/quilt-native/0.64-r0/sysroot-destdir/'), d) 0004:
> >>0005:
> >>0006:relocatable_binaries_preprocess(d)
> >> 
> >>0007:
> >> File: 'chrpath.bbclass', lineno: 7, function: rpath_replace
> >> 
> >>0003:
> >>0004:for bindir in bindirs:
> >>0005:#bb.note ("Processing directory " + bindir)
> >>0006:directory = path + "/" + bindir
> >>
> >>*** 0007:process_dir (path, directory, d)
> >>
> >>0008:
> >> File: 'chrpath.bbclass', lineno: 44, function: process_dir
> >> 
> >>0040:perms = None
> >>0041:else:
> >>0042:# Temporarily make the file writeable so we
> >>can
> >> 
> >> chrpath it 0043:os.chmod(fpath, perms|stat.S_IRWXU)
> >> 
> >>*** 0044:process_file(cmd, fpath, rootdir, baseprefix,
> >>tmpdir,
> >> 
> >> d) 0045:
> >>0046:if perms:
> >>0047:os.chmod(fpath, perms)
> >> 
> >>0048:
> >> File: 'chrpath.bbclass', lineno: 4, function: process_file_linux
> >> 
> >>0001:def process_file_linux(cmd, fpath, rootdir, baseprefix,
> >>tmpdir,
> >> 
> >> d): 0002:import subprocess as sub
> >> 
> >>0003:
> >>*** 0004:p = sub.Popen([cmd, '-l',
> >> 
> >> fpath],stdout=sub.PIPE,stderr=sub.PIPE) 0005:err, out =
> >> p.communicate()
> >> 
> >>0006:# If returned succesfully, process stderr for results
> >>0007:if p.returncode != 0:
> >>0008:return
> >> 
> >> File: '/usr/lib/python2.7/subprocess.py', lineno: 710, function: __init__
> >> 
> >>0706:cwd, env, universal_newlines,
> >>0707:startupinfo, creationflags,
> >> 
> >> shell, to_close, 0708:p2cread, p2cwrite,
> >> 
> >>0709:c2pread, c2pwrite,
> >>
> >>*** 0710:errread, errwrite)
> >>
> >>0711:excep

[yocto] OpenEmbedded Developers European Meeting in Dublin after ELCE and YP dev day

2015-09-21 Thread Philip Balister

Just a reminder we will have a meeting on Oct 9 in Dublin after ELCE and
the YP developer day.

This is a good place to meet other OE developers and discuss your issues
and concerns. All OpenEmbedded developers/users are welcome.

Please add your name to the attendee list here:

http://openembedded.org/wiki/OEDEM_2015

Soon we'll try and start beating the suggested topics into a more
organized agenda so we can focus our time together.

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

Re: [yocto] [OE-core] packageconfig for non-autotooled project

2015-09-21 Thread Trevor Woerner

Hey Khem,

On 09/21/15 13:03, Khem Raj wrote:
>
> Look at the patches I have posted for raspberry pi layer
>

Found them. Awesome, thanks! :-)
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

Re: [yocto] packageconfig for non-autotooled project

Re: [yocto] specify compiler version in recipe

Re: [yocto] bitbake error

[yocto] bitbake error

Re: [yocto] Dumping sysvinit

[yocto] Change in bitbake behaviour?

Re: [yocto] bitbake error

Re: [yocto] packageconfig for non-autotooled project

[yocto] specify compiler version in recipe

Re: [yocto] packageconfig for non-autotooled project

Re: [yocto] [OE-core] packageconfig for non-autotooled project

[yocto] packageconfig for non-autotooled project

Re: [yocto] libsoup license

Re: [yocto] bitbake error

Re: [yocto] Dumping sysvinit

Re: [yocto] bitbake error

[yocto] OpenEmbedded Developers European Meeting in Dublin after ELCE and YP dev day

Re: [yocto] [OE-core] packageconfig for non-autotooled project

19 matches

Site Navigation

Mail list logo

Footer information