#autoconf
autogen.sh not found installng Hercules #autoconf
#gnu #autoconf / #automake tipp:
# tar-ustar: use ustar format of tar (POSIX 1003.1-1988) to lift the
# 99 character limit on filenames (it is now 155 for the directory and
# 256-dir for the file). Needs Automake 1.9 or newer
# see https://www.gnu.org/software/automake/manual/1.10/html_node/Options.html#index-Option_002c-tar_002dv7
# and https://www.gnu.org/software/tar/manual/html_node/Formats.html#Formats
AM_INIT_AUTOMAKE([1.9 tar-ustar])
(this is planned to become a default in make dist—the limit is there to support some really old tar implementations—but currently the default is still tar-v7 with max 99 chars)
Time for cleanup after identifying two "interesting" issues:
1.) #FreeBSD ports come with a Templates/config.site file which is normally used by #GNU #autoconf, containing quite a lot of "cache variables" so autoconf can avoid running the actual tests. Nice, but completely wrong when targeting #Linux. So, add an empty "CONFIG_SITE=" variable to every linux port, and suddenly I can also remove some explicit cache variables again 🙈
2.) I'm building the "native" toolchain for #Linuxulator --with-sysroot=/compat/linux, which makes sure the linker reliably finds startup files and system libs, without stuff from FreeBSD base interfering. BUT: This completely breaks when some explicit lib path to /usr/lib or /usr/lib64 is added (and many build systems will do that), because sysroot doesn't apply here. Therefore, add wrapper scripts around gcc and g++ filtering out any "-L/usr/lib" or "-L/usr/lib64" argument 🙈 with that, Linux #bash builds without any patches! 🥳
Now, waiting for builds.
Several macros are obsoleted in #autoconf for various reasons (typically they failed to quote properly, couldn't be extended for more recent issues, etc.). They are still supported, but deprecated: their use should be avoided.
During the jump from Autoconf version 1 to version 2, most of the macros were renamed to use a more uniform and descriptive naming scheme, but their signature did not change.
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) 😜
Gripe of the day: #autoconf cross-compiling is not possible if your target system m4 binary location is other than that of the host system. I had to resort to sed-patching the specific scripts (autom4te and autoupdate). #fightingwindmills
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
If you design an application that relies on network connectivity. Don't just exclusively rely on #NetworkDiscovery #Autoconf / #Broadcast #multicast
Some of the saner people use #NetworkSegmentation #VLAN #Firewall
Today in the Autoconf lottery. Which standard option does actually cause the build system to cross compile the binary?
I woke up suddenly with a dream that I forgot a password. And now I am reading #autoconf manual.
m1? m2? no thanks, but I'd fancy some m4!!!
#autoconf
configure.ac
Makefile.am
The files that have been committed to version control in a typical modern Web project:
.browserslistrc
.buildpacks
.codeclimate.yml
.deepsource.toml
.dockerignore
.editorconfig
.env.test
.env.vagrant
.eslintignore
.foreman
.haml-lint.yml
.nvmrc
.prettierignore
.pretterrc.js
.rspec
.rubocop.yml
.ruby-gemset
.ruby-version
.slugignore
.yarnclean
Aptfile
Capfile
Gemfile
Procfile
Procfile.dev
Rakefile
Vagrantfile
Is that a joke?
Au secoure
The comments are priceless
https://askubuntu.com/questions/27677/cannot-find-install-sh-install-sh-or-shtool-in-ac-aux

Oh, le nouveau #GLMF avec mon article sur #autotools, enfin !
https://boutique.ed-diamond.com/en-kiosque/1516-gnulinux-magazine-234.html
"Ceci indique l'article est ou sera très prochainement publié dans : #GLMF 234 (février)."
Ah cool, mon article sur #autotools va enfin sortir (c'était prévu pour un HS mais y avait pas la place)…
Il explique comment partir de zéro avec #autoconf & friends, et quelques trucs pour maintenir les projets utilisant ça.
Quelqu'un pense que c'est utile de demander la republication en CC-nc-nd plus tard ?
Quand on vous dit qu'#autoconf c'est dangereux !
#GNU #Autoconf: AC_COMPILE_IFELSE can be unsafe as an undefined macro can turn into a valid function call. One may prefer AC_LINK_IFELSE (when applicable) for this reason. Example: https://gforge.inria.fr/scm/viewvc.php/mpfr/trunk/acinclude.m4?r1=12448&r2=12447&pathrev=12448 #autotools #unix
And now on to debug issues with #iffe utility, a very interesting alternative to #autoconf
http://web.archive.org/web/20131107204006/http://www2.research.att.com:80/~astopen/
And now on to debug issues with #iffe utility, a very interesting alternative to #autoconf
http://web.archive.org/web/20131107204006/http://www2.research.att.com:80/~astopen/