GNOME Bugzilla – Bug 747393
cerbero: Properly specify aclocal system directories
Last modified: 2015-04-12 11:28:50 UTC
Currently the cerbero dist/build "system" m4 directories are specified with -I arguments to aclocal The problem with that is that aclocal will search for m4 in that order (first system directories, then local ones), whereas the logic should be the opposite (it first looks for m4 in local directories and *then* look in the 'system' ones) The patches fixes that by using the proper aclocal arguments --system-acdir
Created attachment 300999 [details] [review] cerbero: Properly specify aclocal system directories aclocal needs to know the difference between local and system m4 directories otherwise it will pick up the m4 in the wrong order (it should first pick from the specified local m4 directories and *then* if not present check in the system directories).
Created attachment 301001 [details] [review] cerbero: Properly specify aclocal search directories aclocal needs to know the difference between local and system m4 directories otherwise it will pick up the m4 in the wrong order (it should first pick from the specified local m4 directories and *then* if not present check in the system directories). We don't need to specify the build ac directory since aclocal already knows that. What we *do* need to specify is our local 'dist' ac directory containing the m4 of previously compiled packages, and that should be done solely by setting the proper ACLOCAL_FLAGS. If a package fails after this commit, check that ACLOCAL_FLAGS gets properly set as the *last* argument of aclocal.
Created attachment 301002 [details] [review] cerbero: Properly specify aclocal search directories aclocal needs to know the difference between local and system m4 directories otherwise it will pick up the m4 in the wrong order (it should first pick from the specified local m4 directories and *then* if not present check in the system directories). We don't need to specify the build ac directory since aclocal already knows that. What we *do* need to specify is our local 'dist' ac directory containing the m4 of previously compiled packages, and that should be done solely by setting the proper ACLOCAL_FLAGS. If a package fails after this commit, check that ACLOCAL_FLAGS gets properly set as the *last* argument of aclocal. Tip: You can check the include order by looking at autom4te.cache/requests
commit 7b107bea8db7767e105ca895771c9bf7915255c7 Author: Edward Hervey <bilboed@bilboed.com> Date: Mon Apr 6 09:04:45 2015 +0200 cerbero: Properly specify aclocal search directories aclocal needs to know the difference between local and system m4 directories otherwise it will pick up the m4 in the wrong order (it should first pick from the specified local m4 directories and *then* if not present check in the system directories). We don't need to specify the build ac directory since aclocal already knows that. What we *do* need to specify is our local 'dist' ac directory containing the m4 of previously compiled packages, and that should be done solely by setting the proper ACLOCAL_FLAGS. If a package fails after this commit, check that ACLOCAL_FLAGS gets properly set as the *last* argument of aclocal. Tip: You can check the include order by looking at autom4te.cache/requests https://bugzilla.gnome.org/show_bug.cgi?id=747393
*** Bug 747713 has been marked as a duplicate of this bug. ***