linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: DENX ELDK Kernel
Date: Tue, 15 Jul 2003 16:16:03 +0200	[thread overview]
Message-ID: <20030715141608.A765AC6D82@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 15 Jul 2003 16:01:12 +0200." <3F140928.60403@imc-berlin.de>


In message <3F140928.60403@imc-berlin.de> you wrote:
>
> If I'd built the ELDK from scratch and used Linux-2.4.20 include files
> to build "glibc (and all the rest of the target ELDK apps)" I should
> build my "applications against the newer Linux kernel"! Shouldn't I?

Yes.

> And in general: shouldn't I used a glibc that "matches" the kernel
> version?

If you want to be absolutely safe, yes. But so far we have  not  seen
any  real  problems when - for example - running the 2.4.4 built libs
and tools on a 2.4.20+ kernel.

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
God may be subtle, but He isn't plain mean.         - Albert Einstein

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-07-15 14:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15 13:06 DENX ELDK Kernel Brian Padalino
2003-07-15 13:21 ` Wolfgang Denk
2003-07-15 13:41 ` Jeff Kowing
2003-07-15 13:51   ` Wolfgang Denk
2003-07-15 14:01     ` Steven Scholz
2003-07-15 14:16       ` Wolfgang Denk [this message]
2003-07-15 15:08       ` Jeff Kowing

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=20030715141608.A765AC6D82@atlas.denx.de \
    --to=wd@denx.de \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=steven.scholz@imc-berlin.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).