All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen.5i5j-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: James Hogan <james.hogan-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
Cc: Tony Breeds
	<tony-B47dsA4koDqXvyopL2yb9tBPR1lH4CV8@public.gmane.org>,
	linux-metag-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Fengguang Wu
	<fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [Consult] About tool chains of metag
Date: Mon, 09 Dec 2013 10:21:49 +0800	[thread overview]
Message-ID: <52A5293D.3090105@gmail.com> (raw)
In-Reply-To: <3435055.6ve26xcMIH@radagast>

On 12/09/2013 04:24 AM, James Hogan wrote:
> On Sunday 08 December 2013 18:25:30 Chen Gang wrote:
>>   Assembler messages:
>>   Error: unrecognized option -minim
>>   make[2]: *** [crtbegin.o] Error 1
>>   make[2]: *** Waiting for unfinished jobs....
> 
> Did you use meta2_defconfig in buildroot as I suggested?
> 

Oh, sorry, I didn't, I missed understanding (originally, I only noticed
meta2_defconfig for Linux kernel, didn't notice another meta2_defconfig
for global).

Next, I will/should try.

> It has --enable-meta-default in BR2_EXTRA_GCC_CONFIG_OPTIONS which prevents 
> the compiler defaulting to minim (which isn't supported for Linux).
> 

Thank you very much for your details information (after that, we can
generate cross compiler).

And I will/should use "--enable-meta-default" and another options to
generate individual cross-compiler and continue to compile kernel with
allmodconfig.


:-)

Thanks.
-- 
Chen Gang

Open, share, and attitude like air, water and life which God blessed
--
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

      reply	other threads:[~2013-12-09  2:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-04  5:45 [Consult] About tool chains of metag Chen Gang
     [not found] ` <529EC18D.5040602-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-12-04 12:02   ` James Hogan
     [not found]     ` <529F19DA.5050805-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
2013-12-04 16:23       ` James Hogan
     [not found]         ` <529F5719.1000400-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
2013-12-05  1:57           ` Chen Gang
     [not found]             ` <529FDD81.7010000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-12-05  8:46               ` Chen Gang
     [not found]                 ` <52A03D77.3000503-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-12-05  9:41                   ` James Hogan
     [not found]                     ` <52A04A5F.9030001-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
2013-12-05 10:20                       ` Chen Gang
2013-12-05 10:20                         ` Chen Gang
2013-12-08 10:25           ` Chen Gang
     [not found]             ` <52A4491A.2010808-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-12-08 20:24               ` James Hogan
2013-12-09  2:21                 ` Chen Gang [this message]

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=52A5293D.3090105@gmail.com \
    --to=gang.chen.5i5j-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=james.hogan-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org \
    --cc=linux-metag-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=tony-B47dsA4koDqXvyopL2yb9tBPR1lH4CV8@public.gmane.org \
    /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.