<?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: C, headers</title>
	<atom:link href="http://blog.milkfarmsoft.com/2008/07/c-headers/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.milkfarmsoft.com/2008/07/c-headers/</link>
	<description>Programming for Mac and Web</description>
	<lastBuildDate>Thu, 04 Aug 2011 07:10:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
<atom:link rel="hub" href="http://pubsubhubbub.appspot.com" />
	<atom:link rel="hub" href="http://superfeedr.com/hubbub" />
		<item>
		<title>By: Stuart Herbert</title>
		<link>http://blog.milkfarmsoft.com/2008/07/c-headers/comment-page-1/#comment-51447</link>
		<dc:creator>Stuart Herbert</dc:creator>
		<pubDate>Mon, 14 Jul 2008 08:06:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.milkfarmsoft.com/?p=84#comment-51447</guid>
		<description>Hi Alexey,

You&#039;re trying to fight decades of UNIX tradition here :(  Two options that are useful:

1) Run separate chroot environments for each of your different build combinations.  Takes time to setup, and eats disk space, but once setup, they are less frustrating than trying to mix and match the way you are.
2) Run separate Xen based virtual machines for each of your different build combinations :)

Hope that helps,
Stu</description>
		<content:encoded><![CDATA[<p>Hi Alexey,</p>
<p>You&#8217;re trying to fight decades of UNIX tradition here <img src='http://blog.milkfarmsoft.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' />   Two options that are useful:</p>
<p>1) Run separate chroot environments for each of your different build combinations.  Takes time to setup, and eats disk space, but once setup, they are less frustrating than trying to mix and match the way you are.<br />
2) Run separate Xen based virtual machines for each of your different build combinations <img src='http://blog.milkfarmsoft.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Hope that helps,<br />
Stu</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: indeyets</title>
		<link>http://blog.milkfarmsoft.com/2008/07/c-headers/comment-page-1/#comment-51034</link>
		<dc:creator>indeyets</dc:creator>
		<pubDate>Fri, 11 Jul 2008 04:43:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.milkfarmsoft.com/?p=84#comment-51034</guid>
		<description>autotools work on other level. They help to locate headers and libraries, but in the end, I still will be left with:

&quot;gcc -I/sw/include -I/usr/include …&quot;

and if for compilation of this exact file I need 1 file from /usr, other from /sw, but similiar (but other versions) files exist in both package-roots I will end with both files from /sw used, and autotools won&#039;t be able to help me</description>
		<content:encoded><![CDATA[<p>autotools work on other level. They help to locate headers and libraries, but in the end, I still will be left with:</p>
<p>&#8220;gcc -I/sw/include -I/usr/include …&#8221;</p>
<p>and if for compilation of this exact file I need 1 file from /usr, other from /sw, but similiar (but other versions) files exist in both package-roots I will end with both files from /sw used, and autotools won&#8217;t be able to help me</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay Pipes</title>
		<link>http://blog.milkfarmsoft.com/2008/07/c-headers/comment-page-1/#comment-51029</link>
		<dc:creator>Jay Pipes</dc:creator>
		<pubDate>Fri, 11 Jul 2008 03:19:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.milkfarmsoft.com/?p=84#comment-51029</guid>
		<description>&quot;Anyway, FHS doesn’t help in resolution of conflicting C-libraries&quot;

True, but what about using autotools?  Surely the AC_ macros can work some wonders here?  Not the easiest or most intuitive to learn, but I bet they&#039;d be able to solve much of these problems...

Cheers!

-jay</description>
		<content:encoded><![CDATA[<p>&#8220;Anyway, FHS doesn’t help in resolution of conflicting C-libraries&#8221;</p>
<p>True, but what about using autotools?  Surely the AC_ macros can work some wonders here?  Not the easiest or most intuitive to learn, but I bet they&#8217;d be able to solve much of these problems&#8230;</p>
<p>Cheers!</p>
<p>-jay</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: indeyets</title>
		<link>http://blog.milkfarmsoft.com/2008/07/c-headers/comment-page-1/#comment-50708</link>
		<dc:creator>indeyets</dc:creator>
		<pubDate>Tue, 08 Jul 2008 17:18:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.milkfarmsoft.com/?p=84#comment-50708</guid>
		<description>Bill: it doesn&#039;t really help, if you need to manage independent package-roots.

FHS is good for end-users and for developers of single-packages.

Anyway, FHS doesn&#039;t help in resolution of conflicting C-libraries</description>
		<content:encoded><![CDATA[<p>Bill: it doesn&#8217;t really help, if you need to manage independent package-roots.</p>
<p>FHS is good for end-users and for developers of single-packages.</p>
<p>Anyway, FHS doesn&#8217;t help in resolution of conflicting C-libraries</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Karwin</title>
		<link>http://blog.milkfarmsoft.com/2008/07/c-headers/comment-page-1/#comment-50704</link>
		<dc:creator>Bill Karwin</dc:creator>
		<pubDate>Tue, 08 Jul 2008 16:26:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.milkfarmsoft.com/?p=84#comment-50704</guid>
		<description>You should check out the Filesystem Hierarchy Standard (http://proton.pathname.com/fhs/pub/fhs-2.3.html).  It might help you manage the software more easily if you follow the guidelines in that standard.</description>
		<content:encoded><![CDATA[<p>You should check out the Filesystem Hierarchy Standard (<a href="http://proton.pathname.com/fhs/pub/fhs-2.3.html" rel="nofollow">http://proton.pathname.com/fhs/pub/fhs-2.3.html</a>).  It might help you manage the software more easily if you follow the guidelines in that standard.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: indeyets</title>
		<link>http://blog.milkfarmsoft.com/2008/07/c-headers/comment-page-1/#comment-50679</link>
		<dc:creator>indeyets</dc:creator>
		<pubDate>Tue, 08 Jul 2008 10:40:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.milkfarmsoft.com/?p=84#comment-50679</guid>
		<description>thanks, Adriano. fixed</description>
		<content:encoded><![CDATA[<p>thanks, Adriano. fixed</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adriano</title>
		<link>http://blog.milkfarmsoft.com/2008/07/c-headers/comment-page-1/#comment-50678</link>
		<dc:creator>Adriano</dc:creator>
		<pubDate>Tue, 08 Jul 2008 10:37:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.milkfarmsoft.com/?p=84#comment-50678</guid>
		<description>Good post, man. Only one thing: you write &quot;complexity arouses&quot;. &#039;arouses&#039; doesn&#039;t mean what you think. It especially doesn&#039;t mean &quot;arises&quot;.</description>
		<content:encoded><![CDATA[<p>Good post, man. Only one thing: you write &#8220;complexity arouses&#8221;. &#8216;arouses&#8217; doesn&#8217;t mean what you think. It especially doesn&#8217;t mean &#8220;arises&#8221;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

