From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/453 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Is "memory.h" wanted? Date: Tue, 23 Aug 2011 08:17:44 -0400 Message-ID: <20110823121744.GD132@brightrain.aerifal.cx> References: <20110822183710.c2fcfa28.idunham@lavabit.com> <20110823014433.GC132@brightrain.aerifal.cx> <20110823000637.813c40f2.idunham@lavabit.com> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1314101982 16608 80.91.229.12 (23 Aug 2011 12:19:42 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 23 Aug 2011 12:19:42 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-454-gllmg-musl=m.gmane.org@lists.openwall.com Tue Aug 23 14:19:38 2011 Return-path: Envelope-to: gllmg-musl@lo.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by lo.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1Qvpx9-0001T6-FJ for gllmg-musl@lo.gmane.org; Tue, 23 Aug 2011 14:19:35 +0200 Original-Received: (qmail 20189 invoked by uid 550); 23 Aug 2011 12:19:34 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 20181 invoked from network); 23 Aug 2011 12:19:34 -0000 Content-Disposition: inline In-Reply-To: <20110823000637.813c40f2.idunham@lavabit.com> User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:453 Archived-At: On Tue, Aug 23, 2011 at 12:06:37AM -0700, Isaac Dunham wrote: > On Mon, 22 Aug 2011 21:44:33 -0400 > Rich Felker wrote: > > > On Mon, Aug 22, 2011 at 06:37:10PM -0700, Isaac Dunham wrote: > > > I recently tried building OpenSSL, and it failed to build due to a > > > missing "memory.h". > > > > Which, IIRC, means a BSD-flavored/other legacy string.h > > > Is this header desired for compatability, or should code using it be considered > > > non-conformant and patched? > > > > Probably both, i.e. we should add it and OpenSSL should be patched. In > > the long term I'm thinking about adding #warning to all of the > > nonsensical legacy headers and wrong-location headers (missing sys/- > > prefix or incorrect sys/- prefix) to help track down and correct such > > errors in programs. > I had assumed the header wanted was a libc header; however, when I > looked up memory.h, the recommended header to use was a *private* > kernel header (not one of the cleaned headers). There was talk about Where did this information come from? The *only* thing "memory.h" is for is memcpy, memset, etc. which belong in string.h and have always been in string.h. The whole "memory.h" thing was some BSD nonsense, probably because they preferred their bzero, bcopy, etc. interfaces and were bitter than mem* was adopted by ANSI/ISO C. Rich