Re: [oe] [oe-core][PATCH] pcmciautils: Correct definition of PCMCIAUTILS_VERSION to avoid segmentation fault

2013-04-01 Thread Takeshi Hamasaki
2013/3/31 Martin Jansa martin.ja...@gmail.com:
 oe-core patches need to go to
 openembedded-c...@lists.openembedded.org

 please resend

I subscribed the list and sent it there.
Thanks,
-- 
Takeshi Hamasaki

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


Re: [oe] Finding out the IMAGE_BASENAME of the image beeing built

2013-04-01 Thread Takeshi Hamasaki
Hi Ulf,

I couldn't find the reason your recipe is stand alone,
because it doesn't generate image by itself. Does it?

My idea is written under the quote. How is it?


Let me go back to your question in first mail.

2013/3/30 Ulf Samuelsson openembed...@emagii.com:
 Trying create a programming script recipe and need to find out the
 IMAGE_BASENAME of the bitbake target
 so I can get the filename of the image

 ${MACHINE}-${IMAGE_BASENAME}.ubi

 I.E: if I do

 $ MACHINE=beagleboard  bitbake some-image

 and some-image_1.0.bb contains

 IMAGE_BASENAME = renamed-image

 Then the resulting image will be

 beagleboard-renamed-image.ubi

 How get this info from another recipe?

  your-image.bb  from here 
include some-image.bb

 ((( use  ${IMAGE_BASENAME} and ${MACHINE} for your process )))

 ((( after that, redefine IMAGE_BASENAME and other variables if necessary. )))

 your-image.bb  to here 

-- 
Takeshi Hamasaki

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


Re: [oe] Finding out the IMAGE_BASENAME of the image beeing built

2013-03-30 Thread Takeshi Hamasaki
Hi Ulf,

$ MACHINE=beagleboard  bitbake -e some-image

shows all variables including $IMAGE_BASENAME without actually
building the image.
Using grep you can take the value of IMAGE_BASENAME, like as:

$ MACHINE=beagleboard  bitbake -e some-image | grep ^IMAGE_BASENAME

Does it help you?

If possible, consider to use hooks, for example, IMAGE_POSTPROCESS_COMMAND .
Refer image.bbclass for details. It might make things straiter.

Regards,
-- 
Takeshi Hamasaki

2013/3/30 Ulf Samuelsson openembed...@emagii.com:
 Trying create a programming script recipe and need to find out the
 IMAGE_BASENAME of the bitbake target
 so I can get the filename of the image

 ${MACHINE}-${IMAGE_BASENAME}.ubi

 I.E: if I do

 $ MACHINE=beagleboard  bitbake some-image

 and some-image_1.0.bb contains

 IMAGE_BASENAME = renamed-image

 Then the resulting image will be

 beagleboard-renamed-image.ubi

 How get this info from another recipe?

 BR
 Ulf Samuelsson


 ___
 Openembedded-devel mailing list
 Openembedded-devel@lists.openembedded.org
 http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


[oe] [oe-core][PATCH] pcmciautils: Correct definition of PCMCIAUTILS_VERSION to avoid segmentation fault

2013-03-30 Thread Takeshi Hamasaki
This is to fix segmentation fault from pccardctl command.
-DPCMCIAUTILS_VERSION=\'${PV}\' passes PCMCIAUILTS_VERSION to compiler as a 
multi-character constant, not a string.

---
 meta/recipes-bsp/pcmciautils/pcmciautils.inc |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-bsp/pcmciautils/pcmciautils.inc 
b/meta/recipes-bsp/pcmciautils/pcmciautils.inc
index 80271d6..0651236 100644
--- a/meta/recipes-bsp/pcmciautils/pcmciautils.inc
+++ b/meta/recipes-bsp/pcmciautils/pcmciautils.inc
@@ -21,7 +21,7 @@ export udevrulesdir = ${nonarch_base_libdir}/udev/rules.d
 export UDEV = 1
 LD = ${CC}
 CFLAGS =+ -I${S}/src
-CFLAGS =+ -DPCMCIAUTILS_VERSION=\'${PV}\'
+CFLAGS =+ -DPCMCIAUTILS_VERSION=\\${PV}\\
 
 PARALLEL_MAKE = 
 EXTRA_OEMAKE = -e 'STRIP=echo' 'LIB_OBJS=-lc -lsysfs' 'LEX=flex'
-- 
1.7.10.4


___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


Re: [oe] Adding a recipe to oe bitbake

2013-03-24 Thread Takeshi Hamasaki
Hi David,

do you use the file name task-arago.xyz.bb
for the task called  task-arago-xyz?

They don't match, just curious for me, and it explains your progress:

2013/3/23 David Hirst hirst...@gmail.com:
 OK, now I have some progress, what I have done is to drop the task and call
 pure-ftpd directly from tisdk-rootfs-image

Regards,
-- 
Takeshi Hamasaki



2013/3/23 David Hirst hirst...@gmail.com:
 OK, now I have some progress, what I have done is to drop the task and call
 pure-ftpd directly from tisdk-rootfs-image

 and I get the following in the image. Somehow this just seems wrong but it
 works

 hirst689@hirst689-HP-Z210-Workstation:~/oe-layersetup/build/arago-tmp-external-arago-toolchain/deploy/images$
 tar tvf tisdk-rootfs-image-am335x-evm.tar.gz | grep pure
 -rwxr-xr-x root/root  9744 2013-03-22 14:28 ./usr/sbin/pure-mrtginfo
 -rwxr-xr-x root/root  5196 2013-03-22 14:28 ./usr/sbin/pure-uploadscript
 -rwxr-xr-x root/root  5184 2013-03-22 14:28 ./usr/sbin/pure-authd
 -rwxr-xr-x root/root112184 2013-03-22 14:28 ./usr/sbin/pure-ftpd
 -rwxr-xr-x root/root 12360 2013-03-22 14:28 ./usr/sbin/pure-quotacheck
 -rwxr-xr-x root/root  5248 2013-03-22 14:28 ./usr/sbin/pure-ftpwho
 -rwxr-xr-x root/root 6964 2013-03-22 14:28
 ./usr/bin/pure-statsdecode
 -rwxr-xr-x root/root28972 2013-03-22 14:28 ./usr/bin/pure-pw
 -rwxr-xr-x root/root 6568 2013-03-22 14:28 ./usr/bin/pure-pwconvert
 -rw-r--r-- root/root   208 2013-03-22 14:44
 ./var/lib/opkg/info/pure-ftpd.list
 -rw-r--r-- root/root   442 2013-03-22 14:28
 ./var/lib/opkg/info/pure-ftpd.control
 hirst689@hirst689-HP-Z210-Workstation:~/oe-layersetup/build/arago-tmp-external-arago-toolchain/deploy/images$



 On Fri, Mar 22, 2013 at 1:53 PM, Gary Thomas g...@mlbassoc.com wrote:

 On 2013-03-22 11:31, David Hirst wrote:

 Here are the results, the same as before, in the build directories all
 seems fine but the final output only has the /usr/share/man/man8/files

 in
 oe-layersetup/build/arago-tmp-**external-arago-toolchain/work/**
 armv7a-vfp-neon-oe-linux-**gnueabi/pure-ftpd-1.0.29-r0/**image/usr/sbin
 are the following files:

 pure-authd  pure-ftpd  pure-ftpwho  pure-mrtginfo  pure-quotacheck
 pure-uploadscript

 in
 oe-layersetup/build/arago-tmp-**external-arago-toolchain/work/**
 armv7a-vfp-neon-oe-linux-**gnueabi/pure-ftpd-1.0.29-r0/**image/usr/bin
 are the following files:

 pure-pw  pure-pwconvert  pure-statsdecode

 in
 oe-layersetup/build/arago-tmp-**external-arago-toolchain/work/**
 armv7a-vfp-neon-oe-linux-**gnueabi/pure-ftpd-1.0.29-r0/**
 image/usr/share/man/man8

 pure-authd.8  pure-ftpd.8  pure-ftpwho.8  pure-mrtginfo.8  pure-pw.8
 pure-pwconvert.8  pure-quotacheck.8  pure-statsdecode.8
  pure-uploadscript.8


 You still didn't answer the question about the version of bitbake, the OE
 metadata, etc.
 which does make a difference...

 Try adding this line in your pure-ftpd recipe:
   FILES_${PN} += /usr/sbin



 hirst689@hirst689-HP-Z210-**Workstation:~/oe-layersetup/**
 build/arago-tmp-external-**arago-toolchain/deploy/images$
 tar tvf tisdk-rootfs-image-am335x-evm.**tar.gz | grep pure*

 -rw-r--r-- root/root  4151 2013-03-22 12:36
 ./usr/share/man/man8/pure-**uploadscript.8
 -rw-r--r-- root/root  3187 2013-03-22 12:36
 ./usr/share/man/man8/pure-pw.8
 -rw-r--r-- root/root  2169 2013-03-22 12:36
 ./usr/share/man/man8/pure-**quotacheck.8
 -rw-r--r-- root/root  1123 2013-03-22 12:36
 ./usr/share/man/man8/pure-**statsdecode.8
 -rw-r--r-- root/root   764 2013-03-22 12:36
 ./usr/share/man/man8/pure-**pwconvert.8
 -rw-r--r-- root/root  4160 2013-03-22 12:36
 ./usr/share/man/man8/pure-**authd.8
 -rw-r--r-- root/root  2119 2013-03-22 12:36
 ./usr/share/man/man8/pure-**mrtginfo.8
 -rw-r--r-- root/root 28755 2013-03-22 12:36
 ./usr/share/man/man8/pure-**ftpd.8
 -rw-r--r-- root/root  2449 2013-03-22 12:36
 ./usr/share/man/man8/pure-**ftpwho.8



 On Fri, Mar 22, 2013 at 11:02 AM, David Hirst hirst...@gmail.com wrote:

  I did a bitbake tisdk-rootfs-image -c clean
 I will try the cleanstate
 It seems really difficult to get started from an absolutely clean slate,
 some where status is held that gets in the way
 I will let you know

 Thanks so far




 On Fri, Mar 22, 2013 at 10:51 AM, Gary Thomas g...@mlbassoc.com wrote:

  On 2013-03-22 08:42, David Hirst wrote:

  OK,
   Sorry for the carpet bombing! I added this to tisdk-rootfs-image
 task-arago-xyz \ to look for the new task file
 I have included the task and pure-ftpd bb files also. I would love to
 understand why this does not work.


 What steps did you run after making this change?
 What version of bitbake are you using?

 Most likely, bitbake did not [fully] realize that you made a change.
 I'd try something like this:
% bitbake tisdk-rootfs-image -c cleansstate
% bitbake tisdk-rootfs-image
 and see what happens.

 BTW, top-posting is evil :-(


  ==**tisd**k

Re: [oe] ATNGW100

2013-03-24 Thread Takeshi Hamasaki
Hi Justin,

according to the DISTRO name,
you have to specify something exists in
source/meta-angstrom/conf/distro/ directory.

I guess you can find angstrom-v2012.05.conf or something there.
Thus
DISTRO=angstrom-v2012.05
helps you to walk one step forward.
-- 
Takeshi Hamasaki

2013/3/25 Justin Seitz j...@bughunter.ca:
 Hey all,

 I am pretty new to OE, and having followed some scattered instructions on 
 building the ATNGW100 I have been unsuccessful with the new OE core. My 
 local.conf includes the directives:

 TARGET_OS = “linux-uclibc”
 MACHINE = “atngw100#8243;
 DISTRO = “angstrom-2008.1#8243;
 ANGSTROMLIBC = “uclibc”

 Which it complains that angstrom-2008.1 cannot be found as a distro. Is this 
 a case that I can just pull the configs from the OE-classic repo over or is 
 there a guide somewhere that I can't find in YOCTO that describes how I can 
 move the ATNGW100 build over to the new OE-core?

 Thanks in advance,

 JMS

 ___
 Openembedded-devel mailing list
 Openembedded-devel@lists.openembedded.org
 http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


Re: [oe] Building with gcc-4.6 is not working

2013-02-21 Thread Takeshi Hamasaki
Hi,

2013/2/21 Marcin Juszkiewicz marcin.juszkiew...@linaro.org:
 CalledProcessError: Command 'tar -cf - -C
 /tmp/del/oe46/build/tmp-eglibc/work/armv7ahf-vfp-neon-oe-linux-gnueabi/gcc-cross-initial/linaro-4.6-r5/pkgdata
 -ps . | tar -xf - -C
 /tmp/del/oe46/build/tmp-eglibc/pkgdata/armv7ahf-vfp-neon-oe-linux-gnueabi'
 returned non-zero exit status 2 with output tar:
 /tmp/del/oe46/build/tmp-eglibc/work/armv7ahf-vfp-neon-oe-linux-gnueabi/gcc-cross-initial/linaro-4.6-r5/pkgdata:
 Cannot chdir: No such file or directory

this is the part where you must dig into.

The pair of tar commands are used to copy directory tree, and first
one can't source directory:
/tmp/del/oe46/build/tmp-eglibc/work/armv7ahf-vfp-neon-oe-linux-gnueabi/gcc-cross-initial/linaro-4.6-r5/pkgdata
-- 
Takeshi Hamasaki

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


Re: [oe] build dependency cycles in openembedded

2013-02-18 Thread Takeshi Hamasaki
Hi,

you can find the line like:
DEPENDS = XX-native
in some recipes.

So, you can describe dependency to native tools from target build if necessary.
I guess this is the answer for the sentence what I have read the
second paragraph of [1]:

 Since the full distribution for the new architecture is not yet available,
 dependency cycles have to be broken during cross as well as native 
 compilation.

I can't answer how the dependency to -native chosen, in which
recipe and to which native tools.
When I start to try OpenEmbedded, the dependencies were already well-built.
Maybe there is someone who can answer for deeper question.

Regards,
-- 
Takeshi Hamasaki

2013/2/18 Johannes Schauer j.scha...@email.de:
 Dear list,

 I am analyzing build dependency graphs for rpm and deb based binary
 distributions. I gave a talk about my work on this years FOSDEM [1]. To 
 improve
 my work I was looking into Gentoo and Openembedded.

 While build dependency cycles in Gentoo are easily taken care of by manually
 compiling some source packages with different USE flags, how is this topic
 handled in OpenEmbedded?

 Searching the wiki, mailinglist and internet I was not able to find good
 sources which explain how serious the problem of build dependency cycles in
 OpenEmbedded is when bootstrapping a new target from nothing. I also did not
 find how build dependency cycles are dealt with, should they occur.

 Could you direct me to some resources which document the status and handling 
 of
 build dependency cycles in OpenEmbedded?

 Thanks!

 cheers, josch

 [1] https://fosdem.org/2013/schedule/event/debian_bootstrap/

 ___
 Openembedded-devel mailing list
 Openembedded-devel@lists.openembedded.org
 http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


Re: [oe] build dependency cycles in openembedded

2013-02-18 Thread Takeshi Hamasaki
Before continuing to write reply,
I want to make sure about the usage of the word native:

in OpenEmbedded recipe, let's say, when you work on a x86-64 system to build
for target system which has ARM architecture,

if you want to borrow a xz tool from x86-64 environment: you can write
 DEPENDS = xz-native

if you depends on xz tool build on target environment: you just write
 DEPENDS = xz

Is this the custom you assume?

What I had to find was the word native is used to point the target environment
in [1].
-- 
Takeshi Hamasaki

2013/2/18 Johannes Schauer j.scha...@email.de:
 Hi,

 Quoting Takeshi Hamasaki (2013-02-18 13:26:38)
 you can find the line like:
 DEPENDS = XX-native
 in some recipes.

 So, you can describe dependency to native tools from target build if 
 necessary.

 Sure, when cross compiling you can satisfy lots of dependencies by native
 binaries but others need the foreign version. In Debian based distribution,
 this distinction for cross build dependency resolution is made using
 Multi-Arch.

 Since some of the cross build dependencies can be satisfied by (already
 available) native tools, the dependency cycle situation is *much* less severe
 during cross compilation than it is during native compilation.

 But still, even when one wants to cross compile a native, minimal Debian build
 system (just containing the init, shell and compiler) one runs into build
 dependency cycles because some dependencies have to be satisfied by foreign
 (not yet built) binaries and thereby creating some dependency cycles.

 Is it different in OpenEmbedded?

 cheers, josch

 ___
 Openembedded-devel mailing list
 Openembedded-devel@lists.openembedded.org
 http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


Re: [oe] opkg-make-index not found

2013-02-18 Thread Takeshi Hamasaki
Hi,

this may or may not help you:

$ bitbake -e package-index  bbenv.package-index
$ grep PACKAGEINDEXES bbenv.package-index
(
 for me, the result was:

 # PACKAGEINDEXES= package_update_index_ipk;
 PACKAGEINDEXES=package_update_index_ipk;

)

Then I tried searching package_update_index_ipk in bbenv.package-index
using a text editor. It is a function, and in it, opkg-make-index
is called in a line:

 flock $pkgdir/Packages.flock -c opkg-make-index -r $pkgdir/Packages
-p $pkgdir/Packages -m $pkgdir/

What do you find in your box?

-- 
Takeshi Hamasaki

2013/2/18 Jaap de Jong jaap.dej...@nedap.com:

 On 02/16/2013 07:51 AM, Takeshi Hamasaki wrote:

 if I do

  bitbake package-index

 it crashes with the message

  | /bin/bash: opkg-make-index: command not found

 This is on a 64 debian machine, possibly the wrong path is searched?
 (there is a opkg-make-index under sysroots/x86_64-linux/usr/bin)



 If you doubt the PATH setting, you should check the output from:
 $ bitbake -e | grep '^export PATH'


 Well opkg-make-index is in the path.

 Something strange is happening here.
 If I edit package-index.bb and add a call to opkg-make-index

do_package_index() {
 set -ex
opkg-make-index   ### ADDED CODE
 ${PACKAGEINDEXES}
 set +ex
}


 it shows an error message when invoking bitbake package-index showing that
 opkg-make-index is actualy working...

///

 .../build/tmp-angstrom_v2012_05-eglibc/sysroots/x86_64-linux/usr/bin/opkg-make-index
[-h] [-s] [-m] [-l Packages.filelist] [-p Packages] [-r
Packages.old] [-L localesdir] [-v] packagesdir
NOTE: package package-index-1.0-r0: task do_package_index: Failed
///

 Any idea?




 ___
 Openembedded-devel mailing list
 Openembedded-devel@lists.openembedded.org
 http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


Re: [oe] opkg-make-index not found

2013-02-15 Thread Takeshi Hamasaki
Hi,

 This is on a 64 debian machine, possibly the wrong path is searched?

If you doubt the PATH setting, you should check the output from:
$ bitbake -e | grep '^export PATH'

-- 
Takeshi Hamasaki

2013/2/15 Jaap de Jong jaap.dej...@nedap.com:
 Hi All,

 if I do

 bitbake package-index

 it crashes with the message

 | /bin/bash: opkg-make-index: command not found

 This is on a 64 debian machine, possibly the wrong path is searched?
 (there is a opkg-make-index under sysroots/x86_64-linux/usr/bin)

 Is this a known problem?
 Thanks!

 Jaap



 ___
 Openembedded-devel mailing list
 Openembedded-devel@lists.openembedded.org
 http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


Re: [oe] User Application with Shared Library - do_rootfs fails

2013-02-06 Thread Takeshi Hamasaki
I can't find DEPENDS keyword and RDEPENDS keyword in your recipes.
Is it done at will?
-- 
Takeshi Hamasaki

2013/2/5 Thomas Besemer thomas.bese...@gmail.com:
 I am generating some source code in the OE/Yocto world.  This work requires
 that a shared library exist.  I am able to to build the shared library, and
 maybe install it, and then build the test code against it.  Both these
 builds work.  Final assembly of Root FS fails.

 Below are my two recipes.  Appears that the libgcpy_gc6016sa.so does not
 get installed correctly (does build).  The recipe for gcpytest does work,
 but it does find the library during build.

 If I build each indepdent of the other, it's fine.  But, once I try to
 build core-image-minimal it complains that the library is not there.


 | error: Failed dependencies:

 | libgcpy_gc6016.so.1 is needed by gcpytest-1-r0.armv7a_vfp_neon

 ---

 gcpy-dev.bb

 DESCRIPTION = GCPY Server application

 SECTION = gcsim

 LICENSE = MIT

 LIC_FILES_CHKSUM =
 file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302

 PR = r0

 SRC_URI = file://gcpy-dev.tar

 S = ${WORKDIR}

 do_compile() {

 oe_runmake

 }

 do_install() {

 oe_libinstall -so libgcpy_gc6016 ${STAGING_LIBDIR}

 install -m 0644 ${S}/gcpy_target_lib.h ${STAGING_INCDIR}

 oe_libinstall -so libgcpy_gc6016.so ${D}${libdir}

 }

  EXTRA_OEMAKE += V=1 ARCH=${TARGET_ARCH}
 GC5330_TOOL_PREFIX=${TARGET_PREFIX} SKIP_STRIP=y

 FILES_${PN}-dev = ${D}${libdir}/libgcpy_gc6016.so

 ---

 gcpytest.bb

 DESCRIPTION = Simple GCPY Test application

 SECTION = gcsim

 LICENSE = MIT

 LIC_FILES_CHKSUM =
 file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302

 PR = r0

 SRC_URI = file://gcpytest.c

 S = ${WORKDIR}

 do_compile() {

 ${CC} gcpytest.c -o gcpytest -lgcpy_gc6016 -lrt

 }

 do_install() {

 install -d ${D}${bindir}

 install -m 0755 gcpytest ${D}${bindir}

 }

 REQUIRES =  gcpy-dev
 ___
 Openembedded-devel mailing list
 Openembedded-devel@lists.openembedded.org
 http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


Re: [oe] Angstrom build failure

2013-01-17 Thread Takeshi Hamasaki
Hi,

Do you want systemd and udev to be build same time?
I'm not sure it is same problem or not,
I've read some thread about confliction between systemd and udev.
http://comments.gmane.org/gmane.comp.handhelds.openembedded/55775

adding a line
PREFERRED_PROVIDER_udev = systemd
in conf/local.conf helped me to go to next step.

Regards,
-- 
Takeshi Hamasaki

2013/1/17 R U Local roystonva...@slingshot.co.nz:
 Dear All,
 I'm getting the following failure building an Angstrom image.

 | checking for UDEV... no
 | configure: error: Package requirements ( libudev = 172 ) were not met:
 |
 | No package 'libudev' found
 |
 | Consider adjusting the PKG_CONFIG_PATH environment variable if you
 | installed software in a non-standard prefix.
 |
 | Alternatively, you may set the environment variables UDEV_CFLAGS
 | and UDEV_LIBS to avoid the need to call pkg-config.
 | See the pkg-config man page for more details.
 | ERROR: oe_runconf failed
 NOTE: package systemd-git-r28: task do_configure: Failed
 ERROR: Task 518
 (/home/service/oe/sources/meta-openembedded/meta-oe/recipes-core/systemd/sys
 temd_git.bb, do_configure) failed with exit code '1'
 NOTE: Tasks Summary: Attempted 2549 tasks of which 2548 didn't need to be
 rerun and 1 failed.

 My build environment is:
 OE Build Configuration:
 BB_VERSION= 1.15.2
 TARGET_ARCH   = arm
 TARGET_OS = linux-gnueabi
 MACHINE   = pandaboard
 DISTRO= angstrom
 DISTRO_VERSION= v2012.05
 TUNE_FEATURES = armv7a vfp neon cortexa9
 TARGET_FPU= vfp-neon
 meta-angstrom =
 angstrom-v2012.05-yocto1.2:6a2febed13f179c042c2371b2e86286c80c0df5e
 meta-oe
 toolchain-layer
 meta-efl
 meta-gpe
 meta-gnome
 meta-xfce
 meta-initramfs= denzil:c0117f5ad7d1fe18d149bda426c7134ff24daae8
 meta-opie = master:efa3892b20a4ef80274e56e5633ebd62c16f9731
 meta-java = master:3386ea6c96096f107f43f282f654e5afa456109e
 meta-browser  = master:c47f59df2e723495679c751cbdf6a8c6adec4b6a
 meta-mono = master:83f8233b0498aadb18bf7605c3ba6c71d9e13a3a
 meta-kde  = master:5b0882d951cfd71886d423c190faaa7c7f932333
 meta-ti   = denzil:95e9cf6299f5bae6965fe6fc4abe3eeb631df196
 meta-efikamx  = master:2c09a3a780b23448e8a6ca964256ff7f5ccba65d
 meta-nslu2= master:3d9fc951b05b4df476374b6fc3085ebac7f293ee
 meta-htc
 meta-nokia
 meta-openmoko
 meta-palm = master:2b106be01228f64298d6cb338f93088806594344
 meta-handheld = master:1f05a15aceb4c3a19fa070463b58125b5658b2a9
 meta-raspberrypi  = denzil:34eef2ea4f5f24630dbb73b386861430167b8431
 meta-intel
 meta-sugarbay
 meta-crownbay
 meta-emenlow
 meta-fishriver
 meta-fri2
 meta-jasperforest
 meta-n450 = master:f75f9b6f68473eb0efac802409608f8389be0030
 meta  = denzil:0a9e8bf35afd5990c1b586bba5eb68f643458a4b


 Any pointers would be appreciated.

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


[oe] /etc/init.d/networking from netbase package

2013-01-16 Thread Takeshi Hamasaki
Now I'm trying to build a simple image which includes udev and netbase.
(I know that main stream is using systemd, but my C7x0 has too short memory
 to operate systemd.)

After the build, I noticed /etc/init.d/networking is not installed on the
rootfs while netbase_4.47-r1.ipk includes this file.

Is there any magic behind that prevents this file installed or removes this
file after the package installation?

According to https://bugzilla.yoctoproject.org/show_bug.cgi?id=2486
there is a plan to split /etc/init.d/networking out of netbase package,
but this change is not applied yet, for my understanding.

Now I'm on the denzil branch, angstrom-2012.05.

Actually I want to make a new bug on yoctobugzilla,
due to the mail server problem on my side I can't
finish the registration process for few more days.

Regards,
-- 
Takeshi Hamasaki

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


Re: [oe] [meta-initramfs][PATCH] symbolic link to resource.h is also necessary to build with linux kernel 3.2.

2013-01-15 Thread Takeshi Hamasaki
2013/1/15 Andrea Adami andrea.ad...@gmail.com:
 Hi,

 you are using an outdated recipe, the issue is already fixed.
 Please update your meta-initramfs layer and you'll get klibc_2.0.2.

Thank you for your advice,
according to the output from
 $ git branch
at sources/meta-openembedded/meta-initramfs/ directory, there are two
branches available.

* denzil
  master

Do you mean that I have to do:
 $ git checkout master
there?
Or is there any trick using oebb.sh?
(Though I can't find anything suggesting this from ./oebb.sh --help)
-- 
Takeshi Hamasaki

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


Re: [oe] [meta-initramfs][PATCH] symbolic link to resource.h is also necessary to build with linux kernel 3.2.

2013-01-15 Thread Takeshi Hamasaki
Hi,

2013/1/15 Andrea Adami andrea.ad...@gmail.com:
 Ah, I see now: you are using the denzil branch with klibc_1.5.25.

 This version was the last one built against kernel headers: starting
 with 1.5.26 the recipe uses linux-libc-headers for building.
 So for denzil, with kernel 3.2,  I suggest you to:

 a) add your patch and be happy with 1.5.25
 b) update to 1.5.26, backporting the commits form master
 c) checkout meta-initramfs master and get klibc_2.0.2 (pls remove
 linux-yocto-tiny-kexecboot_3.4.bb or you'll get errors)

I choose a) for a while, say, until Angstrom 2012.12 is released.
b) and c) are also helpful advice, thank you so much.
-- 
Takeshi hamasaki

___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


[oe] [meta-initramfs][PATCH] symbolic link to resource.h is also necessary to build with linux kernel 3.2.

2013-01-14 Thread Takeshi Hamasaki
---
 meta-initramfs/recipes-devtools/klibc/klibc_1.5.25.bb |3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta-initramfs/recipes-devtools/klibc/klibc_1.5.25.bb 
b/meta-initramfs/recipes-devtools/klibc/klibc_1.5.25.bb
index ae43753..8e096d9 100644
--- a/meta-initramfs/recipes-devtools/klibc/klibc_1.5.25.bb
+++ b/meta-initramfs/recipes-devtools/klibc/klibc_1.5.25.bb
@@ -1,4 +1,4 @@
-PR = ${INC_PR}.0
+PR = ${INC_PR}.1
 
 export INST = ${D}
 
@@ -11,6 +11,7 @@ do_compile_prepend() {
 ln -sf 
${STAGING_KERNEL_DIR}/arch/${TARGET_ARCH}/include/generated/asm/errno.h 
${STAGING_KERNEL_DIR}/arch/${TARGET_ARCH}/include/asm/errno.h
 ln -sf 
${STAGING_KERNEL_DIR}/arch/${TARGET_ARCH}/include/generated/asm/ioctl.h 
${STAGING_KERNEL_DIR}/arch/${TARGET_ARCH}/include/asm/ioctl.h
 ln -sf 
${STAGING_KERNEL_DIR}/arch/${TARGET_ARCH}/include/generated/asm/poll.h 
${STAGING_KERNEL_DIR}/arch/${TARGET_ARCH}/include/asm/poll.h
+ln -sf 
${STAGING_KERNEL_DIR}/arch/${TARGET_ARCH}/include/generated/asm/resource.h 
${STAGING_KERNEL_DIR}/arch/${TARGET_ARCH}/include/asm/resource.h
 fi
 
 }
-- 
1.7.10.4


___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel