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
build randomly fails with automake-1.16 #529
Comments
I see this same failure on Ubuntu 17.10 when building I have no problem building @bmwiedemann what version of |
We are building with automake-1.16.1 in openSUSE:Factory. Building for Leap:15.1 with automake-1.15.1 indeed does not fail in this way. So maybe libheimdal triggers a problem/regression in automake-1.16 ? |
The following I can apply this commit on I've no idea if this is a |
@bmwiedemann it might be worth updating the title of this issue to reference |
@nicowilliams sorry for the ping, but any ideas on this one? |
@MilhouseVH my opinion is that since your have identified the specific change which introduced a regression in automake 1.16 that the bug report be filed against automake. The commit message for http://git.savannah.gnu.org/cgit/automake.git/commit/?id=f4e91bfc490da63209aad19636568da3b955dcd4&h=master indicates that there should be no change in behavior. Shorter pathnames are supposed to be used when doing so would not introduce an ambiguity. Clearly that change breaks Heimdal. Notifying the author of the unintended side effect of the commit is the appropriate thing to do. Unfortunately Heimdal will need to work around this regression as well. |
@jaltman thanks for the reply. And thanks for prompting me to dig a little deeper - I have in fact now found an There may be a work-around[4] but I'm not entirely sure how this can be applied to I've sent a reply to the |
My mailing list post is here: https://lists.gnu.org/archive/html/automake/2019-10/msg00000.html |
This Either this isn't an |
The comments in the mailing list messages you referenced suggest it's something to do with pathname equivalences, e.g. |
I'm trying with automake-1.16.2 on macOS but haven't been able to duplicate the issue yet. |
With automake-1.16.2 (and latest autoconf/libtool) on Ubuntu 18.04.3 LTS and Heimdal master I can't seem to duplicate this using |
OK. Could you please try grabbing commit cc6a3f3 and seeing if that fixes it? |
Commit cc6a3f3 fixed it for me (still with automake-1.16.1). If others don't object, this issue can be closed. |
I'll leave it to @jaltman to close, in case he wants to cut another release. |
@lhoward many thanks for taking a look at this! I'm testing with Previously,
(build log: http://ix.io/2h34) With cc6a3f3,
(build log: http://ix.io/2h33, and build log with
In both cases I'm building |
Since "master" 7055365 doesn't experience the problem there must be more commits on master that fix build dependency issues that must be cherry-picked to "heimdal-7-1-branch". |
@MilhouseVH please try building c4cff68 which is the new tip of the heimdal-7-1-branch |
BTW OT but @bmwiedemann – when did SuSE switch back to Heimdal? |
@jaltman I will build latest |
@MilhouseVH I think @jaltman is asking you to build |
@jaltman ah OK thanks - as soon as I re-establish contact with my VM I'll give it a go! |
@MilhouseVH thanks for testing. I'm closing this issue. |
When building heimdal-7.5.0 in openSUSE with make -j1, we get
to reproduce:
I think there is some dependency not specified in
lib/hcrypto/Makefile.am
and when doing a parallel build, it usually gets created in time from a parallel job.This bug was found while working on reproducible builds for openSUSE.
The text was updated successfully, but these errors were encountered: