-
Notifications
You must be signed in to change notification settings - Fork 13
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
Fails to build with autoconf 2.70 #16
Comments
@fmarier Thanks for the head's up, I'm still rocking AC 2.69 locally. I'll have to pluck down the latest, test this out, and see if I can fix it, thanks again. |
@fmarier I've created an updated configure and configure.ac. I think/hope this solves the issue that Debian is experiencing. |
I'm having problems reproducing the build failure with autoconf 2.70. My apologies, I should have tried that first before filing this bug :/ Were you able to see the current version of pdfresurrect fail to build with 2.69? With respect to your fix, I think the following will be problematic on distros that use an earlier version of autoconf:
Let me ask the Debian reporter more information and let's park this issue until he gets back to me. With respect to the next stable version of Debian/Ubuntu, it's not a big deal anyways because they're going to ship with autoconf2.69. So if you've got other fixes you'd like to see in these distros, feel free to release without addressing any autoconf2.70 issues. |
No worries! I still think it's good to at least be prepared for the autoconf update.
I have no issues building with 2.69. I do have one change for the upcoming debian update, which I plan on cutting a release the next two weeks. |
Another datapoint: I am able to build pdfresurrect 0.23 with no problems on macOS 10.15.7, both as shipped with its autoconf-2.69-generated configure script and if I autoreconf with autoconf 2.71. |
I haven't had a chance to reproduce this myself and come up with a patch, but in case you are preparing a new release soon, it might be worth trying it with autoconf 2.7.0 since it appears to be broken with that version: https://bugs.debian.org/978877
The text was updated successfully, but these errors were encountered: