re-reading this post by @zwol about the state of the art of the #Autotools

https://www.owlfolio.org/development/autoconf-swot/

it seems that the support of the servers for issue tracking and the paperwork for intellectual property issues are holding back the health of the Autotools

I was thinking

as for issue tracking, it'd be nice (and probably relatively easy) to host the Autools suite on #Forgejo

as it seems to be the most sensible FLOSS oriented solution (currently)

as for paperwork...

Hitting the next roadblock in my #FreeBSD #Linuxulator "userland from source" project: #Linux #Python is causing trouble. I got it to build and package, but runtime parts are wrong, *somehow* the "/compat/linux" prefix "sneaks in" 😞 (still didn't understand how exactly...).

You might ask why port python at all, and indeed, I didn't plan to do so initially.

The issue is build systems. With the goal to port shared libraries that might be needed by (closed-source) Linux binaries, not all of them use plain #make (or #GNU #autotools) for building.

#cmake is popular, so I'll need it. To build it using shared libraries itself, one of its prerequisites needs #meson, which, in turn, requires python. 🤯

Ahh, welcome to dependency hell 😜

Don't forget autoreconf if it is required ... #autotools

@jhx Hell, guess I love to hate that ...

I at least managed to have #GCC's libstdc++ configure script (#GNU #autotools generated) complete successfully. On #FreeBSD, targeting #Linux using binutils and GCC configured for cross-building.

It is soooo horrible, and all this kerfuffle is only needed because somehow, this script fails to detect that I *am* cross-building here. 🤯

@jhx Debugging some #GNU #autotools generated configure script is awesome fun ... not.

Right now trying to get #GCC's libstdc++ to build (for #Linux, but still cross-building from #FreeBSD). Something is quite borked there ...

Got over it and created an upstream PR for #fvwm3!

Well, I *knew* I would run into some #autotools foo. Can't use #autoconf to substitute @bindir@ in the .desktop file, it expands to ${exec_prefix}/bin (literally) 😜

https://github.com/fvwmorg/fvwm3/pull/876

Just thought #GNU #autotools was the worst build system ever, when I suddenly remembered #MSBuild.

Context, should "upstream" some change to #fvwm3 which was now done locally in the #FreeBSD #port, and upstream uses autotools.

dnl #M4 sux! 😏

If you are planning to write free software, become a free software developer or simply want your programs to build almost everywhere; you should definitely bookmark and read this tutorial. It will save you a lot of pain.

The GNU Project Build Tools

https://www.sourceware.org/autobook/autobook/autobook.html#Top

#gnu #gnulinux #freesoftware #fsf #development #software #autotools #dev #hackers

23PC Oil Filter Wrench Set#oilfilter #autotools

I stopped feeling bad about #autotools files (configure.ac Makefile.am m4/*) when I realized how much noise a new maven package throws on your disk.
The main difference is: for #maven / #npm / #cargo / #gradle / #bazel / ... these are autogenerated.

That’s why I started #conf: https://hg.sr.ht/~arnebab/conf — auto-generation for autotools projects with `conf new --lang <language>`.

It needs more templates … contributions welcome!
(just send me a patch or a link to pull from)
#gnu #make #freesoftware

You know how some people that know Java don't put it on their résumé because they don't want to work in Java?

For me, that's #autotools, #autoconf, #automake

PSA: please switch your projects to #Meson

Welcome to VIKTEC's booth. #autotools #BritishExhibition

Dzisiejsza przygoda w #Gentoo:

tmux nie buduje się. Sypie się na niekompatybilnej deklaracji forkpty() w compat.h.

Zaglądam do compat.h. forkpty() jest zadeklarowane wówczas, gdy HAVE_FORKPTY nie jest spełnione.

Zaglądam do config.log. forkpty() nie zostaje odnalezione, bo configure próbuje konsolidować przypadkowe programy z -levent_core@CMAKE_DEBUG_POSTFIX@.

W tym momencie można już domyślić się, na czym polega problem: https://github.com/libevent/libevent/issues/1459

#CMake #autotools

@grin @sullybiker The main problem with #shell scripts is that they’re glue for other commands that may or may not be installed and may or may not be the same as those used by the author.

It’s why #dehydrated has so much logic detecting the installed flavor of awk, sed, grep, diff, et al. “Portable” shell is like portable #C—riddled with brittle environmental tests (thus begetting things like #GNU #Autotools).

Even #testssl admitted defeat and can run from a #Docker #container now.

@chjara @rq That sort of concern is also a major part of just why the #Autotools ecosystem exists at all.

Which is the best Ball Joint Anchor Pin Press Set sales team in china #autotools name

Have spent untold hours today fighting with #gnulib and #autotools only to find out that my problem was a weird shell alias thing. 😭😭

My book order just arrived 😃
#autotools #c

Guix has tools to make your program relocatable, that is, let it run in a location unknown at compile time. This is a really cool feature.

However, it has limitations. You can’t use it on windows (provided you could solve the problem with symlinks…), where this is a big issue.

In the mean time, Gnulib provides an easy way that makes your programs *and libraries* relocatable.

https://www.gnu.org/software/gnulib/manual/html_node/Supporting-Relocation.html

#guix #gnulib #mingw #c #development #autotools

Guix has tools to make your program relocatable, that is, let it run in a location unknown at compile time. This is a really cool feature.

However, it has limitations. You can’t use it on windows (provided you could solve the problem with symlinks…), where this is a big issue.

In the mean time, Gnulib provides an easy way that makes your programs *and libraries* relocatable.

https://www.gnu.org/software/gnulib/manual/html_node/Supporting-Relocation.html

#guix #gnulib #mingw #c #development #autotools