Comments on: Building TRB on a 2022 Vintage Musl Gentoo http://billymg.com/2022/01/building-trb-on-a-2022-vintage-musl-gentoo/ Mon, 13 Apr 2026 18:23:22 +0000 http://polimedia.us hourly 1 By: A Beginner's Guide to Installing Gentoo: Part One « billymg http://billymg.com/2022/01/building-trb-on-a-2022-vintage-musl-gentoo/comment-page-1/#comment-515 A Beginner's Guide to Installing Gentoo: Part One « billymg Sat, 12 Mar 2022 16:51:40 +0000 http://billymg.com/?p=85#comment-515 [...] Building TRB on a 2022 Vintage Musl Gentoo [...] [...] Building TRB on a 2022 Vintage Musl Gentoo [...]

]]> By: Jacob Welsh http://billymg.com/2022/01/building-trb-on-a-2022-vintage-musl-gentoo/comment-page-1/#comment-499 Jacob Welsh Thu, 03 Feb 2022 20:00:30 +0000 http://billymg.com/?p=85#comment-499 Cheers. Spending some time getting to know http://fixpoint.welshcomputing.com/2022/the-simplest-way-yet-to-fetch-bitcoin-code/ may be helpful for that guide of yours; at least in my view it's a game-changer. I suppose it would depend on your evaluation of the classical vtrons and their dependencies. Cheers. Spending some time getting to know http://fixpoint.welshcomputing.com/2022/the-simplest-way-yet-to-fetch-bitcoin-code/ may be helpful for that guide of yours; at least in my view it's a game-changer. I suppose it would depend on your evaluation of the classical vtrons and their dependencies.

]]> By: billymg http://billymg.com/2022/01/building-trb-on-a-2022-vintage-musl-gentoo/comment-page-1/#comment-498 billymg Mon, 31 Jan 2022 23:11:58 +0000 http://billymg.com/?p=85#comment-498 Thank you for the clarifications and for the links to the new patches. Cool stuff with the Boost build trimming, seems like a big win. I'll try them out as soon as I get a chance and publish my results. As I mentioned in the article, I'm working on a guide that even users new to linux can follow in order to build a working TRB machine. Any patches that make that process faster and/or easier would definitely be helpful so I appreciate the note. Thank you for the clarifications and for the links to the new patches. Cool stuff with the Boost build trimming, seems like a big win. I'll try them out as soon as I get a chance and publish my results.

As I mentioned in the article, I'm working on a guide that even users new to linux can follow in order to build a working TRB machine. Any patches that make that process faster and/or easier would definitely be helpful so I appreciate the note.

]]> By: Jacob Welsh http://billymg.com/2022/01/building-trb-on-a-2022-vintage-musl-gentoo/comment-page-1/#comment-497 Jacob Welsh Mon, 31 Jan 2022 00:55:51 +0000 http://billymg.com/?p=85#comment-497 Congrats on getting this far in the swamps. I had another couple patches out that may be of interest including <a href="http://fixpoint.welshcomputing.com/2021/a-tetrad-of-tuneups-for-bitcoind/?b=bitcoin_boost_prune_built_libs&e=#select" rel="nofollow">one that resolves the python thing</a> at the root (that it was touching python at all was a bug in my view). It should have pinged back to whaack's report too, if only *that* functionality weren't so thoroughly broken. > I'm not sure why I only bumped into this now, considering the function was first added to GCC all the way back at version 4.7.0. Yeah. Just from the context in the linked patch it looks like it was named deliberately to fill in the gap for *older* gccs where the builtin wasn't available. So I'm guessing it's some ifdef/autoconfiguration tangle that's failed for whatever reason on the verschlimmbessert system and that would be the level to look at, if it's worth looking at all. FWIW, in the build on Gales I do get a series of "warning: conflicting types for built-in function '__atomic_compare_exchange'" coming from dbinc/atomic.h:179. It's also mildly bothersome that an external Boost is getting mixed into things at all. Possibly it's getting headers from /usr/include and linking libraries from the shipped version, or vice versa - rather asking for trouble. Congrats on getting this far in the swamps.

I had another couple patches out that may be of interest including one that resolves the python thing at the root (that it was touching python at all was a bug in my view). It should have pinged back to whaack's report too, if only *that* functionality weren't so thoroughly broken.

> I'm not sure why I only bumped into this now, considering the function was first added to GCC all the way back at version 4.7.0.

Yeah. Just from the context in the linked patch it looks like it was named deliberately to fill in the gap for *older* gccs where the builtin wasn't available. So I'm guessing it's some ifdef/autoconfiguration tangle that's failed for whatever reason on the verschlimmbessert system and that would be the level to look at, if it's worth looking at all. FWIW, in the build on Gales I do get a series of "warning: conflicting types for built-in function '__atomic_compare_exchange'" coming from dbinc/atomic.h:179.

It's also mildly bothersome that an external Boost is getting mixed into things at all. Possibly it's getting headers from /usr/include and linking libraries from the shipped version, or vice versa - rather asking for trouble.

]]>