-
-
Notifications
You must be signed in to change notification settings - Fork 307
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
autoreconf -fi
fails on Debian unstable
#560
Comments
Did you use |
No, just autoconf (2.69). |
Using |
I think we are still stuck at autoreconf-2.13 (which is strangely missing from https://github.com/OSGeo/grass/blob/master/REQUIREMENTS.html - any idea @landam or anyone else?). Does anyone have experience in upgrading from autoreconf-2.13 to autoreconf-2.69? |
As reported in Debian Bug #992810, What needs to happen to make GRASS work with newer 2.13 is likely to be removed, that would make building GRASS on Debian impossible. |
|
The changes from #1845 fail to apply to 7.8.6-RC2, so I cannot test them with the Debian package. Is backporting those changes to 7.8.x feasible? |
Backporting it shouldn’t be a problem, the question of making that big a change at this stage for 7.8.6 is another matter. If you are willing to test a backported draft PR just for testing the concept I’m more than glad to put up one. |
The DESTDIR change was not appropriate for the 7.8 patch release either, so I'd be fine with the autoconf changes for 7.8. With Markus still recovering, it seems unlikely that a 7.8.6 or 8.0.0 release will happen any time soon. If the changes are backported to 7.8 I'll gladly carry the patch in the Debian package until the release in which they're included. |
Well, we are discussing how to coordinate this. At least 7.8.6, should be released soon. We might have a video call next Tuesday September 14th. Link will be posted in grass-dev mailing list soon before the meeting. |
Thanks for the backport, that fails with autoconf 2.71 though:
The same happens when using the autoconf2.69 package:
|
Will look into this, however what draws my immediate attention is the the fact that with 2.70 or 2.71 the filename |
Sorry, now I browsed all the quoted log, you already did 2.69. |
There seems to be leftovers with 2.69 from trying with 2.71:
|
With 2.69 I get:
|
That's not it, every run was done in a new chroot session. I rather think that autoconf2.69 is not really version 2.69, it depends on autoconf unlike autoconf2.13, suggesting that it uses it. It works in a bullseye chroot with autoconf (2.69-14), but that doesn't help for the Debian package which targets unstable. |
Could you try #1870? |
With #1870 and autoconf 2.71 I get:
|
Forcing autoreconf to use autoconf2.69, autom4te2.69, and autoheader2.69 instead of only autoconf2.69 works for Debian unstable. It still fails with autoconf (2.71-2) after applying the changes from #1870:
|
At least some progress. I get a similar result though. Something is not working with |
I just pushed an update to #1870, which solved the latest issue for me. Please try that. |
That works for me with autoconf (2.71-2) on Debian unstable too. Very happy that |
That is indeed great news, thanks a bunch for your cooperation! I just merged #1870 to the 7.8 branch. Please close this issue if you think it has been resolved. |
I see 7.8.6 on Debian is out, seemingly without patches related to this reported issue. Closing. |
Building the grass package on Debian unstable fails:
This applies to 7.8.2 & 7.8.3-rc1 at least, likely all versions of grass.
To reproduce (on Debian unstable):
Verbose output of
autoreconf
&autoheader
:This may be caused by the upgrade to automake 1.16.2.
The text was updated successfully, but these errors were encountered: