All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Scholz <steven.scholz@imc-berlin.de>
To: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: ELDK 2.0, glibc and kernel 2.4.20???
Date: Tue, 12 Nov 2002 13:58:47 +0100	[thread overview]
Message-ID: <3DD0FB07.D624FC40@imc-berlin.de> (raw)
In-Reply-To: 3DB4BE6200027CEE@mss3n.bluewin.ch


> >Hi guys, Hi Wolfgang,
> >
> >I am using ELDK 1.0 for development. Thanks for that great tool chain!
> >
> >Now I want to switch from 1.0 to version 2.
> >
> >Do I have to rebuild the glibc comming with the ELDK 2.0 to use it with
> a
> >2.4.19/20 kernel instead of the 2.4.4 that comes with this kit?
>
> This is normally not necessary. So far we have not realized any problems
>
> with 2.4.19 kernels. BTW: it´s the same dilemma with ELDK 1.0.
>

I know. I did once. And I don't want to do it again! :o)

Let's say I want to use the O_DIRECT feature with files. Of course O_DIRECT is
not defined in 2.4.4 but in 2.4.19.

So would it be enough to define the flag O_DIRECT in my application?
Since all that glibc does is passing the flags to the kernel while opening a
file, doesn't it?

Cheers,

Steven

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

      reply	other threads:[~2002-11-12 12:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-12  8:12 ELDK 2.0, glibc and kernel 2.4.20??? Steven Scholz
2002-11-12  9:40 ` ppc_8xx-gcc 2.95.3 Monta Vista does not do ANY loop unrolling Joakim Tjernlund
2002-11-12 15:22   ` Tom Rini
2002-11-12 16:09     ` Joakim Tjernlund
2002-11-12 16:25       ` Tom Rini
2002-11-12 16:46         ` Joakim Tjernlund
2002-11-12 18:40           ` Tom Rini
2002-11-12 21:30             ` Joakim Tjernlund
2002-11-12 19:56           ` Mark Hatle
2002-11-12 21:33             ` Joakim Tjernlund
2002-11-12 12:39 ` ELDK 2.0, glibc and kernel 2.4.20??? wolfgang.grandegger
2002-11-12 12:58   ` Steven Scholz [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=3DD0FB07.D624FC40@imc-berlin.de \
    --to=steven.scholz@imc-berlin.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.