Noc.Social

argv minus oneIt's been a while since I ran a build with <a href="https://mastodon.sdf.org/tags/autoconf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#autoconf</a> / <a href="https://mastodon.sdf.org/tags/autotools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#autotools</a>. I had forgotten just how many different little things it checks for.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 noreferrer" target="_blank">#Rust</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.

Abbie Normalsay I need a build system for a projectsuch build system needs to be able to check if some libraries/features are available on the target OSmy project is written in an interpeted high level language but it calls some C libssay I don't want to use the autotools but I'd like my build system to be FLOSSwhat are my options ?<a href="https://floss.social/tags/buildsystem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#buildsystem</a> <a href="https://floss.social/tags/Autotools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Autotools</a>

:rss: Qiita - 人気の記事XZ Utils backdoor (CVE-2024-3094) 解説 <a href="https://qiita.com/naokiwa/items/203f558f5dd2a999b862?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items" rel="nofollow noopener noreferrer" target="_blank">https://qiita.com/naokiwa/items/203f558f5dd2a999b862?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items</a><a href="https://rss-mstdn.studiofreesia.com/tags/qiita" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#qiita</a> <a href="https://rss-mstdn.studiofreesia.com/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://rss-mstdn.studiofreesia.com/tags/xz" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#xz</a> <a href="https://rss-mstdn.studiofreesia.com/tags/sshd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sshd</a> <a href="https://rss-mstdn.studiofreesia.com/tags/autotools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#autotools</a> <a href="https://rss-mstdn.studiofreesia.com/tags/lzma" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#lzma</a>

0xC0DEC0DE07E9So, if my goal is just to restore autotools happy-path of `./configure && make && make install` I need maybe ten lines of shell including the explainer blurb. If my goal is to create the best and universally-loved and appreciated one true CMake wrapper - a thing that is both normal to want and possible to achieve - then I need Python with custom `argparse.Action`s and some sort of reality-distortion field to avoid bike-shedding and yak-shaving. <a href="https://hachyderm.io/tags/CMake" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CMake</a> <a href="https://hachyderm.io/tags/autotools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#autotools</a>

0xC0DEC0DE07E9Autotools-skeuomorphic Makefile is super easy. Corresponding configure script still in progress; doing that in Python. Then it finally occurred to me that one of the stumbling blocks is that autotools configure is stateless - it blows away the old configuration every time - where CMake keeps its configuration state and lets you mutate it incrementally. Now I need to wonder if my skeuomorphic configure script should blow away the build/binary directory each run… <a href="https://hachyderm.io/tags/CMake" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CMake</a> <a href="https://hachyderm.io/tags/autotools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#autotools</a>

dstuGot side-tracked on a project where step 1 is converting something from Autotools to Bazel. The lack of a sufficiently functional "make install" in Bazel is disappointing but not surprising, and I'll just live with that for now. Shell scripts won't save us, but they'll get us where we want to go until there's time to build something better. (Writing Starlark rules is not very fun.)<a href="https://mastodon.sdf.org/tags/autotools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#autotools</a> <a href="https://mastodon.sdf.org/tags/make" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#make</a> <a href="https://mastodon.sdf.org/tags/bazel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bazel</a> <a href="https://mastodon.sdf.org/tags/rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rust</a> <a href="https://mastodon.sdf.org/tags/clang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#clang</a>

LY我在想，花在 <a href="https://infosec.exchange/tags/Autotools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Autotools</a> 上的碳排放是多少…一次 ./configure都能花五分钟……

Michal VyskočilMe (being a smart ass): you know <a href="https://witter.cz/tags/autotools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#autotools</a> is an obsolete horrible mess of M4 and shell> This works, because the ./dev.sh build command downloads all the major dependencies of <a href="https://witter.cz/tags/kitty" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#kitty</a> as pre-built binaries for your platform and builds kitty to use these rather than system libraries.Me (a humble version): that's worse somehow ... can I try to turn it off and on again?<a href="https://witter.cz/tags/itcrowd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#itcrowd</a>

David Runge<a href="https://chaos.social/tags/autofools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#autofools</a> is when you can't install files because of concurrency issues 👌Please.... **please** just stop using <a href="https://chaos.social/tags/autotools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#autotools</a> 🥺 <a href="https://chaos.social/tags/ArchLinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ArchLinux</a> <a href="https://chaos.social/tags/PackagerLife" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PackagerLife</a>

रञ्जित (Ranjit Mathew)Sure, but <a href="https://mastodon.social/tags/Windows" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Windows</a> is still an Achilles Heal for the <a href="https://mastodon.social/tags/AutoTools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AutoTools</a>, unless you use <a href="https://mastodon.social/tags/MinGW" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MinGW</a> & <a href="https://mastodon.social/tags/MSYS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MSYS</a>:“What Autoconf Got Right”, Leah Neukirchen (<a href="https://leahneukirchen.org/blog/archive/2024/04/what-autoconf-got-right.html" rel="nofollow noopener noreferrer" target="_blank">https://leahneukirchen.org/blog/archive/2024/04/what-autoconf-got-right.html</a>).Via HN: <a href="https://news.ycombinator.com/item?id=40544336" rel="nofollow noopener noreferrer" target="_blank">https://news.ycombinator.com/item?id=40544336</a>On Lobsters: <a href="https://lobste.rs/s/ebnqzl/what_autoconf_got_right" rel="nofollow noopener noreferrer" target="_blank">https://lobste.rs/s/ebnqzl/what_autoconf_got_right</a><a href="https://mastodon.social/tags/Unix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Unix</a> <a href="https://mastodon.social/tags/Autoconf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Autoconf</a> <a href="https://mastodon.social/tags/Build" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Build</a> <a href="https://mastodon.social/tags/Configure" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Configure</a>

Ada StevensonTrying to wrap my head around the <a href="https://mastodon.social/tags/libtool" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#libtool</a> and <a href="https://mastodon.social/tags/pkgconf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pkgconf</a> vs pkg-config situation. What is going on? Why is libtool bad, what is wrong with .la files, what does libtool do that pkgconf doesn't, and what does pkg-config do that neither of them do?? If anyone seeing this has dealt/is dealing with this linking/tooling situation I'd love to hear your thoughts :) Very curious.<a href="https://mastodon.social/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#programming</a> <a href="https://mastodon.social/tags/freedesktop" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#freedesktop</a> <a href="https://mastodon.social/tags/autotools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#autotools</a> <a href="https://mastodon.social/tags/dependencies" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dependencies</a>

mofosyneMade a post about setting up an autotool based project via a bash script I written <a href="https://briankhuu.com/blog/2024/04/11/initialise-minimal-autotools-script/" rel="nofollow noopener noreferrer" target="_blank">https://briankhuu.com/blog/2024/04/11/initialise-minimal-autotools-script/</a><a href="https://mastodon.social/tags/bash" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bash</a> <a href="https://mastodon.social/tags/autotools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#autotools</a> <a href="https://mastodon.social/tags/build" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#build</a> <a href="https://mastodon.social/tags/make" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#make</a> <a href="https://mastodon.social/tags/makefile" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#makefile</a> <a href="https://mastodon.social/tags/C99" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#C99</a> <a href="https://mastodon.social/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#programming</a>

T_XBetter late than never, but I think I was now able to create a C library via <a href="https://chaos.social/tags/autotools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#autotools</a> thanks to David Wheeler's great tutorial and introduction on YouTube: <a href="https://www.youtube.com/watch?v=4q_inV9M_us&list=PL1jSu6GGefBlGgdOeDpsKuCEy1ERNyCUZ" rel="nofollow noopener noreferrer" target="_blank">https://www.youtube.com/watch?v=4q_inV9M_us&list=PL1jSu6GGefBlGgdOeDpsKuCEy1ERNyCUZ</a>. All a lot easier than I had expected! I think all these noisy extra files with autotools and blown up configure.ac/Makefile.am files in other projects scared me off in the past. But actually it's now easier than writing a Makefile by hand, imo. Many thanks <a href="https://infosec.exchange/@davidawheeler" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@davidawheeler</a>!

JdeBP<a href="https://mastodon.social/@cks" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@cks</a> I'm thinking more on the lines of educating programmers that it is not 1995, and just replacing these conditionals with <a href="https://tty0.social/tags/include" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#include</a> <stdio.h> and the like. It's making hundreds of thousands of programs (going by the GitHub search results alone) look far more complex in the portability arena than they truly are.And this is, of course, a maintenance burden. Any future maintainer has to learn something that has been obsolete for 1/4 of a century. Whereas reality is simple.<a href="https://tty0.social/tags/autotools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#autotools</a>

TermuxWe're migrating one of our projects from <a href="https://fosstodon.org/tags/autotools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#autotools</a> to <a href="https://fosstodon.org/tags/cmake" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cmake</a> after the <a href="https://fosstodon.org/tags/xz" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#xz</a> incident. Although we aren't distributing any release tarballs with the generated 'configure' and other scripts, we still think this should improve the overall readability of the build scripts.<a href="https://github.com/termux/termux-elf-cleaner/pull/31" rel="nofollow noopener noreferrer" target="_blank">https://github.com/termux/termux-elf-cleaner/pull/31</a>

JdeBP<a href="https://mastodon.social/@cks" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@cks</a> It's not even the major step of conversion away, but just getting rid of the stuff that doesn't apply in 2024, and really last applied back in the 1990s, like the tests for <string.h>, <stdio.h>, <errno.h>, and so forth.It's a fair bet that the overwhelming majority of programs that have all of the <a href="https://tty0.social/tags/autotools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#autotools</a>-driven conditional tests for these things have no "else" code for the case where the detection fails.

JdeBP<a href="https://mastodon.social/@cks" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@cks</a> Counterpoint: Why do so many ./configure scripts still perform tests for <string.h> and suchlike? How many programs would genuinely compile and work without the Standard C library stuff that still gets checked for in 2024?<a href="https://tty0.social/tags/autotools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#autotools</a>

argv minus one<a href="https://infosec.exchange/@malwareminigun" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@malwareminigun</a> <a href="https://infosec.exchange/@lcamtuf" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@lcamtuf</a> Let this be a lesson to basically everyone: boilerplate is a security threat. It conceals malicious code. Come up with better languages, better libraries, macros, whatever. But boilerplate is evil and must be exterminated.<a href="https://cybervillains.com/@djm" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@djm</a> <a href="https://mstdn.party/tags/xz" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#xz</a> <a href="https://mstdn.party/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cybersecurity</a> <a href="https://mstdn.party/tags/autotools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#autotools</a>

Diego Elio PettenòFor many years I have been one of the prominent experts in <a href="https://mastodon.social/tags/Autotools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Autotools</a>. If you think I'd recommend using them for modern software, you're mistaken.Start with <a href="https://flameeyes.blog/2009/05/01/the-long-awaited-build-systems-post-part-1-maybe/?mtm_campaign=social&mtm_kwd=mastodon" rel="nofollow noopener noreferrer" target="_blank">https://flameeyes.blog/2009/05/01/the-long-awaited-build-systems-post-part-1-maybe/?mtm_campaign=social&mtm_kwd=mastodon</a>

KornelSeriously, in retrospect, <a href="https://mastodon.social/tags/autotools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#autotools</a> itself is a massive supply-chain security risk.It has normalized shipping and running tens of thousands of lines of arbitrary executable code without any safeguards.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.

Administered by:

Server stats:

Trending now

Administered by:

Server stats:

AutoToolsBack

Trending now