Vincent Lefevre <[EMAIL PROTECTED]> on Tuesday, March 20, 2007 at 4:44 AM -0800 wrote: >> On Mar 19, 2007, at 10:29 PM, Yves de Champlain wrote: >> >However, configure will always fail looking for malloc.h, so >> >wouldn't it be a good idea to have macports install a dummy >> >malloc.h ? > >> I personally don't think this is a good solution (first of >> all, to what particular problem?). If a configure script is failing >> upon not finding malloc.h I'd say that's a problem with the software >> and should be reported to its authors (upstream, not MacPorts). > >I agree with you. And I think that the dummy malloc.h should be >removed from the cgilib port, in particular because it leads to >build failure for calc: > > http://trac.macosforge.org/projects/macports/ticket/11093 > >(the configure script detects the presence of the dummy malloc.h >provided by the cgilib port, then the build fails because of this, >for an unknown reason).
cgilib was one of the first ports I made. I think I just followed some manual install instructions. I'll patch the port to use stdlib tonight. Thanks for pointing that out, I didn't notice the ticket mentioned cgilib. Mark _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev
