<?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: Building TRB on CentOS 6.9, Notes on a Few Gotchas</title>
	<atom:link href="http://ztkfg.com/2020/07/building-trb-on-centos-69-notes-on-a-few-gotchas/feed/" rel="self" type="application/rss+xml" />
	<link>http://ztkfg.com/2020/07/building-trb-on-centos-69-notes-on-a-few-gotchas/</link>
	<description>198.211.113.164 // 6326 273B 61A7 00AF 4CD9 5A7B 8C6C AB19 24A6 4DEC</description>
	<pubDate>Tue, 21 Apr 2026 11:51:32 +0000</pubDate>
	<generator>http://polimedia.us</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: whaack</title>
		<link>http://ztkfg.com/2020/07/building-trb-on-centos-69-notes-on-a-few-gotchas/#comment-318</link>
		<dc:creator>whaack</dc:creator>
		<pubDate>Tue, 14 Jul 2020 21:49:07 +0000</pubDate>
		<guid isPermaLink="false">http://ztkfg.com/?p=472#comment-318</guid>
		<description>I actually wound up "successfully" building trb with jfw's patch on centos 6.9. From my understanding, since I built on a potentially "dirty" OS, my trb may have a dependency  whose binary-in-use differs from the expected ones that come from either building w/ rotor or building on Gales w/ jfw's patch.</description>
		<content:encoded><![CDATA[<p>I actually wound up "successfully" building trb with jfw's patch on centos 6.9. From my understanding, since I built on a potentially "dirty" OS, my trb may have a dependency  whose binary-in-use differs from the expected ones that come from either building w/ rotor or building on Gales w/ jfw's patch.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robinson Dorion</title>
		<link>http://ztkfg.com/2020/07/building-trb-on-centos-69-notes-on-a-few-gotchas/#comment-317</link>
		<dc:creator>Robinson Dorion</dc:creator>
		<pubDate>Tue, 14 Jul 2020 17:40:46 +0000</pubDate>
		<guid isPermaLink="false">http://ztkfg.com/?p=472#comment-317</guid>
		<description>So in the end did you build trb with rotor ?</description>
		<content:encoded><![CDATA[<p>So in the end did you build trb with rotor ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacob Welsh</title>
		<link>http://ztkfg.com/2020/07/building-trb-on-centos-69-notes-on-a-few-gotchas/#comment-315</link>
		<dc:creator>Jacob Welsh</dc:creator>
		<pubDate>Sat, 11 Jul 2020 15:31:43 +0000</pubDate>
		<guid isPermaLink="false">http://ztkfg.com/?p=472#comment-315</guid>
		<description>Thanks for clarifying. I'll note my Gales bootstrap procedure establishes a minimal process environment, inheriting external variables by whitelist only, and thus wouldn't trip up on weird LD_LIBRARY_PATH and such. Ofc it's not a drop-in replacement for 'rotor' at present, but that might make an interesting project, perhaps once Gales itself is a bit more V conforming.

When I get to doing a full TRB fetch &#38; build script I might see if I can reproduce the python thing on a CentOS 6, as I'd rather it work if the fix is simple enough. Ultimately though this will be a losing battle at least until the &lt;a href="http://trilema.com/2020/forum-logs-for-22-jun-2019/#2540964" rel="nofollow"&gt;excess&lt;/a&gt; autoconf &lt;a href="http://trilema.com/2020/forum-logs-for-22-jun-2019/#2540990" rel="nofollow"&gt;DWIMism&lt;/a&gt; is removed from those Big Three dependencies - preferably by integrating the necessary parts into the TRB tree proper.</description>
		<content:encoded><![CDATA[<p>Thanks for clarifying. I'll note my Gales bootstrap procedure establishes a minimal process environment, inheriting external variables by whitelist only, and thus wouldn't trip up on weird LD_LIBRARY_PATH and such. Ofc it's not a drop-in replacement for 'rotor' at present, but that might make an interesting project, perhaps once Gales itself is a bit more V conforming.</p>
<p>When I get to doing a full TRB fetch &amp; build script I might see if I can reproduce the python thing on a CentOS 6, as I'd rather it work if the fix is simple enough. Ultimately though this will be a losing battle at least until the <a href="http://trilema.com/2020/forum-logs-for-22-jun-2019/#2540964" rel="nofollow">excess</a> autoconf <a href="http://trilema.com/2020/forum-logs-for-22-jun-2019/#2540990" rel="nofollow">DWIMism</a> is removed from those Big Three dependencies - preferably by integrating the necessary parts into the TRB tree proper.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: whaack</title>
		<link>http://ztkfg.com/2020/07/building-trb-on-centos-69-notes-on-a-few-gotchas/#comment-312</link>
		<dc:creator>whaack</dc:creator>
		<pubDate>Thu, 09 Jul 2020 00:53:07 +0000</pubDate>
		<guid isPermaLink="false">http://ztkfg.com/?p=472#comment-312</guid>
		<description>@Jacob Welsh.

Ah yes. Thank you for pointing this out, the first error I received related to LD_LIBRARY_PATH was when I tried to build trb without your two patches.</description>
		<content:encoded><![CDATA[<p>@Jacob Welsh.</p>
<p>Ah yes. Thank you for pointing this out, the first error I received related to LD_LIBRARY_PATH was when I tried to build trb without your two patches.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacob Welsh</title>
		<link>http://ztkfg.com/2020/07/building-trb-on-centos-69-notes-on-a-few-gotchas/#comment-311</link>
		<dc:creator>Jacob Welsh</dc:creator>
		<pubDate>Wed, 08 Jul 2020 21:12:27 +0000</pubDate>
		<guid isPermaLink="false">http://ztkfg.com/?p=472#comment-311</guid>
		<description>But you couldn't have been running with my system_compiler patch in this case, otherwise there wouldn't be buildroot messages, no?

The "sane environment required" does seem a bit of a cop-out. One could make a list of systems know to work by starting from fresh installs.</description>
		<content:encoded><![CDATA[<p>But you couldn't have been running with my system_compiler patch in this case, otherwise there wouldn't be buildroot messages, no?</p>
<p>The "sane environment required" does seem a bit of a cop-out. One could make a list of systems know to work by starting from fresh installs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: whaack</title>
		<link>http://ztkfg.com/2020/07/building-trb-on-centos-69-notes-on-a-few-gotchas/#comment-310</link>
		<dc:creator>whaack</dc:creator>
		<pubDate>Wed, 08 Jul 2020 16:35:07 +0000</pubDate>
		<guid isPermaLink="false">http://ztkfg.com/?p=472#comment-310</guid>
		<description>From a discussion in #therealbitcoin and rereading jfw's article on the build system overhaul for bitcoind, I realized that I had missed the point where the operator of jfw's build overhaul vpatch is expected to have a "sane environment." My local centOS 6.9 does not make the cut. Without jfw's patch I may have been able to successfully build boost without having to switch my python version.

http://logs.nosuchlabs.com/log/therealbitcoin/2020-07-08#1000784</description>
		<content:encoded><![CDATA[<p>From a discussion in #therealbitcoin and rereading jfw's article on the build system overhaul for bitcoind, I realized that I had missed the point where the operator of jfw's build overhaul vpatch is expected to have a "sane environment." My local centOS 6.9 does not make the cut. Without jfw's patch I may have been able to successfully build boost without having to switch my python version.</p>
<p><a href="http://logs.nosuchlabs.com/log/therealbitcoin/2020-07-08#1000784" rel="nofollow">http://logs.nosuchlabs.com/log/therealbitcoin/2020-07-08#1000784</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
