From: Khem Raj <raj.khem@gmail.com>
To: Harinath maddelal <Harinath.maddela@inedasystems.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Error while buildng SGX
Date: Mon, 2 May 2016 08:45:58 -0700 [thread overview]
Message-ID: <6D8F8D7A-41DF-4CF7-8363-059BA95294FB@gmail.com> (raw)
In-Reply-To: <PN1PR01MB03335EB964C553EDFD8B3C9BEF790@PN1PR01MB0333.INDPRD01.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 2417 bytes --]
> On May 1, 2016, at 10:44 PM, Harinath maddelal <Harinath.maddela@inedasystems.com> wrote:
>
> Hi
>
>> The same builds fine when i use my local gcc of version 4.8.3.
>
> By this i mean we are using our local copy of mips toolchain(mips-linux-gnu-gcc-4.8.3)
>
> So i have used poky mips toolchain to build the entire poky(except SGX).
> SGX is built with our local copy of mips toolchain (as it was giving the build errors when built with poky mips toolchain, log file attached for reference)
SGX build system is probably hardcoding CC/CXX variables and not letting environment to override it. When you build with poky, its important
that CC and CXX variables are effective in the components make system.
>
> Is there any way to build the complete poky using local mips toolchain rather than using the poky mips toolchain? I just want to know how to use our local toolchain setup to build entire poky.
you should look into external toolchain recipes, Some samples like sourcery toolchain and Linaro toolchain are available as samples.
I for one would advise to not go this route. Since you are not able to take advantage of integration that YP had done using internal
toolchain.
>
> Kindly help me in this regard
>
> Thanks and Regards,
> Harinath
>
>
> ________________________________________
> From: Khem Raj <raj.khem@gmail.com>
> Sent: Saturday, April 30, 2016 7:41:40 AM
> To: Harinath maddelal
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Error while buildng SGX
>
> On Thu, Apr 28, 2016 at 6:34 AM, Harinath maddelal
> <Harinath.maddela@inedasystems.com> wrote:
>> Hi all,
>>
>>
>> When i build sgx using yocto, im getting following errors.
>>
>> The same builds fine when i use my local gcc of version 4.8.3.
>>
>>
>> I have used 1.8.1 Yocto its using 4.9.2 gcc.
>>
>>
>> Can you please help me resolve the issue. Thanks in advance
>>
>>
>> Following is the console build error log
>
> Please provide compiler cmdline for the failing compile, most probably
> its due to messed up -isystem
> on cmdline
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
> <log.do_compile>
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]
next prev parent reply other threads:[~2016-05-02 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 13:34 Error while buildng SGX Harinath maddelal
2016-04-29 3:21 ` Harinath maddelal
2016-04-30 2:11 ` Khem Raj
2016-05-02 5:44 ` Harinath maddelal
2016-05-02 15:45 ` Khem Raj [this message]
2016-05-03 5:43 ` Harinath maddelal
2016-05-06 3:16 ` Harinath maddelal
2016-05-06 4:10 ` Khem Raj
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=6D8F8D7A-41DF-4CF7-8363-059BA95294FB@gmail.com \
--to=raj.khem@gmail.com \
--cc=Harinath.maddela@inedasystems.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.