Hi Barry. GCC can be switched at runtime by supplying -march=* and/or
-mcpu=* flags to the compiler, just as you have done below. The
'--with-arch=*' lines you see below set what GCC compiles to by
default.
Does your chip have a FPU? If not, it's probably the
--with-fpu=vfpv3-d16 line that's ca
Hi All,
After downloading linaro toolchain by apt-get in ubuntu, I compiled
the uboot for ARM1136 SoC with -march=armv5 option. And it can compile
successfully. Then I let the uboot run on target boards and system
failed due to "undefined instructions". Checked linaro toolchain
options, it is:
#ar
On Wed, Mar 23, 2011 at 11:59:11AM +0100, Goswin von Brederlow wrote:
>
>As a side note the debian-cd package needs to also consider Built-Using
>when creating source images.
Yup, we'll need to consider that. I'm looking forwards to having all
the stuff we need properly dealt with, however it's do
Philipp Kern writes:
> On 2011-03-23, Goswin von Brederlow wrote:
>> Also does the testing transition consider the Built-Using? If I specify
>> 'Built-Using: gcc-4.5 (= 4.5.2-5)' will the package be blocked from
>> entering testing until gcc-4.5 (= 4.5.2-5) has entered and block gcc-4.5
>> (= 4.
Mark Hymers writes:
> On Tue, 22, Mar, 2011 at 01:57:42PM +, Hector Oron spoke thus..
>> Hi Mark,
>>
>> 2011/3/22 Mark Hymers :
>>
>> > The current design is the Binary packages can contain an additional
>> > control field: Built-Using.
>>
>> First of all, thanks very much for taking care
Mark Hymers writes:
> On Mon, 14, Mar, 2011 at 02:04:30PM +, Hector Oron spoke thus..
>> Hi,
>>
>> 2009/11/2 Mark Hymers :
>> > On Mon, 02, Nov, 2009 at 12:43:42PM +, Philipp Kern spoke thus..
>> >> Of course it is a sane approach but very special care needs to be taken
>> >> when
>> >>
