From: lamikr <lamikr@cc.jyu.fi>
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: Linux-omap-open-source@linux.omap.com
Subject: Re: Building kenel error
Date: Fri, 18 Aug 2006 23:29:43 +0300 [thread overview]
Message-ID: <44E62337.5090604@cc.jyu.fi> (raw)
In-Reply-To: <EA12F909C0431D458B9D18A176BEE4A5072DABC7@dlee02.ent.ti.com>
Woodruff, Richard wrote:
>> I never had success of using gcc-4.0.2 and later on 2.6.16/17 kernel.
>>
> So
>
>> I just stick with the older gcc-3.4.1. Which version of tool chain are
>> you using for 2.6.16 or 2.6.17 kernel? Any advantages of using the
>>
> later
>
>> version of the compiler?
>> Thanks,
>> kwan
>>
>
> We have to use several different versions. Currently I use 3.4.0,
> 3.4.3, and 3.3.1 on older kernels. On the latest kernels we will use
> 4.1.0. We have built these, gotten them from a vendor, or gotten from
> www.codesourcery.com .
>
> One of the main reasons for using CodeSourcery based tool chains is they
> provide newer ARM support though ARMv7 (including VFP & VFP2). If you
> are doing gaming with the OMAP2 3d core it can provide a nice boost.
>
Do you know does codesourcery or somebody else done yet eabi gcc that
would support armv4 or armv4t?
Mika
next prev parent reply other threads:[~2006-08-18 20:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 18:56 Building kenel error Woodruff, Richard
2006-08-18 20:15 ` Brian Swetland
2006-08-18 20:29 ` lamikr [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-18 20:33 Woodruff, Richard
2006-08-18 20:26 Woodruff, Richard
2006-08-18 12:04 Woodruff, Richard
2006-08-18 16:24 ` Hingkwan Huen
2006-08-18 18:50 ` Dirk Behme
2006-08-18 9:18 kabbin
2006-08-15 9:47 kabbin
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=44E62337.5090604@cc.jyu.fi \
--to=lamikr@cc.jyu.fi \
--cc=Linux-omap-open-source@linux.omap.com \
--cc=r-woodruff2@ti.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 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.