-
Notifications
You must be signed in to change notification settings - Fork 16
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
[20241112] Compilation failure on armhf #81
Comments
This is strange. True, some of the test programs require certain directories to exist. There are default names for these, which include "newforms" and "smallnf", which are used unless the environment variables NF_DIR and SNF_DIR are set to something else. In the test directory's Makefile (see tests/Makefile.am) these two are set to nftmp and snftmp respectively, and directories with these names are created before the tests run and deleted afterwards. So there is something in the way you are testing things which are circumventing this: in your example, where you run tmanin by itself, it will indeed fail as you have not set those variables and the directories newforms and smallnf do not exist. This does not, though, explain why the test failed while running "make check". |
I was hit by the same issue on The problem seems to be that you assume More specifically, in line https://github.com/JohnCremona/eclib/blob/master/libsrc/arith.cc#L384
you seem to be assuming that The actual crash in the report comes from A possible workaround might be to use |
Thanks for the detective work @tornaria . I will look at it after the holiday. |
I finally found some time to have a look at the eclib package in Debian - sorry I was away that long.
I updated it to 20241112, and checked it on armhf, since there were failures there last time. It fails, but the error message doesn't look very informative:
Since the last started test seemed to be tmanin, I tried:
and indeed the directories newforms and smallnf don't exist... but that doesn't look like an arch-specific issue, so I'm a bit at a loss as to what the issue actually is.
The text was updated successfully, but these errors were encountered: