From: "HappyPhot" <happyphot@gmail.com>
To: "Wolfgang Denk" <wd@denx.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Error: unknown pseudo-op: `.cfi_startproc'
Date: Thu, 29 Dec 2005 17:25:08 +0800 [thread overview]
Message-ID: <002e01c60c59$c8fd6470$0860120a@photon> (raw)
In-Reply-To: 20051228091612.B43D3353A66@atlas.denx.de
> In message <007801c60b72$eb4988c0$0860120a@photon> you wrote:
>>
>> I am using ELDK (2005-06-07) and
>> linux-2.6.15-rc2-2005-12-03-2208.tar.bz2
>> to build the kernel. But there are some errors:
>>
>> .../arch/powerpc/kernel/vdso32/gettimeofday.S: Assembler messages:
>> .../arch/powerpc/kernel/vdso32/gettimeofday.S:28: Error: unknown
>> pseudo-op:
>> `.cfi_startproc'
>> .../arch/powerpc/kernel/vdso32/gettimeofday.S:30: Error: unknown
>> pseudo-op:
>> `.cfi_register'
>> .......
>>
>> Anybody knows what happened ? And is there any way to solve ?
>
> ELDK 3.1 uses binutils-2.14; the current Linux kernel was changed to
> use assembler syntax which is not supported by the GNU assembler in
> this version. See for example
> http://ozlabs.org/pipermail/linuxppc64-dev/2005-February/003179.html
>
> I don't understand why this was done, either. Especially as the
> current Linux kernel documentation ("Documentation/Changes") still
> claims that binutils 2.12 would be sufficient.
>
> You will have to update your toolchain (i. e. use ELDK 4.0) for
> working with current 2.6 kernels.
>
> Best regards,
>
> Wolfgang Denk
Hi,
Is there any "ready to burn" iso image of ELDK 4.0
available for download ? I cannot find one.
thank you,
/HappyPhot
prev parent reply other threads:[~2005-12-29 9:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-28 5:52 Error: unknown pseudo-op: `.cfi_startproc' HappyPhot
2005-12-28 9:16 ` Wolfgang Denk
2005-12-29 9:25 ` HappyPhot [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='002e01c60c59$c8fd6470$0860120a@photon' \
--to=happyphot@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=wd@denx.de \
/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;
as well as URLs for NNTP newsgroup(s).