From: Bryan Wu <bryan.wu@analog.com>
To: Jan Dittmer <jdi@l4x.org>
Cc: Mike Frysinger <vapier.adi@gmail.com>,
bryan.wu@analog.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Blackfin arch fixes (try #2)
Date: Wed, 11 Jul 2007 10:09:23 +0800 [thread overview]
Message-ID: <1184119763.22259.6.camel@roc-desktop> (raw)
In-Reply-To: <4693D39A.2040103@l4x.org>
On Tue, 2007-07-10 at 20:44 +0200, Jan Dittmer wrote:
> Mike Frysinger wrote:
> > On 7/4/07, Jan Dittmer <jdi@l4x.org> wrote:
> >> Mike Frysinger wrote:
> >>> On 7/3/07, Jan Dittmer <jdi@l4x.org> wrote:
> >>>> Bryan Wu wrote:
> >>>>> 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:
> >>> we'll post new toolchain binaries in a bit
> >> Hrm, somehow I don't understand it. On [1] you're
> >> talking about gcc 4.1.2 and binutils 2.17 supporting
> >> the -mcpu switch. But if you download the 2007R1 RC9
> >> toolchain from the Files section of the site (tar.gz)
> >> you actually get 4.1.1 without mcpu support. But the
> >> version string from gcc indicates 07r1.
> >> Care to explain?
> >
> > the syntax of the -mcpu option was extended
>
> With the current -elf toolchain from svn (-uclinux toolchain fails to
> build) I get the following error:
>
> CC fs/binfmt_script.o
> CC fs/binfmt_elf_fdpic.o
> CC fs/binfmt_flat.o
> fs/binfmt_flat.c: In function ‘decompress_exec’:
> fs/binfmt_flat.c:293: warning: label ‘out’ defined but not used
> fs/binfmt_flat.c: In function ‘load_flat_file’:
> fs/binfmt_flat.c:462: warning: format ‘%x’ expects type ‘unsigned int’,
> but argument 3 has type ‘long int’
> fs/binfmt_flat.c:462: warning: format ‘%x’ expects type ‘unsigned int’,
> but argument 4 has type ‘long int’
> fs/binfmt_flat.c:549: warning: passing argument 1 of ‘ksize’ makes
> pointer from integer without a cast
> fs/binfmt_flat.c:601: warning: passing argument 1 of ‘ksize’ makes
> pointer from integer without a cast
> fs/binfmt_flat.c:760:50: error: macro "flat_get_addr_from_rp" requires 4
> arguments, but only 3 given
> fs/binfmt_flat.c:760: error: ‘flat_get_addr_from_rp’ undeclared (first
> use in this function)
> fs/binfmt_flat.c:760: error: (Each undeclared identifier is reported
> only once
> 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
>
> Expected?
>
> Jan
Yes, It should be, because a binfmt_flat patch hacking by blackfin is
not merged by mainline. Please apply the 2 patches in the SVN trunk
uclinux-dist/bfin_patch/lkml_patch/ and you can find the information
about these 2 patches in uclinux-dist/bfin_patch/lkml_patch/README.
Thanks
- Bryan Wu
prev parent reply other threads:[~2007-07-11 2:03 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
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 [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=1184119763.22259.6.camel@roc-desktop \
--to=bryan.wu@analog.com \
--cc=jdi@l4x.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vapier.adi@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox