FL-1894 brought in update of automake to 1.14. This was done just a few days ago.
I went to rebuild media-gfx/graphviz to debug an issue in my personal code. I needed to rebuild the graphviz so that I could trace memory leaks with valgrind.
Problem was that graphviz (built before) gave no problems but suddenly just stopped on the compile phase complaining that it needed automake-1.13. Since slotting wasn't an issue, I was able to re-emerge automake-1.13. The rebuild of graphviz worked fine.
Is this really a bug with ebuilds or upstream where build fails because of a dependency on a specific automake?
Question
digifuzzy
FL-1894 brought in update of automake to 1.14. This was done just a few days ago.
I went to rebuild media-gfx/graphviz to debug an issue in my personal code. I needed to rebuild the graphviz so that I could trace memory leaks with valgrind.
Problem was that graphviz (built before) gave no problems but suddenly just stopped on the compile phase complaining that it needed automake-1.13. Since slotting wasn't an issue, I was able to re-emerge automake-1.13. The rebuild of graphviz worked fine.
Is this really a bug with ebuilds or upstream where build fails because of a dependency on a specific automake?
Link to comment
Share on other sites
6 answers to this question
Recommended Posts