Summary: | dev-libs/libhome-0.10.1 incompatible with libtool 2.2 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Xavian-Anderson Macpherson <Shingoshi> |
Component: | [OLD] Development | Assignee: | Apache Team - Bugzilla Reports <apache-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 212763 | ||
Attachments: | libhome-0.10.1-x86_64-buildlog_emergeinfo_environment |
Description
Xavian-Anderson Macpherson
2008-05-08 10:10:46 UTC
Created attachment 152441 [details]
libhome-0.10.1-x86_64-buildlog_emergeinfo_environment
All in one file.
I think it should work if rm ${S}/aclocal.m4 is added before eautoreconf. I think it contains only the old libtool.m4 other macros are in configure.in (well, they should be in acinclude.m4, not very clean) (In reply to comment #2) > I think it should work if > rm ${S}/aclocal.m4 > is added before eautoreconf. > I think it contains only the old libtool.m4 > other macros are in configure.in (well, they should be in acinclude.m4, not > very clean) > So is this something that's up to the user to do, or is this the responsibility of the maintainer? Shingoshi I don't understand your question. If you're asking `should the upstream have put libtool.m4 in acinclude.m4`, then in my not-so-humble opinion they shouldn't have, unless they were trying to make this work with some old-and-broken version of aclocal or they didn't understood autotools. As libhome seem to be no longer in the development, I think it was the former (I'm giving them benefit of doubt). fixed, thanks |