linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Lo Chun Chung <lcsquare2@yahoo.com.hk>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Can ELDK 3.1.1 compile Linux 2.6 Kernel?
Date: Wed, 11 Jan 2006 21:37:25 +0100	[thread overview]
Message-ID: <20060111203725.28A82352B1E@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 11 Jan 2006 16:36:57 +0800." <20060111083657.77699.qmail@web53707.mail.yahoo.com>

In message <20060111083657.77699.qmail@web53707.mail.yahoo.com> you wrote:
> 
>   I just downloaded ELDK 3.1.1 (from denx) and LINUX kernel 2.6 (from kernel.org), and I compile the kernel for powerpc arch.
>    
>   but during I compile to the file under the directory vdso32, the following compile errors occur:
>    
>   arch/powerpc/kernel/vdso32/gettimeofday.S: Assembler messages:
>   arch/powerpc/kernel/vdso32/gettimeofday.S:28: Error: unknown pseudo-op: `.cfi_startproc'
...

Yes, they changed the Linux kernel such that it  cannot  be  compiled
any more using binutils version 2.14 which is used in ELDK 3.x

>   What's wrong with my compiler? Or ELDK cannot compile 2.6 kernel? What I can do now?

Please wait until the end of the week, then download ELDK  4.0,  then
be happy ;-)

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"To IBM, 'open' means there is a modicum  of  interoperability  among
some of their equipment."                            - Harv Masterson

  reply	other threads:[~2006-01-11 20:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-11  8:36 Can ELDK 3.1.1 compile Linux 2.6 Kernel? Lo Chun Chung
2006-01-11 20:37 ` Wolfgang Denk [this message]
2006-01-12  6:10   ` Lo Chun Chung
2006-01-13  6:18 ` Ron Kellam

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=20060111203725.28A82352B1E@atlas.denx.de \
    --to=wd@denx.de \
    --cc=lcsquare2@yahoo.com.hk \
    --cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).