eclipse-poky: Can't build from Eclipse, but command line build works

eclipse-poky: Can't build from Eclipse, but command line build works

[Bryan Evenson]

I am trying to get the Yocto Eclipse plug-in setup so that I can build my application from Eclipse.  I am *almost* there, but the final build is not working.  I'm assuming there are some path/rights issues somewhere in the chain because I can build from the command line.  I'm looking for some help in figuring out where the difference is.

I am using Fedora 21 64-bit for a host system.  I am using Eclipse Kepler; I also have Eclipse Luna installed, but I had to install Eclipse Kepler since another plugin I am using does not yet have support for Eclipse Luna.  I am on poky/daisy HEAD and have been able successfully build my image (image based on core-image-minimal with a few extra applications).  Under Eclipse Kepler, I installed the pre-build plug-in from the Yocto Eclipse Update Site as instructed in the Yocto Project Development Manual for Poky 1.6.2.  I am using my existing toolchain in the build directory, so I issued "bitbake meta-ide-support" to generate the cross-toolchain support.  I then followed the instructions under "Extracting the Root Filesystem" in the ADT Manual to extract the root filesystem.  Specifically, I sourced the newly created environment script and then called "runqemu-extract-sdk <my_built_image.tar.gz> <sysroot_destination_directory>".  Then, from Eclipse I setup the Yocto Project ADT for a "Build System Derived Toolchain", I set the Toolchain Root Directory to my Poky build directory, and I set the Sysroot location to my extracted sysroot directory.

After the initial environment setup, from Eclipse I selected File->New->C Project, and selected a "Hello World ANSI C Autotools Project" under the "Yocto Project ADT Autotools Project" options.  For the new project, if I select "Reconfigure Project" the configuration fails with the following error:

	checking whether the C compiler works... no

From checking config.log, here are the details on the build failure:

	configure:3289: checking whether the C compiler works
	configure:3311: arm-poky-linux-gnueabi-gcc  -march=armv5te -marm -mthumb-interwork -mtune=arm926ej-s --sysroot=$SDKTARGETSYSROOT  -g -O0  --sysroot=/<home_path>/extracted_sysroot_1.6.2  --sysroot=/<home_path>/extracted_sysroot_1.6.2  --sysroot=/<home_path>/extracted_sysroot_1.6.2 conftest.c  >&5
	/<home_path>/poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld: cannot find crt1.o: No such file or directory
	/<home_path>/poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld: cannot find crti.o: No such file or directory
	/<home_path>/poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld: cannot find crtbegin.o: No such file or directory
	/<home_path>/poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld: cannot find -lgcc
	/<home_path>/poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld: cannot find -lgcc_s
	/<home_path>/poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld: cannot find -lc
	/<home_path>/poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld: cannot find -lgcc
	/<home_path>/poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld: cannot find -lgcc_s
	/<home_path>/poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld: cannot find crtend.o: No such file or directory
	/<home_path>/poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld: cannot find crtn.o: No such file or directory
	collect2: error: ld returned 1 exit status
	configure:3315: $? = 1
	configure:3353: result: no
	configure: failed program was:
	| /* confdefs.h */
	| #define PACKAGE_NAME "adt_test_app"
	| #define PACKAGE_TARNAME "adt_test_app"
	| #define PACKAGE_VERSION "0.1.0"
	| #define PACKAGE_STRING "adt_test_app 0.1.0"
	| #define PACKAGE_BUGREPORT ""
	| #define PACKAGE_URL ""
	| #define PACKAGE "adt_test_app"
	| #define VERSION "0.1.0"
	| /* end confdefs.h.  */
	| 
	| int
	| main ()
	| {
	| 
	|   ;
	|   return 0;
	| }
	configure:3358: error: in `/<home_path>/workspace_kepler/adt_test_app':
	configure:3360: error: C compiler cannot create executables

Note that <home_path> included the actual path to my home directory in config.log but I changed it to <home_path> for the purposes of this e-mail (yes, I'm paranoid).

However, if I instead open a terminal, go to my project directory and do the following:

	source <path_to_Poky_build_directory>/environment-setup-arm926ejste-poky-linux-gnueabi
	./configure ${CONFIGURE_FLAGS}

The project configures without a problem.  I can then either build from the command line or I can build from Eclipse.  It seems very odd to me that the configure doesn't work from Eclipse, but once it is configured I can build without issue.  Anyone have any ideas as to what I have wrong in my setup?

Thanks,
Bryan

Re: eclipse-poky: Can't build from Eclipse, but command line build works

[Minchev, Todor]

[-- Attachment #1: Type: text/plain, Size: 6345 bytes --]

Hello Bryan,

On Wed, 2015-03-11 at 13:45 +0000, Bryan Evenson wrote:
> I am trying to get the Yocto Eclipse plug-in setup so that I can build my application from Eclipse.  I am *almost* there, but the final build is not working.  I'm assuming there are some path/rights issues somewhere in the chain because I can build from the command line.  I'm looking for some help in figuring out where the difference is.
> 
> I am using Fedora 21 64-bit for a host system.  I am using Eclipse Kepler; I also have Eclipse Luna installed, but I had to install Eclipse Kepler since another plugin I am using does not yet have support for Eclipse Luna.  I am on poky/daisy HEAD and have been able successfully build my image (image based on core-image-minimal with a few extra applications).  Under Eclipse Kepler, I installed the pre-build plug-in from the Yocto Eclipse Update Site as instructed in the Yocto Project Development Manual for Poky 1.6.2.  I am using my existing toolchain in the build directory, so I issued "bitbake meta-ide-support" to generate the cross-toolchain support.  I then followed the instructions under "Extracting the Root Filesystem" in the ADT Manual to extract the root filesystem.  Specifically, I sourced the newly created environment script and then called "runqemu-extract-sdk <my_built_image.tar.gz> <sysroot_destination_directory>".  Then, from Eclipse I setup the Yocto Project AD
>  T for a "Build System Derived Toolchain", I set the Toolchain Root Directory to my Poky build directory, and I set the Sysroot location to my extracted sysroot directory.
> 
> After the initial environment setup, from Eclipse I selected File->New->C Project, and selected a "Hello World ANSI C Autotools Project" under the "Yocto Project ADT Autotools Project" options.  For the new project, if I select "Reconfigure Project" the configuration fails with the following error:
> 
> 	checking whether the C compiler works... no
> 
> From checking config.log, here are the details on the build failure:
> 
> 	configure:3289: checking whether the C compiler works
> 	configure:3311: arm-poky-linux-gnueabi-gcc  -march=armv5te -marm -mthumb-interwork -mtune=arm926ej-s --sysroot=$SDKTARGETSYSROOT  -g -O0  --sysroot=/<home_path>/extracted_sysroot_1.6.2  --sysroot=/<home_path>/extracted_sysroot_1.6.2  --sysroot=/<home_path>/extracted_sysroot_1.6.2 conftest.c  >&5

It appears that your toolchain is configured properly, however the  GNU
linker (ld) cannot find the libraries it needs to link the binary. 

I suspect that the culprit is "--sysroot=$SDKTARGETSYSROOT"

There should be an environment setup file

/<home_path>/poky/poky-build/tmp/environment-setup-XX


If you open it you will see SDKTARGETSYSROOT environment variable. It
most likely points to a different sysroot path. Please change it to
point to the directory where you extracted your sysroot
(/<home_path>/extracted_sysroot_1.6.2), create a new project and see if
that builds OK.


> 	/<home_path>/poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld: cannot find crt1.o: No such file or directory
> 	/<home_path>/poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld: cannot find crti.o: No such file or directory
> 	/<home_path>/poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld: cannot find crtbegin.o: No such file or directory
> 	/<home_path>/poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld: cannot find -lgcc
> 	/<home_path>/poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld: cannot find -lgcc_s
> 	/<home_path>/poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld: cannot find -lc
> 	/<home_path>/poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld: cannot find -lgcc
> 	/<home_path>/poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld: cannot find -lgcc_s
> 	/<home_path>/poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld: cannot find crtend.o: No such file or directory
> 	/<home_path>/poky/poky-build/tmp/sysroots/x86_64-linux/usr/libexec/arm926ejste-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.8.2/ld: cannot find crtn.o: No such file or directory
> 	collect2: error: ld returned 1 exit status
> 	configure:3315: $? = 1
> 	configure:3353: result: no
> 	configure: failed program was:
> 	| /* confdefs.h */
> 	| #define PACKAGE_NAME "adt_test_app"
> 	| #define PACKAGE_TARNAME "adt_test_app"
> 	| #define PACKAGE_VERSION "0.1.0"
> 	| #define PACKAGE_STRING "adt_test_app 0.1.0"
> 	| #define PACKAGE_BUGREPORT ""
> 	| #define PACKAGE_URL ""
> 	| #define PACKAGE "adt_test_app"
> 	| #define VERSION "0.1.0"
> 	| /* end confdefs.h.  */
> 	| 
> 	| int
> 	| main ()
> 	| {
> 	| 
> 	|   ;
> 	|   return 0;
> 	| }
> 	configure:3358: error: in `/<home_path>/workspace_kepler/adt_test_app':
> 	configure:3360: error: C compiler cannot create executables
> 
> Note that <home_path> included the actual path to my home directory in config.log but I changed it to <home_path> for the purposes of this e-mail (yes, I'm paranoid).
> 
> However, if I instead open a terminal, go to my project directory and do the following:
> 
> 	source <path_to_Poky_build_directory>/environment-setup-arm926ejste-poky-linux-gnueabi
> 	./configure ${CONFIGURE_FLAGS}

> The project configures without a problem.  I can then either build from the command line or I can build from Eclipse.  It seems very odd to me that the configure doesn't work from Eclipse, but once it is configured I can build without issue.  Anyone have any ideas as to what I have wrong in my setup?
> 

This builds, but it most likely uses the rootfs bundled in the
poky-build directory as pointed to by SDKTARGETSYSROOT and not the
rootfs which your extracted.

Thanks,
Todor

> Thanks,
> Bryan


[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5229 bytes --]

Re: eclipse-poky: Can't build from Eclipse, but command line build works

[Bryan Evenson]

[-- Attachment #1: Type: text/plain, Size: 5731 bytes --]

Todor,

> It appears that your toolchain is configured properly, however the  GNU linker (ld) cannot find the libraries it needs to link the binary.
> I suspect that the culprit is "--sysroot=$SDKTARGETSYSROOT"
> There should be an environment setup file
>
> /<home_path>/poky/poky-build/tmp/environment-setup-XX
>
> If you open it you will see SDKTARGETSYSROOT environment variable. It most likely points to a different sysroot path.
> Please change it to point to the directory where you extracted your sysroot (/<home_path>/extracted_sysroot_1.6.2),
> create a new project and see if that builds OK.

I've been having a few other issues with Eclipse (Install New Software menu item disappearing, other plugins disappearing after restarting, etc.), so I uninstalled eclipse, deleted my ~/.eclipse and workspace directories and re-installed Eclipse.  I need to run Eclipse Kepler (another plugin I'm using isn't ready for Eclipse Luna), so I followed these instructions for installing Eclipse by hand: http://www.92wiki.com/en/blog/detail/install-eclipse-kepler-on-fedora-17-18-19-centos-red-hat-rhel-5-6.   I also edited my environment setup script as suggested.  I then reinstalled all necessary plugins as described in the ADT manual.  I pointed the toolchain to my build directory and the sysroot location to my extracted sysroot.  I then followed the steps in the ADT manual to create a new Hello World Yocto ADT project.  I verified the SDKTARGETSYSROOT environment variable in the new project points to my extracted sysroot.  When I attempted to build, I get the following output:


Invoking autogen.sh in build directory: /<home_path>/workspace/adt_test/

Command-line environment variables:
         CFLAGS=" -g -O0  --sysroot=/<home_path>/extracted_sysroot_1.6.2" CXXFLAGS=" -g -O0  --sysroot=/<home_path>/extracted_sysroot_1.6.2" LDFLAGS=" --sysroot=/<home_path>/extracted_sysroot_1.6.2" CPPFLAGS=" --sysroot=/<home_path>/extracted_sysroot_1.6.2"

sh -c "/<home_path>/workspace/adt_test/autogen.sh --with-libtool-sysroot=/<home_path>/extracted_sysroot_1.6.2 --target=arm-poky-linux-gnueabi --host=arm-poky-linux-gnueabi --build=x86_64-linux --with-libtool-sysroot=/<home_path>/extracted_sysroot_1.6.2"
aclocal: warning: couldn't open directory '/<home_path>/extracted_sysroot_1.6.2/usr/share/aclocal': No such file or directory
configure.ac:16: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms are deprecated.  For more info, see:
configure.ac:16: http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation
configure.ac:20: installing './compile'
configure.ac:20: installing './config.guess'
configure.ac:20: installing './config.sub'
configure.ac:16: installing './install-sh'
configure.ac:16: installing './missing'
src/Makefile.am: installing './depcomp'
configure: loading site script /<home_path>/poky/meta/site/endian-little
configure: loading site script /<home_path>/poky/meta/site/arm-common
configure: loading site script /<home_path>/poky/meta/site/common-linux
configure: loading site script /<home_path>/poky/meta/site/common-glibc
configure: loading site script /<home_path>/poky/meta/site/arm-linux
configure: loading site script /<home_path>/poky/meta/site/common
configure: loading site script /<home_path>/poky/meta-openembedded/meta-oe/site/endian-little
configure: loading site script /<home_path>/poky/poky-build/tmp/sysroots/at91sam9x5ek/usr/share/arm-poky-linux-gnueabi_config_site.d/ncurses_config
configure: loading site script /<home_path>/poky/poky-build/tmp/sysroots/at91sam9x5ek/usr/share/arm-poky-linux-gnueabi_config_site.d/eglibc_config
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for arm-poky-linux-gnueabi-strip... arm-poky-linux-gnueabi-strip
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking build system type... x86_64-pc-linux-gnu
checking host system type... arm-poky-linux-gnueabi
checking how to print strings... printf
checking for style of include used by make... GNU
checking for arm-poky-linux-gnueabi-gcc... arm-poky-linux-gnueabi-gcc  -march=armv5te -marm -mthumb-interwork -mtune=arm926ej-s --sysroot=$SDKTARGETSYSROOT
checking whether the C compiler works... no
configure: error: in `/<home_path>/workspace/adt_test':
configure: error: in `/<home_path>/workspace/adt_test':
configure: error: C compiler cannot create executables
configure: error: C compiler cannot create executables
See `config.log' for more details

Configuration failed with error

The bold lines are ones that I see as a potential problem.  First, the system couldn't find aclocal in my extracted sysroot.  I took a look in the directory listed, and aclocal is not in there.  I think the configure script also found the build system's install and mkdir (/usr/bin/install and /usr/bin/mkdir).  I don't know if there is supposed to be one of these in the extracted sysroot or not, but I thought it was worth noting.

On a possibly related topic, I noticed that the Eclipse Indexer is using the build system's header files.  For example, if I open the main source file from the Hellow World application, place my cursor on the line "#include <stdlib.h>" and hit F3, /usr/include/stdlib.h opens up instead of stdlib.h from my toolchain.  Under the Eclipse project, for the listed Includes directories it has the following:

/usr/include
/usr/lib/gcc/x86_64-redhat-linux/4.9.2/include
/usr/local/include

Any thoughts on how to fix these issues?

Thanks,
Bryan


[-- Attachment #2: Type: text/html, Size: 7692 bytes --]

Re: eclipse-poky: Can't build from Eclipse, but command line build works

[Minchev, Todor]

[-- Attachment #1: Type: text/plain, Size: 6439 bytes --]

On Thu, 2015-03-12 at 13:43 +0000, Bryan Evenson wrote:
> Todor,
>  
> > It appears that your toolchain is configured properly, however the
> GNU linker (ld) cannot find the libraries it needs to link the
> binary. 
> > I suspect that the culprit is "--sysroot=$SDKTARGETSYSROOT"
> > There should be an environment setup file
> > 
> > /<home_path>/poky/poky-build/tmp/environment-setup-XX
> >
> > If you open it you will see SDKTARGETSYSROOT environment variable.
> It most likely points to a different sysroot path.
> > Please change it to point to the directory where you extracted your
> sysroot (/<home_path>/extracted_sysroot_1.6.2),
> > create a new project and see if that builds OK.
>  
> I've been having a few other issues with Eclipse (Install New Software
> menu item disappearing, other plugins disappearing after restarting,
> etc.), so I uninstalled eclipse, deleted my ~/.eclipse and workspace
> directories and re-installed Eclipse.  I need to run Eclipse Kepler
> (another plugin I'm using isn't ready for Eclipse Luna), so I followed
> these instructions for installing Eclipse by hand:
> http://www.92wiki.com/en/blog/detail/install-eclipse-kepler-on-fedora-17-18-19-centos-red-hat-rhel-5-6.   I also edited my environment setup script as suggested.  I then reinstalled all necessary plugins as described in the ADT manual.  I pointed the toolchain to my build directory and the sysroot location to my extracted sysroot.  I then followed the steps in the ADT manual to create a new Hello World Yocto ADT project.  I verified the SDKTARGETSYSROOT environment variable in the new project points to my extracted sysroot.  When I attempted to build, I get the following output:
>  
>  
> Invoking autogen.sh in build
> directory: /<home_path>/workspace/adt_test/
>  
> Command-line environment variables:
>         CFLAGS=" -g -O0
> --sysroot=/<home_path>/extracted_sysroot_1.6.2" CXXFLAGS=" -g -O0
> --sysroot=/<home_path>/extracted_sysroot_1.6.2" LDFLAGS="
> --sysroot=/<home_path>/extracted_sysroot_1.6.2" CPPFLAGS="
> --sysroot=/<home_path>/extracted_sysroot_1.6.2"
>  
> sh -c "/<home_path>/workspace/adt_test/autogen.sh
> --with-libtool-sysroot=/<home_path>/extracted_sysroot_1.6.2
> --target=arm-poky-linux-gnueabi --host=arm-poky-linux-gnueabi
> --build=x86_64-linux
> --with-libtool-sysroot=/<home_path>/extracted_sysroot_1.6.2"
> aclocal: warning: couldn't open directory
> '/<home_path>/extracted_sysroot_1.6.2/usr/share/aclocal': No such file
> or directory
> configure.ac:16: warning: AM_INIT_AUTOMAKE: two- and three-arguments
> forms are deprecated.  For more info, see:
> configure.ac:16:
> http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation
> configure.ac:20: installing './compile'
> configure.ac:20: installing './config.guess'
> configure.ac:20: installing './config.sub'
> configure.ac:16: installing './install-sh'
> configure.ac:16: installing './missing'
> src/Makefile.am: installing './depcomp'
> configure: loading site
> script /<home_path>/poky/meta/site/endian-little
> configure: loading site script /<home_path>/poky/meta/site/arm-common
> configure: loading site
> script /<home_path>/poky/meta/site/common-linux
> configure: loading site
> script /<home_path>/poky/meta/site/common-glibc
> configure: loading site script /<home_path>/poky/meta/site/arm-linux
> configure: loading site script /<home_path>/poky/meta/site/common
> configure: loading site
> script /<home_path>/poky/meta-openembedded/meta-oe/site/endian-little
> configure: loading site
> script /<home_path>/poky/poky-build/tmp/sysroots/at91sam9x5ek/usr/share/arm-poky-linux-gnueabi_config_site.d/ncurses_config
> configure: loading site
> script /<home_path>/poky/poky-build/tmp/sysroots/at91sam9x5ek/usr/share/arm-poky-linux-gnueabi_config_site.d/eglibc_config
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for arm-poky-linux-gnueabi-strip...
> arm-poky-linux-gnueabi-strip
> checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking whether make supports nested variables... yes
> checking build system type... x86_64-pc-linux-gnu
> checking host system type... arm-poky-linux-gnueabi
> checking how to print strings... printf
> checking for style of include used by make... GNU
> checking for arm-poky-linux-gnueabi-gcc... arm-poky-linux-gnueabi-gcc
> -march=armv5te -marm -mthumb-interwork -mtune=arm926ej-s --sysroot=
> $SDKTARGETSYSROOT
> checking whether the C compiler works... no
> configure: error: in `/<home_path>/workspace/adt_test':
> configure: error: in `/<home_path>/workspace/adt_test':
> configure: error: C compiler cannot create executables
> configure: error: C compiler cannot create executables
> See `config.log' for more details

This is a different error. There seems to be a mismatch between your
toolchain and rootfs. Could you please share the full name of 

my_built_image.tar.gz from

runqemu-extract-sdk <my_built_image.tar.gz>
<sysroot_destination_directory>"

>  
> Configuration failed with error
>  
> The bold lines are ones that I see as a potential problem.  First, the
> system couldn't find aclocal in my extracted sysroot.  I took a look
> in the directory listed, and aclocal is not in there.  I think the
> configure script also found the build system's install and mkdir
> (/usr/bin/install and /usr/bin/mkdir).  I don't know if there is
> supposed to be one of these in the extracted sysroot or not, but I
> thought it was worth noting.
>  
> On a possibly related topic, I noticed that the Eclipse Indexer is
> using the build system's header files.  For example, if I open the
> main source file from the Hellow World application, place my cursor on
> the line "#include <stdlib.h>" and hit F3, /usr/include/stdlib.h opens
> up instead of stdlib.h from my toolchain.  Under the Eclipse project,
> for the listed Includes directories it has the following:
>  
> /usr/include
> /usr/lib/gcc/x86_64-redhat-linux/4.9.2/include
> /usr/local/include

Eclipse is showing the host headers, but it will use the headers from
your sysroot during the actual build.

>  
> Any thoughts on how to fix these issues?
>  
> Thanks,
> Bryan
>  


[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5229 bytes --]

Re: eclipse-poky: Can't build from Eclipse, but command line build works

[Bryan Evenson]

> -----Original Message-----
> From: Minchev, Todor [mailto:todor.minchev@intel.com]
> Sent: Thursday, March 12, 2015 1:50 PM
> To: Bryan Evenson
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] eclipse-poky: Can't build from Eclipse, but command line
> build works
> 
> On Thu, 2015-03-12 at 13:43 +0000, Bryan Evenson wrote:
> > Todor,
> >
> > > It appears that your toolchain is configured properly, however the
> > GNU linker (ld) cannot find the libraries it needs to link the
> > binary.
> > > I suspect that the culprit is "--sysroot=$SDKTARGETSYSROOT"
> > > There should be an environment setup file
> > >
> > > /<home_path>/poky/poky-build/tmp/environment-setup-XX
> > >
> > > If you open it you will see SDKTARGETSYSROOT environment variable.
> > It most likely points to a different sysroot path.
> > > Please change it to point to the directory where you extracted your
> > sysroot (/<home_path>/extracted_sysroot_1.6.2),
> > > create a new project and see if that builds OK.
> >
> > I've been having a few other issues with Eclipse (Install New Software
> > menu item disappearing, other plugins disappearing after restarting,
> > etc.), so I uninstalled eclipse, deleted my ~/.eclipse and workspace
> > directories and re-installed Eclipse.  I need to run Eclipse Kepler
> > (another plugin I'm using isn't ready for Eclipse Luna), so I followed
> > these instructions for installing Eclipse by hand:
> > http://www.92wiki.com/en/blog/detail/install-eclipse-kepler-on-fedora-
> 17-18-19-centos-red-hat-rhel-5-6.   I also edited my environment setup script
> as suggested.  I then reinstalled all necessary plugins as described in the ADT
> manual.  I pointed the toolchain to my build directory and the sysroot
> location to my extracted sysroot.  I then followed the steps in the ADT
> manual to create a new Hello World Yocto ADT project.  I verified the
> SDKTARGETSYSROOT environment variable in the new project points to my
> extracted sysroot.  When I attempted to build, I get the following output:
> >
> >
> > Invoking autogen.sh in build
> > directory: /<home_path>/workspace/adt_test/
> >
> > Command-line environment variables:
> >         CFLAGS=" -g -O0
> > --sysroot=/<home_path>/extracted_sysroot_1.6.2" CXXFLAGS=" -g -O0
> > --sysroot=/<home_path>/extracted_sysroot_1.6.2" LDFLAGS="
> > --sysroot=/<home_path>/extracted_sysroot_1.6.2" CPPFLAGS="
> > --sysroot=/<home_path>/extracted_sysroot_1.6.2"
> >
> > sh -c "/<home_path>/workspace/adt_test/autogen.sh
> > --with-libtool-sysroot=/<home_path>/extracted_sysroot_1.6.2
> > --target=arm-poky-linux-gnueabi --host=arm-poky-linux-gnueabi
> > --build=x86_64-linux
> > --with-libtool-sysroot=/<home_path>/extracted_sysroot_1.6.2"
> > aclocal: warning: couldn't open directory
> > '/<home_path>/extracted_sysroot_1.6.2/usr/share/aclocal': No such file
> > or directory
> > configure.ac:16: warning: AM_INIT_AUTOMAKE: two- and three-
> arguments
> > forms are deprecated.  For more info, see:
> > configure.ac:16:
> >
> http://www.gnu.org/software/automake/manual/automake.html#Moderni
> ze-AM_005fINIT_005fAUTOMAKE-invocation
> > configure.ac:20: installing './compile'
> > configure.ac:20: installing './config.guess'
> > configure.ac:20: installing './config.sub'
> > configure.ac:16: installing './install-sh'
> > configure.ac:16: installing './missing'
> > src/Makefile.am: installing './depcomp'
> > configure: loading site
> > script /<home_path>/poky/meta/site/endian-little
> > configure: loading site script /<home_path>/poky/meta/site/arm-common
> > configure: loading site
> > script /<home_path>/poky/meta/site/common-linux
> > configure: loading site
> > script /<home_path>/poky/meta/site/common-glibc
> > configure: loading site script /<home_path>/poky/meta/site/arm-linux
> > configure: loading site script /<home_path>/poky/meta/site/common
> > configure: loading site
> > script /<home_path>/poky/meta-openembedded/meta-oe/site/endian-
> little
> > configure: loading site
> > script /<home_path>/poky/poky-
> build/tmp/sysroots/at91sam9x5ek/usr/share/arm-poky-linux-
> gnueabi_config_site.d/ncurses_config
> > configure: loading site
> > script /<home_path>/poky/poky-
> build/tmp/sysroots/at91sam9x5ek/usr/share/arm-poky-linux-
> gnueabi_config_site.d/eglibc_config
> > checking for a BSD-compatible install... /usr/bin/install -c
> > checking whether build environment is sane... yes
> > checking for arm-poky-linux-gnueabi-strip...
> > arm-poky-linux-gnueabi-strip
> > checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
> > checking for gawk... gawk
> > checking whether make sets $(MAKE)... yes
> > checking whether make supports nested variables... yes
> > checking build system type... x86_64-pc-linux-gnu
> > checking host system type... arm-poky-linux-gnueabi
> > checking how to print strings... printf
> > checking for style of include used by make... GNU
> > checking for arm-poky-linux-gnueabi-gcc... arm-poky-linux-gnueabi-gcc
> > -march=armv5te -marm -mthumb-interwork -mtune=arm926ej-s --
> sysroot=
> > $SDKTARGETSYSROOT
> > checking whether the C compiler works... no
> > configure: error: in `/<home_path>/workspace/adt_test':
> > configure: error: in `/<home_path>/workspace/adt_test':
> > configure: error: C compiler cannot create executables
> > configure: error: C compiler cannot create executables
> > See `config.log' for more details
> 
> This is a different error. There seems to be a mismatch between your
> toolchain and rootfs. Could you please share the full name of
> 
> my_built_image.tar.gz from
> 
> runqemu-extract-sdk <my_built_image.tar.gz>
> <sysroot_destination_directory>"
> 

core-image-my-minimal-at91sam9x5ek.tar.gz

It's the root filesystem that I built and runs on our target hardware.  It's based on core-image-minimal with a few additional packages.  Are there some additional (or some specific) packages that are needed for it to be a suitable rootfs for this purpose?

Thanks,
Bryan

> >
> > Configuration failed with error
> >
> > The bold lines are ones that I see as a potential problem.  First, the
> > system couldn't find aclocal in my extracted sysroot.  I took a look
> > in the directory listed, and aclocal is not in there.  I think the
> > configure script also found the build system's install and mkdir
> > (/usr/bin/install and /usr/bin/mkdir).  I don't know if there is
> > supposed to be one of these in the extracted sysroot or not, but I
> > thought it was worth noting.
> >
> > On a possibly related topic, I noticed that the Eclipse Indexer is
> > using the build system's header files.  For example, if I open the
> > main source file from the Hellow World application, place my cursor on
> > the line "#include <stdlib.h>" and hit F3, /usr/include/stdlib.h opens
> > up instead of stdlib.h from my toolchain.  Under the Eclipse project,
> > for the listed Includes directories it has the following:
> >
> > /usr/include
> > /usr/lib/gcc/x86_64-redhat-linux/4.9.2/include
> > /usr/local/include
> 
> Eclipse is showing the host headers, but it will use the headers from
> your sysroot during the actual build.
> 
> >
> > Any thoughts on how to fix these issues?
> >
> > Thanks,
> > Bryan
> >

Re: eclipse-poky: Can't build from Eclipse, but command line build works

[Bryan Evenson]

Todor,

> -----Original Message-----
> From: Minchev, Todor [mailto:todor.minchev@intel.com]
> Sent: Thursday, March 12, 2015 1:50 PM
> To: Bryan Evenson
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] eclipse-poky: Can't build from Eclipse, but command line
> build works
> 
> On Thu, 2015-03-12 at 13:43 +0000, Bryan Evenson wrote:
> > Todor,
> >
> > > It appears that your toolchain is configured properly, however the
> > GNU linker (ld) cannot find the libraries it needs to link the
> > binary.
> > > I suspect that the culprit is "--sysroot=$SDKTARGETSYSROOT"
> > > There should be an environment setup file
> > >
> > > /<home_path>/poky/poky-build/tmp/environment-setup-XX
> > >
> > > If you open it you will see SDKTARGETSYSROOT environment variable.
> > It most likely points to a different sysroot path.
> > > Please change it to point to the directory where you extracted your
> > sysroot (/<home_path>/extracted_sysroot_1.6.2),
> > > create a new project and see if that builds OK.
> >
> > I've been having a few other issues with Eclipse (Install New Software
> > menu item disappearing, other plugins disappearing after restarting,
> > etc.), so I uninstalled eclipse, deleted my ~/.eclipse and workspace
> > directories and re-installed Eclipse.  I need to run Eclipse Kepler
> > (another plugin I'm using isn't ready for Eclipse Luna), so I followed
> > these instructions for installing Eclipse by hand:
> > http://www.92wiki.com/en/blog/detail/install-eclipse-kepler-on-fedora-
> 17-18-19-centos-red-hat-rhel-5-6.   I also edited my environment setup script
> as suggested.  I then reinstalled all necessary plugins as described in the ADT
> manual.  I pointed the toolchain to my build directory and the sysroot
> location to my extracted sysroot.  I then followed the steps in the ADT
> manual to create a new Hello World Yocto ADT project.  I verified the
> SDKTARGETSYSROOT environment variable in the new project points to my
> extracted sysroot.  When I attempted to build, I get the following output:
> >
> >
> > Invoking autogen.sh in build
> > directory: /<home_path>/workspace/adt_test/
> >
> > Command-line environment variables:
> >         CFLAGS=" -g -O0
> > --sysroot=/<home_path>/extracted_sysroot_1.6.2" CXXFLAGS=" -g -O0
> > --sysroot=/<home_path>/extracted_sysroot_1.6.2" LDFLAGS="
> > --sysroot=/<home_path>/extracted_sysroot_1.6.2" CPPFLAGS="
> > --sysroot=/<home_path>/extracted_sysroot_1.6.2"
> >
> > sh -c "/<home_path>/workspace/adt_test/autogen.sh
> > --with-libtool-sysroot=/<home_path>/extracted_sysroot_1.6.2
> > --target=arm-poky-linux-gnueabi --host=arm-poky-linux-gnueabi
> > --build=x86_64-linux
> > --with-libtool-sysroot=/<home_path>/extracted_sysroot_1.6.2"
> > aclocal: warning: couldn't open directory
> > '/<home_path>/extracted_sysroot_1.6.2/usr/share/aclocal': No such file
> > or directory
> > configure.ac:16: warning: AM_INIT_AUTOMAKE: two- and three-
> arguments
> > forms are deprecated.  For more info, see:
> > configure.ac:16:
> >
> http://www.gnu.org/software/automake/manual/automake.html#Moderni
> ze-AM_005fINIT_005fAUTOMAKE-invocation
> > configure.ac:20: installing './compile'
> > configure.ac:20: installing './config.guess'
> > configure.ac:20: installing './config.sub'
> > configure.ac:16: installing './install-sh'
> > configure.ac:16: installing './missing'
> > src/Makefile.am: installing './depcomp'
> > configure: loading site
> > script /<home_path>/poky/meta/site/endian-little
> > configure: loading site script /<home_path>/poky/meta/site/arm-common
> > configure: loading site
> > script /<home_path>/poky/meta/site/common-linux
> > configure: loading site
> > script /<home_path>/poky/meta/site/common-glibc
> > configure: loading site script /<home_path>/poky/meta/site/arm-linux
> > configure: loading site script /<home_path>/poky/meta/site/common
> > configure: loading site
> > script /<home_path>/poky/meta-openembedded/meta-oe/site/endian-
> little
> > configure: loading site
> > script /<home_path>/poky/poky-
> build/tmp/sysroots/at91sam9x5ek/usr/share/arm-poky-linux-
> gnueabi_config_site.d/ncurses_config
> > configure: loading site
> > script /<home_path>/poky/poky-
> build/tmp/sysroots/at91sam9x5ek/usr/share/arm-poky-linux-
> gnueabi_config_site.d/eglibc_config
> > checking for a BSD-compatible install... /usr/bin/install -c
> > checking whether build environment is sane... yes
> > checking for arm-poky-linux-gnueabi-strip...
> > arm-poky-linux-gnueabi-strip
> > checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
> > checking for gawk... gawk
> > checking whether make sets $(MAKE)... yes
> > checking whether make supports nested variables... yes
> > checking build system type... x86_64-pc-linux-gnu
> > checking host system type... arm-poky-linux-gnueabi
> > checking how to print strings... printf
> > checking for style of include used by make... GNU
> > checking for arm-poky-linux-gnueabi-gcc... arm-poky-linux-gnueabi-gcc
> > -march=armv5te -marm -mthumb-interwork -mtune=arm926ej-s --
> sysroot=
> > $SDKTARGETSYSROOT
> > checking whether the C compiler works... no
> > configure: error: in `/<home_path>/workspace/adt_test':
> > configure: error: in `/<home_path>/workspace/adt_test':
> > configure: error: C compiler cannot create executables
> > configure: error: C compiler cannot create executables
> > See `config.log' for more details
> 
> This is a different error. There seems to be a mismatch between your
> toolchain and rootfs. Could you please share the full name of
> 
> my_built_image.tar.gz from
> 
> runqemu-extract-sdk <my_built_image.tar.gz>
> <sysroot_destination_directory>"
> 

I have been able to get things to build, but not exactly in a suggested manner.  I copied the entire target sysroot directory (~/poky/poky_build/tmp/sysroots/at91sam9x5ek) to the previously mentioned sysroot destination directory.  I re-ran "bitbake meta-ide-support" just to ensure I had a clean copy.  I then modified the SDKTARGETSYSROOT to point to my copied sysroot location.  With this setup, I was able to get the project to build from Eclipse.  It's working, but it's a little ugly getting there.

So I'm assuming I'm starting at the wrong point for the sysroot to extract.  What do other people do? 

Thanks,
Bryan

> >
> > Configuration failed with error
> >
> > The bold lines are ones that I see as a potential problem.  First, the
> > system couldn't find aclocal in my extracted sysroot.  I took a look
> > in the directory listed, and aclocal is not in there.  I think the
> > configure script also found the build system's install and mkdir
> > (/usr/bin/install and /usr/bin/mkdir).  I don't know if there is
> > supposed to be one of these in the extracted sysroot or not, but I
> > thought it was worth noting.
> >
> > On a possibly related topic, I noticed that the Eclipse Indexer is
> > using the build system's header files.  For example, if I open the
> > main source file from the Hellow World application, place my cursor on
> > the line "#include <stdlib.h>" and hit F3, /usr/include/stdlib.h opens
> > up instead of stdlib.h from my toolchain.  Under the Eclipse project,
> > for the listed Includes directories it has the following:
> >
> > /usr/include
> > /usr/lib/gcc/x86_64-redhat-linux/4.9.2/include
> > /usr/local/include
> 
> Eclipse is showing the host headers, but it will use the headers from
> your sysroot during the actual build.
> 
> >
> > Any thoughts on how to fix these issues?
> >
> > Thanks,
> > Bryan
> >

Re: eclipse-poky: Can't build from Eclipse, but command line build works

[Minchev, Todor]

[-- Attachment #1: Type: text/plain, Size: 1738 bytes --]

*snip*

> > This is a different error. There seems to be a mismatch between your
> > toolchain and rootfs. Could you please share the full name of
> > 
> > my_built_image.tar.gz from
> > 
> > runqemu-extract-sdk <my_built_image.tar.gz>
> > <sysroot_destination_directory>"
> > 
> 
> I have been able to get things to build, but not exactly in a suggested manner.  I copied the entire target sysroot directory (~/poky/poky_build/tmp/sysroots/at91sam9x5ek) to the previously mentioned sysroot destination directory.  I re-ran "bitbake meta-ide-support" just to ensure I had a clean copy.  I then modified the SDKTARGETSYSROOT to point to my copied sysroot location.  With this setup, I was able to get the project to build from Eclipse.  It's working, but it's a little ugly getting there.
> 

core-image-minimal builds a very small image, which doesn't have all
headers and libraries required to link even a simple binary

> So I'm assuming I'm starting at the wrong point for the sysroot to extract.  What do other people do? 

You have two options here:

1) Generate a standalone toolchain and sdk installer.

bitbake -c populate_sdk your_image_name

This will generate an installer script-tarball in
~/poky/poky_build/tmp/deploy/sdk/

Execute this script and follow the installation instructions. This will
extract both the toolchain and sysroot to a directory of your choice
(e.g. /opt/poky/1.6.2/).

When you configure the Yocto ADT plugin in Eclipse, select "Standalone
pre-built toolchain" before you point it to the sysroot and toolchain
directories created by the installer above. 
 

2) Base your image on one of the development images (e.g.
core-image-minimal-dev)

Cheers,
Todor




[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5229 bytes --]

Re: eclipse-poky: Can't build from Eclipse, but command line build works

[Bryan Evenson]

Todor,

> -----Original Message-----
> From: Minchev, Todor [mailto:todor.minchev@intel.com]
> Sent: Friday, March 13, 2015 4:59 AM
> To: Bryan Evenson
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] eclipse-poky: Can't build from Eclipse, but command line
> build works
> 
> *snip*
> 
> > > This is a different error. There seems to be a mismatch between your
> > > toolchain and rootfs. Could you please share the full name of
> > >
> > > my_built_image.tar.gz from
> > >
> > > runqemu-extract-sdk <my_built_image.tar.gz>
> > > <sysroot_destination_directory>"
> > >
> >
> > I have been able to get things to build, but not exactly in a suggested
> manner.  I copied the entire target sysroot directory
> (~/poky/poky_build/tmp/sysroots/at91sam9x5ek) to the previously
> mentioned sysroot destination directory.  I re-ran "bitbake meta-ide-
> support" just to ensure I had a clean copy.  I then modified the
> SDKTARGETSYSROOT to point to my copied sysroot location.  With this setup,
> I was able to get the project to build from Eclipse.  It's working, but it's a little
> ugly getting there.
> >
> 
> core-image-minimal builds a very small image, which doesn't have all
> headers and libraries required to link even a simple binary
> 
> > So I'm assuming I'm starting at the wrong point for the sysroot to extract.
> What do other people do?
> 
> You have two options here:
> 
> 1) Generate a standalone toolchain and sdk installer.
> 
> bitbake -c populate_sdk your_image_name
> 
> This will generate an installer script-tarball in
> ~/poky/poky_build/tmp/deploy/sdk/
> 
> Execute this script and follow the installation instructions. This will
> extract both the toolchain and sysroot to a directory of your choice
> (e.g. /opt/poky/1.6.2/).
> 
> When you configure the Yocto ADT plugin in Eclipse, select "Standalone
> pre-built toolchain" before you point it to the sysroot and toolchain
> directories created by the installer above.
> 
> 
> 2) Base your image on one of the development images (e.g.
> core-image-minimal-dev)
> 

So *that* explains why I've never been able to get the Eclipse plug-in to work.  I'd suggest adding the above detail to the "Extracting a Root Filesystem" section of the manual.

For a frame of reference, I do two separate actions.  I'll use bitbake to build our full production image.  We also have a few userspace applications in which I'll build through Eclipse and test on the actual hardware.  We interface with enough external devices that testing with the QEMU doesn't work too well and we'll need to test on actual hardware.  So I just need to build something that I can then run on the actual hardware.  After re-reading the "Extracting the Root Filesystem" section, I think there is an assumption that someone would only be doing this for QEMU purposes.  I think some details stating what is needed out of the extracted filesystem for development would be beneficial.

Thanks,
Bryan

> Cheers,
> Todor
> 
>