On Thursday 07 June 2007, Jesper Juhl wrote: > On 07/06/07, Mike Frysinger <[email protected]> wrote: > > This patch basically copies the gnulib version of memmem() into > > scripts/kallsyms.c. While a useful function, it isn't in POSIX so some > > systems (like Darwin) choose to omit it. How do others feel ? > > Do people actually build Linux kernels on Darwin & *BSD systems? If > they do then why? in the embedded world, yes ... everything is being cross-compiled and deployed on different hardware anyways, so the build env shouldnt matter > What I'm getting at is; why do we care if it will build there? that was the [rfc] part of the e-mail ... i got enough complaints from people OS X people to put together the patch -mike
Attachment:
signature.asc
Description: This is a digitally signed message part.
- References:
- [patch/rfc] implement memmem() locally in kallsyms.c
- From: Mike Frysinger <[email protected]>
- Re: [patch/rfc] implement memmem() locally in kallsyms.c
- From: "Jesper Juhl" <[email protected]>
- [patch/rfc] implement memmem() locally in kallsyms.c
- Prev by Date: Re: 2.6.22-rc: regression: no irda0 interface (2.6.21 was OK), smsc does not find chip
- Next by Date: Re: Bad behaviour after hdparm -M 128
- Previous by thread: Re: [patch/rfc] implement memmem() locally in kallsyms.c
- Next by thread: Re: [patch/rfc] implement memmem() locally in kallsyms.c
- Index(es):
 |