-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[Bug]: autom4te from package autoconf doesn't recognise installed m4, thus fails to work at all #7361
Comments
Please share the full output so we can see what it runs. Does not happen on aarch64 so probably arm specific. Possibly related to #7232 |
Interesting. (Btw is it possible to log into the Termux environment via adb or such? Retyping the full logs is a bit clunky)
The physical CPU is armv7 btw (should be application type |
Yeah, see for example: https://glow.li/posts/access-termux-via-usb/
I think the l just indicates that it is "little-endian", but what exactly the model numbers mean are beyond me. I will dig out an arm device to see if I can reproduce it later. Do you get any more information if you run |
Running
For som reason |
Should be fixed properly in m4 though. Reported in #7361.
Thanks for locatinf the issue and pushing a workaround so quickly! Also thanks for the adb link! I'm not sure if you want to keep this issue open as a reminder about the underlying issue with |
PR #7701 is yet another workaround that makes For a "proper" fix, we would need to modify the function |
@xtkoba great, thanks! Do you have any reference for why this is needed, for only arm? Is it a problem with the ndk or a problem in the source code of m4? |
I am sorry but I have not yet investigated this problem further. I just came up with the workaround by looking at the
|
Problem description
autoreconf stopped working at all with autom4te claiming to not find a sufficiently recent GNU m4, yet such a version is installed.
What steps will reproduce the bug?
In an up-to-date Termux environment:
Currently the last step leads to:
Yet, m4 get's automatically installed and
m4 --version
claims it ism4 (GNU M4) 1.4.19
.This even happen's with libass commits I previously compiled from git succesfully like this in Termux. Unfortunately I can't tell anymore which exact upgrade caused the regression, since to troubleshoot I once wiped and reinstalled termux from FDroid to rule out any bugged states/package installs.
What is the expected behavior?
autoreconf is succesful, allowing to configure and compile the sources from git.
System information
Version of the presumably most relevant packages as reported by
apt-cache policy
:termux-info:
The text was updated successfully, but these errors were encountered: