-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aclocal disappeared? #11114
Comments
I assume that it is part of
There were some reshuffle with toolchain and base-devel packages.
Always welcomed! 🤗 But need some testing. |
Some tools have been moved. `aclocal` (and likely other tools, but this was the first one making an error in the deps-win*-native CI jobs) is now in `automake-wrapper` package, which itself is a dependency of `autotools`. Cf. msys2/MINGW-packages#11114
Awesome, thanks. Would be nice if https://packages.msys2.org had a by-file package search (like https://packages.debian.org/ does for instance), for the people who don't have easy access to the CLI tools (I build for Windows through a CI). :-) Anyway I now pushed installing the |
Yeah, that would be useful. But pacman already does that job. i.e. user preference. |
As I said, I don't have access to pacman. Well I could push a test commit in some feature branch, just have our CI pull a full runner all this just to run the command you proposed above, whose answer I would look parsing manually long CI logs. But it would be a bit overboard, right. ;-) |
For file search, you can follow this issue msys2/msys2-web#5 |
We also had to install |
Hi!
We have a dependency on
aalib
, an old ascii-art library which I was building locally in our CI (because it's not in MSYS2) for quite some time without problem.Our script is here: https://gitlab.gnome.org/GNOME/gimp/-/blob/master/build/windows/gitlab-ci/build-deps-msys2.sh#L53
It used to work without a problem until now, but today I rebuilt and got this error:
(if I recall, we needed to run
aclocal
explicitly because the tarball was very old and we needed to update some files in there, to work on modern machines, which invalidated the build system; anywayaclocal
is pretty basic tool and should stay available 🙂)I can see we had a successful build with the same script at least on March 25 (so 3 days ago). Something seems to have happened, and aclocal disappeared from whichever package it used to be in. Or maybe it got moved to another MSYS2 package we now need to install?
P.S.: by the way, if you ever wanted to package
aalib
, it would be nice too. Not sure why I never asked. But it would not invalidate this report,aclocal
is a needed tool! 😛The text was updated successfully, but these errors were encountered: