<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: GNUMake 3.80 and failed malloc</title>
	<atom:link href="http://blog.yimingliu.com/2008/09/16/gnumake-380-and-failed-malloc/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.yimingliu.com/2008/09/16/gnumake-380-and-failed-malloc/</link>
	<description>source control for my (useless) knowledge</description>
	<lastBuildDate>Wed, 18 Aug 2010 00:32:33 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: yiming</title>
		<link>http://blog.yimingliu.com/2008/09/16/gnumake-380-and-failed-malloc/comment-page-1/#comment-36</link>
		<dc:creator>yiming</dc:creator>
		<pubDate>Fri, 14 Nov 2008 04:56:00 +0000</pubDate>
		<guid isPermaLink="false">https://blog.yimingliu.com/2008/09/16/gnumake-380-and-failed-malloc/#comment-36</guid>
		<description>Are you on Xcode 2.4 on Tiger?  Are you compiling within an Xcode project?  Or separately on the command-line?&lt;br/&gt;&lt;br/&gt;For compiling within Xcode 2.4 on Tiger, there should only be one copy of gnumake - the one in /usr/bin.  If you are in fact using a Makefile, this implies you&#039;re using the external build function of Xcode, since Xcode itself has its own build system.  In this case, check your Project&#039;s Target(s) and overall Project configuration, and make sure it specifies the appropriate custom-compile script.  &lt;br/&gt;&lt;br/&gt;If you are compiling on the command-line, check your path and make sure the make being picked up is the new make you installed.  &quot;which make&quot; should show you the path being picked up, and &quot;make --version&quot; should show you the version used.&lt;br/&gt;&lt;br/&gt;For Xcode 3.0 on Leopard, there&#039;s another copy of gnumake in /Developer/usr/bin, which is used by the dev tools.  But Leopard should ship with GNU Make 3.81, so your particular problem in that case might be elsewhere.</description>
		<content:encoded><![CDATA[<p>Are you on Xcode 2.4 on Tiger?  Are you compiling within an Xcode project?  Or separately on the command-line?</p>
<p>For compiling within Xcode 2.4 on Tiger, there should only be one copy of gnumake &#8211; the one in /usr/bin.  If you are in fact using a Makefile, this implies you&#8217;re using the external build function of Xcode, since Xcode itself has its own build system.  In this case, check your Project&#8217;s Target(s) and overall Project configuration, and make sure it specifies the appropriate custom-compile script.  </p>
<p>If you are compiling on the command-line, check your path and make sure the make being picked up is the new make you installed.  &#8220;which make&#8221; should show you the path being picked up, and &#8220;make &#8211;version&#8221; should show you the version used.</p>
<p>For Xcode 3.0 on Leopard, there&#8217;s another copy of gnumake in /Developer/usr/bin, which is used by the dev tools.  But Leopard should ship with GNU Make 3.81, so your particular problem in that case might be elsewhere.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://blog.yimingliu.com/2008/09/16/gnumake-380-and-failed-malloc/comment-page-1/#comment-35</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Fri, 14 Nov 2008 04:33:00 +0000</pubDate>
		<guid isPermaLink="false">https://blog.yimingliu.com/2008/09/16/gnumake-380-and-failed-malloc/#comment-35</guid>
		<description>How do you get Xcode to recognize a new version of make?&lt;br/&gt;&lt;br/&gt;Simply replacing /usr/bin/make doesn&#039;t seem to have fixed my malloc crash.&lt;br/&gt;&lt;br/&gt;Thanks for the help!</description>
		<content:encoded><![CDATA[<p>How do you get Xcode to recognize a new version of make?</p>
<p>Simply replacing /usr/bin/make doesn&#8217;t seem to have fixed my malloc crash.</p>
<p>Thanks for the help!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
