Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!ihnp4.ucsd.edu!dog.ee.lbl.gov!agate!howland.reston.ans.net!vixen.cso.uiuc.edu!news.uoregon.edu!usenet.coe.montana.edu!bsd.coe.montana.edu!nate From: nate@bsd.coe.montana.edu (Nate Williams) Newsgroups: comp.unix.bsd Subject: Re: malloc.h? Date: 3 Aug 1994 14:18:24 GMT Organization: Montana State University, Bozeman Montana Lines: 22 Message-ID: <31o8vg$l6k@pdq.coe.montana.edu> References: <31mbpc$8ia@cyberspace.com> NNTP-Posting-Host: 153.90.192.29 In article <31mbpc$8ia@cyberspace.com>, Robert Mobbs <monk@cyberspace.com> wrote: >Thanks for those of you who responded to my request for the olvwm >server. >However, all sources I have found require the <malloc.h> header... >As far as I know, this is not available under BSD. Sure it is, but since 'malloc.h' is non-POSIX, it isn't going to be added to BSD. However, you can either create one that includes 'unistd.h', or FIX your code to not include 'malloc.h'. Obviously, the latter solution is the 'better' in the long run, but for quick and dirty adding a simple malloc.h would do get you by. Nate -- nate@bsd.coe.montana.edu | FreeBSD core member and all around tech. nate@cs.montana.edu | weenie. work #: (406) 994-4836 | home #: (406) 586-0579 | Available for contract/otherwise work.