Bernd Wurst wrote: > On Saturday 10 May 2008, Sam Varshavchik wrote: > >> I do not believe that AC_USE_SYSTEM_EXTENSIONS is a macro in the stock >> autoconf, this looks like something that's Gentoo-specific. >> > > No, this is not gentoo specific. :) > Google for the keyword and you'll find a lot outside gentoo. >
Sam didn't mean that you'll only ever see that error on Gentoo, he meant that you won't see that error when building Courier anywhere else. Courier's build scripts don't call aclocal with "-I m4", and I can't really figure out why Gentoo's scripts would detect that this is the proper thing to do. All the same, Gentoo's scripts are the ones which are creating the problem when building Courier, which makes this a Gentoo-specific problem. >> aclocal -I m4 is not normally run as part of building Courier. >> > > I pointed out this issue some weeks ago: Gentoo stops compilation because > some > macro files inside the courier tarball are compiled for some rather outdated > build environment (sorry, don't know the details any more). > Yes, we did discuss this on the list. Gentoo insists that ltmain.sh is exactly the same version installed on the host running the build, and will re-run autotools otherwise. That doesn't explain why it uses "-I m4" when there's no m4 directory. Perhaps the best thing to do, in order to prevent Gentoo's build scripts from doing the wrong thing, is for Gentoo's ebuild to treat Courier according to its CVS build directions (http://www.courier-mta.org/cvs.html) and run autobloat before it does anything else. That way all of the autotools junk will match the versions on the build host, and there won't be any cause for Gentoo's scripts to guess at how they should be updated. Right? > In order to build this with a current system, you need to run some things, > like the above. > Gentoo believes that to be true, but no other platform mandates it. > Gentoo does not change anything what can cause problems here. It just runs > the > regular stuff for compiling things. Neither autoconf nor any other toolset is > really modified, so upcoming bugs that are not located in the envorinment > (e.g. installation location of other packages, configure arguments, ...) are > most likely upstream bugs. > That is only true for Gentoo's definition of "the regular stuff". Gentoo does what it does for other packages; it doesn't do what Courier's documentation or build scripts indicate is the correct process. There is no "bug" per se in Courier or in autotools; there is only a problem introduced by Gentoo's build scripts guessing at what the build process should be and getting it wrong. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
