shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

255
active users

#autotools

0 posts0 participants0 posts today
argv minus one<p>It's been a while since I ran a build with <a href="https://mastodon.sdf.org/tags/autoconf" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>autoconf</span></a> / <a href="https://mastodon.sdf.org/tags/autotools" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>autotools</span></a>. I had forgotten just how many different little things it checks for.</p><p>One of the main things it's checking for is whether certain headers and functions exist. That reminds me: <a href="https://mastodon.sdf.org/tags/Rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Rust</span></a> `cfg` directives really ought to allow a predicate of “such-and-such function/type/whatever exists”. Then you can, for example, call a libc function that exists only on platforms that have it, with fallback on platforms that don't.</p>
Kornel<p>Seriously, in retrospect, <a href="https://mastodon.social/tags/autotools" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>autotools</span></a> itself is a massive supply-chain security risk.</p><p>It has normalized shipping and running tens of thousands of lines of arbitrary executable code without any safeguards.</p><p>Code that is so mind-numbingly awful that nobody will review it, and written in a language that is full of gotchas that are sneaky eval gadgets.</p>
Felix Palmen 📯<p>Today's progress on <a href="https://techhub.social/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FreeBSD</span></a> <a href="https://techhub.social/tags/Linuxulator" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linuxulator</span></a> "userland from source" project: We have build systems! 🥳 </p><p>Supported now (apart of plain <a href="https://techhub.social/tags/make" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>make</span></a>): GNU <a href="https://techhub.social/tags/autotools" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>autotools</span></a> (including <a href="https://techhub.social/tags/autoreconf" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>autoreconf</span></a>), <a href="https://techhub.social/tags/cmake" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cmake</span></a>, <a href="https://techhub.social/tags/meson" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>meson</span></a> and <a href="https://techhub.social/tags/ninja" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ninja</span></a>!</p><p>They're all supported with their original <a href="https://techhub.social/tags/ports" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ports</span></a> "USES", by some <a href="https://techhub.social/tags/bmake" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bmake</span></a> trickery in my new "USES=linuxsrc", fixing up just the parts that are different when building from/for the Linuxulator (like adjusting dependencies and commands to use the <a href="https://techhub.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a>-native versions).</p><p>Ok, no <a href="https://techhub.social/tags/scons" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>scons</span></a> yet, didn't need it so far 🙈</p>