Re: [yocto] eclipse-poky: Can't build from Eclipse, but command line build works
Hello Bryan, On Wed, 2015-03-11 at 13:45 +, 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 > ". 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=//extracted_sysroot_1.6.2 > --sysroot=//extracted_sysroot_1.6.2 > --sysroot=//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 //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 (//extracted_sysroot_1.6.2), create a new project and see if that builds OK. > > //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 > > //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 > > //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 > > //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 > > //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 > > //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 > > //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 > > //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 > > //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 > > //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_STRI
Re: [yocto] eclipse-poky: Can't build from Eclipse, but command line build works
On Thu, 2015-03-12 at 13:43 +, 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 > > > > //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 (//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: //workspace/adt_test/ > > Command-line environment variables: > CFLAGS=" -g -O0 > --sysroot=//extracted_sysroot_1.6.2" CXXFLAGS=" -g -O0 > --sysroot=//extracted_sysroot_1.6.2" LDFLAGS=" > --sysroot=//extracted_sysroot_1.6.2" CPPFLAGS=" > --sysroot=//extracted_sysroot_1.6.2" > > sh -c "//workspace/adt_test/autogen.sh > --with-libtool-sysroot=//extracted_sysroot_1.6.2 > --target=arm-poky-linux-gnueabi --host=arm-poky-linux-gnueabi > --build=x86_64-linux > --with-libtool-sysroot=//extracted_sysroot_1.6.2" > aclocal: warning: couldn't open directory > '//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 //poky/meta/site/endian-little > configure: loading site script //poky/meta/site/arm-common > configure: loading site > script //poky/meta/site/common-linux > configure: loading site > script //poky/meta/site/common-glibc > configure: loading site script //poky/meta/site/arm-linux > configure: loading site script //poky/meta/site/common > configure: loading site > script //poky/meta-openembedded/meta-oe/site/endian-little > configure: loading site > script > //poky/poky-build/tmp/sysroots/at91sam9x5ek/usr/share/arm-poky-linux-gnueabi_config_site.d/ncurses_config > configure: loading site > script > //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 `//workspace/adt_test': > configure: error: in `//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 " > > Configuration failed with error > > The bold lines are ones that I see as a potential problem. First, the > system couldn't find aclo
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 > > " > > > > 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 smime.p7s Description: S/MIME cryptographic signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] eclipe-yocto: SDKTARGETSYSROOT not being expanded correctly
Hello Bryan,
On Mon, 2015-03-16 at 13:09 +, Bryan Evenson wrote:
> I am using version 1.6.2 of the Yocto Eclipse plug-in (from
> http://downloads.yoctoproject.org/releases/eclipse-plugin/1.6.2/kepler/)
> under Fedora 21. After some recent issues with getting the plug-in to
> compile my application, I noticed that I am having a variable expansion
> problem with CC.
>
> I followed the instructions for building an SDK for my image and I am using
> the pre-built toolchain. In the environment script for the SDK, CC is
> defined as follows:
>
> export CC="arm-poky-linux-gnueabi-gcc -march=armv5te -marm
> -mthumb-interwork -mtune=arm926ej-s --sysroot=$SDKTARGETSYSROOT"
>
> I then generate new a simple Yocto Hello World C project and build the
> application. It builds just fine, but I see the following in the console
> output:
>
> arm-poky-linux-gnueabi-gcc -march=armv5te -marm -mthumb-interwork
> -mtune=arm926ej-s --sysroot=DKTARGETSYSROOT
>
> However, if I go to Project->Properties->C/C++ Build->Environment and change
> the CC environment variable to the following:
>
> arm-poky-linux-gnueabi-gcc -march=armv5te -marm -mthumb-interwork
> -mtune=arm926ej-s --sysroot=${SDKTARGETSYSROOT}
>
> then the SDKTARGETSYSROOT is properly expanded to the correct value. Is
> anyone else seeing this problem, or is this due to the version of tools that
> exist on Fedora 21?
I just reproduced this bug and opened a bugzilla issue to track it.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7462
Thank you for taking the time to report this issue.
Thanks,
Todor
>
> Thanks,
> Bryan
smime.p7s
Description: S/MIME cryptographic signature
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto Eclipse Plugin
Hello Abhinav, On Mon, 2015-04-13 at 18:27 +, Bipnesh, Abhinav (Abhinav) wrote: > Hi All, > > I am trying to setup the Yocto Eclipse Plugin for Eclipse (Luna release). I > am able to install the Juno release plugin for 1.7.1 release. But while > configuring it I am facing issues as below > 1. When I try to provide BitBake directory as part of tool chain I get an > error that need to build meta-ide-support before configuring it. > As I did build meta-ide-support before setting up the path as I can see an > environment file present under /tmp path. You will need to provide the path to the build directory. This is the directory holding tmp. > 2. If I select Standard SDK option then it accepts the same i.e. it accept > environment file present under tmp directory as vaild which I suppose it > should not do. > 3. I already has Makefile based project which I am trying to configure in > eclipse by selecting Yocto as Toolchain. > But when I try to build it I am seeing its using platform GCC instead of > Yocto tool chain. Selecting the correct directory should set up the cross-compiler environment and fix this. > > How to fix the same as I cant change this project to an CMake based project. > > Is there as way I can use Kepler plugin instead of Juno as when I try the > same with Luna I am getting dependencies errors. You can find the plugin releases here: http://downloads.yoctoproject.org/releases/eclipse-plugin/ Cheers, Todor smime.p7s Description: S/MIME cryptographic signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto Eclipse Plugin
Hello Abinhav, This is most likely caused by a mismatch between the plugin build (juno) and the IDE (luna). Please install the luna build of the plugin from here: https://autobuilder.yoctoproject.org/pub/nightly/CURRENT/eclipse-plugin/luna/org.yocto.sdk-development-201504140001-archive.zip Thanks, Todor On Tue, 2015-04-14 at 08:39 +, Bipnesh, Abhinav (Abhinav) wrote: > Hi, > > > > I was using the same URL as you suggested for the Yocto Eclipse > Plugin. Below is the snapshot of the error I am getting when I try to > configure it as Build System derived tool chain > > > > > > > > > > I already did build meta-ide-support and can see the > environment-setup-ppce5500-fsl-linux under /tmp. If I > select Standalone SDK the it starts work without any issue. > > > > > > Second issue I am facing is that when I import my existing project > which is a Makefile base I can see option for Yocto CMake Build > (Toolchain) as below > > > > > > > > So how to fix this as need to make it working with existing Makefile > based project. > > > > > > Any thoughts how to fix these issues. > > > > Thanks, > > Abhinav > > > > -Original Message- > From: Minchev, Todor [mailto:todor.minc...@intel.com] > Sent: Tuesday, April 14, 2015 12:38 > To: Bipnesh, Abhinav (Abhinav) > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] Yocto Eclipse Plugin > > > > Hello Abhinav, > > > > On Mon, 2015-04-13 at 18:27 +, Bipnesh, Abhinav (Abhinav) wrote: > > > Hi All, > > > > > > I am trying to setup the Yocto Eclipse Plugin for Eclipse (Luna > release). I am able to install the Juno release plugin for 1.7.1 > release. But while configuring it I am facing issues as below > > > > > 1. When I try to provide BitBake directory as part of tool chain I > get an error that need to build meta-ide-support before configuring > it. > > > As I did build meta-ide-support before setting up the path as I can > see an environment file present under /tmp > path. > > > > You will need to provide the path to the build directory. This is the > > directory holding tmp. > > > > > 2. If I select Standard SDK option then it accepts the same i.e. it > accept environment file present under tmp directory as vaild which I > suppose it should not do. > > > 3. I already has Makefile based project which I am trying to > configure in eclipse by selecting Yocto as Toolchain. > > > But when I try to build it I am seeing its using platform GCC > instead of Yocto tool chain. > > > > Selecting the correct directory should set up the cross-compiler > > environment and fix this. > > > > > > How to fix the same as I cant change this project to an CMake based > project. > > > > > > Is there as way I can use Kepler plugin instead of Juno as when I > try the same with Luna I am getting dependencies errors. > > > > You can find the plugin releases here: > > https://urldefense.proofpoint.com/v2/url?u=http-3A__downloads.yoctoproject.org_releases_eclipse-2Dplugin_&d=AwIFaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=geJ1wB7xRIMmteYB2Fo8esL32BOWvwP1HmY0YuLEB4E&m=Hg_RatI-pPFNhlwlj3rvSiP3RspGPYNzHRBg-XaXN1U&s=11DZqLCED8UtaM9vU0YxGMeaNWGlerPzTawEoVwuJd4&e= > > > > > Cheers, > > Todor > > > > smime.p7s Description: S/MIME cryptographic signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto Eclipse Plugin
Hello Abhinav, On Wed, 2015-04-15 at 10:15 +, Bipnesh, Abhinav (Abhinav) wrote: > Hi Todor, > > I tried with below link and still observe the same issue. It didn’t identify > the bitbake directory environment files and report same errors. In your previous email you mentioned that the cross compiler variables are populated for the hello world example. If that's the case the IDE must have parsed the environment setup file. Please open a bug here so we can track this issue and I will investigate the problem. https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Eclipse%20Plugin Thanks, Todor > > Thanks, > Abhinav > > -----Original Message- > From: Minchev, Todor [mailto:todor.minc...@intel.com] > Sent: Tuesday, April 14, 2015 17:20 > To: Bipnesh, Abhinav (Abhinav) > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] Yocto Eclipse Plugin > > Hello Abinhav, > > This is most likely caused by a mismatch between the plugin build (juno) > and the IDE (luna). Please install the luna build of the plugin from > here: > > https://urldefense.proofpoint.com/v2/url?u=https-3A__autobuilder.yoctoproject.org_pub_nightly_CURRENT_eclipse-2Dplugin_luna_org.yocto.sdk-2Ddevelopment-2D201504140001-2Darchive.zip&d=AwIFaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=geJ1wB7xRIMmteYB2Fo8esL32BOWvwP1HmY0YuLEB4E&m=xo2lJGQ9ANMp6iXK5QeTFxfGaBn9HAZBpwjlrurzJSg&s=6lW-2yvLIg91mRJrVqXU608Eon92Q0K2p5jUJSptFFI&e= > > > Thanks, > Todor > > On Tue, 2015-04-14 at 08:39 +, Bipnesh, Abhinav (Abhinav) wrote: > > Hi, > > > > > > > > I was using the same URL as you suggested for the Yocto Eclipse > > Plugin. Below is the snapshot of the error I am getting when I try to > > configure it as Build System derived tool chain > > > > > > > > > > > > > > > > > > > > > I already did build meta-ide-support and can see the > > environment-setup-ppce5500-fsl-linux under /tmp. If I > > select Standalone SDK the it starts work without any issue. > > > > > > > > > > > > Second issue I am facing is that when I import my existing project > > which is a Makefile base I can see option for Yocto CMake Build > > (Toolchain) as below > > > > > > > > > > > > > > > > So how to fix this as need to make it working with existing Makefile > > based project. > > > > > > > > > > > > Any thoughts how to fix these issues. > > > > > > > > Thanks, > > > > Abhinav > > > > > > > > -Original Message- > > From: Minchev, Todor [mailto:todor.minc...@intel.com] > > Sent: Tuesday, April 14, 2015 12:38 > > To: Bipnesh, Abhinav (Abhinav) > > Cc: yocto@yoctoproject.org > > Subject: Re: [yocto] Yocto Eclipse Plugin > > > > > > > > Hello Abhinav, > > > > > > > > On Mon, 2015-04-13 at 18:27 +, Bipnesh, Abhinav (Abhinav) wrote: > > > > > Hi All, > > > > > > > > > > I am trying to setup the Yocto Eclipse Plugin for Eclipse (Luna > > release). I am able to install the Juno release plugin for 1.7.1 > > release. But while configuring it I am facing issues as below > > > > > > > > > 1. When I try to provide BitBake directory as part of tool chain I > > get an error that need to build meta-ide-support before configuring > > it. > > > > > As I did build meta-ide-support before setting up the path as I can > > see an environment file present under /tmp > > path. > > > > > > > > You will need to provide the path to the build directory. This is the > > > > directory holding tmp. > > > > > > > > > 2. If I select Standard SDK option then it accepts the same i.e. it > > accept environment file present under tmp directory as vaild which I > > suppose it should not do. > > > > > 3. I already has Makefile based project which I am trying to > > configure in eclipse by selecting Yocto as Toolchain. > > > > > But when I try to build it I am seeing its using platform GCC > > instead of Yocto tool chain. > > > > > > > > Selecting the correct directory should set up the cross-compiler > > > > environment and fix this. > > > > > > > > > > How to fix the same as I cant change this project to an CMake based > > project. > > > > > > > > > > Is there as way I can use Kepler plugin instead of Juno as when I > > try the same with Luna I am getting dependencies errors. > > > > > > > > You can find the plugin releases here: > > > > https://urldefense.proofpoint.com/v2/url?u=http-3A__downloads.yoctoproject.org_releases_eclipse-2Dplugin_&d=AwIFaQ&c=BFpWQw8bsuKpl1SgiZH64Q&r=geJ1wB7xRIMmteYB2Fo8esL32BOWvwP1HmY0YuLEB4E&m=Hg_RatI-pPFNhlwlj3rvSiP3RspGPYNzHRBg-XaXN1U&s=11DZqLCED8UtaM9vU0YxGMeaNWGlerPzTawEoVwuJd4&e= > > > > > > > > > > Cheers, > > > > Todor > > > > > > > > > smime.p7s Description: S/MIME cryptographic signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Eclipse build of existing cmake project
Hello Ruben, > > What I did: > I built an image and support for eclipse (meta-ide-support) for beagle > bone black (BBB). > I am able to create a new project in eclipse and build and run this > new project on my hardware. > > > I have an existing CMAKE project which should run on BBB. > I know how to write an recipe for my project and build this existing > project with bitbake. > > > What I want to do: > I want to build my existing cmake project with eclipse. Is there any > possibility to import existing cmake projects to eclipse and do a > build using yocto toolchain? > The easiest way to do this is to create a "Hello World C CMake Project" with the template provided by the Yocto plugin and import your source and CMakeLists.txt file in place of the default main.c and CMakeLists.txt. Regards, Todor > -- > Ruben Schwarz | SOTEC | r.schw...@sotec.eu | T +49 7033 5458 34 | F > +49 7033 5458 95 > > www.sotec.eu | www.cloudwuerdig.com > -- > SOTEC Software Entwicklungs GmbH + Co Mikrocomputertechnik KG > Calwer Straße 11, D-75395 Ostelsheim > Sitz Ostelsheim, Amtsgericht Stuttgart HRA 330821/HRB 330664, > Geschäftsführer: Florian Holz > Cloudwürdig® ist eine eingetragene Marke der SOTEC Software > Entwicklungs GmbH + Co Mikrocomputertechnik KG > > Der Inhalt dieser e-Mail ist ausschließlich für den bezeichneten > Adressaten bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser > e-Mail oder dessen Vertreter sein sollten, so beachten Sie bitte, dass > jede Form der Kenntnisnahme, Veröffentlichung, Vervielfältigung oder > Weitergabe des Inhalts dieser e-Mail unzulässig ist. Wir bitten Sie, > sich in diesem Fall mit dem Absender der e-Mail in Verbindung zu > setzen. > > The content of this e-mail is meant exclusively for the person to whom > it is addressed. If you are not the person to whom this e-mail is > addressed or his/her representative, please be informed, that any form > of knowledge, publication, duplication or distribution of the content > of this e-mail is inadmissible. We ask you, therefore, in such a case > to please contact the sender of this e-mail. > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto smime.p7s Description: S/MIME cryptographic signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Compilation error in yocto eclipse
Hello Raghavendra, On Wed, 2015-05-13 at 10:34 +, Raghavendra Kakarla wrote: > Hi, > > > I have some some issue with compiling the example source code in yocto > eclipse environment. > Which sample did you try to compile? > > I got following error: > > > 12:48:03 Build of configuration Build (GNU) for project example > > make all > make: *** No rule to make target `all'. Stop. > > > I built generated the tool chain and sysroot from my build system > using bitbake command. Could you please provide a bit more details about how you built your toolchain. And also how did you configure the Yocto Eclipse plug-in. > > > Could please help me in resolving this issue. Cheers, Todor > > > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto smime.p7s Description: S/MIME cryptographic signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Issue with yocto ADT
Hello Raghavendra, Please try the following: Right click on your project - Properties - C/C++ Build - Select the 'Behavior' tab - untick 'Build on resource save' and remove 'all' from the 'Build' field Cheers, Todor On Fri, 2015-05-15 at 09:32 +, Raghavendra Kakarla wrote: > Hi All, > > > I have problem with the ADT while i am building the autotool example > helloword project which is given in the "yocto ADT autotool project". > > > Could you please help me in resolving this issue. > > > I followed the following steps for installing the adt in my > development PC: > > > > I built the toolchain using the following command: > > $cd ~/poky > $source ./oe-init-build-env > $bitbake meta-ide-support > > > Extract the root file system by using the following commands: > > $cd ~ > $source ~/poky/build/tmp/environment-setup-mips32r2el-poky-linux > $runqemu-extract-sdk \ > ~/poky/build/tmp/deploy/images/arqlyn/ > core-image-minimal-dhruwa_ioe-20150511102759.rootfs.tar.bz2\ > $HOME/arqlyn > > I followed the command given in the yocto project dev-manual for > installing eclipse and adding yocto plugin to eclipse. > > I Gave the following data to the eclipse for configuring the > cross-compiler options: > > 1. I select the "Build System Derived Toolchain" > 2.point the toolchain path to "home/testuser/poky/build" > 3.gave sysroot path to /home/testuser/arqlyn > > After entered this information I got the my machine-name in the > "select the target architecture" filed. > > After this I create a autotool support project and tried to build but > it gives the error. > > Regards, > > Raghavendra. > > > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto smime.p7s Description: S/MIME cryptographic signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Issue with yocto ADT
Hello Raghavendra, Could you please pastebin the makefile from your project? http://pastebin.com/ Cheers, Todor On Fri, 2015-05-15 at 10:47 +, Raghavendra Kakarla wrote: > Hi Todor, > > Thank you for your reply. > > By default we have the setting like this only. > > But we got the error. > > Thanks, > Raghavendra. > ________ > From: Minchev, Todor > Sent: Friday, May 15, 2015 4:05 PM > To: Raghavendra Kakarla > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] Issue with yocto ADT > > Hello Raghavendra, > > Please try the following: > > Right click on your project - Properties - C/C++ Build - Select the > 'Behavior' tab - untick 'Build on resource save' and remove 'all' from > the 'Build' field > > Cheers, > Todor > > On Fri, 2015-05-15 at 09:32 +, Raghavendra Kakarla wrote: > > Hi All, > > > > > > I have problem with the ADT while i am building the autotool example > > helloword project which is given in the "yocto ADT autotool project". > > > > > > Could you please help me in resolving this issue. > > > > > > I followed the following steps for installing the adt in my > > development PC: > > > > > > > > I built the toolchain using the following command: > > > > $cd ~/poky > > $source ./oe-init-build-env > > $bitbake meta-ide-support > > > > > > Extract the root file system by using the following commands: > > > > $cd ~ > > $source ~/poky/build/tmp/environment-setup-mips32r2el-poky-linux > > $runqemu-extract-sdk \ > > ~/poky/build/tmp/deploy/images/arqlyn/ > > core-image-minimal-dhruwa_ioe-20150511102759.rootfs.tar.bz2\ > > $HOME/arqlyn > > > > I followed the command given in the yocto project dev-manual for > > installing eclipse and adding yocto plugin to eclipse. > > > > I Gave the following data to the eclipse for configuring the > > cross-compiler options: > > > > 1. I select the "Build System Derived Toolchain" > > 2.point the toolchain path to "home/testuser/poky/build" > > 3.gave sysroot path to /home/testuser/arqlyn > > > > After entered this information I got the my machine-name in the > > "select the target architecture" filed. > > > > After this I create a autotool support project and tried to build but > > it gives the error. > > > > Regards, > > > > Raghavendra. > > > > > > > > -- > > ___ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > smime.p7s Description: S/MIME cryptographic signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Issue with yocto ADT
On Fri, 2015-05-15 at 11:33 +, Raghavendra Kakarla wrote: > Hi Todor, > > It is an autotool based example. > It is not generated makefile itself. > Is it an example you created yourself or is it the autotools C Hello World template provided by the Yocto Eclipse Plug-in. > I attached the makefile.in and makefile.am file to the paste bin. Could you please paste the Makefile and share the pastebin link? > Thanks, > > Raghavendra. > > > ________ > From: Minchev, Todor > Sent: Friday, May 15, 2015 4:41 PM > To: Raghavendra Kakarla > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] Issue with yocto ADT > > Hello Raghavendra, > > Could you please pastebin the makefile from your project? > > http://pastebin.com/ > > Cheers, > Todor > > On Fri, 2015-05-15 at 10:47 +, Raghavendra Kakarla wrote: > > Hi Todor, > > > > Thank you for your reply. > > > > By default we have the setting like this only. > > > > But we got the error. > > > > Thanks, > > Raghavendra. > > > > From: Minchev, Todor > > Sent: Friday, May 15, 2015 4:05 PM > > To: Raghavendra Kakarla > > Cc: yocto@yoctoproject.org > > Subject: Re: [yocto] Issue with yocto ADT > > > > Hello Raghavendra, > > > > Please try the following: > > > > Right click on your project - Properties - C/C++ Build - Select the > > 'Behavior' tab - untick 'Build on resource save' and remove 'all' from > > the 'Build' field > > > > Cheers, > > Todor > > > > On Fri, 2015-05-15 at 09:32 +, Raghavendra Kakarla wrote: > > > Hi All, > > > > > > > > > I have problem with the ADT while i am building the autotool example > > > helloword project which is given in the "yocto ADT autotool project". > > > > > > > > > Could you please help me in resolving this issue. > > > > > > > > > I followed the following steps for installing the adt in my > > > development PC: > > > > > > > > > > > > I built the toolchain using the following command: > > > > > > $cd ~/poky > > > $source ./oe-init-build-env > > > $bitbake meta-ide-support > > > > > > > > > Extract the root file system by using the following commands: > > > > > > $cd ~ > > > $source ~/poky/build/tmp/environment-setup-mips32r2el-poky-linux > > > $runqemu-extract-sdk \ > > > ~/poky/build/tmp/deploy/images/arqlyn/ > > > core-image-minimal-dhruwa_ioe-20150511102759.rootfs.tar.bz2\ > > > $HOME/arqlyn > > > > > > I followed the command given in the yocto project dev-manual for > > > installing eclipse and adding yocto plugin to eclipse. > > > > > > I Gave the following data to the eclipse for configuring the > > > cross-compiler options: > > > > > > 1. I select the "Build System Derived Toolchain" > > > 2.point the toolchain path to "home/testuser/poky/build" > > > 3.gave sysroot path to /home/testuser/arqlyn > > > > > > After entered this information I got the my machine-name in the > > > "select the target architecture" filed. > > > > > > After this I create a autotool support project and tried to build but > > > it gives the error. > > > > > > Regards, > > > > > > Raghavendra. > > > > > > > > > > > > -- > > > ___ > > > yocto mailing list > > > yocto@yoctoproject.org > > > https://lists.yoctoproject.org/listinfo/yocto > > > smime.p7s Description: S/MIME cryptographic signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Issue with yocto ADT
Hello Raghavendra, On Mon, 2015-05-18 at 05:07 +, Raghavendra Kakarla wrote: > Hi Todor, > > Could you please let me know the cause for the issue. Please pastebin your Makefile and share the pastebin link. Seem like your project is corrupt and the Makefile is not generated correctly. Have you tried to delete the project and create a new one? > Thanks in advance. > > Regards, > Raghavendra K. > > > > From: Raghavendra Kakarla > Sent: Friday, May 15, 2015 5:31 PM > To: Minchev, Todor > Cc: yocto@yoctoproject.org > Subject: RE: [yocto] Issue with yocto ADT > > Hi Todor, > > It is provided by the Yocto eclipse plugin itself. > > Regards, > Raghavendra. > > From: Minchev, Todor > Sent: Friday, May 15, 2015 5:27 PM > To: Raghavendra Kakarla > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] Issue with yocto ADT > > On Fri, 2015-05-15 at 11:33 +, Raghavendra Kakarla wrote: > > Hi Todor, > > > > It is an autotool based example. > > It is not generated makefile itself. > > > > Is it an example you created yourself or is it the autotools C Hello > World template provided by the Yocto Eclipse Plug-in. > > > I attached the makefile.in and makefile.am file to the paste bin. > > Could you please paste the Makefile and share the pastebin link? > > > Thanks, > > > > Raghavendra. > > > > > > > > From: Minchev, Todor > > Sent: Friday, May 15, 2015 4:41 PM > > To: Raghavendra Kakarla > > Cc: yocto@yoctoproject.org > > Subject: Re: [yocto] Issue with yocto ADT > > > > Hello Raghavendra, > > > > Could you please pastebin the makefile from your project? > > > > http://pastebin.com/ > > > > Cheers, > > Todor > > > > On Fri, 2015-05-15 at 10:47 +, Raghavendra Kakarla wrote: > > > Hi Todor, > > > > > > Thank you for your reply. > > > > > > By default we have the setting like this only. > > > > > > But we got the error. > > > > > > Thanks, > > > Raghavendra. > > > > > > From: Minchev, Todor > > > Sent: Friday, May 15, 2015 4:05 PM > > > To: Raghavendra Kakarla > > > Cc: yocto@yoctoproject.org > > > Subject: Re: [yocto] Issue with yocto ADT > > > > > > Hello Raghavendra, > > > > > > Please try the following: > > > > > > Right click on your project - Properties - C/C++ Build - Select the > > > 'Behavior' tab - untick 'Build on resource save' and remove 'all' from > > > the 'Build' field > > > > > > Cheers, > > > Todor > > > > > > On Fri, 2015-05-15 at 09:32 +, Raghavendra Kakarla wrote: > > > > Hi All, > > > > > > > > > > > > I have problem with the ADT while i am building the autotool example > > > > helloword project which is given in the "yocto ADT autotool project". > > > > > > > > > > > > Could you please help me in resolving this issue. > > > > > > > > > > > > I followed the following steps for installing the adt in my > > > > development PC: > > > > > > > > > > > > > > > > I built the toolchain using the following command: > > > > > > > > $cd ~/poky > > > > $source ./oe-init-build-env > > > > $bitbake meta-ide-support > > > > > > > > > > > > Extract the root file system by using the following commands: > > > > > > > > $cd ~ > > > > $source ~/poky/build/tmp/environment-setup-mips32r2el-poky-linux > > > > $runqemu-extract-sdk \ > > > > ~/poky/build/tmp/deploy/images/arqlyn/ > > > > core-image-minimal-dhruwa_ioe-20150511102759.rootfs.tar.bz2\ > > > > $HOME/arqlyn > > > > > > > > I followed the command given in the yocto project dev-manual for > > > > installing eclipse and adding yocto plugin to eclipse. > > > > > > > > I Gave the following data to the eclipse for configuring the > > > > cross-compiler options: > > > > > > > > 1. I select the "Build System Derived Toolchain" > > > > 2.point the toolchain path to "home/testuser/poky/build" > > > > 3.gave sysroot path to /home/testuser/arqlyn > > > > > > > > After entered this information I got the my machine-name in the > > > > "select the target architecture" filed. > > > > > > > > After this I create a autotool support project and tried to build but > > > > it gives the error. > > > > > > > > Regards, > > > > > > > > Raghavendra. > > > > > > > > > > > > > > > > -- > > > > ___ > > > > yocto mailing list > > > > yocto@yoctoproject.org > > > > https://lists.yoctoproject.org/listinfo/yocto > > > > > > smime.p7s Description: S/MIME cryptographic signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Issue with yocto ADT
On Mon, 2015-05-18 at 16:55 +, Raghavendra Kakarla wrote: > Hi Todor, > > I created four more new projects. > > For all the projects I gives error like this only. Is the error message the same as the original one you posted about a missing make `all` target? > Can send those projects make files? Please share both your working and non-working Makefiles. > > But when I give the sysroot path in eclipse to the > poky/build/tmp/sysroot/machine it worked properly. > > When we give the extracted sysroot it gives problem. > Regards, > Raghavendra. > ____________ > From: Minchev, Todor [todor.minc...@intel.com] > Sent: Monday, May 18, 2015 9:51 PM > To: Raghavendra Kakarla > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] Issue with yocto ADT > > Hello Raghavendra, > > On Mon, 2015-05-18 at 05:07 +, Raghavendra Kakarla wrote: > > Hi Todor, > > > > Could you please let me know the cause for the issue. > Please pastebin your Makefile and share the pastebin link. > > Seem like your project is corrupt and the Makefile is not generated > correctly. > > Have you tried to delete the project and create a new one? > > > Thanks in advance. > > > > Regards, > > Raghavendra K. > > > > > > > > From: Raghavendra Kakarla > > Sent: Friday, May 15, 2015 5:31 PM > > To: Minchev, Todor > > Cc: yocto@yoctoproject.org > > Subject: RE: [yocto] Issue with yocto ADT > > > > Hi Todor, > > > > It is provided by the Yocto eclipse plugin itself. > > > > Regards, > > Raghavendra. > > > > From: Minchev, Todor > > Sent: Friday, May 15, 2015 5:27 PM > > To: Raghavendra Kakarla > > Cc: yocto@yoctoproject.org > > Subject: Re: [yocto] Issue with yocto ADT > > > > On Fri, 2015-05-15 at 11:33 +, Raghavendra Kakarla wrote: > > > Hi Todor, > > > > > > It is an autotool based example. > > > It is not generated makefile itself. > > > > > > > Is it an example you created yourself or is it the autotools C Hello > > World template provided by the Yocto Eclipse Plug-in. > > > > > I attached the makefile.in and makefile.am file to the paste bin. > > > > Could you please paste the Makefile and share the pastebin link? > > > > > Thanks, > > > > > > Raghavendra. > > > > > > > > > > > > From: Minchev, Todor > > > Sent: Friday, May 15, 2015 4:41 PM > > > To: Raghavendra Kakarla > > > Cc: yocto@yoctoproject.org > > > Subject: Re: [yocto] Issue with yocto ADT > > > > > > Hello Raghavendra, > > > > > > Could you please pastebin the makefile from your project? > > > > > > http://pastebin.com/ > > > > > > Cheers, > > > Todor > > > > > > On Fri, 2015-05-15 at 10:47 +, Raghavendra Kakarla wrote: > > > > Hi Todor, > > > > > > > > Thank you for your reply. > > > > > > > > By default we have the setting like this only. > > > > > > > > But we got the error. > > > > > > > > Thanks, > > > > Raghavendra. > > > > > > > > From: Minchev, Todor > > > > Sent: Friday, May 15, 2015 4:05 PM > > > > To: Raghavendra Kakarla > > > > Cc: yocto@yoctoproject.org > > > > Subject: Re: [yocto] Issue with yocto ADT > > > > > > > > Hello Raghavendra, > > > > > > > > Please try the following: > > > > > > > > Right click on your project - Properties - C/C++ Build - Select the > > > > 'Behavior' tab - untick 'Build on resource save' and remove 'all' from > > > > the 'Build' field > > > > > > > > Cheers, > > > > Todor > > > > > > > > On Fri, 2015-05-15 at 09:32 +, Raghavendra Kakarla wrote: > > > > > Hi All, > > > > > > > > > > > > > > > I have problem with the ADT while i am building the autotool example > > > > > helloword project which is given in the "yocto ADT autotool project". > > > > > > > > > > > > > > > Could you please help me in resolving this issue. > > > > > > > > > >
Re: [yocto] Issue with yocto ADT
On Tue, 2015-05-19 at 07:07 +, Raghavendra Kakarla wrote: > Hi Todor, > > For not working scenario there is no makefile created. > > For working scenario using build directory sysroot makefiles are created. So configure fails to create your Makefile. You probably see something like this in your config.log: configure: error: C compiler cannot create executables configure: error: C compiler cannot create executables See `config.log' for more details Please have a look at this thread, it explains how to resolve this problem: https://lists.yoctoproject.org/pipermail/yocto/2015-March/024089.html Cheers, Todor > > I attaching the makefile for working scenario. > > Regards, > > Raghavendra K. > ________ > From: Minchev, Todor > Sent: Tuesday, May 19, 2015 12:13 PM > To: Raghavendra Kakarla > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] Issue with yocto ADT > > On Mon, 2015-05-18 at 16:55 +, Raghavendra Kakarla wrote: > > Hi Todor, > > > > I created four more new projects. > > > > For all the projects I gives error like this only. > > Is the error message the same as the original one you posted about a > missing make `all` target? > > > Can send those projects make files? > > Please share both your working and non-working Makefiles. > > > > > But when I give the sysroot path in eclipse to the > > poky/build/tmp/sysroot/machine it worked properly. > > > > When we give the extracted sysroot it gives problem. > > Regards, > > Raghavendra. > > > > From: Minchev, Todor [todor.minc...@intel.com] > > Sent: Monday, May 18, 2015 9:51 PM > > To: Raghavendra Kakarla > > Cc: yocto@yoctoproject.org > > Subject: Re: [yocto] Issue with yocto ADT > > > > Hello Raghavendra, > > > > On Mon, 2015-05-18 at 05:07 +, Raghavendra Kakarla wrote: > > > Hi Todor, > > > > > > Could you please let me know the cause for the issue. > > Please pastebin your Makefile and share the pastebin link. > > > > Seem like your project is corrupt and the Makefile is not generated > > correctly. > > > > Have you tried to delete the project and create a new one? > > > > > Thanks in advance. > > > > > > Regards, > > > Raghavendra K. > > > > > > > > > > > > From: Raghavendra Kakarla > > > Sent: Friday, May 15, 2015 5:31 PM > > > To: Minchev, Todor > > > Cc: yocto@yoctoproject.org > > > Subject: RE: [yocto] Issue with yocto ADT > > > > > > Hi Todor, > > > > > > It is provided by the Yocto eclipse plugin itself. > > > > > > Regards, > > > Raghavendra. > > > > > > From: Minchev, Todor > > > Sent: Friday, May 15, 2015 5:27 PM > > > To: Raghavendra Kakarla > > > Cc: yocto@yoctoproject.org > > > Subject: Re: [yocto] Issue with yocto ADT > > > > > > On Fri, 2015-05-15 at 11:33 +, Raghavendra Kakarla wrote: > > > > Hi Todor, > > > > > > > > It is an autotool based example. > > > > It is not generated makefile itself. > > > > > > > > > > Is it an example you created yourself or is it the autotools C Hello > > > World template provided by the Yocto Eclipse Plug-in. > > > > > > > I attached the makefile.in and makefile.am file to the paste bin. > > > > > > Could you please paste the Makefile and share the pastebin link? > > > > > > > Thanks, > > > > > > > > Raghavendra. > > > > > > > > > > > > > > > > From: Minchev, Todor > > > > Sent: Friday, May 15, 2015 4:41 PM > > > > To: Raghavendra Kakarla > > > > Cc: yocto@yoctoproject.org > > > > Subject: Re: [yocto] Issue with yocto ADT > > > > > > > > Hello Raghavendra, > > > > > > > > Could you please pastebin the makefile from your project? > > > > > > > > http://pastebin.com/ > > > > > > > > Cheers, > > > > Todor > > > > > > > > On Fri, 2015-05-15 at 10:47 +, Raghavendra Kakarla wrote: > > > > > Hi Todor, > > > > > > > > > > Thank you for your reply. > > > > > > > > > > By defaul
Re: [yocto] Issue with yocto ADT
On Tue, 2015-05-19 at 09:49 +, Raghavendra Kakarla wrote: > Hi Todor, > > Thank you for your reply. > > Now I am able to build the application with my extracted rootfs. > > I built the rootfs for our machine. > > for launching the qemu from the eclipse,is it required we should build it for > qemu? > I have the previously built qemu kernel image and i give it path to the > eclipse's qemu kernel path field. > > Qemu is launched but it gives error while switching from kernel to rootfs i.e > init script execution problem. If your rootfs does not have /sbin/init, your kernel won't be able to execute the topmost parent process(init) and the boot will fail? What is the error message? > > Regards, > Raghavendra. > > From: Minchev, Todor > Sent: Tuesday, May 19, 2015 1:14 PM > To: Raghavendra Kakarla > Cc: Surya Dommeti; Ramakrishna Chatram; yocto@yoctoproject.org > Subject: Re: [yocto] Issue with yocto ADT > > On Tue, 2015-05-19 at 07:07 +, Raghavendra Kakarla wrote: > > Hi Todor, > > > > For not working scenario there is no makefile created. > > > > For working scenario using build directory sysroot makefiles are created. > > So configure fails to create your Makefile. You probably see something > like this in your config.log: > > configure: error: C compiler cannot create executables > configure: error: C compiler cannot create executables > See `config.log' for more details > > Please have a look at this thread, it explains how to resolve this > problem: > > https://lists.yoctoproject.org/pipermail/yocto/2015-March/024089.html > > Cheers, > Todor > > > > > I attaching the makefile for working scenario. > > > > Regards, > > > > Raghavendra K. > > > > From: Minchev, Todor > > Sent: Tuesday, May 19, 2015 12:13 PM > > To: Raghavendra Kakarla > > Cc: yocto@yoctoproject.org > > Subject: Re: [yocto] Issue with yocto ADT > > > > On Mon, 2015-05-18 at 16:55 +, Raghavendra Kakarla wrote: > > > Hi Todor, > > > > > > I created four more new projects. > > > > > > For all the projects I gives error like this only. > > > > Is the error message the same as the original one you posted about a > > missing make `all` target? > > > > > Can send those projects make files? > > > > Please share both your working and non-working Makefiles. > > > > > > > > But when I give the sysroot path in eclipse to the > > > poky/build/tmp/sysroot/machine it worked properly. > > > > > > When we give the extracted sysroot it gives problem. > > > Regards, > > > Raghavendra. > > > > > > From: Minchev, Todor [todor.minc...@intel.com] > > > Sent: Monday, May 18, 2015 9:51 PM > > > To: Raghavendra Kakarla > > > Cc: yocto@yoctoproject.org > > > Subject: Re: [yocto] Issue with yocto ADT > > > > > > Hello Raghavendra, > > > > > > On Mon, 2015-05-18 at 05:07 +, Raghavendra Kakarla wrote: > > > > Hi Todor, > > > > > > > > Could you please let me know the cause for the issue. > > > Please pastebin your Makefile and share the pastebin link. > > > > > > Seem like your project is corrupt and the Makefile is not generated > > > correctly. > > > > > > Have you tried to delete the project and create a new one? > > > > > > > Thanks in advance. > > > > > > > > Regards, > > > > Raghavendra K. > > > > > > > > > > > > > > > > From: Raghavendra Kakarla > > > > Sent: Friday, May 15, 2015 5:31 PM > > > > To: Minchev, Todor > > > > Cc: yocto@yoctoproject.org > > > > Subject: RE: [yocto] Issue with yocto ADT > > > > > > > > Hi Todor, > > > > > > > > It is provided by the Yocto eclipse plugin itself. > > > > > > > > Regards, > > > > Raghavendra. > > > > > > > > From: Minchev, Todor > > > > Sent: Friday, May 15, 2015 5:27 PM > > > > To: Raghavendra Kakarla > > > > Cc: yocto@yoctoproject.org > > > > Subject: Re: [yocto] Issue with yocto ADT > > > > > > > > On Fri, 2015-05-15 at 11:33 +, Raghavendra Kakarla wrote: &
Re: [yocto] Issue with yocto ADT
On Tue, 2015-05-19 at 12:03 +, Raghavendra Kakarla wrote: > Hi Todor, > sbin/init script is there in the rootfile system. > > But i built rootfile system for my BSP and I give this rootfs to the eclipse > sysroot path. > > And i select the qemu instead of externel hardware. I give the qemu kernel > path to prevuiously built qemumips kernel image which is built before my BSP > is built. > > When I click on the "external Tool -> qemu_mips-poky-linux" qemu image is > booted and gives the following error. > ->sbin/init exist but could not execute it > This error message should be followed by an error number. Also check that your /sbin/init is executable. > Regards, > Raghavenmdra K. > > From: Minchev, Todor > Sent: Tuesday, May 19, 2015 5:01 PM > To: Raghavendra Kakarla > Cc: Surya Dommeti; Ramakrishna Chatram; yocto@yoctoproject.org > Subject: Re: [yocto] Issue with yocto ADT > > On Tue, 2015-05-19 at 09:49 +, Raghavendra Kakarla wrote: > > Hi Todor, > > > > Thank you for your reply. > > > > Now I am able to build the application with my extracted rootfs. > > > > I built the rootfs for our machine. > > > > for launching the qemu from the eclipse,is it required we should build it > > for qemu? > > I have the previously built qemu kernel image and i give it path to the > > eclipse's qemu kernel path field. > > > > Qemu is launched but it gives error while switching from kernel to rootfs > > i.e init script execution problem. > > If your rootfs does not have /sbin/init, your kernel won't be able to > execute the topmost parent process(init) and the boot will fail? What is > the error message? > > > > > Regards, > > Raghavendra. > > > > From: Minchev, Todor > > Sent: Tuesday, May 19, 2015 1:14 PM > > To: Raghavendra Kakarla > > Cc: Surya Dommeti; Ramakrishna Chatram; yocto@yoctoproject.org > > Subject: Re: [yocto] Issue with yocto ADT > > > > On Tue, 2015-05-19 at 07:07 +, Raghavendra Kakarla wrote: > > > Hi Todor, > > > > > > For not working scenario there is no makefile created. > > > > > > For working scenario using build directory sysroot makefiles are created. > > > > So configure fails to create your Makefile. You probably see something > > like this in your config.log: > > > > configure: error: C compiler cannot create executables > > configure: error: C compiler cannot create executables > > See `config.log' for more details > > > > Please have a look at this thread, it explains how to resolve this > > problem: > > > > https://lists.yoctoproject.org/pipermail/yocto/2015-March/024089.html > > > > Cheers, > > Todor > > > > > > > > I attaching the makefile for working scenario. > > > > > > Regards, > > > > > > Raghavendra K. > > > > > > From: Minchev, Todor > > > Sent: Tuesday, May 19, 2015 12:13 PM > > > To: Raghavendra Kakarla > > > Cc: yocto@yoctoproject.org > > > Subject: Re: [yocto] Issue with yocto ADT > > > > > > On Mon, 2015-05-18 at 16:55 +, Raghavendra Kakarla wrote: > > > > Hi Todor, > > > > > > > > I created four more new projects. > > > > > > > > For all the projects I gives error like this only. > > > > > > Is the error message the same as the original one you posted about a > > > missing make `all` target? > > > > > > > Can send those projects make files? > > > > > > Please share both your working and non-working Makefiles. > > > > > > > > > > > But when I give the sysroot path in eclipse to the > > > > poky/build/tmp/sysroot/machine it worked properly. > > > > > > > > When we give the extracted sysroot it gives problem. > > > > Regards, > > > > Raghavendra. > > > > > > > > From: Minchev, Todor [todor.minc...@intel.com] > > > > Sent: Monday, May 18, 2015 9:51 PM > > > > To: Raghavendra Kakarla > > > > Cc: yocto@yoctoproject.org > > > > Subject: Re: [yocto] Issue with yocto ADT > > > > > > > > Hello Raghavendra, > > > > > > > > On Mon, 2015-05-18 at 05:07 +, Raghavendra Kakarla wrote: > > > > > Hi Todor, >
[yocto] merging eclipse-poky-juno & eclipse-poky-kepler
Hello, I just wanted to check if anyone is using the Yocto ADT Eclipse plug-in from the eclipse-poky repo here: http://git.yoctoproject.org/cgit/cgit.cgi/eclipse-poky/ This repo hasn't been maintained for a couple of years. The most up-to-date code for the ADT plug-ins for Eclipse Juno & Kepler can be found in these two repos. http://git.yoctoproject.org/cgit/cgit.cgi/eclipse-poky-juno/ http://git.yoctoproject.org/cgit/cgit.cgi/eclipse-poky-kepler/ We have decided to merge the two repos above and maintain the plug-in under the original eclipse-poky repo for all versions of Eclipse. In other words, we are planning to overwrite eclipse-poky with the merge result from eclipse-poky-juno and eclipse-poky-kepler. I am planning to do this on Friday, 27 Feb 2015. If anyone has any objections please let me know before then. Thanks, Todor smime.p7s Description: S/MIME cryptographic signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] merging eclipse-poky-juno & eclipse-poky-kepler
On Wed, 2015-02-25 at 14:17 +, Flanagan, Elizabeth wrote: > On 25 February 2015 at 13:12, Minchev, Todor wrote: > > Hello, > > > > I just wanted to check if anyone is using the Yocto ADT Eclipse plug-in > > from the eclipse-poky repo here: > > > > http://git.yoctoproject.org/cgit/cgit.cgi/eclipse-poky/ > > > > This repo hasn't been maintained for a couple of years. The most > > up-to-date code for the ADT plug-ins for Eclipse Juno & Kepler can be > > found in these two repos. > > > > http://git.yoctoproject.org/cgit/cgit.cgi/eclipse-poky-juno/ > > http://git.yoctoproject.org/cgit/cgit.cgi/eclipse-poky-kepler/ > > > > We have decided to merge the two repos above and maintain the plug-in > > under the original eclipse-poky repo for all versions of Eclipse. > > In other words, we are planning to overwrite eclipse-poky with the merge > > result from eclipse-poky-juno and eclipse-poky-kepler. > > > > I am planning to do this on Friday, 27 Feb 2015. If anyone has any > > objections please let me know before then. > > > > My only concern is that we: > > - maintain history All history is preserved. > - get autobuilder changes in when the merge is done > > If you could explain the eventual layout of the new merged repo, that > would be grand. All branches and tags from the eclipse-poky-kepler and eclipse-poky-juno repositories will be reachable with the same branch/tag names and the kepler or juno prefix respectively. The development(master) branches for juno, kepler and luna are: juno-master kepler-master luna-master master - tracks the master branch for the latest supported Eclipse release (luna-master at present) This is the repo structure after the merge: Branches juno-master juno/1.1_M1 juno/1.1_M2 juno/1.1_M4 juno/1.2_M1 juno/1.2_M2 juno/1.2_M3 juno/1.2_M4 juno/1.3_M1 juno/1.3_M2 juno/1.3_M3 juno/1.3_M4 juno/1.3_M5 juno/1.3_beta juno/1.4_M1 juno/1.4_M3 juno/1.4_M4 juno/1.4_M5 juno/daisy juno/danny juno/denzil juno/dizzy juno/dora juno/dylan juno/edison kepler-master kepler/daisy kepler/dizzy kepler/dora * luna-master master Tags juno/1.1_M1.rc1 juno/1.1_M1.rc2 juno/1.1_M2.final juno/1.1_M2.rc1 juno/1.1_M2.rc3 juno/1.1_M3.final juno/1.1_M3.rc3 juno/1.1_M4.rc2+ juno/1.1_M4.rc4 juno/1.2_M1.final juno/1.2_M1.rc1 juno/1.2_M1.rc2 juno/1.2_M2.final juno/1.2_M2.rc1 juno/1.2_M3.final juno/1.2_M3.rc1 juno/1.2_M4.rc1 juno/1.2_M4.rc4 juno/1.2_M4.rc4.0 juno/1.3 juno/1.3.2 juno/1.3.2.final juno/1.3_M1.final juno/1.3_M2.final juno/1.3_M2.rc1 juno/1.3_M3.final juno/1.3_M3.rc2 juno/1.3_M4.final juno/1.3_M4.rc1 juno/1.3_M5.rc1 juno/1.3_M5.rc2 juno/1.3_M5.rc3 juno/1.3_M5.rc4 juno/1.4.1.rc1 juno/1.4_M1.final juno/1.4_M1.rc1 juno/1.4_M3.final juno/1.4_M3.rc1 juno/1.4_M3.rc2 juno/1.4_M4.final juno/1.4_M4.rc1 juno/1.4_M5.final juno/1.4_M5.rc1 juno/1.4_M5.rc2 juno/1.4_M5.rc3 juno/1.4_M6.rc1 juno/1.5_M1.final juno/1.5_M1.rc1 juno/1.5_M2.rc1 juno/1.5_M3 juno/1.5_M3.final juno/1.5_M3.rc1 juno/1.5_M4 juno/1.5_M4.final juno/1.5_M4.rc1 juno/1.5_M4.rc2 juno/1.5_M4.rc3 juno/1.5_M5.rc1 juno/1.5_M5.rc2 juno/1.5_M5.rc3 juno/1.5_M5.rc4 juno/1.5_M5.rc5 juno/1.5_M5.rc6 juno/1.5_M5.rc7 juno/1.5_M5.rc8 juno/1.6_M1 juno/1.6_M1.final juno/1.6_M1.rc1 juno/1.6_M2 juno/1.6_M3 juno/1.6_M3.final juno/1.6_M4 juno/bernard-5.0 juno/daisy-11.0.0 juno/daisy-11.0.1 juno/daisy-11.0.2 juno/danny-8.0.1 juno/danny-8.0.2 juno/denzil-7.0 juno/denzil-7.0.0 juno/denzil-7.0.1 juno/denzil-7.0.1_rc2 juno/denzil-7.0.2 juno/dizzy-12.0.0 juno/dizzy-12.0.1 juno/dora-10.0.0 juno/dora-10.0.1 juno/dora-10.0.1.final juno/dora-10.0.2 juno/dora-10.0.3 juno/dora-10.0.4 juno/dylan-9.0.0 juno/dylan-9.0.1 juno/dylan-9.0.1.rc1 juno/dylan-9.0.2 juno/dylan-9.0.2.rc1 juno/dylan-9.0.3 juno/dylan-9.0.4 juno/edison-6.0 juno/edison-6.0.1 juno/edison-6.0.1.final juno/edison-6.0.1.release juno/edison-6.0.2 juno/edison-6.0.2_rc1 juno/poky-10.0.0.final juno/poky-10.0.1 juno/poky-10.0.1.final juno/yocot-1.4.2 juno/yocto-1.4.1 juno/yocto-1.4.2 juno/yocto-1.4.2.rc1 juno/yocto-1.4.3 juno/yocto-1.4.4 juno/yocto-1.5 juno/yocto-1.5.1 juno/yocto-1.5.1.final juno/yocto-1.5.2 juno/yocto-1.5.3 juno/yocto-1.5.4 juno/yocto-1.5.final juno/yocto-1.5_M5.rc2 juno/yocto-1.6 juno/yocto-1.6.1 juno/yocto-1.6.2 juno/yocto-1.7 juno/yocto-1.7.1 juno/yocto_1.5_M5.rc8 kepler/1.5_M3 kepler/1.5_M3.final kepler/1.5_M3.rc1 kepler/1.5_M4 kepler/1.5_M4.final kepler/1.5_M4.rc1 kepler/1.5_M4.rc2 kepler/1.5_M4.rc3 kepler/1.5_M5.rc1 kepler/1.5_M5.rc2 kepler/1.5_M5.rc3 kepler/1.5_M5.rc4 kepler/1.5_M5.rc5 kepler/1.5_M5.rc6 kepler/1.5_M5.rc7 kepler/1.5_M5.rc8 kepler/1.6_M1 kepler/1.6_M1.final kepler/1.6_M1.rc1 kepler/1.6_M2 kepler/1.6_M3 kepler/1.6_M3.final kepler/1.6_M4 kepler/daisy-11.0.0 kepler/daisy-11.0.1 kepler/daisy-11.0.2 kepler/dizzy-12.0.0 kepler/dizzy-12.0.1 kepler/dora-10
[yocto] merging eclipse-poky-juno & eclipse-poky-kepler
I just wanted to check if anyone is using the Yocto ADT Eclipse plug-in from the eclipse-poky repo here: http://git.yoctoproject.org/cgit/cgit.cgi/eclipse-poky/ This repo hasn't been maintained for a couple of years. The most up-to-date code for the ADT plug-in for Eclipse Juno & Kepler can be found in these two repos. http://git.yoctoproject.org/cgit/cgit.cgi/eclipse-poky-juno/ http://git.yoctoproject.org/cgit/cgit.cgi/eclipse-poky-kepler/ We have decided to merge the two repos above and maintain the plug-in under the original eclipse-poky repo for all versions of Eclipse. In other words, we are planning to overwrite eclipse-poky with the merge result from eclipse-poky-juno and eclipse-poky-kepler. I am planning to do this on Friday, 27 Feb 2015. If anyone has any objections please let me know before then. Thanks, Todor smime.p7s Description: S/MIME cryptographic signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [ANNOUNCEMENT] Chameleonsocks 1.0 is now available
Chameleonsocks provides containerized system-wide redsocks-based TCP redirector to generic SOCKS or HTTP proxies. It is particularly useful for people who use Yocto on firewalled networks where the real Internet is accessed through proxies. The installer script can be downloaded from the upstream repository: https://github.com/crops/chameleonsocks This release includes the following functionality: --install : Install chameleonsocks --upgrade : Upgrade existing installation --uninstall: Uninstall chameleonsocks --install-ui : Install container management UI --uninstall-ui : Uninstall container management UI --start: Stop chameleonsocks --stop : Start chameleonsocks --version : Display chameleonsocks version Todor Minchev Intel Open Source Technology Center -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [RMC][PATCH v2] RMC: Support x32 build
On Thu, 2017-07-06 at 13:46 -0700, Todor Minchev wrote: > On Thu, 2017-07-06 at 13:37 -0700, Khem Raj wrote: > > On Thu, Jul 6, 2017 at 1:08 PM, Todor Minchev > > wrote: > > > On Wed, 2017-07-05 at 12:39 -0700, swee.aun.k...@intel.com wrote: > > >> From: sweeaun > > >> > > >> RMC efi is needed to compiled as 64 bits even DEFAULTTUNE is x32. > > >> > > >> Signed-off-by: sweeaun > > >> --- > > >> Makefile.efi | 3 +++ > > >> 1 file changed, 3 insertions(+) > > >> > > >> diff --git a/Makefile.efi b/Makefile.efi > > >> index 4f69dfe..95e0f8c 100644 > > >> --- a/Makefile.efi > > >> +++ b/Makefile.efi > > >> @@ -16,6 +16,9 @@ RMC_INSTALL_LIB_PATH := $(RMC_INSTALL_PREFIX)/lib/ > > >> > > >> RMC_CFLAGS := -DRMC_EFI -Wall -I$(TOPDIR)/inc -fpic -nostdinc -nostdlib > > >> -fno-builtin -std=gnu90 > > >> > > >> +#RMC efi is needed to be compiled as 64 bit even DEFAULTTUNE is x32 > > >> +CC := $(patsubst -mx32, -m64, $(CC)) > > >> + > > > > > > > does this mean package is overriding CC passed from env ? > > if yes then I think app should be fixed to respect CC if set in env > > and only set it if CC env is not set > > +1 > > The app respects both CC and CFLAGS from the env. They have to be set to > the correct values before the Makefile is called. > > > > > > Since this is not an RMC-specific problem, I believe that we shouldn't > > > patch the compiler flags in the RMC Makefile. This patch will provide > > > the desired outcome only when RMC is built with meta-intel. A better > > > alternative will be to split rmc.bb into rmc.bb (userspace app) and > > > rmc-efi.bb (efi library) and modify the compiler flags for each recipe. > > > I will send a patch that does this. This patch should fix the x32 builds. https://lists.yoctoproject.org/pipermail/meta-intel/2017-July/004818.html --Todor > > > > > >> all: librmcefi > > >> > > >> $(RMC_LIB_OBJ): %.efi.o: %.c > > > > > > > > > -- > > > ___ > > > yocto mailing list > > > yocto@yoctoproject.org > > > https://lists.yoctoproject.org/listinfo/yocto > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
