linux-kernel - Re: [patch/rfc] implement memmem() locally in kallsyms.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200706071144.50242.vapier@gentoo.org>
Date:	Thu, 7 Jun 2007 11:44:49 -0400
From:	Mike Frysinger <vapier@...too.org>
To:	"Jesper Juhl" <jesper.juhl@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [patch/rfc] implement memmem() locally in kallsyms.c

On Thursday 07 June 2007, Jesper Juhl wrote:
> On 07/06/07, Mike Frysinger <vapier@...too.org> 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

Download attachment "signature.asc " of type "application/pgp-signature" (828 bytes)