[yocto] Kernel Panic: /sbin/init not found

Hello all, My Yocto build environment was working perfectly until last week when I got kernel panic caused by missing/sbin/init. When I examined the image, I found that /sbin/init is indeed absent from the root image. To troubleshoot the issue, I tried building a stock Yocto whose target platfo

Re: [yocto] Kernel Panic: /sbin/init not found

> -Original Message- > From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com] > Sent: Thursday, April 02, 2015 7:37 PM > To: Yu, Chan KitX > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] Kernel Panic: /sbin/init not found > > Hi Chan Kit, > > On T

Re: [yocto] Kernel Panic: /sbin/init not found

> -Original Message- > From: Yu, Chan KitX > Sent: Friday, April 03, 2015 2:30 PM > To: 'Paul Eggleton' > Cc: yocto@yoctoproject.org > Subject: RE: [yocto] Kernel Panic: /sbin/init not found > > > > > -Original Message-

Re: [yocto] Kernel Panic: /sbin/init not found

> -Original Message- > From: ChenQi [mailto:qi.c...@windriver.com] > Sent: Friday, April 03, 2015 3:03 PM > To: Yu, Chan KitX; Paul Eggleton > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] Kernel Panic: /sbin/init not found > > On 04/03/2015 02:43

Re: [yocto] Kernel Panic: /sbin/init not found

> -Original Message- > From: Yu, Chan KitX > Sent: Friday, April 03, 2015 3:06 PM > To: Chen, Qi (Wind River); Paul Eggleton > Cc: yocto@yoctoproject.org > Subject: RE: [yocto] Kernel Panic: /sbin/init not found > > > > > -Original Message--

Re: [yocto] Kernel Panic: /sbin/init not found

, Virgil [mailto:virgil.sm...@flir.com] > Sent: Tuesday, April 07, 2015 1:13 AM > To: Paul Eggleton > Cc: Yu, Chan KitX; yocto@yoctoproject.org > Subject: RE: [yocto] Kernel Panic: /sbin/init not found > > > > This is not true in the general case. You definitely can use &g

[yocto] Issue with compiling x264 package in Yocto

Hi all, I had the following issues with building x264 package in Yocto ERROR: Fetcher failure: Fetch command failed with exit code 128, output: Cloning into bare repository '/home/autoeye/daisy/poky/mybuilds/downloads/git2/git.videolan.org.x264.git'... FATAL: Failed to determine SOCKS server. fa

Re: [yocto] Issue with compiling x264 package in Yocto

: Thursday, December 04, 2014 7:17 AM To: Yu, Chan KitX Cc: yocto@yoctoproject.org; yuchan...@gmail.com Subject: Re: [yocto] Issue with compiling x264 package in Yocto On 3 December 2014 at 05:40, Yu, Chan KitX mailto:chan.kitx...@intel.com>> wrote: Weirdly, git cloning that repository

Re: [yocto] Issue with compiling x264 package in Yocto

. So I’m stuck here now getting x264 to git clone ☹ I also added GIT_PROXY_COMMAND to oe-git-proxy but no luck. Chan Kit From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: Thursday, December 04, 2014 7:17 AM To: Yu, Chan KitX Cc: yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>;

Re: [yocto] Issue with compiling x264 package in Yocto

I got it to compile thanks to Boon Leong. Consider this issue resolved for now. Chan Kit From: Ong, Boon Leong Sent: Thursday, December 04, 2014 2:49 PM To: Yu, Chan KitX; Burton, Ross Cc: 'yocto@yoctoproject.org'; 'yuchan...@gmail.com' Subject: RE: [yocto] Issue with compi

[yocto] do_fetch() with svn which has http prefix

Hi, I need to do svn checkout http://llvm.org/svn/llvm-project/llvm/trunk but since that repo has a http prefix, I don't think it's smart enough to recognize that the link is actually an SVN repo. So how do I work around this problem? Thanks, Chan Kit -- ___

[yocto] Need guidance on compiling clang+rt-compiler+llvm 3.3

Hi guys, Before I go to my errors let me outline the steps I took. I started off with the LLVM recipe that I got from http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-core/llvm . Then I added the following to llvm.inc's do_configure_prepend() because I wanted to compile Clan

Re: [yocto] Building clang with Yocto

Hi Jim, How did you jam the clang compiler into the SDK tarball? Chan Kit -Original Message- From: Jim Rafert [mailto:j...@spectralogic.com] Sent: Tuesday, December 09, 2014 1:48 AM To: yocto@yoctoproject.org; Yu, Chan KitX Subject: Building clang with Yocto Hello Chan, I have been

Re: [yocto] Building clang with Yocto

ginal Message- From: Yu, Chan KitX Sent: Tuesday, December 09, 2014 9:19 AM To: 'Jim Rafert'; yocto@yoctoproject.org Subject: RE: Building clang with Yocto Hi Jim, How did you jam the clang compiler into the SDK tarball? Chan Kit -Original Message- From: Jim Rafert [mailto:j...@s

Re: [yocto] Building clang with Yocto

heorghisan [mailto:liviu.gheorghi...@enea.com] Sent: Wednesday, December 10, 2014 12:27 AM To: Yu, Chan KitX; Jim Rafert; yocto@yoctoproject.org Subject: Re: [yocto] Building clang with Yocto Hello Yu, Jim I think you can get the clang executable into the SDK installer script with something like thi

Re: [yocto] Building clang with Yocto

ries. I suppose I can specify some other configuration options there but I have no idea what to specify the configure parameter --target= . x64 did not do any good. So any idea? Thanks, Chan Kit From: Yu, Chan KitX Sent: Wednesday, December 10, 2014 11:25 AM To: Liviu Gheorghisan; Ji

Re: [yocto] Building clang with Yocto

include/llvm/Support/BranchProbability.h:27:3: error: 'uint32_t' does not name a type uint32_t N; I tried adding #include to that header but no luck. -Original Message- From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com] Sent: Monday, December 22, 2014 7:22 P

Re: [yocto] Building clang with Yocto

Question: Does the fact that Yocto is based on elibc rather than libc be the cause of the incompatibility here? -Original Message- From: Jim Rafert [mailto:j...@spectralogic.com] Sent: Wednesday, December 24, 2014 12:58 AM To: Yu, Chan KitX; Paul Eggleton Cc: yocto@yoctoproject.org

[yocto] LLVM/CLang only works in Multilib x64

Hi all, As some of you might know through IRC and the mailing list itself, I'm trying to get LLVM/CLang to work in Yocto in platforms other than x64 multilib. To set the purpose of this email clear, I am only trying to get LLVM to work as host-only compiler. As much as I want to get LLVM cross