* Compiling gcc for A15 in Yocto @ 2013-07-10 15:51 Saran, Sajesh Kumar 2013-07-10 15:52 ` Saran, Sajesh Kumar 2013-07-10 15:53 ` Maupin, Chase 0 siblings, 2 replies; 9+ messages in thread From: Saran, Sajesh Kumar @ 2013-07-10 15:51 UTC (permalink / raw) To: meta-arago@arago-project.org, Senicic, Djordje [-- Attachment #1: Type: text/plain, Size: 235 bytes --] Hi, We are trying to compile gcc for ARM (A15). The cloning of SVN repo is very slow and taking very long time (~6 hours and still continuing). Have anybody have similar experience on building gcc on ARM? Regards, Sajesh [-- Attachment #2: Type: text/html, Size: 2155 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Compiling gcc for A15 in Yocto 2013-07-10 15:51 Compiling gcc for A15 in Yocto Saran, Sajesh Kumar @ 2013-07-10 15:52 ` Saran, Sajesh Kumar 2013-07-10 16:32 ` Denys Dmytriyenko 2013-07-10 15:53 ` Maupin, Chase 1 sibling, 1 reply; 9+ messages in thread From: Saran, Sajesh Kumar @ 2013-07-10 15:52 UTC (permalink / raw) To: meta-arago@arago-project.org, Senicic, Djordje [-- Attachment #1: Type: text/plain, Size: 627 bytes --] I am not clear in last e-mail. We are trying to compile gcc for ARM in an X86 Ubuntu machine. Regards, Sajesh From: meta-arago-bounces@arago-project.org [mailto:meta-arago-bounces@arago-project.org] On Behalf Of Saran, Sajesh Kumar Sent: Wednesday, July 10, 2013 11:51 AM To: meta-arago@arago-project.org; Senicic, Djordje Subject: [meta-arago] Compiling gcc for A15 in Yocto Hi, We are trying to compile gcc for ARM (A15). The cloning of SVN repo is very slow and taking very long time (~6 hours and still continuing). Have anybody have similar experience on building gcc on ARM? Regards, Sajesh [-- Attachment #2: Type: text/html, Size: 3646 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Compiling gcc for A15 in Yocto 2013-07-10 15:52 ` Saran, Sajesh Kumar @ 2013-07-10 16:32 ` Denys Dmytriyenko 2013-07-11 2:23 ` Siddharth Heroor 0 siblings, 1 reply; 9+ messages in thread From: Denys Dmytriyenko @ 2013-07-10 16:32 UTC (permalink / raw) To: Saran, Sajesh Kumar; +Cc: meta-arago@arago-project.org, Senicic, Djordje On Wed, Jul 10, 2013 at 03:52:47PM +0000, Saran, Sajesh Kumar wrote: > I am not clear in last e-mail. > > We are trying to compile gcc for ARM in an X86 Ubuntu machine. Sajesh, If you use recent recipes in Yocto to build gcc from sources, it doesn't use any git or svn repositories any more, but downloads a release tarball. I've done it before and there's an easy way to enable it in Arago - just set TOOLCHAIN_TYPE=internal -- Denys > From: meta-arago-bounces@arago-project.org [mailto:meta-arago-bounces@arago-project.org] On Behalf Of Saran, Sajesh Kumar > Sent: Wednesday, July 10, 2013 11:51 AM > To: meta-arago@arago-project.org; Senicic, Djordje > Subject: [meta-arago] Compiling gcc for A15 in Yocto > > Hi, > > We are trying to compile gcc for ARM (A15). > The cloning of SVN repo is very slow and taking very long time (~6 hours and still continuing). > > Have anybody have similar experience on building gcc on ARM? > > Regards, > Sajesh > > _______________________________________________ > meta-arago mailing list > meta-arago@arago-project.org > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Compiling gcc for A15 in Yocto 2013-07-10 16:32 ` Denys Dmytriyenko @ 2013-07-11 2:23 ` Siddharth Heroor 2013-07-11 2:57 ` Denys Dmytriyenko 0 siblings, 1 reply; 9+ messages in thread From: Siddharth Heroor @ 2013-07-11 2:23 UTC (permalink / raw) To: Denys Dmytriyenko; +Cc: meta-arago@arago-project.org, Senicic, Djordje On 7/10/2013 10:02 PM, Denys Dmytriyenko wrote: > On Wed, Jul 10, 2013 at 03:52:47PM +0000, Saran, Sajesh Kumar wrote: >> I am not clear in last e-mail. >> >> We are trying to compile gcc for ARM in an X86 Ubuntu machine. > > Sajesh, > > If you use recent recipes in Yocto to build gcc from sources, it doesn't use > any git or svn repositories any more, but downloads a release tarball. I've > done it before and there's an easy way to enable it in Arago - just set > TOOLCHAIN_TYPE=internal > Slightly related question. Is it possible to get tools-sdk as a IMAGE_FEATURE? I haven't been able to do that successfully. We use the Linaro 4.7 as an external toolchain, but having tools-sdk with gcc-linaro-4.7 as the compiler running on the target is very useful. Any tips/suggestions on how to go about adding it? I'll submit patches once I get it in place, but I'm currently stuck at the start. -- Sid ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Compiling gcc for A15 in Yocto 2013-07-11 2:23 ` Siddharth Heroor @ 2013-07-11 2:57 ` Denys Dmytriyenko 2013-07-11 3:34 ` Siddharth Heroor 0 siblings, 1 reply; 9+ messages in thread From: Denys Dmytriyenko @ 2013-07-11 2:57 UTC (permalink / raw) To: Siddharth Heroor; +Cc: meta-arago@arago-project.org, Senicic, Djordje On Thu, Jul 11, 2013 at 07:53:12AM +0530, Siddharth Heroor wrote: > On 7/10/2013 10:02 PM, Denys Dmytriyenko wrote: > > On Wed, Jul 10, 2013 at 03:52:47PM +0000, Saran, Sajesh Kumar wrote: > >> I am not clear in last e-mail. > >> > >> We are trying to compile gcc for ARM in an X86 Ubuntu machine. > > > > Sajesh, > > > > If you use recent recipes in Yocto to build gcc from sources, it doesn't use > > any git or svn repositories any more, but downloads a release tarball. I've > > done it before and there's an easy way to enable it in Arago - just set > > TOOLCHAIN_TYPE=internal > > > > Slightly related question. Is it possible to get tools-sdk as a > IMAGE_FEATURE? I haven't been able to do that successfully. We use the > Linaro 4.7 as an external toolchain, but having tools-sdk with > gcc-linaro-4.7 as the compiler running on the target is very useful. Linaro toolchain is a cross-compiler and we use pre-built binaries that are to be run on x86 to generate code for ARM. It won't be possible to run it on the target (ARM). You'd need to compile the toolchain from sources for ARM. That is what Sajesh and Djordje were asking for - to be able to build gcc for the target from sources... -- Denys ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Compiling gcc for A15 in Yocto 2013-07-11 2:57 ` Denys Dmytriyenko @ 2013-07-11 3:34 ` Siddharth Heroor 2013-07-11 4:11 ` Denys Dmytriyenko 0 siblings, 1 reply; 9+ messages in thread From: Siddharth Heroor @ 2013-07-11 3:34 UTC (permalink / raw) To: Denys Dmytriyenko; +Cc: meta-arago@arago-project.org, Senicic, Djordje On 7/11/2013 8:27 AM, Denys Dmytriyenko wrote: > On Thu, Jul 11, 2013 at 07:53:12AM +0530, Siddharth Heroor wrote: >> On 7/10/2013 10:02 PM, Denys Dmytriyenko wrote: >>> On Wed, Jul 10, 2013 at 03:52:47PM +0000, Saran, Sajesh Kumar wrote: >>>> I am not clear in last e-mail. >>>> >>>> We are trying to compile gcc for ARM in an X86 Ubuntu machine. >>> >>> Sajesh, >>> >>> If you use recent recipes in Yocto to build gcc from sources, it doesn't use >>> any git or svn repositories any more, but downloads a release tarball. I've >>> done it before and there's an easy way to enable it in Arago - just set >>> TOOLCHAIN_TYPE=internal >>> >> >> Slightly related question. Is it possible to get tools-sdk as a >> IMAGE_FEATURE? I haven't been able to do that successfully. We use the >> Linaro 4.7 as an external toolchain, but having tools-sdk with >> gcc-linaro-4.7 as the compiler running on the target is very useful. > > Linaro toolchain is a cross-compiler and we use pre-built binaries that are to > be run on x86 to generate code for ARM. It won't be possible to run it on the > target (ARM). You'd need to compile the toolchain from sources for ARM. That > is what Sajesh and Djordje were asking for - to be able to build gcc for the > target from sources... > I was looking at meta-linaro/recipes-devtools/gcc. The gcc-linaro* recipes should allow building the compiler from source with SRC_URI set to something like https://launchpad.net/gcc-linaro/4.7/4.7-${RELEASE}/+download/gcc-${PV}-${RELEASE}.tar.bz2. I want to use the prebuilt cross-compiler to generate an image which has gcc-linaro-4.7 and corresponding tools-sdk features (i.e autotools, pkgconfig etc..). That means it downloads the linaro toolchain source and builds it to run _on the target_. Right now, bitbake -s | grep gcc gives gcc :4.5-r49+svnr184907 gcc-cross :4.5-r49+svnr184907 gcc-cross-canadian-arm :4.5-r49+svnr184907 gcc-cross-initial :4.5-r49+svnr184907 gcc-cross-intermediate :4.5-r49+svnr184907 gcc-crosssdk :4.5-r49+svnr184907 :4.7.2-r13 gcc-crosssdk-initial :4.5-r49+svnr184907 :4.7.2-r13 gcc-crosssdk-intermediate :4.5-r49+svnr184907 gcc-runtime :4.5-r49+svnr184907 gccmakedep 1:1.0.2-r3 libgcc :4.5-r49+svnr184907 nativesdk-gcc-runtime :4.5-r49+svnr184907 :4.7.2-r13 nativesdk-libgcc :4.5-r49+svnr184907 :4.7.2-r13 I'm wondering what's the way to override these values (not touching TOOLCHAIN_EXTERNAL) to allow gcc-linaro-4.7 to be picked up. The prebuilt toolchain would then build gcc-linaro-4.7 and then add it to the image. The rationale is that Cortex A15 devices (like OMAP5/DRA7xx and Keystone2) are pretty fast. For an individual linux developer, having a toolchain on the image, makes it trivial to develop software - by eliminating cross-compiling. -- Sid ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Compiling gcc for A15 in Yocto 2013-07-11 3:34 ` Siddharth Heroor @ 2013-07-11 4:11 ` Denys Dmytriyenko 2013-07-11 4:22 ` Siddharth Heroor 0 siblings, 1 reply; 9+ messages in thread From: Denys Dmytriyenko @ 2013-07-11 4:11 UTC (permalink / raw) To: Siddharth Heroor; +Cc: meta-arago@arago-project.org, Senicic, Djordje On Thu, Jul 11, 2013 at 09:04:43AM +0530, Siddharth Heroor wrote: > On 7/11/2013 8:27 AM, Denys Dmytriyenko wrote: > > On Thu, Jul 11, 2013 at 07:53:12AM +0530, Siddharth Heroor wrote: > >> On 7/10/2013 10:02 PM, Denys Dmytriyenko wrote: > >>> On Wed, Jul 10, 2013 at 03:52:47PM +0000, Saran, Sajesh Kumar wrote: > >>>> I am not clear in last e-mail. > >>>> > >>>> We are trying to compile gcc for ARM in an X86 Ubuntu machine. > >>> > >>> Sajesh, > >>> > >>> If you use recent recipes in Yocto to build gcc from sources, it doesn't use > >>> any git or svn repositories any more, but downloads a release tarball. I've > >>> done it before and there's an easy way to enable it in Arago - just set > >>> TOOLCHAIN_TYPE=internal > >>> > >> > >> Slightly related question. Is it possible to get tools-sdk as a > >> IMAGE_FEATURE? I haven't been able to do that successfully. We use the > >> Linaro 4.7 as an external toolchain, but having tools-sdk with > >> gcc-linaro-4.7 as the compiler running on the target is very useful. > > > > Linaro toolchain is a cross-compiler and we use pre-built binaries that are to > > be run on x86 to generate code for ARM. It won't be possible to run it on the > > target (ARM). You'd need to compile the toolchain from sources for ARM. That > > is what Sajesh and Djordje were asking for - to be able to build gcc for the > > target from sources... > > I was looking at meta-linaro/recipes-devtools/gcc. The gcc-linaro* > recipes should allow building the compiler from source with SRC_URI set > to something like > https://launchpad.net/gcc-linaro/4.7/4.7-${RELEASE}/+download/gcc-${PV}-${RELEASE}.tar.bz2. > > > I want to use the prebuilt cross-compiler to generate an image which has > gcc-linaro-4.7 and corresponding tools-sdk features (i.e autotools, > pkgconfig etc..). That means it downloads the linaro toolchain source > and builds it to run _on the target_. Correct, that's exactly what I was trying to say :) > Right now, bitbake -s | grep gcc gives > > gcc :4.5-r49+svnr184907 > gcc-cross :4.5-r49+svnr184907 > gcc-cross-canadian-arm :4.5-r49+svnr184907 > gcc-cross-initial :4.5-r49+svnr184907 > gcc-cross-intermediate :4.5-r49+svnr184907 > gcc-crosssdk :4.5-r49+svnr184907 > :4.7.2-r13 > gcc-crosssdk-initial :4.5-r49+svnr184907 > :4.7.2-r13 > gcc-crosssdk-intermediate :4.5-r49+svnr184907 > gcc-runtime :4.5-r49+svnr184907 > gccmakedep 1:1.0.2-r3 > libgcc :4.5-r49+svnr184907 > nativesdk-gcc-runtime :4.5-r49+svnr184907 > :4.7.2-r13 > nativesdk-libgcc :4.5-r49+svnr184907 > :4.7.2-r13 > > I'm wondering what's the way to override these values (not touching > TOOLCHAIN_EXTERNAL) to allow gcc-linaro-4.7 to be picked up. The > prebuilt toolchain would then build gcc-linaro-4.7 and then add it to > the image. First of all, if you are seeing all 4.5 versions selected by default, you are probably using Arago as a cross toolchain - check your TOOLCHAIN_BRAND. Second, to use Linaro gcc compiled from sources, you need to set bunch of PREFERRED_VERSION variables, easily done like this: GCCVERSION = "linaro-4.7%" > The rationale is that Cortex A15 devices (like OMAP5/DRA7xx and > Keystone2) are pretty fast. For an individual linux developer, having a > toolchain on the image, makes it trivial to develop software - by > eliminating cross-compiling. Understood and that's what Keystone guys are doing already. -- Denys ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Compiling gcc for A15 in Yocto 2013-07-11 4:11 ` Denys Dmytriyenko @ 2013-07-11 4:22 ` Siddharth Heroor 0 siblings, 0 replies; 9+ messages in thread From: Siddharth Heroor @ 2013-07-11 4:22 UTC (permalink / raw) To: Denys Dmytriyenko; +Cc: meta-arago@arago-project.org, Senicic, Djordje On 7/11/2013 9:41 AM, Denys Dmytriyenko wrote: > On Thu, Jul 11, 2013 at 09:04:43AM +0530, Siddharth Heroor wrote: >> On 7/11/2013 8:27 AM, Denys Dmytriyenko wrote: >>> On Thu, Jul 11, 2013 at 07:53:12AM +0530, Siddharth Heroor wrote: >>>> On 7/10/2013 10:02 PM, Denys Dmytriyenko wrote: >>>>> On Wed, Jul 10, 2013 at 03:52:47PM +0000, Saran, Sajesh Kumar wrote: >>>>>> I am not clear in last e-mail. >>>>>> >>>>>> We are trying to compile gcc for ARM in an X86 Ubuntu machine. >>>>> >>>>> Sajesh, >>>>> >>>>> If you use recent recipes in Yocto to build gcc from sources, it doesn't use >>>>> any git or svn repositories any more, but downloads a release tarball. I've >>>>> done it before and there's an easy way to enable it in Arago - just set >>>>> TOOLCHAIN_TYPE=internal >>>>> >>>> >>>> Slightly related question. Is it possible to get tools-sdk as a >>>> IMAGE_FEATURE? I haven't been able to do that successfully. We use the >>>> Linaro 4.7 as an external toolchain, but having tools-sdk with >>>> gcc-linaro-4.7 as the compiler running on the target is very useful. >>> >>> Linaro toolchain is a cross-compiler and we use pre-built binaries that are to >>> be run on x86 to generate code for ARM. It won't be possible to run it on the >>> target (ARM). You'd need to compile the toolchain from sources for ARM. That >>> is what Sajesh and Djordje were asking for - to be able to build gcc for the >>> target from sources... >> >> I was looking at meta-linaro/recipes-devtools/gcc. The gcc-linaro* >> recipes should allow building the compiler from source with SRC_URI set >> to something like >> https://launchpad.net/gcc-linaro/4.7/4.7-${RELEASE}/+download/gcc-${PV}-${RELEASE}.tar.bz2. >> >> >> I want to use the prebuilt cross-compiler to generate an image which has >> gcc-linaro-4.7 and corresponding tools-sdk features (i.e autotools, >> pkgconfig etc..). That means it downloads the linaro toolchain source >> and builds it to run _on the target_. > > Correct, that's exactly what I was trying to say :) > > >> Right now, bitbake -s | grep gcc gives >> >> gcc :4.5-r49+svnr184907 >> gcc-cross :4.5-r49+svnr184907 >> gcc-cross-canadian-arm :4.5-r49+svnr184907 >> gcc-cross-initial :4.5-r49+svnr184907 >> gcc-cross-intermediate :4.5-r49+svnr184907 >> gcc-crosssdk :4.5-r49+svnr184907 >> :4.7.2-r13 >> gcc-crosssdk-initial :4.5-r49+svnr184907 >> :4.7.2-r13 >> gcc-crosssdk-intermediate :4.5-r49+svnr184907 >> gcc-runtime :4.5-r49+svnr184907 >> gccmakedep 1:1.0.2-r3 >> libgcc :4.5-r49+svnr184907 >> nativesdk-gcc-runtime :4.5-r49+svnr184907 >> :4.7.2-r13 >> nativesdk-libgcc :4.5-r49+svnr184907 >> :4.7.2-r13 >> >> I'm wondering what's the way to override these values (not touching >> TOOLCHAIN_EXTERNAL) to allow gcc-linaro-4.7 to be picked up. The >> prebuilt toolchain would then build gcc-linaro-4.7 and then add it to >> the image. > > First of all, if you are seeing all 4.5 versions selected by default, you are > probably using Arago as a cross toolchain - check your TOOLCHAIN_BRAND. > > Second, to use Linaro gcc compiled from sources, you need to set bunch of > PREFERRED_VERSION variables, easily done like this: > > GCCVERSION = "linaro-4.7%" Cool. I'll try that. > > >> The rationale is that Cortex A15 devices (like OMAP5/DRA7xx and >> Keystone2) are pretty fast. For an individual linux developer, having a >> toolchain on the image, makes it trivial to develop software - by >> eliminating cross-compiling. > > Understood and that's what Keystone guys are doing already. > Looks like we think alike already ;-) -- Sid ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Compiling gcc for A15 in Yocto 2013-07-10 15:51 Compiling gcc for A15 in Yocto Saran, Sajesh Kumar 2013-07-10 15:52 ` Saran, Sajesh Kumar @ 2013-07-10 15:53 ` Maupin, Chase 1 sibling, 0 replies; 9+ messages in thread From: Maupin, Chase @ 2013-07-10 15:53 UTC (permalink / raw) To: Saran, Sajesh Kumar, meta-arago@arago-project.org, Senicic, Djordje [-- Attachment #1: Type: text/plain, Size: 896 bytes --] I believe Sidd also had some issues when cloning from India. But you can use the pre-built linaro toolchain or there is also a git mirror you could use. Sincerely, Chase Maupin Integration Team Manager Linux Core Product Development e-mail: chase.maupin@ti.com phone: (214) 567-2950 For support: Forums - http://community.ti.com/forums/ Wiki - http://wiki.davincidsp.com/ From: meta-arago-bounces@arago-project.org [mailto:meta-arago-bounces@arago-project.org] On Behalf Of Saran, Sajesh Kumar Sent: Wednesday, July 10, 2013 10:51 AM To: meta-arago@arago-project.org; Senicic, Djordje Subject: [meta-arago] Compiling gcc for A15 in Yocto Hi, We are trying to compile gcc for ARM (A15). The cloning of SVN repo is very slow and taking very long time (~6 hours and still continuing). Have anybody have similar experience on building gcc on ARM? Regards, Sajesh [-- Attachment #2: Type: text/html, Size: 4189 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2013-07-11 4:22 UTC | newest] Thread overview: 9+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2013-07-10 15:51 Compiling gcc for A15 in Yocto Saran, Sajesh Kumar 2013-07-10 15:52 ` Saran, Sajesh Kumar 2013-07-10 16:32 ` Denys Dmytriyenko 2013-07-11 2:23 ` Siddharth Heroor 2013-07-11 2:57 ` Denys Dmytriyenko 2013-07-11 3:34 ` Siddharth Heroor 2013-07-11 4:11 ` Denys Dmytriyenko 2013-07-11 4:22 ` Siddharth Heroor 2013-07-10 15:53 ` Maupin, Chase
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.