Reg: Yocto installation problem

Reg: Yocto installation problem

[Praveenreddy Padamati]

[-- Attachment #1: Type: text/html, Size: 2682 bytes --]

[-- Attachment #2: log.do_configure.10604 --]
[-- Type: application/octet-stream, Size: 5755 bytes --]

DEBUG: Executing python function sysroot_cleansstate
DEBUG: Python function sysroot_cleansstate finished
DEBUG: Executing shell function do_configure
First let's make sure your kit is complete.  Checking...
Would you like to see the instructions? [n]  
Locating common programs...
Checking compatibility between /bin/echo and builtin echo (if any)...
Symbolic links are supported.
Checking how to test for symbolic links...
You can test for symbolic links with 'test -h'.
Checking for cross-compile
No targethost for running compiler tests against defined, running locally
Good, your tr supports [:lower:] and [:upper:] to convert case.
Using [:upper:] and [:lower:] to convert case.
aix   	      dragonfly       irix_4   		nonstopux     stellar   
aix_3         dynix   	      irix_5   		openbsd       sunos_4_0   
aix_4         dynixptx        irix_6   		opus          sunos_4_1   
altos486      epix   	      irix_6_0   	os2   	      super-ux   
amigaos       esix4   	      irix_6_1   	os390         svr4   
atheos        fps   	      isc   		os400         svr5   
aux_3         freebsd         isc_2   		posix-bc      ti1500   
bitrig        freemint        linux-android   	powerux       ultrix_4   
bsdos         genix   	      linux   		qnx   	      umips   
catamount     gnu   	      lynxos   		riscos        unicos   
convexos      gnukfreebsd     midnightbsd   	sco   	      unicosmk   
cxux          gnuknetbsd      mips   		sco_2_3_0     unisysdynix   
cygwin        greenhills      mirbsd   		sco_2_3_1     utekv   
darwin        haiku   	      mpc   		sco_2_3_2     uwin   
dcosx         hpux   	      ncr_tower   	sco_2_3_3     vos   
dec_osf       i386   	      netbsd   		sco_2_3_4   
dos_djgpp     interix         newsos4   	solaris_2   
Which of these apply, if any? [linux]  

You appear to have ELF support.  I'll try to use it for dynamic loading.
If dynamic loading doesn't work, read hints/linux.sh for further information.
Operating system name? [linux]  
Operating system version? [3.16.0-70-generic]  
Installation prefix to use? (~name ok)
[/home/kumarn/imx6_build/fsl-release-bsp/Build/tmp/sysroots/x86_64-linux/usr]  
AFS does not seem to be running...
What installation prefix should I use for installing files? (~name ok)
[/home/kumarn/imx6_build/fsl-release-bsp/Build/tmp/sysroots/x86_64-linux/usr]  
Getting the current patchlevel...
Build a threading Perl? [y]  
Use which C compiler? [gcc ]  
Checking for GNU cc in disguise and/or its version number...
Now, how can we feed standard input to your C preprocessor...
Directories to use for library searches?
[/usr/local/lib /usr/lib/gcc/x86_64-linux-gnu/4.8/include-fixed /usr/include/x86_64-linux-gnu /usr/lib /lib/x86_64-linux-gnu /lib/../lib /usr/lib/x86_64-linux-gnu /usr/lib/../lib /lib /lib64]  
What is the file extension used for shared libraries? [so]  
Make shared library basenames unique? [n]  
Build Perl for SOCKS? [n]  
Try to use long doubles if available? [n]  
Checking for optional libraries...
What libraries to use? [-lpthread -lnsl -ldl -lm -lcrypt -lutil -lc -lposix]  
What optimizer/debugger flag should be used? [-O2]  
Any additional cc flags?
[-D_REENTRANT -D_GNU_SOURCE -fwrapv -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include]  
Let me guess what the preprocessor flags are...
Any additional ld flags (NOT including libraries)?
[-L/home/kumarn/imx6_build/fsl-release-bsp/Build/tmp/sysroots/x86_64-linux/usr/lib -L/home/kumarn/imx6_build/fsl-release-bsp/Build/tmp/sysroots/x86_64-linux/lib -Wl,-rpath-link,/home/kumarn/imx6_build/fsl-release-bsp/Build/tmp/sysroots/x86_64-linux/usr/lib -Wl,-rpath-link,/home/kumarn/imx6_build/fsl-release-bsp/Build/tmp/sysroots/x86_64-linux/lib -Wl,-rpath,/home/kumarn/imx6_build/fsl-release-bsp/Build/tmp/sysroots/x86_64-linux/usr/lib -Wl,-rpath,/home/kumarn/imx6_build/fsl-release-bsp/Build/tmp/sysroots/x86_64-linux/lib -Wl,-O1 -fstack-protector -L/usr/local/lib]  
Checking your choice of C compiler and flags for coherency...
I've tried to compile and run the following simple program:

#include <stdio.h>
int main() { printf("Ok\n"); return(0); }

I used the command:

	gcc -o try -O2 -D_REENTRANT -D_GNU_SOURCE -fwrapv -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -L/home/kumarn/imx6_build/fsl-release-bsp/Build/tmp/sysroots/x86_64-linux/usr/lib -L/home/kumarn/imx6_build/fsl-release-bsp/Build/tmp/sysroots/x86_64-linux/lib -Wl,-rpath-link,/home/kumarn/imx6_build/fsl-release-bsp/Build/tmp/sysroots/x86_64-linux/usr/lib -Wl,-rpath-link,/home/kumarn/imx6_build/fsl-release-bsp/Build/tmp/sysroots/x86_64-linux/lib -Wl,-rpath,/home/kumarn/imx6_build/fsl-release-bsp/Build/tmp/sysroots/x86_64-linux/usr/lib -Wl,-rpath,/home/kumarn/imx6_build/fsl-release-bsp/Build/tmp/sysroots/x86_64-linux/lib -Wl,-O1 -fstack-protector -L/usr/local/lib try.c -lpthread -lnsl -ldl -lm -lcrypt -lutil -lc -lposix
	 ./try

and I got the following output:

/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/libposix.so when searching for -lposix
/usr/bin/ld: skipping incompatible /usr/lib/../lib/libposix.so when searching for -lposix
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../libposix.so when searching for -lposix
/usr/bin/ld: skipping incompatible //usr/lib/libposix.so when searching for -lposix
/usr/bin/ld: cannot find -lposix
collect2: error: ld returned 1 exit status
I can't compile the test program.
You have a BIG problem.  Shall I abort Configure [y]  
Ok.  Stopping Configure.
WARNING: exit code 1 from a shell command.
ERROR: Function failed: do_configure (log file is located at /home/kumarn/imx6_build/fsl-release-bsp/Build/tmp/work/x86_64-linux/perl-native/5.22.0-r0/temp/log.do_configure.10604)

Re: Reg: Yocto installation problem

[Jeff Osier-Mixon]

Hi Praveen - make sure you follow the guidelines in the Quick Start
Guide for which packages need to be installed in Ubuntu before running
bitbake.

http://www.yoctoproject.org/docs/2.1/yocto-project-qs/yocto-project-qs.html

In general, you'll

(1) install the required packages
(2) clone poky from the git repository
(3) check out the current release
(4) run the environment script
(5) then run bitbake

The Quick Start Guide goes over all these steps in detail.

You might also get responses more specific to the Yocto Project by
posting on the yocto mailing list, rather than OE. You can join the
yocto list here:

https://lists.yoctoproject.org/listinfo/yocto

hope this helps


On Wed, Jun 29, 2016 at 9:56 PM, Praveenreddy Padamati
<praveenreddy.p@hcl.com> wrote:
> Hi all,
>
> I am installing the yocto in ubuntu version 14. Installtion is aborted
> intermediately. It comes out with the error
>
> "ERROR: Task 984
> (/home/kumarn/imx6_build/fsl-release-bsp/sources/poky/meta/recipes-devtools/perl/perl-native_5.22.0.bb,
> do_configure) failed with exit code '1'".
>
> Please find the log file in the attachment.
>
> Thanks
> Praveen Reddy P
> 9989642159
>
>
>
> ::DISCLAIMER::
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
> The contents of this e-mail and any attachment(s) are confidential and
> intended for the named recipient(s) only.
> E-mail transmission is not guaranteed to be secure or error-free as
> information could be intercepted, corrupted,
> lost, destroyed, arrive late or incomplete, or may contain viruses in
> transmission. The e mail and its contents
> (with or without referred errors) shall therefore not attach any liability
> on the originator or HCL or its affiliates.
> Views or opinions, if any, presented in this email are solely those of the
> author and may not necessarily reflect the
> views or opinions of HCL or its affiliates. Any form of reproduction,
> dissemination, copying, disclosure, modification,
> distribution and / or publication of this message without the prior written
> consent of authorized representative of
> HCL is strictly prohibited. If you have received this email in error please
> delete it and notify the sender immediately.
> Before opening any email and/or attachments, please check them for viruses
> and other defects.
>
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>



-- 
Jeff Osier-Mixon - Open Source Community Engineer, Intel Corporation