[OE-core] how to check which package is installed for specific image, and whey it is installed?

[Yi Qingliang]

Hello,

I checked the 'taskexp', but can't get what I want.
I want to know what package is installed, and why it is installed,
indeed, for 'systemd-vconsole-setup'.

Thanks!


Yi Qingliang
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [meta-qt5] the QV4 engine will crash result in SIGSEGV

[Yi Qingliang]

sorry!

On Thu, Aug 25, 2016 at 9:34 AM, Burton, Ross <ross.bur...@intel.com> wrote:
> meta-qt5 bugs should go to openembedded-devel@, not -core@.
>
> Ross
>
> On 25 August 2016 at 08:45, Yi Qingliang <niqingliang2...@gmail.com> wrote:
>>
>> bug detail:
>> https://bugs.archlinux.org/task/49723
>>
>> patch:
>>
>> https://git.archlinux.org/svntogit/packages.git/tree/trunk/qt5-declarative-gcc6.patch?h=packages/qt5-declarative
>>
>> Yi Qingliang
>> --
>> ___
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [meta-qt5] the QV4 engine will crash result in SIGSEGV

[Yi Qingliang]

bug detail:
https://bugs.archlinux.org/task/49723

patch:
https://git.archlinux.org/svntogit/packages.git/tree/trunk/qt5-declarative-gcc6.patch?h=packages/qt5-declarative

Yi Qingliang
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [BUG] gcc: require neon on arch without neon

[Yi Qingliang]

https://bugzilla.yoctoproject.org/show_bug.cgi?id=9991

On Tue, Jul 19, 2016 at 3:03 PM, Khem Raj <raj.k...@gmail.com> wrote:
> Thanks. You can open a yp bugzilla to track it or even better send this
> patch backported
>
>
> On Jul 18, 2016 11:53 PM, "Yi Qingliang" <niqingliang2...@gmail.com> wrote:
>>
>> when compiling qtbase in meta-qt5, it says:
>> | ../../include/QtCore/../../../git/src/corelib/global/qendian.h:143:36:
>> fatal error: You must enable NEON instructions (e.g.
>> -mfloat-abi=softfp -mfpu=neon) to use these intrinsics.
>> |  return __builtin_bswap16(source);
>> | ^
>>
>>
>> bug description:
>>   https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71056
>> upstream patch:
>>   https://gcc.gnu.org/viewcvs/gcc?view=revision=236910
>> mirror on github:
>>
>> https://github.com/gcc-mirror/gcc/commit/84d2a5509892b65ed60d39e6e2f9719e3762e40e
>>
>> Yi Qingliang
>> --
>> ___
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [BUG] gcc: require neon on arch without neon

[Yi Qingliang]

when compiling qtbase in meta-qt5, it says:
| ../../include/QtCore/../../../git/src/corelib/global/qendian.h:143:36:
fatal error: You must enable NEON instructions (e.g.
-mfloat-abi=softfp -mfpu=neon) to use these intrinsics.
|  return __builtin_bswap16(source);
| ^


bug description:
  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71056
upstream patch:
  https://gcc.gnu.org/viewcvs/gcc?view=revision=236910
mirror on github:

https://github.com/gcc-mirror/gcc/commit/84d2a5509892b65ed60d39e6e2f9719e3762e40e

Yi Qingliang
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] software implementation opengl

[Yi Qingliang]

Hello.
I'm using qt5 with poky, but there is not gpu/drm on my arm.
I found the mesa has sw implementation of opengl, but I can't make it work.
do you have any experience on it ?

   the qt5 quick 2.0 need opengl, I want use sw opengl implementation
on framebuffer directly.
   and the mesa in poky dropped fbdev.


Yi Qingliang
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] can't compile ffmpeg without x11

[Yi Qingliang]

HELLO!

in ffmpeg.bb:

DEPENDS = "alsa-lib zlib libogg yasm-native libxv"
PACKAGECONFIG ??= "... ${@bb.utils.contains('DISTRO_FEATURES', 'x11',
'x11', '', d)}"


the 'DEPENDS' says it need libxv which need x11, so the x11 detection
in 'PACKAGECONFIG' will not work anymore.

can I use ffmpeg without x11 ? (indeed, I want to use opencv)

the old poky will work with libav, but now libav has been dropped.


Yi Qingliang
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [RFC PATCH 1/2] android-tools: import android-tools from meta-smartphone into oe-core

[Yi Qingliang]

can we compile android system using oe?
the Makefile system of android is too complicated to load/use.

On Mon, Aug 31, 2015 at 10:28 PM, Nicolas Dechesne
 wrote:
> On Mon, Aug 31, 2015 at 4:12 PM, Otavio Salvador
>  wrote:
>>> compared to 'regular' ext4 images , fastboot added the (convenient)
>>> ability to support sparse images, to reduce the size of what is
>>> transmitted over the USB, when flashing (and reduce the size of
>>> writting to eMMC). For devices with 8GB+ eMMC that is a big deal
>>> whether we flash a raw ext4 image, or its sparse'd version. More info
>>> about fastboot sparse format at [1].
>>
>> It does help for images it seems; did you see if someone has propose a
>> patch for e2fstools to enable this?
>
> no, i haven't seen anything there. Note that it would be a
> fastboot-specific sparse format.
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] gcc 5.2 failures

[Yi Qingliang]

using gcc 5.1, the boost statechart library compile fail.

On Mon, Jul 27, 2015 at 9:20 PM, Bruce Ashfield
bruce.ashfi...@windriver.com wrote:
 On 15-07-27 05:30 AM, Richard Purdie wrote:

 I've run a gcc 5.2 test build on the autobuilder:


 http://errors.yoctoproject.org/Errors/Search/?items=10query=3628c3c06fa4195003ac655bcc791acfac775173limit=50

 41 errors (with a few more pending).

 The good news is that if we tweak the security flags, the poky-lsb gcc,
 elfutils, coreutils and iptables issues can be removed and I have a
 patch for this. This leaves:

 3.14 kernel failures for edgerouter, genericx86-64, qemuarm, beaglebone,
 mpc8315e-rdb


 Gah. I had all these building with 5.1 .. chasing gcc is a pain
 with this older kernel.


 openssl issue for p1022ds

 u-boot on imx28evk, p1022ds, mpc8315e-rdb

 xf86-video-imxfb-vivante on imx6qsabresd

 linux-imx issue on imx53qsb

 Some kind of random qemu runtime issue (4 cases).

 At this point I think we likely need to enter bugs into the bugzilla for
 each of these. If we want to switch 1.9 to use this (which I think is
 desirable), we need to get this fixed as a priority.

 Bruce: How do you want to handle the 3.14 issues? Switch to 4.1? or fix
 3.14?


 Now that 4.1 is in place, and I can't really see a large user base that
 needs gcc 5.x with the linux-yocto 3.14 kernel (other folks using
 master with their own kernel's will obviously have to deal with the
 issue in their trees) .. join that with the fact that we need to update
 all the reference boards to 4.1 anyway, my suggestion is that we open
 bugs for the h/w reference updates (and I'll get the appropriate Wind
 River eyes on them) and walk away from burning more cycles on gcc 5.x
 and the 3.14 kernel.

 Cheers,

 Bruce


 Otavio: The freescale machines are looking unwell, can you help us make
 sure the right people know about this?

 Cheers,

 Richard





 --
 ___
 Openembedded-core mailing list
 Openembedded-core@lists.openembedded.org
 http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] zImage-dtb

[Yi Qingliang]

Oh, forgot one thing.
it looks like a function android provided.

On Wed, Jun 24, 2015 at 10:10 AM, Yi Qingliang
niqingliang2...@gmail.com wrote:
 Hello,
 has someone used the zImage-dtb?

 the zImage-dtb will concatenate multiple dtbs append to zImage.
 How the kernel select dtb in running time?

 Yi Qingliang
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] zImage-dtb

[Yi Qingliang]

Hello,
has someone used the zImage-dtb?

the zImage-dtb will concatenate multiple dtbs append to zImage.
How the kernel select dtb in running time?

Yi Qingliang
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] zImage-dtb

[Yi Qingliang]

Hello,
has someone used the zImage-dtb?

the zImage-dtb will concatenate multiple dtbs append to zImage.
How the kernel select dtb in running time?

Yi Qingliang
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] openssh on read-only systemd rootfs

[Yi Qingliang]

Hello,

in 'image.bbclass', I found some logic for openssh running on readonly
rootfs,
but only in sysvinit branch. do we need similar logic in systemd branch?
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] where is the 'libGL.so.*?

[Yi Qingliang]

I have removed 'x11' in 'DISTRO_FEATURE', I don't know if it is the reason.

On Mon, Nov 3, 2014 at 10:43 AM, Yi Qingliang niqingliang2...@gmail.com
wrote:

 Hello,
 I'm using poky with 'meta-qt5'. when compiling qtbase, it said that
 can't find 'libGL.so'.
 the mesa is the default provider of virtual/libgl, but there isn't
 'libGL.so.*' in package 'libgl-mesa'.
 any idea? thanks!

 Yi Qingliang

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] where is the 'libGL.so.*?

[Yi Qingliang]

Hello,
I'm using poky with 'meta-qt5'. when compiling qtbase, it said that
can't find 'libGL.so'.
the mesa is the default provider of virtual/libgl, but there isn't
'libGL.so.*' in package 'libgl-mesa'.
any idea? thanks!

Yi Qingliang
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] boost: fix atomics for armv6

[Yi Qingliang]

It work for me on my s3c6410 board. The new image run without exception.

Signed-off-by: Yi Qingliang niqingliang2...@gmail.com
niqingliang2...@gmail.com

On Sun, Sep 28, 2014 at 11:37 PM, Peter A. Bigot p...@pabigot.com wrote:

 meta-raspberrypi and some other systems are ARMv6k but tell OE that
 they're ARMv6 which doesn't fully support non-word atomics.  armv6k
 does, but Boost didn't handle the recognition correctly in the 1.56
 release.  Backport the patch that fixes the build.

 See: https://svn.boost.org/trac/boost/ticket/10446
 Signed-off-by: Peter A. Bigot p...@pabigot.com
 ---

 Note:

 I have only tested that this fixes the compile problems; I have not
 verified that the resulting library works correctly with respect to
 atomics.  I'm expecting somebody who uses boost on a platform where this
 is relevant to validate the functional behavior if that's necessary.

 Cc: niqingliang2...@gmail.com
 Cc: danismostlik...@gmail.com

 Peter

  ...rt-for-extending-operations-to-GCC-atomic.patch | 412
 +
  meta/recipes-support/boost/boost_1.56.0.bb |   5 +-
  2 files changed, 416 insertions(+), 1 deletion(-)
  create mode 100644
 meta/recipes-support/boost/boost/0001-Added-support-for-extending-operations-to-GCC-atomic.patch

 diff --git
 a/meta/recipes-support/boost/boost/0001-Added-support-for-extending-operations-to-GCC-atomic.patch
 b/meta/recipes-support/boost/boost/0001-Added-support-for-extending-operations-to-GCC-atomic.patch
 new file mode 100644
 index 000..feece81
 --- /dev/null
 +++
 b/meta/recipes-support/boost/boost/0001-Added-support-for-extending-operations-to-GCC-atomic.patch
 @@ -0,0 +1,412 @@
 +From 415db7054723291042e4ff1ffa8fdd5bc8b07163 Mon Sep 17 00:00:00 2001
 +From: Andrey Semashev andrey.semas...@gmail.com
 +Date: Sat, 27 Sep 2014 20:40:09 +0400
 +Subject: [PATCH] Added support for extending operations to GCC atomic
 backend.
 +
 +Fix for #10446. Some platforms (e.g. Raspberry Pi) only support atomic
 ops of some particular size but not less. Use extending arithmetic
 operations for these platforms. Also, make sure bools are always treated as
 8-bit values, even if the actual type is larger. This makes its use in
 atomic, atomic_flag and lock pool more consistent.
 +
 +Upstream-Status: Backport [https://svn.boost.org/trac/boost/ticket/10446]
 +Signed-off-by: Peter A. Bigot p...@pabigot.com
 +
 +---
 + include/boost/atomic/capabilities.hpp   |   1 +
 + include/boost/atomic/detail/atomic_template.hpp |   2 +-
 + include/boost/atomic/detail/caps_gcc_atomic.hpp |  82 +--
 + include/boost/atomic/detail/ops_gcc_atomic.hpp  | 184
 +---
 + 4 files changed, 206 insertions(+), 63 deletions(-)
 +
 +diff --git a/include/boost/atomic/capabilities.hpp
 b/include/boost/atomic/capabilities.hpp
 +index 658dd22..05bbb0f 100644
 +--- a/include/boost/atomic/capabilities.hpp
  b/include/boost/atomic/capabilities.hpp
 +@@ -142,6 +142,7 @@
 + #define BOOST_ATOMIC_ADDRESS_LOCK_FREE BOOST_ATOMIC_POINTER_LOCK_FREE
 +
 + #ifndef BOOST_ATOMIC_BOOL_LOCK_FREE
 ++// We store bools in 1-byte storage in all backends
 + #define BOOST_ATOMIC_BOOL_LOCK_FREE BOOST_ATOMIC_INT8_LOCK_FREE
 + #endif
 +
 +diff --git a/include/boost/atomic/detail/atomic_template.hpp
 b/include/boost/atomic/detail/atomic_template.hpp
 +index 4fd6d79..bc3922a 100644
 +--- a/include/boost/atomic/detail/atomic_template.hpp
  b/include/boost/atomic/detail/atomic_template.hpp
 +@@ -234,7 +234,7 @@ class base_atomic bool, int 
 + {
 + private:
 + typedef bool value_type;
 +-typedef atomics::detail::operations storage_size_of value_type
 ::value, false  operations;
 ++typedef atomics::detail::operations 1u, false  operations;
 +
 + protected:
 + typedef value_type value_arg_type;
 +diff --git a/include/boost/atomic/detail/caps_gcc_atomic.hpp
 b/include/boost/atomic/detail/caps_gcc_atomic.hpp
 +index 8299ad0..f4e7a70 100644
 +--- a/include/boost/atomic/detail/caps_gcc_atomic.hpp
  b/include/boost/atomic/detail/caps_gcc_atomic.hpp
 +@@ -29,66 +29,48 @@
 + #define BOOST_ATOMIC_DETAIL_X86_HAS_CMPXCHG16B 1
 + #endif
 +
 +-#if __GCC_ATOMIC_BOOL_LOCK_FREE == 2
 +-#define BOOST_ATOMIC_FLAG_LOCK_FREE 2
 +-#else
 +-#define BOOST_ATOMIC_FLAG_LOCK_FREE 0
 +-#endif
 +-#if __GCC_ATOMIC_CHAR_LOCK_FREE == 2
 +-#define BOOST_ATOMIC_CHAR_LOCK_FREE 2
 +-#else
 +-#define BOOST_ATOMIC_CHAR_LOCK_FREE 0
 +-#endif
 +-#if __GCC_ATOMIC_CHAR16_T_LOCK_FREE == 2
 +-#define BOOST_ATOMIC_CHAR16_T_LOCK_FREE 2
 +-#else
 +-#define BOOST_ATOMIC_CHAR16_T_LOCK_FREE 0
 +-#endif
 +-#if __GCC_ATOMIC_CHAR32_T_LOCK_FREE == 2
 +-#define BOOST_ATOMIC_CHAR32_T_LOCK_FREE 2
 ++#if defined(BOOST_ATOMIC_DETAIL_X86_HAS_CMPXCHG16B) 
 (defined(BOOST_HAS_INT128) || !defined(BOOST_NO_ALIGNMENT))
 ++#define BOOST_ATOMIC_INT128_LOCK_FREE 2
 + #else
 +-#define BOOST_ATOMIC_CHAR32_T_LOCK_FREE 0
 ++#define BOOST_ATOMIC_INT128_LOCK_FREE 0
 + #endif
 +-#if __GCC_ATOMIC_WCHAR_T_LOCK_FREE == 2
 +-#define

Re: [OE-core] boost 1.56 compile fail

[Yi Qingliang]

https://github.com/boostorg/atomic/commit/415db7054723291042e4ff1ffa8fdd5bc8b07163

 Please, see if it helps in your case.
https://svn.boost.org/trac/boost/ticket/10446


On Mon, Sep 1, 2014 at 7:37 PM, Peter A. Bigot p...@pabigot.com wrote:

  On 08/31/2014 09:31 PM, Yi Qingliang wrote:

 then what's your suggestion for now?


 If the s3c6410 is ARMv6 and does not support ARMv6-K instructions, then
 boost 1.56 does not work for your platform.  Try downgrading to 1.55, or
 asking the Boost folks for a patch to update
 boost/atomic/detail/caps_gcc_atomic.hpp so that it supports that
 architecture, which lacks the byte, half-word, and double-word atomic
 ldrex/strex instruction variants.

 If the s3c6410 does support ARMv6-K instructions, you can try making sure
 it builds with -march=arvm6k.

 I don't know the conditions under which this becomes an OE-Core problem.
 It's not a gcc problem.

 Peter




 On Sat, Aug 30, 2014 at 9:14 AM, Peter A. Bigot p...@pabigot.com wrote:

  On 08/29/2014 04:18 PM, Dan McGregor wrote:

 On 29 August 2014 14:58, Peter A. Bigot p...@pabigot.com wrote:

 On 08/29/2014 03:36 PM, Dan McGregor wrote:

 On 29 August 2014 05:48, Peter A. Bigot p...@pabigot.com wrote:

 On 08/29/2014 06:28 AM, Yi Qingliang wrote:

 hardware: samsung s3c6410

 after updated to latest poky, the boost compile fail!

 error info:
 libs/atomic/src/lockpool.cpp:127:5: error: 'thread_fence' is not a
 member
 of
 'boost::atomics::detail'
 libs/atomic/src/lockpool.cpp:138:5: error: 'signal_fence' is not a
 member
 of
 'boost::atomics::detail'


 after dig into it, I found that:
 the marco 'BOOST_ATOMIC_FLAG_LOCK_FREE' is 0, so it don't include
 'operations_lockfree.hpp' which has 'thread_fence' and 'signal_fence',
 but
 pthread.h at line 21.

 in file 'caps_gcc_atomic.hpp', 'BOOST_ATOMIC_FLAG_LOCK_FREE' is set to
 '0',
 the author think if '__GCC_ATOMIC_BOOL_LOCK_FREE' is 1, the atomic
 serial
 function gcc provided is not lock free.


 This is the sort of GCC internal header indicator that would have
 changed
 value as a result of:



 http://cgit.openembedded.org/openembedded-core/commit/meta/recipes-devtools/gcc/gcc-configure-common.inc?id=0ba6ab39f187ecd4261f08e768f365f461384a3a



 at the end of 'caps_gcc_atomic.hpp', it defined
 'BOOST_ATOMIC_THREAD_FENCE'
 as 2.

 so the conflict is: BOOST_ATOMIC_THREAD_FENCE and
 BOOST_ATOMIC_FLAG_LOCK_FREE

 I don't know it is the new poky problem, or the boost problem, any
 idea?


 My guess is that Boost is making assumptions about what the internal
 GCC
 predefined symbols mean that aren't entirely accurate.  There are
 several
 flags that are used in the libstdc++ headers to indicate whether the
 compiler is using lock-free instructions.

 Boost-1.56 builds without error for my beaglebone target with poky at:

 * 669c07d (HEAD, origin/master, origin/HEAD, master/upstream,
 master/dev)
 [Wed Aug 27 14:24:52 2014 +0100] bitbake: build/data: Write out more
 complete python run files

 so it may have something to do with your target machine.

 It absolutely does. I found that armv6 breaks, but armv6zk and newer
 work.


 Interesting.  There are no armv6zk tune features I can see in poky,
 though
 google suggests it applies to the Raspberry Pi.

 The problem then must be with the first override in this:

 # ARMv6+ adds atomic instructions that affect the ABI in libraries built
 # with TUNE_CCARGS in gcc-runtime.  Make the compiler default to a
 # compatible architecture.  armv6 and armv7a cover the minimum tune
 # features used in OE.
 EXTRA_OECONF_append_armv6 =  --with-arch=armv6
 EXTRA_OECONF_append_armv7a =  --with-arch=armv7-a

 ARMv6 has LDREX/STREX, but ARMv6K adds {LD,ST}REX{B,H,D}.  The same
 problem
 addressed above is likely to happen if the libraries are built with
 armv6k
 but the compiler doesn't default to it.

 There are no armv6k tune parameters I can locate in poky.  What layers
 have
 the tune configurations that are causing problems?

  For me meta-raspberrypi failed to build. Its tuning is -march=armv6
 -mtune=arm1176zjf-s by default. I forced it to -march=armv6zk
 -mtune=arm1176jzf-s, and that worked.


  tl;dr: for now, this can be claimed to be a boost problem, but it may
 rapidly become an OE problem.

 OK, so there's several issues here.

 Extracting the predefined symbols from gcc 4.9.1 with:

arm-poky-linux-gnueabi-g++ -march=armv6 -dM -E -xc++ /dev/null

 and similarly with -march=armv6k shows that the values of these
 atomic-related predefines are different (- = arvm6, + = armv6k):

 -#define __GCC_ATOMIC_BOOL_LOCK_FREE 1
 -#define __GCC_ATOMIC_CHAR16_T_LOCK_FREE 1
 +#define __GCC_ATOMIC_BOOL_LOCK_FREE 2
 +#define __GCC_ATOMIC_CHAR16_T_LOCK_FREE 2
 -#define __GCC_ATOMIC_CHAR_LOCK_FREE 1
 +#define __GCC_ATOMIC_CHAR_LOCK_FREE 2
 -#define __GCC_ATOMIC_LLONG_LOCK_FREE 1
 +#define __GCC_ATOMIC_LLONG_LOCK_FREE 2
 -#define __GCC_ATOMIC_SHORT_LOCK_FREE 1
 +#define __GCC_ATOMIC_SHORT_LOCK_FREE 2
 +#define __GCC_HAVE_SYNC_COMPARE_AND_SWAP_1

[OE-core] libav

[Yi Qingliang]

why there are two versions libav in oe-core? what's the difference?
why the opencv will use the 0.8.x version, but not 9.x version?
does it should use the higher version?

libav 0.8.x has warning:

WARNING: QA Issue: ELF binary
'/mnt/qt5-test/build/tmp/work/armv6-vfp-jilong-linux-gnueabi/libav/0.8.15-r0/packages-split/libswscale/usr/lib/libswscale.so.2.1.0'
has relocations in .text [textrel]
WARNING: QA Issue: ELF binary
'/mnt/qt5-test/build/tmp/work/armv6-vfp-jilong-linux-gnueabi/libav/0.8.15-r0/packages-split/libpostproc/usr/lib/libpostproc.so.52.0.0'
has relocations in .text [textrel]
WARNING: QA Issue: ELF binary
'/mnt/qt5-test/build/tmp/work/armv6-vfp-jilong-linux-gnueabi/libav/0.8.15-r0/packages-split/libavutil/usr/lib/libavutil.so.51.22.2'
has relocations in .text [textrel]
WARNING: QA Issue: ELF binary
'/mnt/qt5-test/build/tmp/work/armv6-vfp-jilong-linux-gnueabi/libav/0.8.15-r0/packages-split/libavformat/usr/lib/libavformat.so.53.21.1'
has relocations in .text [textrel]
WARNING: QA Issue: ELF binary
'/mnt/qt5-test/build/tmp/work/armv6-vfp-jilong-linux-gnueabi/libav/0.8.15-r0/packages-split/libavfilter/usr/lib/libavfilter.so.2.15.0'
has relocations in .text [textrel]
WARNING: QA Issue: ELF binary
'/mnt/qt5-test/build/tmp/work/armv6-vfp-jilong-linux-gnueabi/libav/0.8.15-r0/packages-split/libavdevice/usr/lib/libavdevice.so.53.2.0'
has relocations in .text [textrel]
WARNING: QA Issue: ELF binary
'/mnt/qt5-test/build/tmp/work/armv6-vfp-jilong-linux-gnueabi/libav/0.8.15-r0/packages-split/libavcodec/usr/lib/libavcodec.so.53.35.0'
has relocations in .text [textrel]
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] boost 1.56 compile fail

[Yi Qingliang]

hardware: samsung s3c6410

after updated to latest poky, the boost compile fail!

error info:
libs/atomic/src/lockpool.cpp:127:5: error: 'thread_fence' is not a member
of 'boost::atomics::detail'
libs/atomic/src/lockpool.cpp:138:5: error: 'signal_fence' is not a member
of 'boost::atomics::detail'


after dig into it, I found that:
the marco 'BOOST_ATOMIC_FLAG_LOCK_FREE' is 0, so it don't include
'operations_lockfree.hpp' which has 'thread_fence' and 'signal_fence', but
pthread.h at line 21.

in file 'caps_gcc_atomic.hpp', 'BOOST_ATOMIC_FLAG_LOCK_FREE' is set to '0',
the author think if '__GCC_ATOMIC_BOOL_LOCK_FREE' is 1, the atomic serial
function gcc provided is not lock free.

at the end of 'caps_gcc_atomic.hpp', it defined 'BOOST_ATOMIC_THREAD_FENCE'
as 2.

so the conflict is: *BOOST_ATOMIC_THREAD_FENCE* and
*BOOST_ATOMIC_FLAG_LOCK_FREE*

I don't know it is the new poky problem, or the boost problem, any idea?


Yi Qingliang
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] boost 1.56 compile fail

[Yi Qingliang]

and use 'gcc_atomic' in platform.hpp just for 4.8.x 4.9.x,


#if ((defined(__GNUC__)  ((__GNUC__ * 100 + __GNUC_MINOR__) = 407))

I don't know why low version gcc can do the lock free atomic operation, but
high version can't


On Fri, Aug 29, 2014 at 11:28 AM, Yi Qingliang niqingliang2...@gmail.com
wrote:

 hardware: samsung s3c6410

 after updated to latest poky, the boost compile fail!

 error info:
 libs/atomic/src/lockpool.cpp:127:5: error: 'thread_fence' is not a member
 of 'boost::atomics::detail'
 libs/atomic/src/lockpool.cpp:138:5: error: 'signal_fence' is not a member
 of 'boost::atomics::detail'


 after dig into it, I found that:
 the marco 'BOOST_ATOMIC_FLAG_LOCK_FREE' is 0, so it don't include
 'operations_lockfree.hpp' which has 'thread_fence' and 'signal_fence', but
 pthread.h at line 21.

 in file 'caps_gcc_atomic.hpp', 'BOOST_ATOMIC_FLAG_LOCK_FREE' is set to
 '0', the author think if '__GCC_ATOMIC_BOOL_LOCK_FREE' is 1, the atomic
 serial function gcc provided is not lock free.

 at the end of 'caps_gcc_atomic.hpp', it defined
 'BOOST_ATOMIC_THREAD_FENCE' as 2.

 so the conflict is: *BOOST_ATOMIC_THREAD_FENCE* and
 *BOOST_ATOMIC_FLAG_LOCK_FREE*

 I don't know it is the new poky problem, or the boost problem, any idea?


 Yi Qingliang

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] eglib is dead?

[Yi Qingliang]

Hello,

this morning I have seen that:
http://www.phoronix.com/scan.php?page=news_itempx=MTcyNDY

it said that the eglibc is a dead project, and most feature had 
been merged into glibc at version 2.19.

so maybe we should drop eglibc, and switch back to glibc?

Yi Qingliang
20140620
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] serial console problem

[Yi Qingliang]

Hi,
after update to the latest git version of poky, my image can't start 
the serial console,  i.e. I can't login, I'm using systemd as the init 
manager. any idea?

log:

Freeing init memory: 132K
systemd[1]: systemd 211 running in system mode. (-PAM +LIBWRAP -
AUDIT -SELINUX +IMA +SYSVINIT -LIBCRYPTSETUP -GCRYPT +ACL +XZ -
SECCOMP -APPARMOR)
systemd[1]: Detected architecture 'arm'.

Welcome to Linux!

systemd[1]: Failed to insert module 'autofs4'
systemd[1]: Failed to insert module 'ipv6'
systemd[1]: Set hostname to kl360.
systemd[1]: Initializing machine ID from random generator.
systemd[1]: Starting Forward Password Requests to Wall Directory 
Watch.
systemd[1]: Started Forward Password Requests to Wall Directory 
Watch.
systemd[1]: Expecting device dev-ttySAC0.device...
 Expecting device dev-ttySAC0.device...
systemd[1]: Starting Remote File Systems.
[  OK  ] Reached target Remote File Systems.
systemd[1]: Reached target Remote File Systems.
systemd[1]: Starting Dispatch Password Requests to Console Directory 
Watch.
systemd[1]: Started Dispatch Password Requests to Console Directory 
Watch.
systemd[1]: Starting Paths.
[  OK  ] Reached target Paths.
systemd[1]: Reached target Paths.
systemd[1]: Set up automount Arbitrary Executable File Formats File 
System Automount Point.
systemd[1]: Starting Swap.
[  OK  ] Reached target Swap.
systemd[1]: Reached target Swap.
systemd[1]: Starting Root Slice.
[  OK  ] Created slice Root Slice.
systemd[1]: Created slice Root Slice.
systemd[1]: Starting Journal Socket.
[  OK  ] Listening on Journal Socket.
systemd[1]: Listening on Journal Socket.
systemd[1]: Starting udev Control Socket.
[  OK  ] Listening on udev Control Socket.
systemd[1]: Listening on udev Control Socket.
systemd[1]: Starting Delayed Shutdown Socket.
[  OK  ] Listening on Delayed Shutdown Socket.
systemd[1]: Listening on Delayed Shutdown Socket.
systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
systemd[1]: Starting udev Kernel Socket.
[  OK  ] Listening on udev Kernel Socket.
systemd[1]: Listening on udev Kernel Socket.
systemd[1]: Starting User and Session Slice.
[  OK  ] Created slice User and Session Slice.
systemd[1]: Created slice User and Session Slice.
systemd[1]: Starting System Slice.
[  OK  ] Created slice System Slice.
systemd[1]: Created slice System Slice.
systemd[1]: Started Set Up Additional Binary Formats.
systemd[1]: Starting Journal Service...
 Starting Journal Service...
[  OK  ] Started Journal Service.
systemd[1]: Started Journal Service.
 Starting Apply Kernel Variables...
 Mounting POSIX Message Queue File System...
 Starting Create list of required static device nodes...rrent 
kernel...
 Starting udev Coldplug all Devices...
 Mounting Temporary Directory...
 Starting Remount Root and Kernel File Systems...

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] serial console problem

[Yi Qingliang]

On Wednesday, March 26, 2014 06:06:36 PM Yi Qingliang wrote:
 Hi,
   after update to the latest git version of poky, my image can't start
 the serial console,  i.e. I can't login, I'm using systemd as the init
 manager. any idea?
 
 log:
 
 Freeing init memory: 132K
 systemd[1]: systemd 211 running in system mode. (-PAM +LIBWRAP -
 AUDIT -SELINUX +IMA +SYSVINIT -LIBCRYPTSETUP -GCRYPT +ACL +XZ -
 SECCOMP -APPARMOR)
 systemd[1]: Detected architecture 'arm'.
 
 Welcome to Linux!
 
 systemd[1]: Failed to insert module 'autofs4'
 systemd[1]: Failed to insert module 'ipv6'
 systemd[1]: Set hostname to kl360.
 systemd[1]: Initializing machine ID from random generator.
 systemd[1]: Starting Forward Password Requests to Wall Directory
 Watch.
 systemd[1]: Started Forward Password Requests to Wall Directory
 Watch.
 systemd[1]: Expecting device dev-ttySAC0.device...
  Expecting device dev-ttySAC0.device...
 systemd[1]: Starting Remote File Systems.
 [  OK  ] Reached target Remote File Systems.
 systemd[1]: Reached target Remote File Systems.
 systemd[1]: Starting Dispatch Password Requests to Console 
Directory
 Watch.
 systemd[1]: Started Dispatch Password Requests to Console 
Directory
 Watch.
 systemd[1]: Starting Paths.
 [  OK  ] Reached target Paths.
 systemd[1]: Reached target Paths.
 systemd[1]: Set up automount Arbitrary Executable File Formats File
 System Automount Point.
 systemd[1]: Starting Swap.
 [  OK  ] Reached target Swap.
 systemd[1]: Reached target Swap.
 systemd[1]: Starting Root Slice.
 [  OK  ] Created slice Root Slice.
 systemd[1]: Created slice Root Slice.
 systemd[1]: Starting Journal Socket.
 [  OK  ] Listening on Journal Socket.
 systemd[1]: Listening on Journal Socket.
 systemd[1]: Starting udev Control Socket.
 [  OK  ] Listening on udev Control Socket.
 systemd[1]: Listening on udev Control Socket.
 systemd[1]: Starting Delayed Shutdown Socket.
 [  OK  ] Listening on Delayed Shutdown Socket.
 systemd[1]: Listening on Delayed Shutdown Socket.
 systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
 [  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
 systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
 systemd[1]: Starting udev Kernel Socket.
 [  OK  ] Listening on udev Kernel Socket.
 systemd[1]: Listening on udev Kernel Socket.
 systemd[1]: Starting User and Session Slice.
 [  OK  ] Created slice User and Session Slice.
 systemd[1]: Created slice User and Session Slice.
 systemd[1]: Starting System Slice.
 [  OK  ] Created slice System Slice.
 systemd[1]: Created slice System Slice.
 systemd[1]: Started Set Up Additional Binary Formats.
 systemd[1]: Starting Journal Service...
  Starting Journal Service...
 [  OK  ] Started Journal Service.
 systemd[1]: Started Journal Service.
  Starting Apply Kernel Variables...
  Mounting POSIX Message Queue File System...
  Starting Create list of required static device nodes...rrent
 kernel...
  Starting udev Coldplug all Devices...
  Mounting Temporary Directory...
  Starting Remount Root and Kernel File Systems..


after CONFIG_FHANDLE=y in kernel, everything OK!
please refer:
http://lists.freedesktop.org/archives/systemd-devel/2014-February/016927.html


-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] serial console problem

[Yi Qingliang]

On Wednesday, March 26, 2014 11:16:44 AM Jacob Kroon wrote:
 Hi Yi,
 
 On Wed, Mar 26, 2014 at 11:06 AM, Yi Qingliang 
niqingliang2...@gmail.comwrote:
  Hi,
  
  after update to the latest git version of poky, my image can't
  
  start
  the serial console,  i.e. I can't login, I'm using systemd as the init
  manager. any idea?
  
  log:
  
  Freeing init memory: 132K
  systemd[1]: systemd 211 running in system mode. (-PAM +LIBWRAP 
-
  AUDIT -SELINUX +IMA +SYSVINIT -LIBCRYPTSETUP -GCRYPT +ACL +XZ 
-
  SECCOMP -APPARMOR)
  systemd[1]: Detected architecture 'arm'.
  
  Welcome to Linux!
  
  systemd[1]: Failed to insert module 'autofs4'
  systemd[1]: Failed to insert module 'ipv6'
  systemd[1]: Set hostname to kl360.
  systemd[1]: Initializing machine ID from random generator.
  systemd[1]: Starting Forward Password Requests to Wall Directory
  Watch.
  systemd[1]: Started Forward Password Requests to Wall Directory
  Watch.
  systemd[1]: Expecting device dev-ttySAC0.device...
  
   Expecting device dev-ttySAC0.device...
  
  systemd[1]: Starting Remote File Systems.
  [  OK  ] Reached target Remote File Systems.
  systemd[1]: Reached target Remote File Systems.
  systemd[1]: Starting Dispatch Password Requests to Console 
Directory
  Watch.
  systemd[1]: Started Dispatch Password Requests to Console 
Directory
  Watch.
  systemd[1]: Starting Paths.
  [  OK  ] Reached target Paths.
  systemd[1]: Reached target Paths.
  systemd[1]: Set up automount Arbitrary Executable File Formats 
File
  System Automount Point.
  systemd[1]: Starting Swap.
  [  OK  ] Reached target Swap.
  systemd[1]: Reached target Swap.
  systemd[1]: Starting Root Slice.
  [  OK  ] Created slice Root Slice.
  systemd[1]: Created slice Root Slice.
  systemd[1]: Starting Journal Socket.
  [  OK  ] Listening on Journal Socket.
  systemd[1]: Listening on Journal Socket.
  systemd[1]: Starting udev Control Socket.
  [  OK  ] Listening on udev Control Socket.
  systemd[1]: Listening on udev Control Socket.
  systemd[1]: Starting Delayed Shutdown Socket.
  [  OK  ] Listening on Delayed Shutdown Socket.
  systemd[1]: Listening on Delayed Shutdown Socket.
  systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
  [  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
  systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
  systemd[1]: Starting udev Kernel Socket.
  [  OK  ] Listening on udev Kernel Socket.
  systemd[1]: Listening on udev Kernel Socket.
  systemd[1]: Starting User and Session Slice.
  [  OK  ] Created slice User and Session Slice.
  systemd[1]: Created slice User and Session Slice.
  systemd[1]: Starting System Slice.
  [  OK  ] Created slice System Slice.
  systemd[1]: Created slice System Slice.
  systemd[1]: Started Set Up Additional Binary Formats.
  systemd[1]: Starting Journal Service...
  
   Starting Journal Service...
  
  [  OK  ] Started Journal Service.
  systemd[1]: Started Journal Service.
  
   Starting Apply Kernel Variables...
   Mounting POSIX Message Queue File System...
   Starting Create list of required static device nodes...rrent
  
  kernel...
  
   Starting udev Coldplug all Devices...
   Mounting Temporary Directory...
   Starting Remount Root and Kernel File Systems...
 
 I had a very similar problem on my Wandboard, using latest systemd 
211.
 The solution for me was to enable CONFIG_FHANDLE in the kernel
 configuration.
 Maybe that could work for you aswell.
 Which makes me wonder if there is any sort infrastructre for handling
 kernel config. deps.
 /Jacob

thanks! it work now.

the kernel config is a problem. my own kernel can't follow the change 
closely.


-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] kernel and boost will recompile every time

[Yi Qingliang]

Hello.

I know the kernel will recompile every time for recent update, and I 
found the boost will also do like that, even I have sstate cache in my own 
server.

How to debug this problem?


-- 
Nanjing Jilong
Yi Qingliang
niqingliang2...@gmail.com
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] kernel and boost will recompile every time

[Yi Qingliang]

On Wednesday, November 27, 2013 03:03:36 AM Martin Jansa wrote:
 On Wed, Nov 27, 2013 at 09:51:22AM +0800, Yi Qingliang wrote:
  Hello.
  
  I know the kernel will recompile every time for recent update, and I
  
  found the boost will also do like that, even I have sstate cache in my own
  server.
  
  How to debug this problem?
 
 kernel rebuilding was fixed few days ago, do you have latest revision?
 
 You can use scripts/sstate-diff-machines.sh to store the signatures
 and then compare them when you notice something unexpectedly rebuilding.

thanks, I will try


-- 
Nanjing Jilong
Yi Qingliang
niqingliang2...@gmail.com
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] kernel build fail after update

[Yi Qingliang]

On Tuesday, November 19, 2013 11:35:14 AM Phil Blundell wrote:
 On Tue, 2013-11-19 at 09:24 +, Phil Blundell wrote:
  On Tue, 2013-11-19 at 07:21 +0800, Yi Qingliang wrote:
  I found one patch 'Use hardlinks for do_populate_sysroot for speed'
  may be related with this error.
  
  The failure only seems to occur with the kernel, whereas I think that
  patch applies to all recipes.
 
 I realise now that this isn't true; assuming you meant
 13259459e200a237ca486cbe1123a0b0a4d1eebf then this is indeed specific to
 kernel.bbclass.
 
 p.

Yes, that is it. 

-- 
Nanjing Jilong
Yi Qingliang
niqingliang2...@gmail.com
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] kernel build fail after update

[Yi Qingliang]

after update poky, I got error when compile my own kernel, it looks like there 
is no directory '/mnt/src/kl360-build/tmp/work/kl360-jilong-linux-
gnueabi/linux-jilong/3.9.4-gitAUTOINC+5dbff4f559/image'.

in my bb file, I only inherit kernel.

I found one patch 'Use hardlinks for do_populate_sysroot for speed' may be 
related with this error.





ERROR: Error executing a python function in /mnt/src/optimus/poky/../meta-
jilong/recipes-kernel/linux/linux-jilong.bb:

The stack trace of python calls that resulted in this exception/failure was:
File: 'sysroot_stage_all', lineno: 6, function: module
 0002:def sysroot_stage_all(d):
 0003:oe.path.copyhardlinktree(d.expand(/mnt/src/kl360-
build/tmp/work/kl360-jilong-linux-gnueabi/linux-jilong/3.9.4-
gitAUTOINC+5dbff4f559/image/usr/src/kernel), d.expand(/mnt/src/kl360-
build/tmp/work/kl360-jilong-linux-gnueabi/linux-jilong/3.9.4-
gitAUTOINC+5dbff4f559/sysroot-destdir//usr/src/kernel))
 0004:
 0005:
 *** 0006:sysroot_stage_all(d)
 0007:
File: 'sysroot_stage_all', lineno: 3, function: sysroot_stage_all
 0001:
 0002:def sysroot_stage_all(d):
 *** 0003:oe.path.copyhardlinktree(d.expand(/mnt/src/kl360-
build/tmp/work/kl360-jilong-linux-gnueabi/linux-jilong/3.9.4-
gitAUTOINC+5dbff4f559/image/usr/src/kernel), d.expand(/mnt/src/kl360-
build/tmp/work/kl360-jilong-linux-gnueabi/linux-jilong/3.9.4-
gitAUTOINC+5dbff4f559/sysroot-destdir//usr/src/kernel))
 0004:
 0005:
 0006:sysroot_stage_all(d)
 0007:
File: '/mnt/src/optimus/poky/meta/lib/oe/path.py', lineno: 93, function: 
copyhardlinktree
 0089:bb.utils.mkdirhier(dst)
 0090:if os.path.isdir(src) and not len(os.listdir(src)):
 0091:return
 0092:
 *** 0093:if (os.stat(src).st_dev ==  os.stat(dst).st_dev):
 0094:# Need to copy directories only with tar first since cp will 
error if two
 0095:# writers try and create a directory at the same time
 0096:cmd = 'cd %s; find . -type d -print | tar -cf - -C %s -p --
files-from - --no-recursion | tar -xf - -C %s' % (src, src, dst)
 0097:check_output(cmd, shell=True, stderr=subprocess.STDOUT)
Exception: OSError: [Errno 2] No such file or directory: '/mnt/src/kl360-
build/tmp/work/kl360-jilong-linux-gnueabi/linux-jilong/3.9.4-
gitAUTOINC+5dbff4f559/image/usr/src/kernel'

ERROR: Function failed: sysroot_stage_all
ERROR: Logfile of failure stored in: /mnt/src/kl360-build/tmp/work/kl360-
jilong-linux-gnueabi/linux-jilong/3.9.4-
gitAUTOINC+5dbff4f559/temp/log.do_populate_sysroot.5146
ERROR: Task 3 (/mnt/src/optimus/poky/../meta-jilong/recipes-
kernel/linux/linux-jilong.bb, do_populate_sysroot) failed with exit code '1'


-- 
Nanjing Jilong
Yi Qingliang
niqingliang2...@gmail.com
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] boost package fail

[Yi Qingliang]

Hello,

I'm working on Archlinux x64. when packaging boost, I got error:

arm-jilong-linux-gnueabi-objcopy:/xxx/tmp/work/armv6-vfp-jilong-linux-
gnueabi/boost/1.54.0-r0/package/usr/lib/libboost_iostreams.so.1.54.0: File 
format not recognized

I don't know why boost compiled with host ARCH.
but I have one machine can done it correctly.
So I compared the two machine, the 'bjam --help' command result is 
different after source yocto environment.

on the failure machine, it will use '/usr/share/boost-build/user-
config.jam'. the success machine don't have this file.

so the different result in this error is: the failure machine installed 
package 'boost-build'.

after remove 'boost-build' from Archlinux and bitbake -c clean boost,
I have done package correctly.

I think it is oe bug, do you think so:)?

-- 
Nanjing Jilong
Yi Qingliang
niqingliang2...@gmail.com
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] systemd getty

[Yi Qingliang]

Hello,
my QT app can't response to key, when tty1 hold by getty.
how to disable getty@tty1.service when generating image?


-- 
Nanjing Jilong
Yi Qingliang
niqingliang2...@gmail.com
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] qt 4.8.5 package error

[Yi Qingliang]

On Monday, July 15, 2013 09:48:15 AM Paul Eggleton wrote:
 On Monday 15 July 2013 09:12:23 Yi Qingliang wrote:
  hello,
  
  I'm using latest poky, when packaging qte, got following error, any 
  idea?
  
 
 Please pull the latest changes, this has been switched back to a warning.

it was latest already, two days before.
I just updated it , no new commit.
maybe you can tell me which commit switched it back to warning?
thanks!

 
 Cheers,
 Paul
-- 
Nanjing Jilong
Yi Qingliang
niqingliang2...@gmail.com
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] boost 1.54 compile fail

[Yi Qingliang]

On Thursday, July 11, 2013 09:30:30 AM Martin Jansa wrote:
 On Thu, Jul 11, 2013 at 09:54:28AM +0800, Yi Qingliang wrote:
  maybe it is the gcc's fault (recently it is updated to 4.8.x in poky)
  
  I can found uintptr_t in cstdint, but it is wrapped by a c99 related
  macro.
 
 See
 http://lists.openembedded.org/pipermail/openembedded-devel/2013-July/091331.
 html https://lists.yoctoproject.org/pipermail/yocto/2013-July/017159.html
 threads

thanks! I have checked that, but the answer is not obvious,
what is the reason? gcc ? eglibc ? or boost ?

 
  On Wednesday, July 10, 2013 04:21:02 PM Yi Qingliang wrote:
   Hello!
   
   after update poky to latest git version, I got failure when compiling
   boost:
   
   the main error is: (indeed, and too many warning!)
   
   | ./boost/atomic/atomic.hpp:202:16: error: 'uintptr_t' was not declared
   | in
   
   this scope
   
   |  typedef atomicuintptr_t atomic_uintptr_t;
   |  
   | ^
   | 
   | ./boost/atomic/atomic.hpp:202:25: error: template argument 1 is
   | invalid
   | 
   |  typedef atomicuintptr_t atomic_uintptr_t;
   |  
   |  ^
   | 
   | ./boost/atomic/atomic.hpp:202:43: error: invalid type in declaration
   | before
   
   ';' token
   
   |  typedef atomicuintptr_t atomic_uintptr_t;
   |  
   |^
   | 
   | In file included from ./boost/system/system_error.hpp:14:0,
   | 
   |  from ./boost/thread/exceptions.hpp:22,
   |  from ./boost/thread/pthread/thread_data.hpp:10,
   |  from ./boost/thread/thread_only.hpp:17,
   |  from libs/thread/src/pthread/thread.cpp:11:
-- 
Nanjing Jilong
Yi Qingliang
niqingliang2...@gmail.com
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] boost 1.54 compile fail

[Yi Qingliang]

Hello!

after update poky to latest git version, I got failure when compiling boost:

the main error is: (indeed, and too many warning!)

| ./boost/atomic/atomic.hpp:202:16: error: 'uintptr_t' was not declared in 
this scope
|  typedef atomicuintptr_t atomic_uintptr_t;
| ^
| ./boost/atomic/atomic.hpp:202:25: error: template argument 1 is invalid
|  typedef atomicuintptr_t atomic_uintptr_t;
|  ^
| ./boost/atomic/atomic.hpp:202:43: error: invalid type in declaration before 
';' token
|  typedef atomicuintptr_t atomic_uintptr_t;
|^
| In file included from ./boost/system/system_error.hpp:14:0,
|  from ./boost/thread/exceptions.hpp:22,
|  from ./boost/thread/pthread/thread_data.hpp:10,
|  from ./boost/thread/thread_only.hpp:17,
|  from libs/thread/src/pthread/thread.cpp:11:



-- 
Nanjing Jilong
Yi Qingliang
niqingliang2...@gmail.com
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] boost 1.54 compile fail

[Yi Qingliang]

maybe it is the gcc's fault (recently it is updated to 4.8.x in poky)

I can found uintptr_t in cstdint, but it is wrapped by a c99 related macro.


On Wednesday, July 10, 2013 04:21:02 PM Yi Qingliang wrote:
 Hello!
 
 after update poky to latest git version, I got failure when compiling boost:
 
 the main error is: (indeed, and too many warning!)
 
 | ./boost/atomic/atomic.hpp:202:16: error: 'uintptr_t' was not declared in
 
 this scope
 
 |  typedef atomicuintptr_t atomic_uintptr_t;
 |  
 | ^
 | 
 | ./boost/atomic/atomic.hpp:202:25: error: template argument 1 is invalid
 | 
 |  typedef atomicuintptr_t atomic_uintptr_t;
 |  
 |  ^
 | 
 | ./boost/atomic/atomic.hpp:202:43: error: invalid type in declaration
 | before
 
 ';' token
 
 |  typedef atomicuintptr_t atomic_uintptr_t;
 |  
 |^
 | 
 | In file included from ./boost/system/system_error.hpp:14:0,
 | 
 |  from ./boost/thread/exceptions.hpp:22,
 |  from ./boost/thread/pthread/thread_data.hpp:10,
 |  from ./boost/thread/thread_only.hpp:17,
 |  from libs/thread/src/pthread/thread.cpp:11:
-- 
Nanjing Jilong
Yi Qingliang
niqingliang2...@gmail.com
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] nativesdk-dbus do_package error

[Yi Qingliang]

I'm using 'systemd'
when building 'meta-toolchain-qte', got following error:

ERROR: QA Issue: nativesdk-dbus: Files/directories were installed but not 
shipped
  /run
  /run/dbus
ERROR: QA Issue: Found library in wrong location: 
/lib/systemd/system/dbus.socket
Found library in wrong location: 
/lib/systemd/system/dbus.target.wants/dbus.socket
Found library in wrong location: 
/lib/systemd/system/sockets.target.wants/dbus.socket
ERROR: QA run found fatal errors. Please consider fixing them.
ERROR: Function failed: do_package_qa
ERROR: Logfile of failure stored in: /media/datum/repo/arm9plf-
build/tmp/work/x86_64-nativesdk-optimussdk-linux/nativesdk-dbus/1.6.8-
r6.0/temp/log.do_package.10490
ERROR: Task 1658 
(virtual:nativesdk:/media/datum/repo/optimus/poky/meta/recipes-
core/dbus/dbus_1.6.8.bb, do_package) failed with exit code '1'
NOTE: Tasks Summary: Attempted 4092 tasks of which 3232 didn't need to be 
rerun and 1 failed.



-- 
Nanjing Jilong
Yi Qingliang
niqingliang2...@gmail.com
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] systemd

[Yi Qingliang]

Hi, All:

I want use systemd, add following into my own distro.conf
 DISTRO_FEATURES_append =  systemd
 VIRTUAL-RUNTIME_init_manager = systemd
 DISTRO_FEATURES_BACKFILL_CONSIDERED = sysvinit

but when do_rootfs for my own image, I got error:
 error: package update-rc.d is not installed
 error: package base-passwd is not installed
 error: package run-postinsts is not installed

Any idea? Thanks!

-- 
Nanjing Jilong
Yi Qingliang
niqingliang2...@gmail.com
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] qt keyboard problem

[Yi Qingliang]

On Thursday, May 16, 2013 04:51:04 PM Slater, Joseph wrote:
  -Original Message-
  From: openembedded-core-boun...@lists.openembedded.org
  [mailto:openembedded-core- boun...@lists.openembedded.org] On Behalf Of
  Yi Qingliang
  Sent: Tuesday, May 14, 2013 11:19 PM
  To: openembedded-core@lists.openembedded.org oe-core layer
  Subject: [OE-core] qt keyboard problem
  
  Hello, all.
  
  I'm running qt application on yocto's qt image. cpu is s3c2442, like
  mini2440.
  
  the problem is:
  
  key event issued by pressing gpio-key eat by 'getty' (from busybox),
  my application can't receive input event,
  if I remove respawn 'getty' for tty1 in /etc/inittab, everything ok.
 
 This could be the same thing I have seen in a slightly different context.
 If so, you can keep the getty's attached to VT's.  Just move the line in
 inittab that starts runlevel 5 to the very end of inittab.  As long as the
 getty's start first, you'll be okay.

you mean: move 'id:5:initdefault:' as the last line of the file, right?







# /etc/inittab: init(8) configuration.
# $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $

# The default runlevel.
id:5:initdefault:

# Boot-time system configuration/initialization script.
# This is run first except when booting in emergency (-b) mode.
si::sysinit:/etc/init.d/rcS

# What to do in single-user mode.
~~:S:wait:/sbin/sulogin

# /etc/init.d executes the S and K scripts upon change
# of runlevel.
#
# Runlevel 0 is halt.
# Runlevel 1 is single-user.
# Runlevels 2-5 are multi-user.
# Runlevel 6 is reboot.

l0:0:wait:/etc/init.d/rc 0
l1:1:wait:/etc/init.d/rc 1
l2:2:wait:/etc/init.d/rc 2
l3:3:wait:/etc/init.d/rc 3
l4:4:wait:/etc/init.d/rc 4
l5:5:wait:/etc/init.d/rc 5
l6:6:wait:/etc/init.d/rc 6
# Normally not reached, but fallthrough in case of emergency.
z6:6:respawn:/sbin/sulogin
S:2345:respawn:/sbin/getty 115200 ttySAC0
# /sbin/getty invocations for the runlevels.
#
# The id field MUST be the same as the last
# characters of the device (after tty).
#
# Format:
#  id:runlevels:action:process
#

1:2345:respawn:/sbin/getty 38400 tty1



 
 Joe
 
  any idea?
  
  
  --
  Nanjing Jilong
  Yi Qingliang
  niqingliang2...@gmail.com
  
  ___
  Openembedded-core mailing list
  Openembedded-core@lists.openembedded.org
  http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
-- 
Nanjing Jilong
Yi Qingliang
niqingliang2...@gmail.com

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

[OE-core] qt keyboard problem

[Yi Qingliang]

Hello, all.

I'm running qt application on yocto's qt image. cpu is s3c2442, like mini2440.

the problem is:

key event issued by pressing gpio-key eat by 'getty' (from busybox), 
my application can't receive input event,
if I remove respawn 'getty' for tty1 in /etc/inittab, everything ok.

any idea?


-- 
Nanjing Jilong
Yi Qingliang
niqingliang2...@gmail.com

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

Re: [OE-core] qt keyboard problem

[Yi Qingliang]

On Wednesday, May 15, 2013 10:18:41 AM Mike Looijmans wrote:
 On 05/15/2013 10:10 AM, Yi Qingliang wrote:
  On Wednesday, May 15, 2013 10:05:45 AM Mike Looijmans wrote:
  On 05/15/2013 08:19 AM, Yi Qingliang wrote:
  I'm running qt application on yocto's qt image. cpu is s3c2442, like
  mini2440.
  
  the problem is:
  
  key event issued by pressing gpio-key eat by 'getty' (from busybox),
  my application can't receive input event,
  if I remove respawn 'getty' for tty1 in /etc/inittab, everything ok.
  
  I solved it by no longer starting the console login. Set the following
  in one of your .conf files (distro or local.conf):
  
  USE_VT = 0
  SYSVINIT_ENABLED_GETTYS = 
  
  You may need to rebuild initscripts for this to have effect.
 
 Alternatively, you could disconnect the console when the GUI starts. You
 probably have some script that sets things up and starts the GUI, so you
 could extend it with the console on/off function.
 
 That allows you to see the boot log on the screen for example, and debug
 things via the console when the GUI isn't running.

Good idea!

 
 I forgot how to do that though, I think is was something in /proc/.

if you remembered, tell me please! thanks!

 
 Mike.
-- 
Nanjing Jilong
Yi Qingliang
niqingliang2...@gmail.com

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

Re: [OE-core] systemd/sysvinit in the 1.4 release

[Yi Qingliang]

Who need hybrid mode?

On Thursday, April 18, 2013 08:29:20 AM Richard Purdie wrote:
 I just wanted to be clear with people what has gone on with sysvinit and
 systemd in the 1.4 release.
 
 Basically I took some patches recently on a trust that certain things
 had been checked and it was found that there were problems with the
 changes after they went in. At some point I have to trust the data I'm
 getting and in this case things broke down.
 
 Since systemd is one of the priority features of this release, releasing
 with it broken was not the right thing to do so at the last minute we've
 basically reverted some of the recent changes to systemd and udev
 (the /sbin relocation) and then tried to fix various issues that arose
 from that (even with the reverts, there were still several issues). I
 appreciate this isn't an ideal thing to do either.
 
 We now have a build of the dylan branch which is likely to become rc2
 and get tested by QA and may well be the final release. We're past the
 point we can consider any changes unless something is seriously broken.
 We're trying to do some additional testing today to determine whether
 there is anything seriously wrong with the recent changes.
 
 I would point out that having the systemd + sysvinit hybrid mode which
 is not something we'd originally planned for gives us a ton of headaches
 since we have to test:
 
 systemd only
 systemd+sysvinit in systemd mode
 systemd+sysvinit in sysvinit mode
 sysinit only
 
 and for each we need to test for each architecture and we then need to
 look at for example multilibs in each case. Currently the autobuilder
 isn't able to help with this although obviously that is something we
 need to fix in the 1.5 cycle.
 
 Cheers,
 
 Richard
 
 
 
 
 
 ___
 Openembedded-core mailing list
 Openembedded-core@lists.openembedded.org
 http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
-- 
Nanjing Jilong
Yi Qingliang
niqingliang2...@gmail.com

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

Re: [OE-core] [PATCH] local.conf.sample: Have comments ready to go for quad-core (4 - 8).

[Yi Qingliang]

On Thursday, April 18, 2013 09:57:16 PM Elvis Dowson wrote:
 On Apr 18, 2013, at 8:51 PM, Robert P. J. Day rpj...@crashcourse.ca 
wrote:
  On Thu, 18 Apr 2013, Enrico Scholz wrote:
  Robert P. J. Day rpjday-L09J2beyid0N/h6p543...@public.gmane.org
  
  writes:
  Have default, commented values for parallelism reflect quad-core
  hosts.
  
  fwiw, I use
  
  PARALLEL_MAKE = \
  
   -j ${@int(os.sysconf(os.sysconf_names['SC_NPROCESSORS_ONLN'])) * 2} \
   -l ${@int(os.sysconf(os.sysconf_names['SC_NPROCESSORS_ONLN'])) *
   150/100} \
  
  
  
  BB_NUMBER_THREADS ?= \
  
   ${@int(os.sysconf(os.sysconf_names['SC_NPROCESSORS_ONLN'])) * 150/100}
  
  which adjusts parallelism automatically.
  
   i'd be perfectly fine with that, too, if someone wants to put that
  
  in instead.
 
 I've noticed that on a quad-core machine (i7) the best setting is to leave
 it at 6 for BB_NUMBER_THREADS and PARALLEL_MAKE.
maybe we need consider the hyper-threading.

CPU_PROC_NUM=`grep ^processor /proc/cpuinfo | sort -u | wc -l`
CPU_CORE_NUM=`grep ^core id /proc/cpuinfo | sort -u | wc -l`

 8, 16, etc don't have any discernable impact, perhaps save 30 to 40 seconds
 off a build. The 3.5Ghz standard CPU frequency can be over-clocked to as
 high as 4.5GHz, but I tested it out at 4.2Ghz and 3.8Ghz, and the
 difference was only 2 to 3 minutes between 3.8GHz and 4.2GHz over-clocked,
 so I currently leave it at 3.8GHz over-clocked.
 
 I'm using two SSDs in a RAID 0 striped configuration, and build times is
 around 22 minutes for a Zynq-7-ZC702 build for core-image-minimal.
 
 Elvis Dowson
 ___
 Openembedded-core mailing list
 Openembedded-core@lists.openembedded.org
 http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
-- 
Nanjing Jilong
Yi Qingliang
niqingliang2...@gmail.com

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

Re: [OE-core] gcc compile error

[Yi Qingliang]

On Tuesday, April 16, 2013 09:10:43 AM Jack Mitchell wrote:
 On 16/04/13 05:38, Yi Qingliang wrote:
  hello, i'm using archlinux, the gcc is 4.8.0.
  
  when compiling gcc 4.7.2 in oe, I got the error:
  | /mnt/src/arm9plf-build/tmp/work-shared/gcc-4.7.2-
  
  r19/gcc-4.7.2/libgcc/libgcc2.c: In function '__absvdi2':
  | /mnt/src/arm9plf-build/tmp/work-shared/gcc-4.7.2-
  
  r19/gcc-4.7.2/libgcc/libgcc2.c:273:1: internal compiler error:
  Segmentation
  fault
 
 Hi,
 
 Many people have run into this problem so far (myself included) and I
 have been told it is the fault of the ArchLinux GCC. Now, I noticed the
 ArchLinux devs pushed a new build of GCC out yesterday, have you tried
 upgrading to that yet and giving it another go?

NO LUCK!

 
 If not, my solution was to move to GCC 4.8 using the patches posted to
 oe-core/oe-dev.

when the oe will upgrade gcc to 4.8 or 4.7.3?

 
 Regards,
 Jack.
-- 
Nanjing Jilong
Yi Qingliang
niqingliang2...@gmail.com

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

[OE-core] gcc compile error

[Yi Qingliang]

hello, i'm using archlinux, the gcc is 4.8.0.

when compiling gcc 4.7.2 in oe, I got the error:

| /mnt/src/arm9plf-build/tmp/work-shared/gcc-4.7.2-
r19/gcc-4.7.2/libgcc/libgcc2.c: In function '__absvdi2':
| /mnt/src/arm9plf-build/tmp/work-shared/gcc-4.7.2-
r19/gcc-4.7.2/libgcc/libgcc2.c:273:1: internal compiler error: Segmentation 
fault



-- 
Nanjing Jilong
Yi Qingliang
niqingliang2...@gmail.com

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

Re: [OE-core] [RFT] GCC 4.8 recipes

[Yi Qingliang]

GREAT!
qt5 is another one I expected!

On Wednesday, March 27, 2013 10:51:50 PM Khem Raj wrote:
 All,
 
 I have added gcc 4.8 recipes and the branch is here
 
 git://git.openembedded.org/openembedded-core-contrib kraj/gcc-4.8
 
 cgit
 
 http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/gcc-4.8
 
 Please test it out on your respective environments if you can.
 
 To enable gcc 4.8 with OE-Core you would
 
 in local.conf set
 
 GCCVERSION = 4.8%
 
 and if you use angstrom. Please checkout 'next' branch of setup-scripts
 and then in conf/local.conf
 
 set
 
 ANGSTROM_GCC_VERSION = 4.8%
 
 My testing so far has been building systems-image for all qemu machines and
 they seem to boot as good as 4.7 did. But I am hoping for wider testing and
 finding issues or very least improve the existing recipes for now and once
 the 1.4 release is done we can then propose it for inclusion in OE-Core
 
 Thanks for your time
 
 
 -Khem
 ___
 Openembedded-core mailing list
 Openembedded-core@lists.openembedded.org
 http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
-- 
Nanjing Jilong
Yi Qingliang
niqingliang2...@gmail.com

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

Re: [OE-core] [RFT] GCC 4.8 recipes

[Yi Qingliang]

it looks like no qt5 embedded?

On Thursday, March 28, 2013 09:29:15 AM Koen Kooi wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 Op 28-03-13 08:36, Yi Qingliang schreef:
  GREAT! qt5 is another one I expected!
 
 https://github.com/meta-qt5/meta-qt5
 
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.5 (Darwin)
 Comment: GPGTools - http://gpgtools.org
 
 iD8DBQFRU/9bMkyGM64RGpERAl3QAKCAXp4hOpSuwT1rLiiuSnvz9IIuhACgiprj
 EQ1skA1go8deCsQFpfCI61U=
 =jolz
 -END PGP SIGNATURE-
 
 
 ___
 Openembedded-core mailing list
 Openembedded-core@lists.openembedded.org
 http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
-- 
Nanjing Jilong
Yi Qingliang
niqingliang2...@gmail.com

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

[OE-core] own-mirrors parse error?

[Yi Qingliang]

I have set SOURCE_MIRROR_URL to my own http server.

when fetching ftp package, e.g. gcc, it will use my server, and done quickly.
but if fetching http package, e.g. db, it will not use my server, but use 
official address.

after checked meta/classes/own-mirrors.bbclass, it contain:
https?$://.*/.* ${SOURCE_MIRROR_URL}

there is not http://, after added:
http://.*/.*${SOURCE_MIRROR_URL}
everything is OK.

so maybe recent commit broke up the https?$ parsing?



-- 
Nanjing Jilong
Yi Qingliang
niqingliang2...@gmail.com

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

[OE-core] download speed problem

[Yi Qingliang]

did you have done speed limit for the yocto source server recently?
I can only get  10KBps :(


-- 
Nanjing Jilong
Yi Qingliang
niqingliang2...@gmail.com

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

Re: [OE-core] core-image-minimal boot problem

[Yi Qingliang]

I have debugged the sysvinit, found that:
the 30seconds is about close(fd) in function:
void print(char *s) (src/init.c)

and the close return 0.
why close will hang for 30seconds?
I asked in sysvinit-devel email list, no response.

anyone can give some suggestion?
THANKS

Nanjing Jilong
Yi Qingliang


On Mon, Jan 14, 2013 at 7:23 AM, Yi Qingliang niqingliang2...@gmail.comwrote:

 I have got something,
 after change the DEBUG to 1 in sysvinit/src/init.h, the pause between
 and after INIT: version 2.88 booting missed.
 add -i to the /sbin/agetty line in /etc/inittab, I got the login prompt,
 (it mean do not display issue).
 but, but, what's the problem.


 On Sun, Jan 13, 2013 at 4:29 PM, Yi Qingliang 
 niqingliang2...@gmail.comwrote:

 can you give some suggestions?
 I have struggled on it for 4days with a big headache.:(

 On Sunday, January 13, 2013 07:29:52 PM Yi Qingliang wrote:
  I have compiled a core-image-minimal running on my s3c2442 board.
  both the kernel and barebox are compiled based on mini2440.
 
  the fs is ubifs.
 
  after set rtc, stop several seconds.
  and the continue mount rootfs.
  when execute sysvinit,
  after print INIT:, stop long time, and then print  version 2.88
 booting.
  stop long time, print a newline.
  stop long time, continue.
  and finally, no shell prompt occur.
 
  I have checked sysvinit code, the INIT: and version 2.88 booting are
  only continuous print, it should not pause between them.
 
  I have changed ubifs to cramfs, no luck.
  and if I uncheck the s3c nand debug option in kernel configuration,
  I can get shell prompt, and login the system, and only that, the boot
 time
  no change.
 
  is there someone can help me?
 
 
 
  =ATTACHE FILE=
 
 
  the serial output is:
 
  booting kernel from /dev/nand0.kernel.bb
  commandline: console=ttySAC0,115200 mini2440=0tbc LANG=en_US.UTF-8
 ip=dhcp
  root=ubi0:arm9plf-rootfs ubi.mtd=3 rootfstype=ubifs noinit
  rd mtdparts=nand:768k(barebox),256k(bareboxenv),5M(kernel),-(fs)
  arch_number: 1999
  Uncompressing Linux... done, booting the kernel.
  Booting Linux on physical CPU 0
  Linux version 3.7.2 (ll@ll-pc) (gcc version 4.7.2 (GCC) ) #23 Sun Jan
 13
  19:14:52 CST 2013
  CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
  CPU: VIVT data cache, VIVT instruction cache
  Machine: NJJL2442
  Memory policy: ECC disabled, Data cache writeback
  CPU S3C2442B (id 0x32440aab)
  S3C24XX Clocks, Copyright 2004 Simtec Electronics
  S3C244X: core 405.000 MHz, memory 101.250 MHz, peripheral 50.625 MHz
  CLOCK: Slow mode (1.500 MHz), fast, MPLL on, UPLL on
  Built 1 zonelists in Zone order, mobility grouping on.  Total pages:
 16256
  Kernel command line: console=ttySAC0,115200 mini2440=0tbc
 LANG=en_US.UTF-8
  ip=dhcp root=ubi0:arm9plf-rootfs ubi.mtd=3 rootfstype=ubif
  s noinitrd mtdparts=nand:768k(barebox),256k(bareboxenv),5M(kernel),-(fs)
  PID hash table entries: 256 (order: -2, 1024 bytes)
  Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
  Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
  Memory: 64MB = 64MB total
  Memory: 60440k/60440k available, 5096k reserved, 0K highmem
  Virtual kernel memory layout:
  vector  : 0x - 0x1000   (   4 kB)
  fixmap  : 0xfff0 - 0xfffe   ( 896 kB)
  vmalloc : 0xc480 - 0xff00   ( 936 MB)
  lowmem  : 0xc000 - 0xc400   (  64 MB)
  modules : 0xbf00 - 0xc000   (  16 MB)
.text : 0xc0008000 - 0xc03f57dc   (4022 kB)
.init : 0xc03f6000 - 0xc04170dc   ( 133 kB)
.data : 0xc0418000 - 0xc043d720   ( 150 kB)
 .bss : 0xc043d744 - 0xc046299c   ( 149 kB)
  NR_IRQS:85
  irq: clearing subpending status 0002
  sched_clock: 32 bits at 200 Hz, resolution 500ns, wraps every
  4294967291ms Console: colour dummy device 80x30
  Calibrating delay loop... 201.52 BogoMIPS (lpj=503808)
  pid_max: default: 32768 minimum: 301
  Mount-cache hash table entries: 512
  CPU: Testing write buffer coherency: ok
  Setting up static identity map for 0x3030ab68 - 0x3030abc0
  devtmpfs: initialized
  NET: Registered protocol family 16
  DMA: preallocated 256 KiB pool for atomic coherent allocations
  MINI2440: Option string mini2440=0tbc
  MINI2440: 't' ignored, touchscreen not compiled in
  MINI2440: LCD [0:240x320] 1:800x480 2:1024x768 3:320x240
  S3C2442: Initialising architecture
  S3C24XX DMA Driver, Copyright 2003-2006 Simtec Electronics
  DMA channel 0 at c4846000, irq 33
  DMA channel 1 at c4846040, irq 34
  DMA channel 2 at c4846080, irq 35
  DMA channel 3 at c48460c0, irq 36
  S3C244X: Clock Support, DVS off
  bio: create slab bio-0 at 0
  SCSI subsystem initialized
  usbcore: registered new interface driver usbfs
  usbcore: registered new interface driver hub
  usbcore: registered new device driver usb
  NET: Registered protocol family 2
  TCP established hash table entries: 2048 (order: 2, 16384 bytes)
  TCP bind hash

[OE-core] core-image-minimal boot problem

[Yi Qingliang]

I have compiled a core-image-minimal running on my s3c2442 board.
both the kernel and barebox are compiled based on mini2440.

the fs is ubifs.

after set rtc, stop several seconds.
and the continue mount rootfs.
when execute sysvinit,
after print INIT:, stop long time, and then print  version 2.88 booting.
stop long time, print a newline.
stop long time, continue.
and finally, no shell prompt occur.

I have checked sysvinit code, the INIT: and version 2.88 booting are only 
continuous print, it should not pause between them.

I have changed ubifs to cramfs, no luck.
and if I uncheck the s3c nand debug option in kernel configuration,
I can get shell prompt, and login the system, and only that, the boot time no 
change.

is there someone can help me?



=ATTACHE FILE=


the serial output is:

booting kernel from /dev/nand0.kernel.bb
commandline: console=ttySAC0,115200 mini2440=0tbc LANG=en_US.UTF-8 ip=dhcp 
root=ubi0:arm9plf-rootfs ubi.mtd=3 rootfstype=ubifs noinit
rd mtdparts=nand:768k(barebox),256k(bareboxenv),5M(kernel),-(fs)
arch_number: 1999
Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0
Linux version 3.7.2 (ll@ll-pc) (gcc version 4.7.2 (GCC) ) #23 Sun Jan 13 
19:14:52 CST 2013
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
CPU: VIVT data cache, VIVT instruction cache
Machine: NJJL2442
Memory policy: ECC disabled, Data cache writeback
CPU S3C2442B (id 0x32440aab)
S3C24XX Clocks, Copyright 2004 Simtec Electronics
S3C244X: core 405.000 MHz, memory 101.250 MHz, peripheral 50.625 MHz
CLOCK: Slow mode (1.500 MHz), fast, MPLL on, UPLL on
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
Kernel command line: console=ttySAC0,115200 mini2440=0tbc LANG=en_US.UTF-8 
ip=dhcp root=ubi0:arm9plf-rootfs ubi.mtd=3 rootfstype=ubif
s noinitrd mtdparts=nand:768k(barebox),256k(bareboxenv),5M(kernel),-(fs)
PID hash table entries: 256 (order: -2, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 60440k/60440k available, 5096k reserved, 0K highmem
Virtual kernel memory layout:
vector  : 0x - 0x1000   (   4 kB)
fixmap  : 0xfff0 - 0xfffe   ( 896 kB)
vmalloc : 0xc480 - 0xff00   ( 936 MB)
lowmem  : 0xc000 - 0xc400   (  64 MB)
modules : 0xbf00 - 0xc000   (  16 MB)
  .text : 0xc0008000 - 0xc03f57dc   (4022 kB)
  .init : 0xc03f6000 - 0xc04170dc   ( 133 kB)
  .data : 0xc0418000 - 0xc043d720   ( 150 kB)
   .bss : 0xc043d744 - 0xc046299c   ( 149 kB)
NR_IRQS:85
irq: clearing subpending status 0002
sched_clock: 32 bits at 200 Hz, resolution 500ns, wraps every 4294967291ms
Console: colour dummy device 80x30
Calibrating delay loop... 201.52 BogoMIPS (lpj=503808)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
Setting up static identity map for 0x3030ab68 - 0x3030abc0
devtmpfs: initialized
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
MINI2440: Option string mini2440=0tbc
MINI2440: 't' ignored, touchscreen not compiled in
MINI2440: LCD [0:240x320] 1:800x480 2:1024x768 3:320x240
S3C2442: Initialising architecture
S3C24XX DMA Driver, Copyright 2003-2006 Simtec Electronics
DMA channel 0 at c4846000, irq 33
DMA channel 1 at c4846040, irq 34
DMA channel 2 at c4846080, irq 35
DMA channel 3 at c48460c0, irq 36
S3C244X: Clock Support, DVS off
bio: create slab bio-0 at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP: reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
NetWinder Floating Point Emulator V0.97 (extended precision)
NTFS driver 2.1.30 [Flags: R/O].
fuse init (API version 7.20)
msgmni has been set to 118
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Console: switching to colour frame buffer device 30x40
s3c2410-lcd s3c2410-lcd: fb0: s3c2410fb frame buffer device
s3c2440-uart.0: ttySAC0 at MMIO 0x5000 (irq = 70) is a S3C2440
console [ttySAC0] enabled
s3c2440-uart.1: ttySAC1 at MMIO 0x50004000 (irq = 73) is a S3C2440
s3c2440-uart.2: ttySAC2 at MMIO 0x50008000 (irq = 76) is a S3C2440
brd: module loaded
loop: module loaded
s3c24xx-nand s3c2440-nand: Tacls=1, 9ns Twrph0=3 29ns, Twrph1=2 19ns
s3c24xx-nand s3c2440-nand: NAND hardware ECC
NAND device: Manufacturer ID: 0xec, Chip ID: 0xa1 (Samsung NAND 128MiB 1,8V 8-
bit), page size: 2048, 

Re: [OE-core] core-image-minimal boot problem

[Yi Qingliang]

On Sunday, January 13, 2013 07:29:52 PM you wrote:
 I have compiled a core-image-minimal running on my s3c2442 board.
 both the kernel and barebox are compiled based on mini2440.
 
 the fs is ubifs.
 
 after set rtc, stop several seconds.
 and the continue mount rootfs.
 when execute sysvinit,
 after print INIT:, stop long time, and then print  version 2.88 booting.
 stop long time, print a newline.
 stop long time, continue.
 and finally, no shell prompt occur.
 
 I have checked sysvinit code, the INIT: and version 2.88 booting are
 only continuous print, it should not pause between them.
 
 I have changed ubifs to cramfs, no luck.
 and if I uncheck the s3c nand debug option in kernel configuration,
 I can get shell prompt, and login the system, and only that, the boot time
 no change.
sorry, it should be:
if I [check] the s3c nand debug option in kernel configuration, 
I can get log in system.
 
 is there someone can help me?
 
 
 
 =ATTACHE FILE=
 
 
 the serial output is:
 
 booting kernel from /dev/nand0.kernel.bb
 commandline: console=ttySAC0,115200 mini2440=0tbc LANG=en_US.UTF-8 ip=dhcp
 root=ubi0:arm9plf-rootfs ubi.mtd=3 rootfstype=ubifs noinit
 rd mtdparts=nand:768k(barebox),256k(bareboxenv),5M(kernel),-(fs)
 arch_number: 1999
 Uncompressing Linux... done, booting the kernel.
 Booting Linux on physical CPU 0
 Linux version 3.7.2 (ll@ll-pc) (gcc version 4.7.2 (GCC) ) #23 Sun Jan 13
 19:14:52 CST 2013
 CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
 CPU: VIVT data cache, VIVT instruction cache
 Machine: NJJL2442
 Memory policy: ECC disabled, Data cache writeback
 CPU S3C2442B (id 0x32440aab)
 S3C24XX Clocks, Copyright 2004 Simtec Electronics
 S3C244X: core 405.000 MHz, memory 101.250 MHz, peripheral 50.625 MHz
 CLOCK: Slow mode (1.500 MHz), fast, MPLL on, UPLL on
 Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
 Kernel command line: console=ttySAC0,115200 mini2440=0tbc LANG=en_US.UTF-8
 ip=dhcp root=ubi0:arm9plf-rootfs ubi.mtd=3 rootfstype=ubif
 s noinitrd mtdparts=nand:768k(barebox),256k(bareboxenv),5M(kernel),-(fs)
 PID hash table entries: 256 (order: -2, 1024 bytes)
 Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
 Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
 Memory: 64MB = 64MB total
 Memory: 60440k/60440k available, 5096k reserved, 0K highmem
 Virtual kernel memory layout:
 vector  : 0x - 0x1000   (   4 kB)
 fixmap  : 0xfff0 - 0xfffe   ( 896 kB)
 vmalloc : 0xc480 - 0xff00   ( 936 MB)
 lowmem  : 0xc000 - 0xc400   (  64 MB)
 modules : 0xbf00 - 0xc000   (  16 MB)
   .text : 0xc0008000 - 0xc03f57dc   (4022 kB)
   .init : 0xc03f6000 - 0xc04170dc   ( 133 kB)
   .data : 0xc0418000 - 0xc043d720   ( 150 kB)
.bss : 0xc043d744 - 0xc046299c   ( 149 kB)
 NR_IRQS:85
 irq: clearing subpending status 0002
 sched_clock: 32 bits at 200 Hz, resolution 500ns, wraps every
 4294967291ms Console: colour dummy device 80x30
 Calibrating delay loop... 201.52 BogoMIPS (lpj=503808)
 pid_max: default: 32768 minimum: 301
 Mount-cache hash table entries: 512
 CPU: Testing write buffer coherency: ok
 Setting up static identity map for 0x3030ab68 - 0x3030abc0
 devtmpfs: initialized
 NET: Registered protocol family 16
 DMA: preallocated 256 KiB pool for atomic coherent allocations
 MINI2440: Option string mini2440=0tbc
 MINI2440: 't' ignored, touchscreen not compiled in
 MINI2440: LCD [0:240x320] 1:800x480 2:1024x768 3:320x240
 S3C2442: Initialising architecture
 S3C24XX DMA Driver, Copyright 2003-2006 Simtec Electronics
 DMA channel 0 at c4846000, irq 33
 DMA channel 1 at c4846040, irq 34
 DMA channel 2 at c4846080, irq 35
 DMA channel 3 at c48460c0, irq 36
 S3C244X: Clock Support, DVS off
 bio: create slab bio-0 at 0
 SCSI subsystem initialized
 usbcore: registered new interface driver usbfs
 usbcore: registered new interface driver hub
 usbcore: registered new device driver usb
 NET: Registered protocol family 2
 TCP established hash table entries: 2048 (order: 2, 16384 bytes)
 TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
 TCP: Hash tables configured (established 2048 bind 2048)
 TCP: reno registered
 UDP hash table entries: 256 (order: 0, 4096 bytes)
 UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
 NET: Registered protocol family 1
 NetWinder Floating Point Emulator V0.97 (extended precision)
 NTFS driver 2.1.30 [Flags: R/O].
 fuse init (API version 7.20)
 msgmni has been set to 118
 io scheduler noop registered
 io scheduler deadline registered
 io scheduler cfq registered (default)
 Console: switching to colour frame buffer device 30x40
 s3c2410-lcd s3c2410-lcd: fb0: s3c2410fb frame buffer device
 s3c2440-uart.0: ttySAC0 at MMIO 0x5000 (irq = 70) is a S3C2440
 console [ttySAC0] enabled
 s3c2440-uart.1: ttySAC1 at MMIO 0x50004000 (irq = 73) is a S3C2440
 s3c2440-uart.2: ttySAC2 at MMIO 0x50008000 (irq = 

Re: [OE-core] [PATCH 00/21][RFC v3] systemd Integration

[Yi Qingliang]

When add it in the oe-core?

On Friday, January 11, 2013 03:23:06 PM Saul Wold wrote:
 On 01/08/2013 04:24 AM, Radu Moisan wrote:
  As Ross suggested I've done the following changes to the previous set:
  * added two patches (the first two) that address multiple init systems
  support,\ as in shifting from default hardcoded sysvinit to something
  more generic while the default values still remains on sysvinit
  * moved automatic setting of PREFERRED_PROVIDER_udev into
  default_providers.inc * removed ahavi-systemd since all it provided was
  service files; now service files are pulled in by avahi-daemon
  * also rebased on master
  
  The following changes since commit 
7e1f8faad0c4b6f490c26f87acc698dd6e002b15:
 perl: Remove bashism from perl-tests.inc (2013-01-07 22:37:37 +)
  
  are available in the git repository at:
 git://git.yoctoproject.org/poky-contrib rmoisan/systemd
 http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=rmoisan/system
 d
  
  Enrico Scholz (1):
 systemd: move disable operation into prerm() script
  
  Holger Hans Peter Freyther (2):
 systemd: Make the main systemd files proper CONFFILES
 systemd: Introduce a create-volatile to create tmp directories
 
 White space 4 spaces vs tab
 
  Khem Raj (1):
 systemd: Fix build when base_libdir is not /lib
  
  Martin Donnelly (2):
 cgroups: Add INSANE_SKIP to avoid warning about .so file
 systemd: Remove sysvinit mount related services if systemd is enabled
  
  Martin Jansa (2):
 systemd: fix FILESPATH to find systemctl
 systemd: add PACKAGES_DYNAMIC
  
  Radu Moisan (13):
 default-distrovars: Add DISTRO_FEATURES_INITMAN to DISTRO_FEATURES
 default-providers: Automatically set PREFERRED_PROVIDER_udev
 systemd: initial integration
 
 I believe this was mentioned before, but can you avoid making white
 space changes, you seem to have changed tabs (which we use tabs for
 shell based functions and 4 spaces for python based functions)
 
 Specifically, I saw some changes in wpa-supplicant-1.0.inc, busybox,
 dropbear, initscripts
 
 For the systemd-serialgetty, can we not carry around a LICENSE file, and
 instead point to the meta/files/common-licenses for a checksum?
 
 Also a load of the patches do not contains Signed-off-by or
 Upstream-Status tags.
 
 systemd: Add systemd_base.bbclass
 systemd: Add systemd option to PREFERRED_PROVIDER_udev
 systemd: set default.target to multi-user.target
 systemd: update FILESPATH with *-native directory
 systemd: disable sysfs.service
 
 White space changes, makes it much harder to review, please fix
 
 systemd: Add systemd-compat-units
 systemd: Add avahi to packagegroup-core-boot
 xserver-nodm-init: Enable systemd support
 util-linux: Enable systemd support
 
 What's the actual change here?  Whitespace?
 
 systemd: Disable xz when building with GPLv3 incompatibility flag
 
 This should go away, I have verified that the license field in xz is
 wrong and should not contain GPLv3 since it's a build macro, not a
 runtime, and the LICENSE field pertains to packaged and installed items
 and their licenses.
 
 Sau!
 
meta/classes/systemd.bbclass   |1 +
meta/classes/systemd_base.bbclass  |  218 +
meta/conf/distro/include/default-distrovars.inc|3 +-
meta/conf/distro/include/default-providers.inc |1 +
meta/recipes-bsp/keymaps/files/keymaps.service |9 +
meta/recipes-bsp/keymaps/keymaps_1.0.bb|9 +-
meta/recipes-connectivity/avahi/avahi.inc  |   23 +-
meta/recipes-connectivity/connman/connman.inc  |6 +
meta/recipes-connectivity/connman/connman_1.4.bb   |3 +-
meta/recipes-connectivity/dhcp/dhcp.inc|   15 +-
meta/recipes-connectivity/dhcp/files/dhcpd.service |   12 +
.../dhcp/files/dhcrelay.service|   10 +
.../openssh/openssh-6.0p1/sshd.socket  |   11 +
.../openssh/openssh-6.0p1/sshd@.service|9 +
.../openssh/openssh-6.0p1/sshdgenkeys.service  |   10 +
meta/recipes-connectivity/openssh/openssh_6.0p1.bb |   14 +-
.../wpa-supplicant/wpa-supplicant-1.0.inc  |   74 +++--
.../wpa-supplicant/wpa-supplicant_1.0.bb   |2 +-
meta/recipes-core/busybox/busybox.inc  |   18 ++
meta/recipes-core/busybox/busybox_1.20.2.bb|4 +-
.../busybox/files/busybox-klogd.service.in |8 +
.../busybox/files/busybox-syslog.service.in|   13 +
meta/recipes-core/dropbear/dropbear.inc|   81 ++---
.../recipes-core/dropbear/dropbear/dropbear.socket |   10 +
.../dropbear/dropbear/dropbear@.service|9 +
.../dropbear/dropbear/dropbearkey.service  |   10 +
.../initscripts-1.0/{urandom = urandom.sh}|0
meta/recipes-core/initscripts/initscripts_1.0.bb   |  164 

Re: [OE-core] core-image-minimal boot problem

[Yi Qingliang]

can you give some suggestions?
I have struggled on it for 4days with a big headache.:(

On Sunday, January 13, 2013 07:29:52 PM Yi Qingliang wrote:
 I have compiled a core-image-minimal running on my s3c2442 board.
 both the kernel and barebox are compiled based on mini2440.
 
 the fs is ubifs.
 
 after set rtc, stop several seconds.
 and the continue mount rootfs.
 when execute sysvinit,
 after print INIT:, stop long time, and then print  version 2.88 booting.
 stop long time, print a newline.
 stop long time, continue.
 and finally, no shell prompt occur.
 
 I have checked sysvinit code, the INIT: and version 2.88 booting are
 only continuous print, it should not pause between them.
 
 I have changed ubifs to cramfs, no luck.
 and if I uncheck the s3c nand debug option in kernel configuration,
 I can get shell prompt, and login the system, and only that, the boot time
 no change.
 
 is there someone can help me?
 
 
 
 =ATTACHE FILE=
 
 
 the serial output is:
 
 booting kernel from /dev/nand0.kernel.bb
 commandline: console=ttySAC0,115200 mini2440=0tbc LANG=en_US.UTF-8 ip=dhcp
 root=ubi0:arm9plf-rootfs ubi.mtd=3 rootfstype=ubifs noinit
 rd mtdparts=nand:768k(barebox),256k(bareboxenv),5M(kernel),-(fs)
 arch_number: 1999
 Uncompressing Linux... done, booting the kernel.
 Booting Linux on physical CPU 0
 Linux version 3.7.2 (ll@ll-pc) (gcc version 4.7.2 (GCC) ) #23 Sun Jan 13
 19:14:52 CST 2013
 CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
 CPU: VIVT data cache, VIVT instruction cache
 Machine: NJJL2442
 Memory policy: ECC disabled, Data cache writeback
 CPU S3C2442B (id 0x32440aab)
 S3C24XX Clocks, Copyright 2004 Simtec Electronics
 S3C244X: core 405.000 MHz, memory 101.250 MHz, peripheral 50.625 MHz
 CLOCK: Slow mode (1.500 MHz), fast, MPLL on, UPLL on
 Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
 Kernel command line: console=ttySAC0,115200 mini2440=0tbc LANG=en_US.UTF-8
 ip=dhcp root=ubi0:arm9plf-rootfs ubi.mtd=3 rootfstype=ubif
 s noinitrd mtdparts=nand:768k(barebox),256k(bareboxenv),5M(kernel),-(fs)
 PID hash table entries: 256 (order: -2, 1024 bytes)
 Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
 Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
 Memory: 64MB = 64MB total
 Memory: 60440k/60440k available, 5096k reserved, 0K highmem
 Virtual kernel memory layout:
 vector  : 0x - 0x1000   (   4 kB)
 fixmap  : 0xfff0 - 0xfffe   ( 896 kB)
 vmalloc : 0xc480 - 0xff00   ( 936 MB)
 lowmem  : 0xc000 - 0xc400   (  64 MB)
 modules : 0xbf00 - 0xc000   (  16 MB)
   .text : 0xc0008000 - 0xc03f57dc   (4022 kB)
   .init : 0xc03f6000 - 0xc04170dc   ( 133 kB)
   .data : 0xc0418000 - 0xc043d720   ( 150 kB)
.bss : 0xc043d744 - 0xc046299c   ( 149 kB)
 NR_IRQS:85
 irq: clearing subpending status 0002
 sched_clock: 32 bits at 200 Hz, resolution 500ns, wraps every
 4294967291ms Console: colour dummy device 80x30
 Calibrating delay loop... 201.52 BogoMIPS (lpj=503808)
 pid_max: default: 32768 minimum: 301
 Mount-cache hash table entries: 512
 CPU: Testing write buffer coherency: ok
 Setting up static identity map for 0x3030ab68 - 0x3030abc0
 devtmpfs: initialized
 NET: Registered protocol family 16
 DMA: preallocated 256 KiB pool for atomic coherent allocations
 MINI2440: Option string mini2440=0tbc
 MINI2440: 't' ignored, touchscreen not compiled in
 MINI2440: LCD [0:240x320] 1:800x480 2:1024x768 3:320x240
 S3C2442: Initialising architecture
 S3C24XX DMA Driver, Copyright 2003-2006 Simtec Electronics
 DMA channel 0 at c4846000, irq 33
 DMA channel 1 at c4846040, irq 34
 DMA channel 2 at c4846080, irq 35
 DMA channel 3 at c48460c0, irq 36
 S3C244X: Clock Support, DVS off
 bio: create slab bio-0 at 0
 SCSI subsystem initialized
 usbcore: registered new interface driver usbfs
 usbcore: registered new interface driver hub
 usbcore: registered new device driver usb
 NET: Registered protocol family 2
 TCP established hash table entries: 2048 (order: 2, 16384 bytes)
 TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
 TCP: Hash tables configured (established 2048 bind 2048)
 TCP: reno registered
 UDP hash table entries: 256 (order: 0, 4096 bytes)
 UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
 NET: Registered protocol family 1
 NetWinder Floating Point Emulator V0.97 (extended precision)
 NTFS driver 2.1.30 [Flags: R/O].
 fuse init (API version 7.20)
 msgmni has been set to 118
 io scheduler noop registered
 io scheduler deadline registered
 io scheduler cfq registered (default)
 Console: switching to colour frame buffer device 30x40
 s3c2410-lcd s3c2410-lcd: fb0: s3c2410fb frame buffer device
 s3c2440-uart.0: ttySAC0 at MMIO 0x5000 (irq = 70) is a S3C2440
 console [ttySAC0] enabled
 s3c2440-uart.1: ttySAC1 at MMIO 0x50004000 (irq = 73) is a S3C2440
 s3c2440-uart.2: ttySAC2 at MMIO 0x50008000 (irq = 76

Re: [OE-core] core-image-minimal boot problem

[Yi Qingliang]

I have got something,
after change the DEBUG to 1 in sysvinit/src/init.h, the pause between
and after INIT: version 2.88 booting missed.
add -i to the /sbin/agetty line in /etc/inittab, I got the login prompt,
(it mean do not display issue).
but, but, what's the problem.


On Sun, Jan 13, 2013 at 4:29 PM, Yi Qingliang niqingliang2...@gmail.comwrote:

 can you give some suggestions?
 I have struggled on it for 4days with a big headache.:(

 On Sunday, January 13, 2013 07:29:52 PM Yi Qingliang wrote:
  I have compiled a core-image-minimal running on my s3c2442 board.
  both the kernel and barebox are compiled based on mini2440.
 
  the fs is ubifs.
 
  after set rtc, stop several seconds.
  and the continue mount rootfs.
  when execute sysvinit,
  after print INIT:, stop long time, and then print  version 2.88
 booting.
  stop long time, print a newline.
  stop long time, continue.
  and finally, no shell prompt occur.
 
  I have checked sysvinit code, the INIT: and version 2.88 booting are
  only continuous print, it should not pause between them.
 
  I have changed ubifs to cramfs, no luck.
  and if I uncheck the s3c nand debug option in kernel configuration,
  I can get shell prompt, and login the system, and only that, the boot
 time
  no change.
 
  is there someone can help me?
 
 
 
  =ATTACHE FILE=
 
 
  the serial output is:
 
  booting kernel from /dev/nand0.kernel.bb
  commandline: console=ttySAC0,115200 mini2440=0tbc LANG=en_US.UTF-8
 ip=dhcp
  root=ubi0:arm9plf-rootfs ubi.mtd=3 rootfstype=ubifs noinit
  rd mtdparts=nand:768k(barebox),256k(bareboxenv),5M(kernel),-(fs)
  arch_number: 1999
  Uncompressing Linux... done, booting the kernel.
  Booting Linux on physical CPU 0
  Linux version 3.7.2 (ll@ll-pc) (gcc version 4.7.2 (GCC) ) #23 Sun Jan 13
  19:14:52 CST 2013
  CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
  CPU: VIVT data cache, VIVT instruction cache
  Machine: NJJL2442
  Memory policy: ECC disabled, Data cache writeback
  CPU S3C2442B (id 0x32440aab)
  S3C24XX Clocks, Copyright 2004 Simtec Electronics
  S3C244X: core 405.000 MHz, memory 101.250 MHz, peripheral 50.625 MHz
  CLOCK: Slow mode (1.500 MHz), fast, MPLL on, UPLL on
  Built 1 zonelists in Zone order, mobility grouping on.  Total pages:
 16256
  Kernel command line: console=ttySAC0,115200 mini2440=0tbc
 LANG=en_US.UTF-8
  ip=dhcp root=ubi0:arm9plf-rootfs ubi.mtd=3 rootfstype=ubif
  s noinitrd mtdparts=nand:768k(barebox),256k(bareboxenv),5M(kernel),-(fs)
  PID hash table entries: 256 (order: -2, 1024 bytes)
  Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
  Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
  Memory: 64MB = 64MB total
  Memory: 60440k/60440k available, 5096k reserved, 0K highmem
  Virtual kernel memory layout:
  vector  : 0x - 0x1000   (   4 kB)
  fixmap  : 0xfff0 - 0xfffe   ( 896 kB)
  vmalloc : 0xc480 - 0xff00   ( 936 MB)
  lowmem  : 0xc000 - 0xc400   (  64 MB)
  modules : 0xbf00 - 0xc000   (  16 MB)
.text : 0xc0008000 - 0xc03f57dc   (4022 kB)
.init : 0xc03f6000 - 0xc04170dc   ( 133 kB)
.data : 0xc0418000 - 0xc043d720   ( 150 kB)
 .bss : 0xc043d744 - 0xc046299c   ( 149 kB)
  NR_IRQS:85
  irq: clearing subpending status 0002
  sched_clock: 32 bits at 200 Hz, resolution 500ns, wraps every
  4294967291ms Console: colour dummy device 80x30
  Calibrating delay loop... 201.52 BogoMIPS (lpj=503808)
  pid_max: default: 32768 minimum: 301
  Mount-cache hash table entries: 512
  CPU: Testing write buffer coherency: ok
  Setting up static identity map for 0x3030ab68 - 0x3030abc0
  devtmpfs: initialized
  NET: Registered protocol family 16
  DMA: preallocated 256 KiB pool for atomic coherent allocations
  MINI2440: Option string mini2440=0tbc
  MINI2440: 't' ignored, touchscreen not compiled in
  MINI2440: LCD [0:240x320] 1:800x480 2:1024x768 3:320x240
  S3C2442: Initialising architecture
  S3C24XX DMA Driver, Copyright 2003-2006 Simtec Electronics
  DMA channel 0 at c4846000, irq 33
  DMA channel 1 at c4846040, irq 34
  DMA channel 2 at c4846080, irq 35
  DMA channel 3 at c48460c0, irq 36
  S3C244X: Clock Support, DVS off
  bio: create slab bio-0 at 0
  SCSI subsystem initialized
  usbcore: registered new interface driver usbfs
  usbcore: registered new interface driver hub
  usbcore: registered new device driver usb
  NET: Registered protocol family 2
  TCP established hash table entries: 2048 (order: 2, 16384 bytes)
  TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
  TCP: Hash tables configured (established 2048 bind 2048)
  TCP: reno registered
  UDP hash table entries: 256 (order: 0, 4096 bytes)
  UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
  NET: Registered protocol family 1
  NetWinder Floating Point Emulator V0.97 (extended precision)
  NTFS driver 2.1.30 [Flags: R/O].
  fuse init (API version 7.20)
  msgmni has been set

Re: [OE-core] glib2.0 and dbus dependency

[Yi Qingliang]

On Friday, January 11, 2013 05:30:55 PM ChenQi wrote:
 On 01/11/2013 02:31 AM, Yi Qingliang wrote:
  when compiling using 4 threads, I got following error.
  the glib2.0-native want find dbus header file.
  If I compiled dbus/dbus-natigve, and then compile glib2.0 OK.
  
  when grep glib2.0 bb files, I can't find dbus in dependency, why?
 
 Hi,
 
 What's the error message?
I can't remember it, somes like can't find dub/dbus.h.

 
 Cheers,
 Chen Qi
 
  ERROR: Function failed: do_compile (see /mnt/src/arm9plf-
  build/tmp/work/x86_64-linux/glib-2.0-native/1_2.34.3-
  r0/temp/log.do_compile.28193 for further information)
  ERROR: Task 1851 (virtual:native:/mnt/src/optimus/poky/meta/recipes-
  core/glib-2.0/glib-2.0_2.34.3.bb, do_compile) failed with exit code '1'
  NOTE: Tasks Summary: Attempted 929 tasks of which 925 didn't need to be
  rerun and 1 failed.
  Waiting for 0 running tasks to finish:
  
  Summary: 1 task failed:
 virtual:native:/mnt/src/optimus/poky/meta/recipes-
  
  core/glib-2.0/glib-2.0_2.34.3.bb, do_compile
  Summary: There was 1 ERROR message shown, returning a non-zero exit code.
  
  
  ___
  Openembedded-core mailing list
  Openembedded-core@lists.openembedded.org
  http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
 
 ___
 Openembedded-core mailing list
 Openembedded-core@lists.openembedded.org
 http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

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

[OE-core] glib2.0 and dbus dependency

[Yi Qingliang]

when compiling using 4 threads, I got following error.
the glib2.0-native want find dbus header file.
If I compiled dbus/dbus-natigve, and then compile glib2.0 OK.

when grep glib2.0 bb files, I can't find dbus in dependency, why?




 
ERROR: Function failed: do_compile (see /mnt/src/arm9plf-
build/tmp/work/x86_64-linux/glib-2.0-native/1_2.34.3-
r0/temp/log.do_compile.28193 for further information)
ERROR: Task 1851 (virtual:native:/mnt/src/optimus/poky/meta/recipes-
core/glib-2.0/glib-2.0_2.34.3.bb, do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 929 tasks of which 925 didn't need to be rerun 
and 1 failed.
Waiting for 0 running tasks to finish:

Summary: 1 task failed:
  virtual:native:/mnt/src/optimus/poky/meta/recipes-
core/glib-2.0/glib-2.0_2.34.3.bb, do_compile
Summary: There was 1 ERROR message shown, returning a non-zero exit code.


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

Re: [OE-core] glib2.0 and dbus dependency

[Yi Qingliang]

On Thursday, January 10, 2013 11:42:53 AM Martin Jansa wrote:
 On Thu, Jan 10, 2013 at 06:31:22PM +, Yi Qingliang wrote:
  when compiling using 4 threads, I got following error.
  the glib2.0-native want find dbus header file.
  If I compiled dbus/dbus-natigve, and then compile glib2.0 OK.
  
  when grep glib2.0 bb files, I can't find dbus in dependency, why?
 
 It was causing cyclic dependency at least when dbus tests were enabled,
 I'm not sure if this was resolved already.
cyclic dependency OMG, do they really need 'cyclic dependency'?
splitting them cannot solve 'cyclic dependency'? am i right?
 
  ERROR: Function failed: do_compile (see /mnt/src/arm9plf-
  build/tmp/work/x86_64-linux/glib-2.0-native/1_2.34.3-
  r0/temp/log.do_compile.28193 for further information)
  ERROR: Task 1851 (virtual:native:/mnt/src/optimus/poky/meta/recipes-
  core/glib-2.0/glib-2.0_2.34.3.bb, do_compile) failed with exit code '1'
  NOTE: Tasks Summary: Attempted 929 tasks of which 925 didn't need to be
  rerun and 1 failed.
  Waiting for 0 running tasks to finish:
  
  Summary: 1 task failed:
virtual:native:/mnt/src/optimus/poky/meta/recipes-
  
  core/glib-2.0/glib-2.0_2.34.3.bb, do_compile
  Summary: There was 1 ERROR message shown, returning a non-zero exit code.
  
  
  ___
  Openembedded-core mailing list
  Openembedded-core@lists.openembedded.org
  http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

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

Re: [OE-core] glib2.0 and dbus dependency

[Yi Qingliang]

On Friday, January 11, 2013 02:52:12 AM Martin Jansa wrote:
 On Fri, Jan 11, 2013 at 09:18:06AM +, Yi Qingliang wrote:
  On Thursday, January 10, 2013 11:42:53 AM Martin Jansa wrote:
   On Thu, Jan 10, 2013 at 06:31:22PM +, Yi Qingliang wrote:
when compiling using 4 threads, I got following error.
the glib2.0-native want find dbus header file.
If I compiled dbus/dbus-natigve, and then compile glib2.0 OK.

when grep glib2.0 bb files, I can't find dbus in dependency, why?
   
   It was causing cyclic dependency at least when dbus tests were enabled,
   I'm not sure if this was resolved already.
  
  cyclic dependency OMG, do they really need 'cyclic dependency'?
  splitting them cannot solve 'cyclic dependency'? am i right?
 
 Please check first if this is still valid:
 http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-December/027987
 .html
 
 I think it was resolved somewhere, but I'm not sure or you can just add
 it and see if it fails :).
indeed, I can't got 'just add what',
maybe you mean just add 'dbus' in glib2.0's DEPENDS?

 I checked the glib2.0, found:
RDEPENDS_${PN}-ptest += \
..
python-dbus \
   
and the 'python-dbus' depends on 'dbus'.
but for glib2.0, it's compiling need dbus, not only running.
 Cheers,

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

Re: [OE-core] disk space problem

[Yi Qingliang]

On Saturday, December 29, 2012 06:07:27 PM Otavio Salvador wrote:
 On Sat, Dec 29, 2012 at 1:09 PM, Yi Qingliang 
niqingliang2...@gmail.com wrote:
  When using poky,  I got following problem:
  
  WARNING: The free inode of /dev/md127 is running low (0.000K left)
  ERROR: Immediately abort since the disk space monitor action is
  ABORT!
  ERROR: Unknown event: bb.event.DiskFull object at 0x47dbed0
  
  the disk is  a raid partition, and fs format is reiserfs, the 'statvfs'
  call in bitbake got a zero f_favail.
  
  I don't know it is feature of reiserfs, or bug of reiserfs driver, or
  python's problem.
  
  Any idea?
 
 I had a similar problem when using btrfs. You can find the bug at
 https://bugzilla.yoctoproject.org/show_bug.cgi?id=3609

The only thing I can do is to disable the disk space motor.
I doubt it is some fs format's feature, but not bug.
If so, the bitbake should consider that.

 Regards,
 
 --
 Otavio Salvador O.S. Systems
 E-mail: ota...@ossystems.com.br  http://www.ossystems.com.br
 Mobile: +55 53 9981-7854  http://projetos.ossystems.com.br

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

[OE-core] disk space problem

[Yi Qingliang]

When using poky,  I got following problem:

WARNING: The free inode of /dev/md127 is running low (0.000K left)
ERROR: Immediately abort since the disk space monitor action is 
ABORT!
ERROR: Unknown event: bb.event.DiskFull object at 0x47dbed0

the disk is  a raid partition, and fs format is reiserfs, the 'statvfs' call 
in bitbake got a zero f_favail.

I don't know it is feature of reiserfs, or bug of reiserfs driver, or python's 
problem.

Any idea?

Yi Qingliang
Nanjing Jilong

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

Re: [OE-core] RFC: systemd integration

[Yi Qingliang]

GREAT!!!

I have asked systemd status in yocto, maybe I can use your branch instead!

THANKS!


On Wednesday, December 19, 2012 07:20:45 PM Radu Moisan wrote:

Hi guys,
I have prepared a branch on poky-contrib (rmoisan/systemd) where I pulled 
systemd from meta-openembedded. The goal is to merge this into oe-core, so 
please take a look and give me your feedback on stuff that needs work or things 
that I might have done wrong, so that I can prepare it for merge.
At this point core-image-minimal and core-image-sato both boot fine with 
systemd. There still are a few warnings but not critical(at runtime), at least 
in my opinion, you may want to take a look at those too.
You can activate systemd by  DISTRO_FEATURES_INITMAN = systemd

Radu



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

[OE-core] how to use meta-toolchain-qte?

[Yi Qingliang]

Hi, All!

I'm making a qte image of my own. and when compiling qt app, I can't generate 
the Makefile.

I have made meta-ide-support, and used the env setup script under 
'build_dir/tmp'.

I can only got qmake2, but no qmake.

after googled, got the meta-toolchain-qte, but how to use it?
where is the coressponding env setup script?


Yi Qingliang
Nanjing Jilong

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

[OE-core] how to use the eclipse plugin with custom project (my own Makefile or qt project)

[Yi Qingliang]

Hi, All!
how to use the eclipse plugin with custom project (my own Makefile or qt 
project)?
the yocto project support autotools, but I don't want to use autotools.

thanks!

Yi Qingliang
Nanjing Jilong

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

[OE-core] how about the 'systemd' status?

[Yi Qingliang]

Hi, All!

how about the systemd status?
I'm using Arch Linux, after transite to systemd, the time from power on to 
enter desktop has been greatly improved.

So I doubt the systemd status about yocto.
(the meta-systemd' is labed deprecated.)

on the openembedded.org, the systemd is meta-openembedded, indeed, I'm 
confused by the `openembedded-core' and `meta-openembedded'.

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

[OE-core] how to change the resolution of qemux86 machine to 320x240?

[Yi Qingliang]

Hi!

I have a s3c2442 system with 320x240 touch screen, and I want use qemux86 to 
simulate it on pc.

I googled, got vga=xxx in kernel arguments, but no success.
use vga=ask can select resolution, but no 320x240.
what's the right way?


Yi Qingliang
Nanjing Jilong

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

Re: [OE-core] how to change the resolution of qemux86 machine to 320x240?

[Yi Qingliang]

On Tuesday, December 11, 2012 11:07:00 AM Marcin Juszkiewicz wrote:
 W dniu 11.12.2012 17:54, Yi Qingliang pisze:
  Hi!
  
  I have a s3c2442 system with 320x240 touch screen, and I want use qemux86
  to simulate it on pc.
  
  I googled, got vga=xxx in kernel arguments, but no success.
  use vga=ask can select resolution, but no 320x240.
  what's the right way?
 
 IIRC one option is to patch vgabios which qemu uses and add new VESA
 mode with this resolution.
 
 We did such thing long time ago for one customer but I do not remember
 details.

Thanks! maybe I can got some clue about the patch?:) If not, use 640x480 
insteadly.

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

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

[OE-core] how to customize the qt4e-demo-image?

[Yi Qingliang]

Hi, all!

I have built a qt4e-demo-image, whose size is  200Mbyte.

but my system only has 128M nand flash.

I have checked the image, and found it installed gtk unexpectedly.
I have not do the depper exploration for package dependency.

what I want is just to get a smaller image, what is the simplest way?

PS: what's problem about gtk dependency? it should not like that.


Yi Qingliang
Nanjing Jilong


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

Re: [OE-core] [oe-core] why recompile gcc-cross/eglibc when update linux package?

[Yi Qingliang]

that's it!!!

I think the version of linux-libc-headers should be same as kernel, in other 
words, use same source code, so I have updated both of them.

VERY THANKS!!!

On Wednesday, December 05, 2012 09:29:18 AM Richard Purdie wrote:
 On Wed, 2012-12-05 at 10:16 +, Yi Qingliang wrote:
  I update the kernel from 3.6.6 to 3.6.9, and recompile it: bitbake linux
  
  but it will recompile eglibc/gcc-cross first, so long time:( why?
  the eglibc will use kernel header? if so, understand.
  but what about gcc-cross?
 
 Did you change linux-libc-headers or the kernel itself?
 
 If you change the libc-headers, gcc-cross will rebuild since it depends
 on eglibc and as you mention, eglibc depends on the headers.
 
 Changing the target kernel recipe shouldn't rebuild any of those.
 
 Cheers,
 
 Richard

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

[OE-core] [oe-core] why recompile gcc-cross/eglibc when update linux package?

[Yi Qingliang]

I update the kernel from 3.6.6 to 3.6.9, and recompile it: bitbake linux

but it will recompile eglibc/gcc-cross first, so long time:( why?
the eglibc will use kernel header? if so, understand.
but what about gcc-cross?

Yi Qingliang
Nanjing Jilong

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

Re: [OE-core] why remove yaffs2?

[Yi Qingliang]

clear, thanks!!!

On Monday, December 03, 2012 03:54:32 PM Richard Purdie wrote:
 On Mon, 2012-12-03 at 14:03 +, niqingliang2...@gmail.com wrote:
  Hi, All:
  
  I have untouched oe for several months, and recently found that yaffs is
  dropped, and also in official kernel, why?
 
 We removed it from OE-Core 18 months ago. The code was old, not working
 particularly well and lacking someone to maintain it so it got moved
 out. I'm sure the tools would be accepted into meta-oe if someone
 updated and cleaned up the recipe for it. For OE-Core you'd have to show
 a larger user base than there currently appears to be...
 
 Cheers,
 
 Richard

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