From: Saul Wold <sgw@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
Zhenhua Luo <zhenhua.luo@freescale.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Schmitt Richard-B43082 <B43082@freescale.com>,
richard.schmitt@freescale.com
Subject: Re: GCC 4.8 Issues with fsl-ppc and fsl-arm (e5000)
Date: Tue, 02 Jul 2013 07:28:37 -0700 [thread overview]
Message-ID: <51D2E395.3000300@linux.intel.com> (raw)
In-Reply-To: <51CB2164.5090102@linux.intel.com>
Any updates on this issue?
Sau!
On 06/26/2013 10:14 AM, Saul Wold wrote:
> On 06/25/2013 11:00 AM, Khem Raj wrote:
>>
>> On Jun 25, 2013, at 10:46 AM, Otavio Salvador
>> <otavio@ossystems.com.br> wrote:
>>
>>> http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/log/?h=imx_2.6.35_11.09.01
>>>
>>>
>>
>> hmm 2.6.35
>>
>>> If you provide me the command I should do, I can get it. Or Saul might
>>> get it from autobuilder as well.
>>
>> something like below. Replace the paths to your tmpdir appropriately
>> in below cmd ( e.g.
>> /builds1/angstrom/build/tmp-angstrom_next-eglibc/work/beaglebone-angstrom-linux-gnueabi
>> might be something else for you and also compiler name and sysroot)
>>
>> cd into kernel srcdir in staging
>> tmp/sysroots/beaglebone/usr/src/kernel/tools/perf
>>
>> arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mthumb-interwork
>> -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8
>> --sysroot=/builds1/angstrom/build/tmp-angstrom_next-eglibc/sysroots/qemuarm
>> -O2 -pipe -g -feliminate-unused-debug-types -D_LARGEFILE64_SOURCE
>> -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -Iutil/include -Iarch/arm/include
>> -I/builds1/angstrom/build/tmp-angstrom_next-eglibc/work/beaglebone-angstrom-linux-gnueabi/perf/1.0-r8/perf-1.0/arch/arm/include/generated/uapi
>> -I/builds1/angstrom/build/tmp-angstrom_next-eglibc/sysroots/beaglebone/usr/src/kernel/arch/arm/include/uapi
>> -I/builds1/angstrom/build/tmp-angstrom_next-eglibc/sysroots/beaglebone/usr/src/kernel/arch/arm/include
>> -I/builds1/angstrom/build/tmp-angstrom_next-eglibc/work/beaglebone-angstrom-linux-gnueabi/perf/1.0-r8/perf-1.0/include/generated/uapi
>> -I/builds1/angstrom/build/tmp-angstrom_next-eglibc/sysroots/beaglebone/usr/src/kernel/include/uapi
>> -I/builds1/angstrom/build/tmp-angstrom_next-eglibc/sysroots/beaglebone/usr/src/kernel
>>
> /include
> -I/builds1/angstrom/build/tmp-angstrom_next-eglibc/work/beaglebone-angstrom-linux-gnueabi/perf/1.0-r8/perf-1.0/util
> -Iutil -I. -I../lib/traceevent/ -D_LARGEFILE64_SOURCE
> -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE
> -I/builds1/angstrom/build/tmp-angstrom_next-eglibc/work/beaglebone-angstrom-linux-gnueabi/perf/1.0-r8/perf-1.0/
> -DLIBELF_SUPPORT -DLIBELF_MMAP -I=/usr/include/slang -DNEWT_SUPPORT
> -DHAVE_ON_EXIT -DBACKTRACE_SUPPORT util/callchain.c -E -dD -o callchain.i
>>
>> and send me callchain.i
>>
> Finally got a hold of a build!
>
> Here's the command that I used:
>
>> arm-poky-linux-gnueabi-gcc -march=armv5te -marm -mthumb-interwork
>> --sysroot=/srv/home/pokybuild/yocto-autobuilder-new/yocto-slave/nightly-fsl-arm/build/build/tmp/sysroots/imx28evk
>> -c -O2 -pipe -g -feliminate-unused-debug-types -D_LARGEFILE64_SOURCE
>> -D_FILE_OFFSET_BITS=64 -Iutil/include -Iarch/arm/include
>> -I../../include
>> -I/srv/home/pokybuild/yocto-autobuilder-new/yocto-slave/nightly-fsl-arm/build/build/tmp/work/imx28evk-poky-linux-gnueabi/perf/1.0-r8/perf-1.0/
>> -DNO_NEWT_SUPPORT -DNO_LIBPERL -DNO_LIBPYTHON -DHAVE_CPLUS_DEMANGLE
>> -DSHA1_HEADER="<openssl/sha.h>" util/callchain.c -E -dD -o callchain.i
>
> I hope this can help.
>
> Sau!
>
next prev parent reply other threads:[~2013-07-02 14:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 17:07 GCC 4.8 Issues with fsl-ppc and fsl-arm (e5000) Saul Wold
2013-06-25 17:42 ` Khem Raj
2013-06-25 17:46 ` Otavio Salvador
2013-06-25 18:00 ` Khem Raj
2013-06-25 18:03 ` Otavio Salvador
2013-06-25 18:09 ` Khem Raj
2013-06-26 17:14 ` Saul Wold
2013-07-02 14:28 ` Saul Wold [this message]
2013-07-02 14:47 ` Otavio Salvador
2013-07-02 14:54 ` Khem Raj
2013-07-02 15:01 ` Otavio Salvador
2013-07-02 15:24 ` Saul Wold
2013-06-26 2:44 ` 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=51D2E395.3000300@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=B43082@freescale.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=raj.khem@gmail.com \
--cc=richard.schmitt@freescale.com \
--cc=zhenhua.luo@freescale.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox