From: Gary Thomas <gary@mlbassoc.com>
To: "Zhang, Jessica" <jessica.zhang@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Eclipse plugin
Date: Tue, 23 Nov 2010 01:33:56 -0700 [thread overview]
Message-ID: <4CEB7C74.4000502@mlbassoc.com> (raw)
In-Reply-To: <9AFCD584B0B67B48AE8D8585BE30BA95133F@orsmsx504.amr.corp.intel.com>
On 11/22/10 11:43, Zhang, Jessica wrote:
> Hi Gary,
>
> I just setup my machine for ppc and create a new auto tools based c project
> and everything seems working fine for me, so if you go
> "Window->Preferecencs->Yocto SDK" in that setup window, do you see "Sysroot"
> field? If yo, somehow you're using the 1.0 plugin, but that's fine, just put
> "/home/gary/mytarget_poky/tmp/sysroots/ppc603e-poky-linux" there. And try
> to reconfigure your project which should trigger autoconfig and the compiler
> should be able to use the correct sysroot setup...
>
> Let me know whether that help or not.
I don't have a Sysroot field on that form, only a "Poky root" which is pointing
to the top of my tree, in your example "/home/gary/mytarget_poky/"
I installed the Yocto SDK 1.0.0.201010202121 from http://www.yoctoproject.org/downloads/eclipse-plugin/
> Gary Thomas wrote:
>> On 11/22/2010 08:24 AM, Gary Thomas wrote:
>>> On 11/22/2010 06:55 AM, Lu, Lianhao wrote:
>>>>
>>>> Gary Thomas wrote on 2010-11-22:
>>>>> Thanks, I installed Helios directly from the Eclipse site and
>>>>> that's working better now. I also installed the components you
>>>>> mention above.
>>>>>
>>>>> When I try to configure Yocto, I'm trying to use the Poky tree
>>>>> method but it doesn't like my tree :-( I pointed it to my build
>>>>> directory (the one which contains tmp/, sstate-cache/ and conf/)
>>>>>
>>>>> What else am I missing?
>>>>>
>>>>
>>>> You need to "bitbake meta-ide-support" before you can use the poky
>>>> tree mode.
>>>
>>> I did that and now I can move a bit farther. I managed to select my
>>> SDK type (ppc603e-poky-linux) and started with the autotools
>>> example. However, I
>>> get this error when trying to run autogen.sh:
>>>
>>>
>>> Generating Makefile in build directory:
>>> /home/gthomas/workspace/yocto_test3
>>>
>>> sh /home/gthomas/workspace/yocto_test3/configure
>>> --host=powerpc-poky-linux --build=i686-linux
>>> --target=powerpc-poky-linux checking for a BSD-compatible install...
>>> /usr/bin/install -c
>>> checking whether build environment is sane... yes
>>> checking for powerpc-poky-linux-strip... no
>>> checking for strip... strip
>>> configure: WARNING: using cross tools not prefixed with host triplet
>>> checking for a thread-safe mkdir -p... /bin/mkdir -p
>>> checking for gawk... gawk
>>> checking whether make sets $(MAKE)... yes
>>> checking build system type... i686-pc-linux-gnu
>>> checking host system type... powerpc-poky-linux-gnu
>>> checking for style of include used by make... GNU
>>> checking for powerpc-poky-linux-gcc... powerpc-poky-linux-gcc
>>> checking whether the C compiler works... no
>>> configure: error: in `/home/gthomas/workspace/yocto_test3':
>>> configure: error: C compiler cannot create executables
>>> See `config.log' for more details.
>>>
>>> Configuration failed with error
>>>
>>> It looks like there is a confusion over the SDK type and the
>>> compiler setup?
>>>
>>
>> BTW, this was on my console (hidden by the eclipse window), in
>> case it helps:
>>
>> get env key CC value powerpc-poky-linux-gcc
>> get env key CXX value powerpc-poky-linux-g++
>> get env key GDB value powerpc-poky-linux-gdb
>> get env key TARGET_PREFIX value powerpc-poky-linux-
>> get env key CONFIGURE_FLAGS value --target=powerpc-poky-linux
>> --host=powerpc-poky-linux --build=i686-linux get env key CFLAGS value
>> -mcpu=603e -mhard-float
>> get env key CXXFLAGS value -mcpu=603e -mhard-float
>> get env key POKY_NATIVE_SYSROOT value
>> /home/gary/mytarget_poky/tmp/sysroots/i686-linux
>> get env key POKY_TARGET_SYSROOT value
>> /home/gary/mytarget_poky/tmp/sysroots/ppc603e-poky-linux
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2010-11-23 8:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 9:13 Eclipse plugin Gary Thomas
2010-11-22 11:27 ` Gary Thomas
2010-11-22 12:50 ` Lu, Lianhao
2010-11-22 13:45 ` Gary Thomas
2010-11-22 13:55 ` Lu, Lianhao
2010-11-22 15:24 ` Gary Thomas
2010-11-22 15:32 ` Gary Thomas
2010-11-22 18:43 ` Zhang, Jessica
2010-11-23 8:33 ` Gary Thomas [this message]
2010-11-23 9:00 ` Lu, Lianhao
2010-11-23 21:43 ` Zhang, Jessica
2010-11-23 21:44 ` Zhang, Jessica
2010-11-24 6:47 ` Gary Thomas
-- strict thread matches above, loose matches on Subject: below --
2013-01-17 12:09 Eclipse Plugin Raul Rosetto Munoz
2013-01-17 19:22 ` Zhang, Jessica
2013-01-18 12:24 ` Flavio Castro Alves Filho
2013-01-18 12:55 ` Björn Arnelid
2013-01-18 13:10 ` Flavio Castro Alves Filho
2013-01-18 13:16 ` Björn Arnelid
2013-01-18 13:49 ` Flavio Castro Alves Filho
2013-01-18 15:00 ` Zhang, Jessica
2013-01-18 15:09 ` Zhang, Jessica
2013-01-19 13:37 ` Flavio Castro Alves Filho
2017-08-16 10:15 Arno Steffens
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CEB7C74.4000502@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=jessica.zhang@intel.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.