Re: [yocto] useradd-example.bb

[Fred Ollinger]

How are you deploying the final image on your device?


From: yocto-boun...@yoctoproject.org  on behalf 
of Jean-Pierre Sainfeld 
Sent: Tuesday, February 13, 2018 1:32 PM
To: yocto@yoctoproject.org
Subject: [yocto] useradd-example.bb

Hi,
I am working on yocto system at the jethro rev level.
I am looking to use the meta-skeleton 
useradd-example.bb recipe
So far I have been successful in adding the required users and group
and creating files in the /usr/share directory
The current issue I am facing is the ownership of the created file
I see the right permissions at the do_install() time
however when the image is loaded in the target
those files are reverted to the root:root permissions

The requirement of our platform is that we can create specific users and
make some specific processes  and data files having the proper uid and ueid.

I have been able to do all this successfully on the target
but not through the yocto build system

Any assistance in this regard would be fantastic and very cool :-)



--
Jean-Pierre Sainfeld
408-508-1741
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] How to add libudev.h

[Fred Ollinger]

I belive this goes in your .bb file:

DEPENDS = " \
udev \
"

RDEPENDS_${PN} = " \
udev \
"

Also, you probably need the right flags for libudev.

Here are docs on that:

https://www.freedesktop.org/software/systemd/man/libudev.html

Of course, you need to tailor your build system to use these and incorporate 
this into your project.

I like automake so here's how to use pkgconfig with automake:

https://autotools.io/pkgconfig/pkg_check_modules.html

NOTE: systemd also provides libudev so if you have systemd, it's likely getting 
installed there and conflicts with udev, but I'm not sure, so you want to look 
into this as well. When I installed source for my debian jessie, I got systemd, 
and not udev sources. YMMV.

Frederick


From: yocto-boun...@yoctoproject.org  on behalf 
of mickael 
Sent: Thursday, November 3, 2016 4:55 AM
To: yocto@yoctoproject.org
Subject: [yocto]  How to add libudev.h

Hi all, i need to build a lib --> openZwave (on a imx6 card) libudev.h.
I have this error during the build :
/home/root/openzwave-1.4.164/cpp/hidapi/linux/hid.c:44:21: fatal error:
libudev.h: No such file or directory
I have tried to add udev to my local.conf but this not resolve the problem.
How i can add it to my build please ?
--
___
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] How to add my own c++ project into a Yocto distro

[Fred Ollinger]

Here's how to write a recipe:


http://www.yoctoproject.org/docs/1.6/dev-manual/dev-manual.html#new-recipe-writing-a-new-recipe


When we started, we also had custom Makefiles. However, we found it was easier 
to add our recipes to automake before making a bitbake recipe.

Automake is a challenge to get started, but worth learning.

I don't regret our move to it.

There are other options that work equally in yocto, though, like cmake.


https://www.gnu.org/software/automake/manual/html_node/Hello-World.html


From: yocto-boun...@yoctoproject.org  on behalf 
of Karim ATIKI 
Sent: Friday, September 23, 2016 12:53 PM
To: yocto@yoctoproject.org
Subject: [yocto] How to add my own c++ project into a Yocto distro


Hi all,


I have setup a Poky distribution based on a core-image-sato image for both 
RaspberryPi and Toradex Colibri T20.

I have an X11 environment working fine.


Right now, I need to compile our software we developped.

I basically need to fetch SVN repositories and finally to launch a makefile to 
get everyting work.

The makefile is however not based on autotools. It's a custom makefiles with 
regular dependencies.


I just don't know how to achieve this step in Yocto ?

Should I add a recipe ?

Is there a link that describes what I need to achieve ?


Thanks


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

Re: [yocto] Compilation error

[Fred Ollinger]

Smells like you didn't include a file.


man 2 close says:


#include 


Frederick


From: yocto-boun...@yoctoproject.org  on behalf 
of Rudolf Streif 
Sent: Monday, September 12, 2016 6:53 PM
To: Vijayakumar Badiger
Cc: Yocto Discussion Mailing List
Subject: Re: [yocto] Compilation error


What recipe? Ideally you want to fix the code and add the function declaration.

Kind regards,
Rudolf J Streif

On Sep 12, 2016 6:26 PM, "Vijayakumar Badiger" 
> wrote:
Hello All,

I am getting an compilation error like below. Can you pls let me know how to 
fix this one. Thanks in advance.



 error: implicit declaration of function 'close' 
[-Werror=implicit-function-declaration]
| close(fd);

Cheers,
Vijay

--
___
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] where to find license files?

[Fred Ollinger]

I'm working on getting a list of license files and I don't know where to get 
the exact text of each license.

Is there a place where this is provided by yocto?

For example, is there some directory which has all the license files?

I see there's an md5sum for each file so I assume this is the case.

Thanks in advance.

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

[yocto] ubuntu xenial support

[Fred Ollinger]

Anyone using Ubuntu Xenial release yet?

Any tricks to get it working?

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

Re: [yocto] Mounting USB drives on a "read-only-rootfs" based system

[Fred Ollinger]

There's also bind mounts as an option.


   The bind mounts.
  Since Linux 2.4.0 it is possible to remount part of the file 
hierarchy somewhere else.  The call is:

 mount --bind olddir newdir

  or by using this fstab entry:

 /olddir /newdir none bind

  After this call the same contents are accessible in two places.  
One can also remount a single  file  (on  a
  single file).


From: yocto-boun...@yoctoproject.org  on behalf 
of Burton, Ross 
Sent: Tuesday, June 14, 2016 7:28 AM
To: Jeffrey D Boyer
Cc: yocto@yoctoproject.org; Christopher Larson
Subject: Re: [yocto] Mounting USB drives on a "read-only-rootfs" based system


On 14 June 2016 at 14:48, Jeffrey D Boyer 
> wrote:
FYI, I'm running 3.14 kernel.  Is this a job for aufs?  If so, how would I go 
about configuring it?

If you want to support arbitrary mounts then it's probably simplest to either 
change /media to be a symlink to /run/media, or put a tmpfs on /media.

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

Re: [yocto] How to execute a git submodule init/update?

[Fred Ollinger]

 $ git submodule init

 $ git submodule update


Also, there's git submodule foreach which allows you to do the same thing to 
each submodule (such as checkout a different branch).


Frederick


From: yocto-boun...@yoctoproject.org  on behalf 
of Burton, Ross 
Sent: Monday, June 6, 2016 3:06 AM
To: s.jar...@esa-grimma.de
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] How to execute a git submodule init/update?


On 6 June 2016 at 10:39, 
> wrote:
I have a git source which need some submodules. For that I need to execute "git 
submodule init" and "git submodule update". Any idea how to do it in a comon 
way?

Use the gitsm: fetcher, which will do that for you.

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

Re: [yocto] mount bind /var/lib and package management

[Fred Ollinger]

Bind mount can allow mount to be two places:

>From the mount manpage:

"   The bind mounts.
  Since Linux 2.4.0 it is possible to remount part of the file 
hierarchy somewhere else.  The call is:

 mount --bind olddir newdir"

If you do this, then you have your files on tmpfs.

Frederick

From: yocto-boun...@yoctoproject.org  on behalf 
of Martin Townsend 
Sent: Wednesday, May 25, 2016 8:07 AM
To: yocto@yoctoproject.org
Subject: [yocto] mount bind /var/lib and package management

Hi,

When using a read only rootfs it mount --binds /var/lib into
/var/volatile/lib which lives in tmpfs and makes sense.  The problem
is that I use dpkg but I'm assuming other package management tools use
/var/lib as their admin dir.

Wouldn't this break package updates as the dpkg database files etc
will then be updated in tmpfs so a power cycle would means the changes
are lost? Or am I missing something?

I tried to mount bind all directories except dpkg which I managed to
get working but other systemd services failed as they expected
/var/lib to be writeable (the service that creates /var/lib/machines).
I suppose I could alter this to remount / rw first but gave up at this
point.

The next thing I tried was to use a new admindir for dpkg, ie
/lib/dpkg which I have working but I had to hack a lot of files
changing /var/lib to /lib including files for apt-get native.  I'm not
confident that I've got them all.

Is there another solution I haven't thought of?

Thanks in advance,
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] Recipe that creates empty /var/log directory is auto-mounted to /var/volatile/log

[Fred Ollinger]

Some people choose a read-only file system. Thus /var/log is not writable.


However, some software expects to use the hard coded path of /var/log.


Thus, there's a symlink to the ramdisk to solve both problems.


From: yocto-boun...@yoctoproject.org  on behalf 
of Paul Knopf 
Sent: Monday, May 9, 2016 7:02 AM
To: yocto@yoctoproject.org
Subject: [yocto] Recipe that creates empty /var/log directory is auto-mounted 
to /var/volatile/log

I have a simple recipe that places files on the system.

-
do_install() {
  # create this directory, because our "normal" fstab file will mount a log 
partition to it.
  install -d ${D}/var/log
  install -d ${D}${sysconfdir}
  install -m 0644 ${WORKDIR}/fstab-normal ${D}${sysconfdir}/fstab
}
-

The fstab-normal file has an entry that mounts a partition to this created 
/var/log directory.

-
/dev/mmcblk0p3   /var/log auto   defaults  0  0
-

However, when the package get's created, /var/log gets pointed to 
/var/volatile/log. Where is this happening, and why?

-
pknopf@ubuntu:~/Git/recipes/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/base-files-fstab-normal/1.0-r0/package$
 tree
.
??? etc
?   ??? fstab
??? var
??? log -> volatile/log
??? volatile
??? log

-

Thanks,
Paul Knopf
Software Engineer
Med X Change, Inc
pkn...@medxchange.com
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Problems building core-minimal-rt on Jethro (2.0.1) and Krogoth (2.1)

[Fred Ollinger]

Perhaps you could cd to the source directory and do:

 $ git pull

Then try to rebuild.

Frederick

From: yocto-boun...@yoctoproject.org  on behalf 
of Ronald Oakes 
Sent: Wednesday, May 4, 2016 7:02 AM
To: Yocto discussion list
Subject: [yocto] Problems building core-minimal-rt on Jethro (2.0.1) and
Krogoth (2.1)

My project will need to be real-time (we're probably putting a crystal
controlled clock in), so I'd like to have the real-time kernel.  So,
I've been attempting to build core-minimal-rt on both 2.0.1 and 2.1.
I get errors on both, albeit different errors.

Jethro:

On 2.0.1, the do-patch for linux-yocto-rt-* fails, ultimately with the
message: "Your branch is behind 'origin/standard/preempt-rt/base' by
691 commits, and can be fast-forwarded." followed by "(use "git pull"
to update your local branch)"

I get this error on all distros, including poky-bleeding.  I've not
been successful in disabling the mirrors just for linux-yocto-rt.  I
am now trying a build, albeit on my slow machine (two cores, where if
I don't force bitbake into running one task at a time, it hangs),
after deleting everything except the conf directory to see if that
makes any difference

Krogoth:

On 2.1, the error message occurs very quickly:

ERROR: Nothing PROVIDES 'linux-yocto-rt' (but
/home/ron/yocto_2.1/poky/meta/recipes-rt/images/core-image-rt.bb
DEPENDS on or otherwise requires it)
ERROR: linux-yocto-rt was skipped: PREFERRED_PROVIDER_virtual/kernel
set to linux-yocto, not linux-yocto-rt
ERROR: linux-yocto-rt was skipped: PREFERRED_PROVIDER_virtual/kernel
set to linux-yocto, not linux-yocto-rt
NOTE: Target 'linux-yocto-rt' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['linux-yocto-rt']
NOTE: Target 'core-image-rt' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['core-image-rt', 'linux-yocto-rt']
ERROR: Required build target 'core-image-rt' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-rt', 'linux-yocto-rt']

---

Any clues as how to work around either?

Ron Oakes
--
___
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] Antwort: Re: how to configure the build packages of a makefile based libary

[Fred Ollinger]

I don't know why that won't work.


Note, if you don't set the PREFIX, they will add /usr/local anyway. Perhaps 
that's the problem.


Here's the relevant Makefile bits for the others to look at:


# Installation related variables and target
PREFIX?=/usr/local
INCLUDE_PATH?=include/hiredis
LIBRARY_PATH?=lib
PKGCONF_PATH?=pkgconfig
INSTALL_INCLUDE_PATH= $(DESTDIR)$(PREFIX)/$(INCLUDE_PATH)
INSTALL_LIBRARY_PATH= $(DESTDIR)$(PREFIX)/$(LIBRARY_PATH)
INSTALL_PKGCONF_PATH= $(INSTALL_LIBRARY_PATH)/$(PKGCONF_PATH)



install: $(DYLIBNAME) $(STLIBNAME) $(PKGCONFNAME)
mkdir -p $(INSTALL_INCLUDE_PATH) $(INSTALL_LIBRARY_PATH)
$(INSTALL) hiredis.h async.h read.h sds.h adapters $(INSTALL_INCLUDE_PATH)
$(INSTALL) $(DYLIBNAME) $(INSTALL_LIBRARY_PATH)/$(DYLIB_MINOR_NAME)
cd $(INSTALL_LIBRARY_PATH) && ln -sf $(DYLIB_MINOR_NAME) $(DYLIBNAME)
$(INSTALL) $(STLIBNAME) $(INSTALL_LIBRARY_PATH)
mkdir -p $(INSTALL_PKGCONF_PATH)
$(INSTALL) $(PKGCONFNAME) $(INSTALL_PKGCONF_PATH)



From: s.jar...@esa-grimma.de <s.jar...@esa-grimma.de>
Sent: Thursday, April 28, 2016 9:09 AM
To: Burton, Ross
Cc: Fred Ollinger; yocto@yoctoproject.org
Subject: Antwort: Re: [yocto] how to configure the build packages of a makefile 
based libary

Hej

sorry - that does not work. Maybe you can show me some working/common code.

Do I have to create the FILE_${PV} or/and FILE_${PV}-dev, FILE_${PV}-static?

The builded files go into the Git dir & the autotools-brokensep is generating 
the package dir. I repeat my question: What are the commands in the bb file to 
build the packages (release, static, dev, whatever ...)?

Sorry - I do not understand at all the steps and theire parameters to build a 
libary. Is there somewhere an example given?

Below my bb file and the console error print.

 libhiredis 
SUMMARY = "libhiredis"
SECTION = "sek4"
LICENSE = "COPYING"
LIC_FILES_CHKSUM = 
"file://${WORKDIR}/git/COPYING;md5=d84d659a35c666d23233e54503aaea51"

# 0.13.3
# SRCREV = "010756025e8cefd1bc66c6d4ed3b1648ef6f1f95"
SRC_URI = "git://github.com/redis/hiredis.git;rev=v0.13.3"

S = "${WORKDIR}/git/"

# we need to pass the Cxx parameter extra to the make call
EXTRA_OEMAKE = "'CC=${CC}' 'RANLIB=${RANLIB}' 'AR=${AR}' 'CFLAGS=${CFLAGS} 
-I${S}/include' 'BUILDDIR=${S}' 'DESTDIR=${D}'"

inherit autotools-brokensep

do_compile() {
oe_runmake all 'CC=${CC}'
}

do_install() {
oe_runmake install 'DESTDIR=${D}'
}
FILES_${PN} += "/user/local"


### consol error ###
ERROR: QA Issue: libhiredis: Files/directories were installed but not shipped 
in any package:
  /usr/local
  /usr/local/lib
  /usr/local/include
  /usr/local/lib/libhiredis.so
  /usr/local/lib/libhiredis.so.0.13
  /usr/local/lib/libhiredis.a
  /usr/local/lib/.debug
  /usr/local/lib/pkgconfig
  /usr/local/lib/.debug/libhiredis.so.0.13
  /usr/local/lib/pkgconfig/hiredis.pc
  /usr/local/include/hiredis
  /usr/local/include/hiredis/sds.h
  /usr/local/include/hiredis/read.h
  /usr/local/include/hiredis/async.h
  /usr/local/include/hiredis/hiredis.h
  /usr/local/include/hiredis/adapters
  /usr/local/include/hiredis/adapters/glib.h
  /usr/local/include/hiredis/adapters/macosx.h
  /usr/local/include/hiredis/adapters/libev.h
  /usr/local/include/hiredis/adapters/libevent.h
  /usr/local/include/hiredis/adapters/qt.h
  /usr/local/include/hiredis/adapters/libuv.h
  /usr/local/include/hiredis/adapters/ae.h
  /usr/local/include/hiredis/adapters/ivykis.h
Please set FILES such that these items are packaged. Alternatively if they are 
unneeded, avoid installing them or delete them within do_install.
libhiredis: 24 installed and not shipped files. [installed-vs-shipped]
NOTE: Tasks Summary: Attempted 388 tasks of which 375 didn't need to be rerun 
and all succeeded.

Mit freundlichen Grüßen

Stefan Jaritz
Entwickler


ESA Elektroschaltanlagen Grimma GmbH
Broner Ring 30
04668 Grimma
Telefon: +49 3437 9211 176
Telefax: +49 3437 9211 26
E-Mail: s.jar...@esa-grimma.de
Internet: www.esa-grimma.de


Geschäftsführer:
Dipl.-Ing. Jörg Gaitzsch
Jörg Reinker

Sitz der Gesellschaft: Grimma
Ust.-ID: DE 141784437
Amtsgericht: Leipzig, HRB 5159
Steuernummer: 238/108/00755


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten
haben, informieren Sie bitte sofort den Absender und löschen Sie diese
Nachricht. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail
ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you are
not the intended recipient (or have received this e-mail in error) please
notify the sender immediately and destroy this e-mail. Any unauthorized
copying, disclosure or distribution of the material in thi

Re: [yocto] how to configure the build packages of a makefile based libary

[Fred Ollinger]

Add to bb recipe:


FILES_${PN} += "/usr/local"


Section 9.2:


https://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#qa-errors-and-warnings




From: yocto-boun...@yoctoproject.org  on behalf 
of Burton, Ross 
Sent: Thursday, April 28, 2016 5:44 AM
To: s.jar...@esa-grimma.de
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] how to configure the build packages of a makefile based 
libary


On 28 April 2016 at 13:09, 
> wrote:
ERROR: QA Issue: libhiredis: Files/directories were installed but not shipped 
in any package:
  /usr/local

It either hard-codes /usr/local as the prefix, or if it respects a prefix 
variable you should also pass in ${prefix} ${libdir} ${includedir} and so on.

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

Re: [yocto] MySQL recipe for yocto

[Fred Ollinger]

| NOTE: nothing to configure


Seems like "configure" file is not there.


That sometimes happens when a source code tree is first checked out for 
developers.


Sometimes there's an "autogen.sh" or you have to run stuff including but not 
limited to "aclocal;autoconf".


I suggest the next step:


1. Post the .bb file here for mysql that you have so far.


2. Look into the source code dir for mysql and look for a "configure" file.


3. Read up on the usual directions on how mysql is now built from your source 
code. Is there a README or the like in there?


4. For a quick sanity test, build the code for your PC to ensure that you can 
do this and you know how the process works.


5. We can take the results of all the rest and fix the .bb file.


Frederick


From: Moti Cohen <motic.m...@gmail.com>
Sent: Wednesday, April 20, 2016 1:39 PM
To: Fred Ollinger
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] MySQL recipe for yocto

OK,
I tried it and the patches errors went away, thanks !
Now, I'm facing a new one related to the do_configure:

ERROR: Function failed: do_configure (log file is located at 
/home/yocto/yocto/build_yocto/build/tmp/work/x86_64-linux/mysql5-native/5.6.29-r0/temp/log.do_configure.7221)
ERROR: Logfile of failure stored in: 
/home/yocto/yocto/build_yocto/build/tmp/work/x86_64-linux/mysql5-native/5.6.29-r0/temp/log.do_configure.7221
Log data follows:
| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing shell function autotools_preconfigure
| DEBUG: Shell function autotools_preconfigure finished
| DEBUG: Executing python function autotools_copy_aclocals
| DEBUG: Python function autotools_copy_aclocals finished
| DEBUG: Executing shell function do_configure
| NOTE: nothing to configure
| sed: can't read 
/home/yocto/yocto/build_yocto/build/tmp/work/x86_64-linux/mysql5-native/5.6.29-r0/mysql-5.6.29/sql/share/Makefile:
 No such file or directory
| WARNING: exit code 2 from a shell command.
| ERROR: Function failed: do_configure (log file is located at 
/home/yocto/yocto/build_yocto/build/tmp/work/x86_64-linux/mysql5-native/5.6.29-r0/temp/log.do_configure.7221)
ERROR: Task 1373 
(/home/yocto/yocto/build_yocto/sources/meta-openembedded/meta-oe/recipes-support/mysql/mysql5-native_5.6.29.bb<http://mysql5-native_5.6.29.bb>,
 do_configure) failed with exit code '1'

the recipe's .inc file include the below line, however it looks like the 
makefile do not exist.

do_configure_append() {
 sed -i /comp_err/d ${S}/sql/share/Makefile
}

Again, any help will be appreciated.




On Wed, Apr 20, 2016 at 10:12 PM, Fred Ollinger 
<fred.ollin...@seescan.com<mailto:fred.ollin...@seescan.com>> wrote:
You can get rid of the patches in the bb file.


Look for SRC_URI


See any .patch files and remove them and try to build again.


Please post build errors.


Frederick


From: Moti Cohen <motic.m...@gmail.com<mailto:motic.m...@gmail.com>>
Sent: Wednesday, April 20, 2016 12:08 PM
To: Fred Ollinger
Cc: yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>
Subject: Re: [yocto] MySQL recipe for yocto

Thanks Fred,

I actually tried it and replaced the PV to a newer one, i used 5.6.29 instead 
of 5.1.40 which is the latest "real" MySQL supported by openembedded. I also 
added the relevant SHA numbers etc.

The problem is that the recipe includes quite a few patches that are now 
showing many errors when applied during the build. I guess that these patches 
are related to the original 5.1.40 version and I'm not sure they should be 
applied to the newer one. Unfortunetly, as I'm not an expert, it seems like it 
will be a difficult task for me to clean these errors.

I realy hope there's a simpler way go about it :)



On Wed, Apr 20, 2016 at 8:25 PM, Fred Ollinger 
<fred.ollin...@seescan.com<mailto:fred.ollin...@seescan.com><mailto:fred.ollin...@seescan.com<mailto:fred.ollin...@seescan.com>>>
 wrote:
I'd start with the mysql recipe and update the source reference and try to 
build it.


If this fails, you might need to change some other things.


Here's a howto on writing a recipe:


https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#new-recipe-writing-a-new-recipe




From: 
yocto-boun...@yoctoproject.org<mailto:yocto-boun...@yoctoproject.org><mailto:yocto-boun...@yoctoproject.org<mailto:yocto-boun...@yoctoproject.org>>
 
<yocto-boun...@yoctoproject.org<mailto:yocto-boun...@yoctoproject.org><mailto:yocto-boun...@yoctoproject.org<mailto:yocto-boun...@yoctoproject.org>>>
 on behalf of Moti Cohen 
<motic.m...@gmail.com<mailto:motic.m...@gmail.com><mailto:motic.m...@gmail.com<mailto:motic.m...@gmail.com>>>
Sent: Wednesday, April 20, 2016 10:18 AM
To: 
yoc

Re: [yocto] MySQL recipe for yocto

[Fred Ollinger]

You can get rid of the patches in the bb file.


Look for SRC_URI


See any .patch files and remove them and try to build again.


Please post build errors.


Frederick


From: Moti Cohen <motic.m...@gmail.com>
Sent: Wednesday, April 20, 2016 12:08 PM
To: Fred Ollinger
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] MySQL recipe for yocto

Thanks Fred,

I actually tried it and replaced the PV to a newer one, i used 5.6.29 instead 
of 5.1.40 which is the latest "real" MySQL supported by openembedded. I also 
added the relevant SHA numbers etc.

The problem is that the recipe includes quite a few patches that are now 
showing many errors when applied during the build. I guess that these patches 
are related to the original 5.1.40 version and I'm not sure they should be 
applied to the newer one. Unfortunetly, as I'm not an expert, it seems like it 
will be a difficult task for me to clean these errors.

I realy hope there's a simpler way go about it :)



On Wed, Apr 20, 2016 at 8:25 PM, Fred Ollinger 
<fred.ollin...@seescan.com<mailto:fred.ollin...@seescan.com>> wrote:
I'd start with the mysql recipe and update the source reference and try to 
build it.


If this fails, you might need to change some other things.


Here's a howto on writing a recipe:


https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#new-recipe-writing-a-new-recipe




From: yocto-boun...@yoctoproject.org<mailto:yocto-boun...@yoctoproject.org> 
<yocto-boun...@yoctoproject.org<mailto:yocto-boun...@yoctoproject.org>> on 
behalf of Moti Cohen <motic.m...@gmail.com<mailto:motic.m...@gmail.com>>
Sent: Wednesday, April 20, 2016 10:18 AM
To: yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>
Subject: [yocto] MySQL recipe for yocto

Hi all,
this is my 1'st post to this list so I hope I'm doing it right :)

I need to add MySQL for my yocto build.
Looking online for a recipe - i found that there is one for MySQL under:
/meta-openembedded/meta-oe/recipes-support/mysql/..
The thing is that instead of MySQL, the recipe reffers to MariaDB which is a 
kind of a drop-in replacemnet and since I need to have the "real" MySQL in my 
build - I cannot use it.
looking into history log of mysql in the meta-openembedded git, it can be seen 
the the switch between MySQL and MariaDB was made at 2013 and from then onwards 
it's MariaDB.

http://cgit.openembedded.org/meta-openembedded/commit/meta-oe/recipes-support/mysql?id=72e23c12296fbc77193898c38426add58d0c2d71

Now to the question, do you know how can I add the "real" MySQL to my build ?
looking before 2013 at the meta-openembedded git i can find a recipe for MySQL 
which seems to support a "real" MySQL however, it's very old version (5.1) and 
I'm not sure how and if I can update it to one of the latest (e.g. MySQL 5.6).

Will appriciate any feedback on this.
Thanks in advance,
Motico

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

Re: [yocto] MySQL recipe for yocto

[Fred Ollinger]

I'd start with the mysql recipe and update the source reference and try to 
build it.


If this fails, you might need to change some other things.


Here's a howto on writing a recipe:


https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#new-recipe-writing-a-new-recipe




From: yocto-boun...@yoctoproject.org  on behalf 
of Moti Cohen 
Sent: Wednesday, April 20, 2016 10:18 AM
To: yocto@yoctoproject.org
Subject: [yocto] MySQL recipe for yocto

Hi all,
this is my 1'st post to this list so I hope I'm doing it right :)

I need to add MySQL for my yocto build.
Looking online for a recipe - i found that there is one for MySQL under:
/meta-openembedded/meta-oe/recipes-support/mysql/..
The thing is that instead of MySQL, the recipe reffers to MariaDB which is a 
kind of a drop-in replacemnet and since I need to have the "real" MySQL in my 
build - I cannot use it.
looking into history log of mysql in the meta-openembedded git, it can be seen 
the the switch between MySQL and MariaDB was made at 2013 and from then onwards 
it's MariaDB.

http://cgit.openembedded.org/meta-openembedded/commit/meta-oe/recipes-support/mysql?id=72e23c12296fbc77193898c38426add58d0c2d71

Now to the question, do you know how can I add the "real" MySQL to my build ?
looking before 2013 at the meta-openembedded git i can find a recipe for MySQL 
which seems to support a "real" MySQL however, it's very old version (5.1) and 
I'm not sure how and if I can update it to one of the latest (e.g. MySQL 5.6).

Will appriciate any feedback on this.
Thanks in advance,
Motico
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Debian Stretch build error "Install SDL devel"

[Fred Ollinger]

Confirmed that commenting out the following in my build/conf/local.conf allowed 
me to build qemu-native. (I don't need qemu at all).

# PACKAGECONFIG_append_pn-qemu-native = " sdl"
# PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
# ASSUME_PROVIDED += "libsdl-native"

Thank-you for the quick and accurate reply.

Frederick

From: Andre McCurdy <armccu...@gmail.com>
Sent: Thursday, March 31, 2016 8:30 PM
To: Fred Ollinger
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Debian Stretch build error "Install SDL devel"

On Thu, Mar 31, 2016 at 3:55 PM, Fred Ollinger
<fred.ollin...@seescan.com> wrote:
> I know that Debian Stretch is not supported, but I'd like to help shake out 
> the errors to get support.
>
>
> I'm on poky
>
>
> commit 9fd145d27ec479668fac490a9f1078089f22bf59
>
>
> I tried to build qemu-native and it failed with the following:
>
>
> | ERROR: User requested feature sdl
> |configure was not able to find it.
> |Install SDL devel
>
>
> libsdl1.2-dev is installed.
>
>
> Any ideas?

See the "Qemu configuration" section of conf/local.conf.

You can either disable qemu support for SDL by commenting out the
following lines:

  PACKAGECONFIG_append_pn-qemu-native = " sdl"
  PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"

Or (if you do actually need qemu with SDL support enabled) try using
OE's version of libsdl instead of the one provided by the host system,
by commenting out:

  ASSUME_PROVIDED += "libsdl-native"

Note that using OE's version of libsdl was only recently enabled in
OE's master branch (see below) so may or may not work with the Dizzy
based release you are using.

  
http://git.openembedded.org/openembedded-core/commit/?id=81f009d173f24501ab0e04d845db74ecb5f8e332


>
> Frederick
> --
> ___
> 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] Debian Stretch build error "Install SDL devel"

[Fred Ollinger]

I know that Debian Stretch is not supported, but I'd like to help shake out the 
errors to get support.


I'm on poky


commit 9fd145d27ec479668fac490a9f1078089f22bf59


I tried to build qemu-native and it failed with the following:


| ERROR: User requested feature sdl
|configure was not able to find it.
|Install SDL devel


libsdl1.2-dev is installed.


Any ideas?


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

[yocto] Qt5 embedded Japanese input

[Fred Ollinger]

There are methods in desktop linux which allow one to input Japanese (and other 
non-Latin language) text into text fields.


Does anyone have any experience with integrating a stand alone solution into a 
Qt5 application?


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

Re: [yocto] [OE-core] [oe] OEDAM, April 8 in San Diego after ELC

[Fred Ollinger]

I'm coming and I'm probably brining another person.

I still have to make the wiki account which failed for some reason before.

Frederick

From: yocto-boun...@yoctoproject.org  on behalf 
of Trevor Woerner 
Sent: Wednesday, March 23, 2016 2:08 PM
To: akuster808; openembedded-de...@lists.openembedded.org; openembedded-core; 
Yocto Project; openembedded-memb...@lists.openembedded.org
Subject: Re: [yocto] [OE-core] [oe] OEDAM, April 8 in San Diego after ELC

On Wed 2016-03-23 @ 09:36:40 AM, akuster808 wrote:
> There are only 10 people signed up.
> Is that enough people to justify the expense room or even meet?

I have no idea what the budget might be or what a room might cost. I'll leave
it to those who do know to worry about the costs versus the benefits.

In any case I certainly think it's still worth meeting. A smaller, more
focused group can sometimes get more done than a larger group. Secondly, it's
my experience that more people always show up than sign up.

With a project like this there will always be things to discuss, and sometimes
a discussion goes better in person rather than online.

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] [PATCH] udev: Rename udev bbappend to eudev.

[Fred Ollinger]

Can someone please let me know what the reasoning behind the switch to eudev?

Sincerely,

Frederick

From: yocto-boun...@yoctoproject.org  on behalf 
of Philip Tricca 
Sent: Sunday, March 6, 2016 12:08 PM
To: mark.ha...@windriver.com
Cc: yocto@yoctoproject.org
Subject: [yocto] [PATCH] udev: Rename udev bbappend to eudev.

Required by switch to eudev in oe-core. Dropping PR since this is
effectively a new recipe.

Signed-off-by: Philip Tricca 
---
 recipes-core/eudev/eudev/init   | 144 
 recipes-core/eudev/eudev/udev-cache |  32 +++
 recipes-core/eudev/eudev_3.1.5.bbappend |   3 +
 recipes-core/udev/udev/init | 144 
 recipes-core/udev/udev/udev-cache   |  32 ---
 recipes-core/udev/udev_182.bbappend |   5 --
 6 files changed, 179 insertions(+), 181 deletions(-)
 create mode 100644 recipes-core/eudev/eudev/init
 create mode 100644 recipes-core/eudev/eudev/udev-cache
 create mode 100644 recipes-core/eudev/eudev_3.1.5.bbappend
 delete mode 100644 recipes-core/udev/udev/init
 delete mode 100644 recipes-core/udev/udev/udev-cache
 delete mode 100644 recipes-core/udev/udev_182.bbappend

diff --git a/recipes-core/eudev/eudev/init b/recipes-core/eudev/eudev/init
new file mode 100644
index 000..9a4b293
--- /dev/null
+++ b/recipes-core/eudev/eudev/init
@@ -0,0 +1,144 @@
+#!/bin/sh
+
+### BEGIN INIT INFO
+# Provides:  udev
+# Required-Start:mountvirtfs
+# Required-Stop:
+# Default-Start: S
+# Default-Stop:
+# Short-Description: Start udevd, populate /dev and load drivers.
+### END INIT INFO
+
+export TZ=/etc/localtime
+
+[ -d /sys/class ] || exit 1
+[ -r /proc/mounts ] || exit 1
+[ -x @UDEVD@ ] || exit 1
+if [ "$use_udev_cache" != "" ]; then
+   [ -f /etc/default/udev-cache ] && . /etc/default/udev-cache
+fi
+[ -f /etc/udev/udev.conf ] && . /etc/udev/udev.conf
+[ -f /etc/default/rcS ] && . /etc/default/rcS
+
+readfiles () {
+   READDATA=""
+   for filename in $@; do
+  if [ -r $filename ]; then
+  while read line; do
+  READDATA="$READDATA$line"
+  done < $filename
+  fi
+   done
+}
+
+kill_udevd () {
+pid=`pidof -x udevd`
+[ -n "$pid" ] && kill $pid
+}
+
+case "$1" in
+  start)
+export ACTION=add
+# propagate /dev from /sys
+echo "Starting udev"
+
+# Check for requireed devtmpfs before trying to start udev and
+# mount a no-existant fs.
+if ! grep -q devtmpfs /proc/filesystems
+then
+echo "Missing devtmpfs, which is required for udev to run";
+echo "Halting..."
+halt
+fi
+# mount the devtmpfs on /dev, if not already done
+LANG=C awk '$2 == "/dev" && ($3 == "devtmpfs") { exit 1 }' /proc/mounts && 
{
+mount -n -o mode=0755 -t devtmpfs none "/dev"
+}
+[ -e /dev/pts ] || mkdir -m 0755 /dev/pts
+[ -e /dev/shm ] || mkdir -m 1777 /dev/shm
+# the automount rule for udev needs /tmp directory available, as /tmp is a 
symlink
+# to /var/tmp which in turn is a symlink to /var/volatile/tmp, we need to 
make sure
+# /var/volatile/tmp directory to be available.
+mkdir -p /var/volatile/tmp
+
+# restorecon /run early to allow mdadm creating dir /run/mdadm
+test ! -x /sbin/restorecon || /sbin/restorecon -F /run
+
+# Cache handling.
+# A list of files which are used as a criteria to judge whether the udev 
cache could be reused.
+CMP_FILE_LIST="/proc/version /proc/cmdline /proc/devices /proc/atags"
+if [ "$use_udev_cache" != "" ]; then
+   if [ "$DEVCACHE" != "" ]; then
+   if [ -e $DEVCACHE ]; then
+   readfiles $CMP_FILE_LIST
+   NEWDATA="$READDATA"
+   readfiles /etc/udev/cache.data
+   OLDDATA="$READDATA"
+   if [ "$OLDDATA" = "$NEWDATA" ]; then
+   tar --directory=/ -xf $DEVCACHE > /dev/null 
2>&1
+   not_first_boot=1
+   [ "$VERBOSE" != "no" ] && echo "udev: using 
cache file $DEVCACHE"
+   [ -e /dev/shm/udev.cache ] && rm -f 
/dev/shm/udev.cache
+   else
+   # Output detailed reason why the cached 
/dev is not used
+   if [ "$VERBOSE" != "no" ]; then
+   echo "udev: udev cache not used"
+   echo "udev: we use $CMP_FILE_LIST 
as criteria to judge whether the cache /dev could be resued"
+   echo "udev: olddata: $OLDDATA"
+   echo "udev: newdata: $NEWDATA"
+

Re: [yocto] Dropping Debian 7 as supported?

[Fred Ollinger]

I run debian right now and it works great.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:Debian GNU/Linux 8.3 (jessie)
Release:8.3
Codename:   jessie

I prefer debian over ubuntu:

1. Simpler footprint so it feels more customizable out of the box. (I know that 
any linux distro is infinitely customizable, but I like a simple install out of 
the box. I feel like ubuntu was ramming more and more things down my throat).

2. I strongly believe different platforms, although are more work, also expose 
more bugs.

3. I started on debian and it's what I'm used to.

4. It makes me feel better.

5. In the past, working on a different distro forced me to be more aware of the 
details of the build process which ultimately makes me a more valuable member 
of the team. Having the attitude that things will just work for us, in my 
opinion, is a bad one for a developer. I'd rather understand things.

(#4 is my primary reason).

I'll be happy to help out with debian support if you need it.

So far, I have zero problems, and it would be nice to not see a scary message 
telling me to change distros if my distro actually works great.

Frederick

From: yocto-boun...@yoctoproject.org  on behalf 
of Nick Leverton 
Sent: Friday, February 12, 2016 5:43 AM
To: yocto@yoctoproject.org
Subject: Re: [yocto] Dropping Debian 7 as supported?

On Thursday 11 Feb 2016 14:32:50 Burton, Ross wrote:
> On 11 February 2016 at 14:21, Nick Leverton  wrote:
> > Possibly a little early - Debian 7 will be going onto LTS security support
> > for
> > two years, starting some time this month.  Quoting from
> > https://wiki.debian.org/LTS
>
> Ah yes, I'd forgotten about the LTS project and was looking at the security
> team.
>
> This does make it less clear, but it's still an old release and we can't
> support/test on everything.

I appreciate that, and I suspect the LTS efforts are of most interest to those
running production servers.  I would think anyone developing on Debian is
likely to be running stable at least.  Although I've worked at many
development companies running elderly LTS versions of Ubuntu, Fedora/Centos,
etc, I admit I've yet to meet one that ran Debian at all.

Nevertheless if I can be of any help in supporting and testing on versions of
Debian, I'm happy to do so.

Nick
--
___
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] Dropping Debian 7 as supported?

[Fred Ollinger]

My apologies.


From: Burton, Ross <ross.bur...@intel.com>
Sent: Friday, February 12, 2016 9:18 AM
To: Fred Ollinger
Cc: Nick Leverton; yocto@yoctoproject.org
Subject: Re: [yocto] Dropping Debian 7 as supported?


On 12 February 2016 at 17:14, Fred Ollinger 
<fred.ollin...@seescan.com<mailto:fred.ollin...@seescan.com>> wrote:
So far, I have zero problems, and it would be nice to not see a scary message 
telling me to change distros if my distro actually works great.

You must have missed the bit where I said that Debian 8 was being supported, I 
just wanted to drop Debian 7.

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

Re: [yocto] libQt5Network.so.5 - How does one get that please?

[Fred Ollinger]

Did you try 

 $ ldd program-name

This should tell you which libraries are missing and where it is looking.

Then you can do:

 $ find / -name libname.so

To find them.

Finally, you can fix your /etc/ld.so.conf with the path to your libs.

Then do

 $ ldconfig # refresh library cache so your libs are found

And you should be able to run your app.

Then, obviously, this can all be put into a bitbake recipe.

Frederick

From: yocto-boun...@yoctoproject.org  on behalf 
of Nathan Sowatskey 
Sent: Friday, February 5, 2016 1:13 AM
To: yocto@yoctoproject.org
Subject: Re: [yocto] libQt5Network.so.5 - How does one get that please?

It turns out that the build is correct, in that the libraries are there, but 
the test program I am using is not finding them :-/

So, for future reference, at least part what is required to work is correct in 
my build.

Regards

Nathan

> On 4 Feb 2016, at 17:39, Nathan Sowatskey  wrote:
>
> Hi
>
> My application has a dependency on libQt5Network.so.5.
>
> I have my build configured here:
>
> https://github.com/DevOps4Networks/iox-yocto-build/tree/master/conf
>
> I expect that some combination of the BBLAYERS and the IMAGE_INSTALL_append 
> should allow me to get that library in my Yocto image.
>
> I am not sure which layer has the qtnetwork recipe in it, as I can’t find 
> that here:
>
> http://layers.openembedded.org/layerindex/branch/master/layers/
>
> Any ideas gratefully received.
>
> Many thanks
>
> Nathan
>
> —
> Nathan John Sowatskey
> Consulting Engineer - Programmable Infrastructure, DevOps, IoT and SDN
> nat...@nathan.to
> www.linkedin.com/in/nathandevops
> XMPP: nathando...@im.koderoot.net
> Google: nathanjohnsowats...@gmail.com
> Skype: nathan_sowatskey
> Twitter: NathanDotTo
> GitHub: https://github.com/DevOps4Networks
> http://www.kipling.org.uk/poems_if.htm
>
> --
> ___
> 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 mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] libgcc_s not present in Yocto image

[Fred Ollinger]

The results should tell us:

 $ files /usr/bin/testprog

What are they? (Sitting on the edge of my seat.)

From: Nathan Sowatskey <nat...@nathan.to>
Sent: Friday, February 5, 2016 10:09 AM
To: Fred Ollinger
Cc: Burton, Ross; yocto@yoctoproject.org
Subject: Re: [yocto] libgcc_s not present in Yocto image

Thanks Fred.

I am using qemux86_64 on Intel i7 chips with OSX.  The target is likewise Intel.

I am assuming that is quite generic, but …

Regards

Nathan

> On 5 Feb 2016, at 19:06, Fred Ollinger <fred.ollin...@seescan.com> wrote:
>
> My guess is that the executable is not compiled for his hardware.
>
>
> Frederick
>
> 
> From: Burton, Ross <ross.bur...@intel.com>
> Sent: Friday, February 5, 2016 9:56 AM
> To: Nathan Sowatskey
> Cc: yocto@yoctoproject.org; Fred Ollinger
> Subject: Re: [yocto] libgcc_s not present in Yocto image
>
>
> On 5 February 2016 at 17:47, Nathan Sowatskey 
> <nat...@nathan.to<mailto:nat...@nathan.to>> wrote:
> find /usr/lib -name libgcc_s.so.1
> root@qemux86-64:~#
>
> I don't have that lib.
>
> As I said, libgcc_s.so.1 is in /lib, not /usr/lib.
>
> With ldd I get:
>
> ldd /usr/bin/testprog
> /usr/bin/ldd: line 117: /usr/bin/testprog: No such file or directory
>
> Well ldd appears to be having a bit of a panic.  Try objdump -p 
> /usr/bin/testprog instead.
>
> Ross

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

Re: [yocto] libgcc_s not present in Yocto image

[Fred Ollinger]

What's the result of:

 $ cat /proc/cpuinfo

(So far, it seems like my hunch was wrong.)

Frederick

From: Nathan Sowatskey <nat...@nathan.to>
Sent: Friday, February 5, 2016 10:12 AM
To: Fred Ollinger
Cc: Burton, Ross; yocto@yoctoproject.org
Subject: Re: [yocto] libgcc_s not present in Yocto image

file /usr/bin/testprog
/usr/bin/testprog: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), 
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 
2.6.24, BuildID[sha1]=26317096ed83d21bc6808f0d2d47b12de1ab31ce, not stripped

Thoughts?

> On 5 Feb 2016, at 19:10, Fred Ollinger <fred.ollin...@seescan.com> wrote:
>
> The results should tell us:
>
> $ files /usr/bin/testprog
>
> What are they? (Sitting on the edge of my seat.)
> 
> From: Nathan Sowatskey <nat...@nathan.to>
> Sent: Friday, February 5, 2016 10:09 AM
> To: Fred Ollinger
> Cc: Burton, Ross; yocto@yoctoproject.org
> Subject: Re: [yocto] libgcc_s not present in Yocto image
>
> Thanks Fred.
>
> I am using qemux86_64 on Intel i7 chips with OSX.  The target is likewise 
> Intel.
>
> I am assuming that is quite generic, but …
>
> Regards
>
> Nathan
>
>> On 5 Feb 2016, at 19:06, Fred Ollinger <fred.ollin...@seescan.com> wrote:
>>
>> My guess is that the executable is not compiled for his hardware.
>>
>>
>> Frederick
>>
>> ____
>> From: Burton, Ross <ross.bur...@intel.com>
>> Sent: Friday, February 5, 2016 9:56 AM
>> To: Nathan Sowatskey
>> Cc: yocto@yoctoproject.org; Fred Ollinger
>> Subject: Re: [yocto] libgcc_s not present in Yocto image
>>
>>
>> On 5 February 2016 at 17:47, Nathan Sowatskey 
>> <nat...@nathan.to<mailto:nat...@nathan.to>> wrote:
>> find /usr/lib -name libgcc_s.so.1
>> root@qemux86-64:~#
>>
>> I don't have that lib.
>>
>> As I said, libgcc_s.so.1 is in /lib, not /usr/lib.
>>
>> With ldd I get:
>>
>> ldd /usr/bin/testprog
>> /usr/bin/ldd: line 117: /usr/bin/testprog: No such file or directory
>>
>> Well ldd appears to be having a bit of a panic.  Try objdump -p 
>> /usr/bin/testprog instead.
>>
>> Ross
>

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

Re: [yocto] libgcc_s not present in Yocto image

[Fred Ollinger]

My guess is that the executable is not compiled for his hardware.


Frederick


From: Burton, Ross <ross.bur...@intel.com>
Sent: Friday, February 5, 2016 9:56 AM
To: Nathan Sowatskey
Cc: yocto@yoctoproject.org; Fred Ollinger
Subject: Re: [yocto] libgcc_s not present in Yocto image


On 5 February 2016 at 17:47, Nathan Sowatskey 
<nat...@nathan.to<mailto:nat...@nathan.to>> wrote:
find /usr/lib -name libgcc_s.so.1
root@qemux86-64:~#

I don't have that lib.

As I said, libgcc_s.so.1 is in /lib, not /usr/lib.

With ldd I get:

ldd /usr/bin/testprog
/usr/bin/ldd: line 117: /usr/bin/testprog: No such file or directory

Well ldd appears to be having a bit of a panic.  Try objdump -p 
/usr/bin/testprog instead.

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

Re: [yocto] libgcc_s not present in Yocto image

[Fred Ollinger]

What are results of:

 $ file testprog

Frederick

From: Nathan Sowatskey <nat...@nathan.to>
Sent: Friday, February 5, 2016 9:47 AM
To: Burton, Ross
Cc: yocto@yoctoproject.org; Fred Ollinger
Subject: Re: [yocto] libgcc_s not present in Yocto image

Hi Ross

Many thanks for following up. Fred also offered some helpful suggestions in a 
different thread.

The program in question was supplied to me by a third party for testing, so I 
shall obscure the name here and call it testprog.

It was installed by:

dpkg -i ./testprog.deb


Where the .deb file was supplied to me. I don’t know what that was built on 
though.

Then:

which testprog
/usr/bin/testprog
/usr/bin/testprog
-sh: /usr/bin/testprog: No such file or directory

Then I:

readelf -a /usr/bin/testprog | grep Shared
 0x0001 (NEEDED) Shared library: [libsnmp.so.30]
 0x0001 (NEEDED) Shared library: [libQt5Network.so.5]
 0x0001 (NEEDED) Shared library: [libQt5SerialPort.so.5]
 0x0001 (NEEDED) Shared library: [libQt5Core.so.5]
 0x0001 (NEEDED) Shared library: [libstdc++.so.6]
 0x0001 (NEEDED) Shared library: [libgcc_s.so.1]
 0x0001 (NEEDED) Shared library: [libpthread.so.0]
 0x0001 (NEEDED) Shared library: [libc.so.6]

Followed by:

find /usr/lib -name libQt5Network.so.5
/usr/lib/libQt5Network.so.5

So, I have that lib.

find /usr/lib -name libgcc_s.so.1
root@qemux86-64:~#

I don’t have that lib.

With ldd I get:

ldd /usr/bin/testprog
/usr/bin/ldd: line 117: /usr/bin/testprog: No such file or directory

So, that’s where I am at this stage.

Regards

Nathan

> On 5 Feb 2016, at 16:50, Burton, Ross <ross.bur...@intel.com> wrote:
>
>
> On 5 February 2016 at 15:24, Nathan Sowatskey <nat...@nathan.to> wrote:
> I suspect that my test program, which was supplied to me as a .deb package, 
> was compiled on Ubuntu, and so links to libgcc_s.so.1. I can’t see any 
> obvious way to get libgcc_s.so.1 on Yocto. I already have:
>
> libgcc contains /lib/libgcc_s.so.1, so it should be installed in your image 
> already:
>
> How are you determining that it isn't in your image, and that your 
> application doesn't work?
>
> Ross

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

Re: [yocto] Problem installing ath10k firmware

[Fred Ollinger]

http://linuxwireless.org/en/users/Drivers/ath10k/firmware/

Seems like you should get the firmware here:

https://github.com/kvalo/ath10k-firmware/tree/master/

and copy it here:

 $ cp firmware-2.bin_10.1.467.2-1 
/lib/firmware/ath10k/QCA988X/hw2.0/firmware-2.bin

Frederick

From: yocto-boun...@yoctoproject.org  on behalf 
of Todd Efflam 
Sent: Monday, February 1, 2016 5:14 PM
To: yocto@yoctoproject.org
Subject: [yocto] Problem installing ath10k firmware

Hello,
We're having a problem getting the ath10k firmware to run with a new
wireless card.  The card uses chip QCA9882.  We've tried installing
ath10k firmware using:
IMAGE_INSTALL_append += linux-firmware-ath10k

in combination with the following kernel configs:
CONFIG_FIRMWARE_IN_KERNEL=y
CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"

we tried adding
CONFIG_EXTRA_FIRMWARE="ath10k/QCA988X/hw2.0/firmware-2.bin
ath10k/QCA988X/hw2.0/board.bin" but this failed as it wasn't able to
locate the files.

After building, we receive the following error when booting our cpu:
ath10k: Could not fetch firmware file 'firmware-2.bin': -2

We then realized lib/firmware contained firmware-4.bin and
firmware-5.bin instead of firmware-2.bin, but after copying
firmware-4.bin to 2 we still received the same error from our cpu.

Has anyone had success getting ath10k to run with firmware-2.bin?  Any
help would be appreciated!

Best,
Todd
--
___
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] How to output all distro features in a given build?

[Fred Ollinger]

I know how to add and remove distro features.

However, what I'm after is how to dynamically list all the distro features that 
a build thinks is needs once all the files are combined together.

For example, one can look at dependencies for a _single_ package by doing:

 $ bitbake -g seescan-image-ccu-dev -u depexp

Also, one can look in the manifest file for all the included packages. This is 
great.

I'm after for a method to do the same for distro features.

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

Re: [yocto] Updating NIC drivers in older Yocto

[Fred Ollinger]

I think #2 is a reasonable solution.?


From: yocto-boun...@yoctoproject.org  on behalf 
of Dave Mulder 
Sent: Tuesday, October 13, 2015 1:30 PM
To: yocto@yoctoproject.org
Subject: [yocto] Updating NIC drivers in older Yocto

I have been using a Sandy Bridge Yocto 1.3 build for a couple years now, on 
off-the-shelf Intel PC motherboards. I also build an application.

I am now looking into using more recent motherboards. The OS boots just fine, 
but the new NICs (Intel, Realtek) are not supported by the old 3.4.11 kernel.

What's the best way to support new NICs?  I can see three options:


1.   New Yocto.  I suspect (but would be happy to be wrong) that my 
application would need to be built against a different sysroot/toolchain, which 
seems like it would cause backward-compatibility problems (can't run new 
application on old OS), and I would prefer to not have multiple builds of the 
application and have to have the host software determine which version is 
needed (it's an embedded application, and the OS is headless).

2.   New kernel, old Yocto.  I don't know that this is actually an option, 
or how new of a kernel can be used in Yocto 1.3.  If this is an option, it 
seems like my application would not need to be rebuilt.

3.   Loadable drivers for new NICs (rather than using the ones built into 
the kernel).  I don't know that this is doable either.

Are there other options?  Can a new application be built that will work with 
multiple versions of the OS?  Is that even a problem, or am I just assuming the 
worst?

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

[yocto] FILESEXTRAPATHS_prepend fails for systemd

[Fred Ollinger]

I'm trying to change my /etc/systemd/journald.conf file.


I have created a file in:


our_system/recipe-core/systemd_%.bbappend


With the contents:


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

I created a directory in the same path called "systemd" and placed our new 
version of journald.conf in it.

Then I did:

bitbake -c cleanall systemd && bitbake systemd
bitbake -c cleanall our_image && bitbake our_image

Then I checked and the old journald.conf is still installed.

What am I doing wrong?

Frederick

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

Re: [yocto] What's mounting this partition?

[Fred Ollinger]

If you have a sda1 drive, you can do:

udevadm test /sys/class/block/sda1

to get debug info.

From: yocto-boun...@yoctoproject.org  on behalf 
of Paul D. DeRocco 
Sent: Sunday, September 27, 2015 2:52 AM
To: 'Khem Raj'
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] What's mounting this partition?

> From: Khem Raj [mailto:raj.k...@gmail.com]
>
> are you installing udev-extraconf into image? IIRC that was
> doing it in my cases some time ago.

That adds some rules to /etc/udev/rules.d, including automounting. I had
that in there for a day or so, because I also need to access an external
flash drive sometimes, but it had some insoluble issues, so I took it out
again. So none of those rules are present now, nor is the mount.sh script.
There are a bunch more rules in /lib/udev/rules.d, but none have anything
to do with mounting, as far as I can see.

I wish there was a way I could see this mysterious mounting happen.
Nothing shows up in dmesg or in journalctl.

--

Ciao,   Paul D. DeRocco
Paulmailto:pdero...@ix.netcom.com

--
___
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] [systemd-devel] How to automount

[Fred Ollinger]

This is in the package: udev-extraconf

On your system look here:

/etc/udev/rules.d/automount.rules

In this file, you'll find the following rules.

The second one auto unmounts.

SUBSYSTEM=="block", ACTION=="add"RUN+="/etc/udev/scripts/mount.sh"

SUBSYSTEM=="block", ACTION=="remove" RUN+="/etc/udev/scripts/mount.sh"

SUBSYSTEM=="block", ACTION=="change", 
ENV{DISK_MEDIA_CHANGE}=="1" RUN+="/etc/udev/scripts/mount.sh"


From: yocto-boun...@yoctoproject.org  on behalf 
of Paul D. DeRocco 
Sent: Tuesday, September 22, 2015 10:45 AM
To: 'Mantas Mikulenas'; yocto@yoctoproject.org
Subject: Re: [yocto] [systemd-devel] How to automount

> From: Mantas Mikulenas [mailto:graw...@gmail.com]
>
> > I don't think there's any way to have something auto-unmount
>
> There certainly is - udev has been unmounting unplugged
> drives for many years. It's done by default.

If creating a udev mount rule automatically does the unmount, then the
simplest thing for me would probably be to do that, and have my
application do a sync after each user-initiated operation. That way, the
drive would remain mounted after the operation, so I could still poke
around on it while debugging, yet there would be no corruption when it's
removed. Thanks for the tip.

--

Ciao,   Paul D. DeRocco
Paulmailto:pdero...@ix.netcom.com

--
___
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] [systemd-devel] How to automount

[Fred Ollinger]

You can see what udev thinks it will do for a given drive by using:

 $ udevadm test /sys/block/sdb1

Given that your drive is in /sys/block/sdb1 (could be sda1, etc).

As for the dirty bit, we had to clear it ourselves.

Frederick


From: Paul D. DeRocco <pdero...@ix.netcom.com>
Sent: Tuesday, September 22, 2015 4:42 PM
To: Fred Ollinger; 'Mantas Mikulenas'; yocto@yoctoproject.org
Subject: RE: [yocto] [systemd-devel] How to automount

> From: Fred Ollinger [mailto:fred.ollin...@seescan.com]
>
> This is in the package: udev-extraconf
>
> On your system look here:
>
> /etc/udev/rules.d/automount.rules
>
> In this file, you'll find the following rules.
>
> The second one auto unmounts.
>
> SUBSYSTEM=="block", ACTION=="add"RUN+="/etc/udev/scripts/mount.sh"
>
> SUBSYSTEM=="block", ACTION=="remove" RUN+="/etc/udev/scripts/mount.sh"
>
> SUBSYSTEM=="block", ACTION=="change",
> ENV{DISK_MEDIA_CHANGE}=="1" RUN+="/etc/udev/scripts/mount.sh"

Well, that started me down a long path. First of all, none of these things
existed because my Yocto build didn't include udev-extraconf. The version
I did two years ago did (although I didn't see it mentioned in my own
metadata), which is why it worked. So I added it back, rebuilt it, and
then tried plugging in a USB flash drive.

The drive appeared as /dev/sdb and /dev/sdb1 (it has a partition table),
The syslog showed the mount.sh script message "Auto-mount of
[/run/media/sdb1] successful", /run/media/sdb1 exists as a directory, but
nothing is mounted there. The next syslog message from FAT-fs said "Volume
was not properly unmounted. Some data may be corrupt. Please run fsck."
When I did that, all I found was that the dirty bit was set, so I
speculated that that caused the mount to somehow be undone.

So I cleaned the dirty bit, synced the file system, unplugged the drive
and plugged it in again. This time the syslog showed the successful mount
message, but no complaint about the drive. Yet it still wasn't mounted.

I can manually mount it, and see its contents. If I then yank the drive,
the mount.sh script doesn't unmount it. I even tweaked the script to log
any attempt to unmount, and it didn't even try.

Whenever I fix the dirty bit, disconnecting and reconnecting logs the
successful mount message, doesn't complain about the dirty bit, but
doesn't mount. Disconnecting again gives me a FAT-fs error "unable to read
boot sector to mark fs as dirty". Connecting again gives me the successful
mount message, and complains about the dirty bit.

Something must be missing here.

--

Ciao,   Paul D. DeRocco
Paulmailto:pdero...@ix.netcom.com

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