public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Dittmer <jdi@l4x.org>
To: bryan.wu@analog.com
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Blackfin arch fixes (try #2)
Date: Tue, 03 Jul 2007 15:58:34 +0200	[thread overview]
Message-ID: <468A560A.9050801@l4x.org> (raw)
In-Reply-To: <1183423041.10353.8.camel@roc-laptop>

Bryan Wu wrote:
> Hi Linus:
> 
> Marco's patch will kill the zero file git-pull error.
> Jie's patch is required because we will release our new Blackfin toolchain.

So, what is the new toolchain version?
gcc 4.1.1 (adi 07r1) / binutils 2.17 doesn't seem to work anymore:

bf533-stamp_defconfig [1]:
   CC      arch/blackfin/kernel/asm-offsets.s
cc1: error: unrecognized command line option "-mcpu=bf533-0.3"
make[2]: *** [arch/blackfin/kernel/asm-offsets.s] Error 1
make[1]: *** [prepare0] Error 2
make: *** [_all] Error 2

bf561-ezkit_defconfig [2]:
   CC      arch/blackfin/kernel/asm-offsets.s
cc1: error: unrecognized command line option "-mcpu=bf561-0.3"
make[2]: *** [arch/blackfin/kernel/asm-offsets.s] Error 1
make[1]: *** [prepare0] Error 2
make: *** [_all] Error 2

previously, there was only this error (defconfig) [3]:
CC      fs/binfmt_flat.o
/tmp/tmp.RAuANA4724/kernel/fs/binfmt_flat.c: In function ‘decompress_exec’:
/tmp/tmp.RAuANA4724/kernel/fs/binfmt_flat.c:293: warning: label ‘out’ defined 
but not used
/tmp/tmp.RAuANA4724/kernel/fs/binfmt_flat.c: In function ‘load_flat_file’:
/tmp/tmp.RAuANA4724/kernel/fs/binfmt_flat.c:462: warning: format ‘%x’ expects 
type ‘unsigned int’, but argument 3 has type ‘long int’
/tmp/tmp.RAuANA4724/kernel/fs/binfmt_flat.c:462: warning: format ‘%x’ expects 
type ‘unsigned int’, but argument 4 has type ‘long int’
/tmp/tmp.RAuANA4724/kernel/fs/binfmt_flat.c:549: warning: passing argument 1 
of ‘ksize’ makes pointer from integer without a cast
/tmp/tmp.RAuANA4724/kernel/fs/binfmt_flat.c:601: warning: passing argument 1 
of ‘ksize’ makes pointer from integer without a cast
/tmp/tmp.RAuANA4724/kernel/fs/binfmt_flat.c:760:50: error: macro 
"flat_get_addr_from_rp" requires 4 arguments, but only 3 given
/tmp/tmp.RAuANA4724/kernel/fs/binfmt_flat.c:760: error: 
‘flat_get_addr_from_rp’ undeclared (first use in this function)
/tmp/tmp.RAuANA4724/kernel/fs/binfmt_flat.c:760: error: (Each undeclared 
identifier is reported only once
/tmp/tmp.RAuANA4724/kernel/fs/binfmt_flat.c:760: error: for each function it 
appears in.)
make[2]: *** [fs/binfmt_flat.o] Error 1
make[1]: *** [fs] Error 2
make: *** [_all] Error 2

Thanks,

Jan

[1] http://l4x.org/k/?d=31517
[2] http://l4x.org/k/?d=31518
[3] http://l4x.org/k/?d=31478

  reply	other threads:[~2007-07-03 14:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-03  0:37 [GIT PULL] Blackfin arch fixes (try #2) Bryan Wu
2007-07-03 13:58 ` Jan Dittmer [this message]
2007-07-03 17:55   ` Mike Frysinger
2007-07-04 20:38     ` Jan Dittmer
2007-07-06  7:22       ` Mike Frysinger
2007-07-06  7:51         ` Jan Dittmer
2007-07-12 21:02           ` Mike Frysinger
2007-07-10 18:44         ` Jan Dittmer
2007-07-10 21:42           ` Robin Getz
2007-07-11  2:09           ` Bryan Wu

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=468A560A.9050801@l4x.org \
    --to=jdi@l4x.org \
    --cc=bryan.wu@analog.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox