Re: [Consult] About tool chains of metag

[Chen Gang <gang.chen.5i5j-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]

Hello Maintainers:

After tried, I guess related binutils and gcc are not match with each
other: gcc support "-minim" option which will pass to gas, but gas can
not recognize it.

With "-mno-minim" option, we can try to bypass this issue (I am just
trying), but it seems not a quite good idea.

Welcome any additional suggestions or completions for it, thanks.


The related error with making manually ("make menuconfig; make" in root
directory also get the same issue):

  /upstream/src/metag/metag-buildroot-metag-core/output/toolchain/gcc-4.2.4-initial/./gcc/xgcc -B/upstream/src/metag/metag-buildroot-metag-core/output/toolchain/gcc-4.2.4-initial/./gcc/ -B/upstream/src/metag/metag-buildroot-metag-core/output/host/usr/metag-buildroot-linux-uclibc/bin/ -B/upstream/src/metag/metag-buildroot-metag-core/output/host/usr/metag-buildroot-linux-uclibc/lib/ -isystem /upstream/src/metag/metag-buildroot-metag-core/output/host/usr/metag-buildroot-linux-uclibc/include -isystem /upstream/src/metag/metag-buildroot-metag-core/output/host/usr/metag-buildroot-linux-uclibc/sys-include -O2 -g -Os -DIN_GCC -DCROSS_COMPILE   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition  -isystem ./include  -I. -I. -I/upstream/src/metag/metag-buildroot-
 metag-core/output/toolchain/gcc-4.2.4/gcc -I/upstream/src/metag/metag-buildroot-metag-core/output/toolchain/gcc-4.2.4/gcc/. -I/upstream/src/metag/metag-buildroot-metag-core/output/toolchain/gcc-4.2.4
/gcc/../include -I/upstream/src/metag/metag-buildroot-metag-core/output/toolchain/gcc-4.2.4/gcc/../libcpp/include -I/upstream/src/metag/metag-buildroot-metag-core/output/host/usr/include -I/upstream/src/metag/metag-buildroot-metag-core/output/host/usr/include -I/upstream/src/metag/metag-buildroot-metag-core/output/toolchain/gcc-4.2.4/gcc/../libdecnumber -I../libdecnumber  -g0 -finhibit-size-directive -fno-inline-functions -fno-exceptions -fno-zero-initialized-in-bss -fno-toplevel-reorder -Dinhibit_libc -fPIC \
    -c /upstream/src/metag/metag-buildroot-metag-core/output/toolchain/gcc-4.2.4/gcc/crtstuff.c -DCRT_END -DCRTSTUFFS_O \
    -o crtendS.o
  Assembler messages:
  Error: unrecognized option -minim
  make[2]: *** [crtbegin.o] Error 1
  make[2]: *** Waiting for unfinished jobs....


Thanks.

On 12/05/2013 12:23 AM, James Hogan wrote:
> On 04/12/13 12:02, James Hogan wrote:
>> On 04/12/13 05:45, Chen Gang wrote:
>>> Could you provide any related information about metag tool chains?
>>>
>>> I plan to cross compile metag with allmodconfig, but now it seems not
>>> quite easy to find related gcc (binutils-2.23.2 support metag, but gcc
>>> main line does not).
>>
>> A buildroot tree containing a gcc-4.2.4 patch can be found here:
>>
>> git://github.com/img-meta/metag-buildroot.git metag-core
>>
>> Use meta2_defconfig
>>
>> There's a known issue with all/random config builds with this toolchain
>> which results in internal compiler errors triggered by the inline asm in
>> arch/metag/include/asm/io.h when used by certain drivers, so I need to
>> update the patch to the latest before these will go away.
> 
> I've pushed a new buildroot branch which has the updated GCC 4.2.4 patch:
> 
> git://github.com/img-meta/metag-buildroot.git metag-core-2013.11
> Again use meta2_defconfig.
> 
> Tony: Is this something you can easily use to generate a Meta toolchain
> for https://www.kernel.org/pub/tools/crosstool/?
> 
> Thanks
> James
> 
>>
>> The other main issue with all/random config builds for Meta is a few
>> missing !METAG dependencies on legacy PC peripherals like SERIO_I8042,
>> which I believe you've already come across for Arc.
>>
>> Please read this thread before attempting to fix them:
>> https://lkml.kernel.org/r/201211161520.03974.arnd-r2nGTMty4D4@public.gmane.org
>>
>> I haven't got around to fixing this properly myself, but it would be a
>> worthwhile improvement if you felt inclined to do so.
> 


-- 
Chen Gang
--
To unsubscribe from this list: send the line "unsubscribe linux-metag" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html