From: Wolfgang Denk <wd@denx.de>
To: Jeff Stevens <JStevens@SYSTRAN.com>
Cc: "'linuxppc-embedded@lists.linuxppc.org'"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: ELDK based on YDL 3.0?
Date: Thu, 13 Nov 2003 17:46:33 +0100 [thread overview]
Message-ID: <20031113164638.3336BC5F59@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 13 Nov 2003 10:04:02 EST." <D13FBFDEA70AD111A44900A0C92316930350B757@postoffice.systran.com>
In message <D13FBFDEA70AD111A44900A0C92316930350B757@postoffice.systran.com> you wrote:
>
> I am currentlly using ELDK v2.1.0 and am wanting to update to kernel
> 2.4.22. I need to update to 2.4.22 for an openIPMI patch that I have. I
That should be no problem. Except for a few rare situations the
kernel is completely independend of the tool chain and userland
applications.
> tried compiling the PPC 2.4.22 kernel, but it complains about the libarg.h
> file missing. I think this is becuase the version of ppc_8xx-gcc in ELDK
> v2.1.0 is too old for the kernel rev 2.4.22. Is that correct? I'd rather
No, this is not correct. We're using the "old" (2.1) ELDK for
production all the time, including latest kernel versions.
> just wait, if you are close to releasing a new version of ELDK.
Don't wait. The problem might not be in the ELDK but somwhere else.
libarg.h? Never heard of that. Which file attempts to include this?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
You cannot propel yourself forward by patting yourself on the back.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2003-11-13 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D13FBFDEA70AD111A44900A0C92316930350B757@postoffice.systran.com>
2003-11-13 16:46 ` Wolfgang Denk [this message]
2003-11-12 18:32 ELDK based on YDL 3.0? Jeff Stevens
2003-11-12 19:41 ` Wolfgang Denk
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=20031113164638.3336BC5F59@atlas.denx.de \
--to=wd@denx.de \
--cc=JStevens@SYSTRAN.com \
--cc=linuxppc-embedded@lists.linuxppc.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