Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 486740

Summary: dev-libs/cyrus-sasl-2.1.26-r3 should not set WANT_AUTOMAKE="1.12"
Product: Gentoo Linux Reporter: wojtek <wojtask9>
Component: [OLD] LibraryAssignee: Net-Mail Packages <net-mail+disabled>
Status: RESOLVED FIXED    
Severity: normal CC: Dessa, dv, whissi
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: Patch for cyrus-sasl-2.1.26-r3.ebuild

Description wojtek 2013-10-02 01:47:15 UTC
It build's ok with 13.4 and 14.1

On my system automake-1.12 wants only cyrus-sasl

Reproducible: Always
Comment 1 Francisco J. Vazquez 2014-02-08 09:55:33 UTC
Created attachment 369854 [details, diff]
Patch for cyrus-sasl-2.1.26-r3.ebuild

For me it only compiles with automake-1.14.1 if I replace AC_CONFIG_MACRO_DIR with AC_CONFIG_MACRO_DIRS in configure.in and saslauthd/configure.in. 

Attached patch for the ebuild.
Comment 2 Thomas Deutschmann (RETIRED) gentoo-dev 2014-02-08 14:06:11 UTC
Hi,

I also saw that dev-libs/cyrus-sasl-2.1.26-r3 was requiring sys-devel/automake-1.12.

I copied the ebuild into my local overlay and removed the

  WANT_AUTOMAKE="1.12"

line to test if it will work with sys-devel/automake-1.14.1.

It failed with:

***** aclocal *****
***** PWD: /var/tmp/portage/dev-libs/cyrus-sasl-2.1.26-r3/work/cyrus-sasl-2.1.26/saslauthd
***** aclocal -I ../cmulocal -I ../config

aclocal-1.14: warning: autoconf input should be named 'configure.ac', not 'configure.in'
aclocal-1.14: error: couldn't open directory '../cmulocal ../config': No such file or directory


The patch from Francisco worked for me (BTW: you swapped old and new file, had to use -R). Thanks!
Comment 3 Patrick Lauer gentoo-dev 2014-02-24 05:30:35 UTC
+  24 Feb 2014; Patrick Lauer <patrick@gentoo.org> +cyrus-sasl-2.1.26-r4.ebuild:
+  Fix configure.in and unrestrict allowed automake versions #486740 #468556
+

Fixes build failures for me, please reopen if you still hit failures with -r4