| Summary: | The build-env isn't enforcing the correct version of automake | ||
|---|---|---|---|
| Product: | cairo | Reporter: | Philip Van Hoof <pvanhoof> |
| Component: | general | Assignee: | Carl Worth <cworth> |
| Status: | RESOLVED FIXED | QA Contact: | cairo-bugs mailing list <cairo-bugs> |
| Severity: | normal | ||
| Priority: | high | CC: | trs80 |
| Version: | 0.9.3 | ||
| Hardware: | x86 (IA32) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | Proposed patch | ||
|
Description
Philip Van Hoof
2005-06-21 14:15:50 UTC
or document the usage of
${AUTOMAKE-automake}
${AUTOCONF-autoconf}
On the GNOME development platform it's uncommon to define the required version
of automake and autoconf this way. The autogen.sh has a variable that can be set
if the version of automake/autoconf matters.
Just to show that there's no such documentation atm
freax@lort:~/cvs/fdo/cairo $ grep AUTOMAKE-automake *
autogen.sh:AUTOMAKE=${AUTOMAKE-automake}
freax@lort:~/cvs/fdo/cairo $
:-)
*** Bug 4097 has been marked as a duplicate of this bug. *** Does adding the line: AUTOMAKE_OPTIONS = 1.7 to the top of cairo/Makefile.am help? I think it may convince the Debian wrapper script to try using a reasonably recent version of automake. (Other distributions will generally have automake pointing to the most recent version.) Created attachment 2964 [details] [review] Proposed patch Bertram Felgenhauer pointed out that things dont' work if automake-1.10 appears since we are doing numeric comparison on the versions. So, I've just removed that future proofing. 2005-08-21 Owen Taylor <otaylor@redhat.com> * autogen.sh: Check automake-<ver> if automake isn't sufficiently new. (#3593, Philip Van Hoof) Move bugs against "cvs" version to "0.9.3" so we can remove the "cvs" version. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.