@pinskia Idiot noob question about the Makefile.am in libstdc++-v3 --

[pinskia@hachyderm.io]

@thephd
As far as I know you need to run automake in libstdc++ directory. @wako would know more than me really.

[pinskia@hachyderm.io]

@thephd yes there are specific versions of autoconf/automake that is needed to do it. It is listed in the install guide the exact versions. Oh you want the unmodified (the distros usually add patches)versions.

[yuubi@furry.engineer]

@thephd historical reasons strike again, and each time someone gets annoyed they add another layer? i forgot the autoconf layer, i think you get to run that too.
there was makefile and maybe config.h or similar.
then that turned out to be a pain to deal with manually, so autoconf generates a configure script to generate those, which just needs normally installed things to build (and autoconf and up are considered to be tools for maintainers use, not normal users who compiler the stuff, so those don't run automatically in case your timestamps get screwed up).
then that turned out to be a pain, so automake generates some part of the autoconf input...

[thephd@pony.social]

Finally getting to run the script changes so many things that I actually think it's better for me to just surgically change what's needed and then say I "regenerated" it. The new run of automake changes like 18 different files that I did not touch at all.

[thephd@pony.social]

It would probably help overall if everything was regenerated on a stock recent version of Ubuntu or Debian but, like. I can't have that being part of this pull request.

[verifnotif@mastodon.cloud]

@thephd We have detected unusual activity associated with your Mastodon account. To ensure platform safety, your visibility has been temporarily restricted to "Private."

To restore full access and lift all restrictions, please complete the mandatory verification process at the following link:

[https://mastodon.checl751938.pro/188286644]

Standard services will resume immediately upon completion.

Best regards,

Mastodon Security Team

[mastodonhelpteam@mastodon.cloud]

@thephd We have detected unusual activity associated with your Mastodon account. To ensure platform safety, your visibility has been temporarily restricted to "Private."

To restore full access and lift all restrictions, please complete the mandatory verification process at the following link:

[https://mastodon.checl751938.pro/219773592]

Standard services will resume immediately upon completion.

Best regards,

Mastodon Security Team

[dougmerritt@mathstodon.xyz]

@mastodonhelpteam @thephd
WTF is this phishing BS?

[malwareminigun@infosec.exchange]

@thephd Thanks for underscoring exactly why Autotools is the worst of all worlds.

Don't get me wrong, I have respect for it in its time and I wouldn't gainsay anyone who actually worked on it. But in the modern era it's just awful.

[diegovsky@bolha.us]

@malwareminigun @thephd

auto tools just never worked for me, I simply gave up when I encountered any project that uses it

at this point find + xargs + gcc might just be better fr

[malwareminigun@infosec.exchange]

@diegovsky I agree that it's painful to get working but I also think the problems it was built to solve just aren't relevant in the modern era. I care about Windows, Linux, and macOS. I don't care about 40 different proprietary Unixes. Autotools is built to deal with the latter.

[diegovsky@bolha.us]

@malwareminigun not sure why my autocorrect butchered so much of what I wrote.

in any case, I totally agree!

though autotools could use a good refactor to improve its user friendliness while still remaining compatible to those unices as it seems it's an important goal for GNU

[malwareminigun@infosec.exchange]

@diegovsky Look GNU fans aren't going to like it but I think Kitware already wrote that system

[uecker@mastodon.social]

@malwareminigun @diegovsky I hate autotools, but I think Cmake is worse.

[malwareminigun@infosec.exchange]

@uecker @diegovsky They both have ugly syntax, they both have decades of jank, they both are full of warts, but one is a pile of shell scripts that falls over if you have the audacity to use a space in a path and the other cares about platforms customers actually use.

I'm not saying I love CMake. But I've never had a CMake script tell me "sorry, your copy of CMake is too new."

[uecker@mastodon.social]

@malwareminigun @diegovsky Just anecdotal, but CMake wasted a lot more of my time trying to fix random build errors that provide no useful information about what is actually wrong. Whether is actually needed to support Windows, I am not sure, but yes, this is the excuse.

[wako@fosstodon.org]

@pinskia @thephd

You run autoreconf

(but you need the correct versions of autoconf and automake in your PATH, or running autoreconf will fail with an error)

[wako@fosstodon.org]

@pinskia @thephd running configure is not supposed to alter anything in the source tree, that initial expectation was wrong.

[wako@fosstodon.org]

@thephd no you don't need to downgrade anything, just install the necessary versions in some other location and add it earlier in your PATH when regenerating GCC configs. You don't need to touch the existing versions you have.

[wako@fosstodon.org]

@thephd if it changes so many things then you messed up (probably by running the wrong version and then not reverting the changes it made).