[gentoo-user] Problems with aclocal

[gentoo-user] Problems with aclocal

[Rafa Griman]

Hi all :)

Got some problems with aclocal :( When running:

    emerge -avDuN --with-bdeps=y world

I get a whole bunch of packages who won't install nor upgrade with the
following error:

     Failed Running aclocal !

Looking through the Forums I saw I've got to mask autoconf. So I added
autoconf to:

     /etc/portage/package.mask

And now I get a whole bunch of errors saying autoconf is masked and I
have to unmask it ... which takes me back to step 1 ...

Right now I have:

# equery list autoconf
 * Searching for autoconf ...
[IP-] [  ] sys-devel/autoconf-2.13:2.1
[IP-] [  ] sys-devel/autoconf-2.69:2.5


# equery list automake
 * Searching for automake ...
[IP-] [  ] sys-devel/automake-1.10.3:1.10
[IP-] [  ] sys-devel/automake-1.11.6:1.11
[IP-] [  ] sys-devel/automake-1.12.6:1.12
[IP-] [  ] sys-devel/automake-1.13.1:1.13


# equery list automake-wrapper
 * Searching for automake-wrapper ...
[IP-] [  ] sys-devel/automake-wrapper-8:0


Any help will be greatly appreciated.

Thanks :)

   Rafa

Re: [gentoo-user] Problems with aclocal

[Alan McKinnon]

On 01/05/2013 23:05, Rafa Griman wrote:
> Hi all :)
> 
> Got some problems with aclocal :( When running:
> 
>     emerge -avDuN --with-bdeps=y world
> 
> I get a whole bunch of packages who won't install nor upgrade with the
> following error:
> 
>      Failed Running aclocal !
> 
> Looking through the Forums I saw I've got to mask autoconf. 

You got that from the Forums, huh?

Um yeah, well, signal to noise there is out the roof.

I'd be double checking exactly what the Forum user said, as masking
autoconf seems to me like a guaranteed way to get portage to whinge very
loud and very long (half the tree DEPENDS on autoconf).

Maybe the poster meant to mask a /specific/ version of autoconf?
Start by masking the latest version you installed and proceed from there.





So I added
> autoconf to:
> 
>      /etc/portage/package.mask
> 
> And now I get a whole bunch of errors saying autoconf is masked and I
> have to unmask it ... which takes me back to step 1 ...
> 
> Right now I have:
> 
> # equery list autoconf
>  * Searching for autoconf ...
> [IP-] [  ] sys-devel/autoconf-2.13:2.1
> [IP-] [  ] sys-devel/autoconf-2.69:2.5
> 
> 
> # equery list automake
>  * Searching for automake ...
> [IP-] [  ] sys-devel/automake-1.10.3:1.10
> [IP-] [  ] sys-devel/automake-1.11.6:1.11
> [IP-] [  ] sys-devel/automake-1.12.6:1.12
> [IP-] [  ] sys-devel/automake-1.13.1:1.13
> 
> 
> # equery list automake-wrapper
>  * Searching for automake-wrapper ...
> [IP-] [  ] sys-devel/automake-wrapper-8:0
> 
> 
> Any help will be greatly appreciated.
> 
> Thanks :)
> 
>    Rafa
> 


-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Problems with aclocal

[Rafa Griman]

Hi Alan,

On Wed, May 1, 2013 at 11:26 PM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> On 01/05/2013 23:05, Rafa Griman wrote:
>> Hi all :)
>>
>> Got some problems with aclocal :( When running:
>>
>>     emerge -avDuN --with-bdeps=y world
>>
>> I get a whole bunch of packages who won't install nor upgrade with the
>> following error:
>>
>>      Failed Running aclocal !
>>
>> Looking through the Forums I saw I've got to mask autoconf.
>
> You got that from the Forums, huh?


Yup. I also saw a post saying he solved his issue by removing all the
versions except the latest one. Tried that too and portage keeps
rebuilding both versions:

# equery list autoconf
 * Searching for autoconf ...
[IP-] [ ] sys-devel/autoconf-2.13:2.1
[IP-] [  ] sys-devel/autoconf-2.69:2.5



> Um yeah, well, signal to noise there is out the roof.
>
> I'd be double checking exactly what the Forum user said, as masking
> autoconf seems to me like a guaranteed way to get portage to whinge very
> loud and very long (half the tree DEPENDS on autoconf).


That's why I'm writing, sounds a bit weird to me ...


> Maybe the poster meant to mask a /specific/ version of autoconf?
> Start by masking the latest version you installed and proceed from there.


Tried that too but still get the same error:

     Failed Running aclocal !

No matter what version I mask in:

     vim /etc/portage/package.mask/masked

I get that same error. I have rebuilt automake and automake-wrapper
too just in case. Have also run:

     revdep-rebuild

     emerge --depclean

     perl-cleaner --all

     python-updater

I have also unmerged the previous versions of automake and left the
latest, but portage rebuilds 2 other versions so I end up with:

# equery list automake
 * Searching for automake ...
[IP-] [  ] sys-devel/automake-1.10.3:1.10
[IP-] [  ] sys-devel/automake-1.11.6:1.11
[IP-] [  ] sys-devel/automake-1.13.1:1.13


TIA

   Rafa

Re: [gentoo-user] Problems with aclocal

[Alan McKinnon]

Top-posting as inline replies don't fit here.

auto* errors can be tricky to solve, in my experience they tend to be
once off weird errors when packages can't quite make sense out of what
the auto* scripts are telling them.

Let's get some facts on the table so we can proceed:

Which packages were failing originally?
What versions of the various auto* packages do you have installed?
When did you last resync the tree?


P.S. You've no doubt seen that forum posts have a high hit-rate of
"throw stuff at the wall and see what sticks", the posts you mention
show that happening. Randomly masking stuff hoping it will work is not a
good fault-finding technique :-)





On 02/05/2013 00:01, Rafa Griman wrote:
> Hi Alan,
> 
> On Wed, May 1, 2013 at 11:26 PM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
>> On 01/05/2013 23:05, Rafa Griman wrote:
>>> Hi all :)
>>>
>>> Got some problems with aclocal :( When running:
>>>
>>>     emerge -avDuN --with-bdeps=y world
>>>
>>> I get a whole bunch of packages who won't install nor upgrade with the
>>> following error:
>>>
>>>      Failed Running aclocal !
>>>
>>> Looking through the Forums I saw I've got to mask autoconf.
>>
>> You got that from the Forums, huh?
> 
> 
> Yup. I also saw a post saying he solved his issue by removing all the
> versions except the latest one. Tried that too and portage keeps
> rebuilding both versions:
> 
> # equery list autoconf
>  * Searching for autoconf ...
> [IP-] [ ] sys-devel/autoconf-2.13:2.1
> [IP-] [  ] sys-devel/autoconf-2.69:2.5
> 
> 
> 
>> Um yeah, well, signal to noise there is out the roof.
>>
>> I'd be double checking exactly what the Forum user said, as masking
>> autoconf seems to me like a guaranteed way to get portage to whinge very
>> loud and very long (half the tree DEPENDS on autoconf).
> 
> 
> That's why I'm writing, sounds a bit weird to me ...
> 
> 
>> Maybe the poster meant to mask a /specific/ version of autoconf?
>> Start by masking the latest version you installed and proceed from there.
> 
> 
> Tried that too but still get the same error:
> 
>      Failed Running aclocal !
> 
> No matter what version I mask in:
> 
>      vim /etc/portage/package.mask/masked
> 
> I get that same error. I have rebuilt automake and automake-wrapper
> too just in case. Have also run:
> 
>      revdep-rebuild
> 
>      emerge --depclean
> 
>      perl-cleaner --all
> 
>      python-updater
> 
> I have also unmerged the previous versions of automake and left the
> latest, but portage rebuilds 2 other versions so I end up with:
> 
> # equery list automake
>  * Searching for automake ...
> [IP-] [  ] sys-devel/automake-1.10.3:1.10
> [IP-] [  ] sys-devel/automake-1.11.6:1.11
> [IP-] [  ] sys-devel/automake-1.13.1:1.13
> 
> 
> TIA
> 
>    Rafa
> 


-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Problems with aclocal

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 878 bytes --]

On Wed, 1 May 2013 23:05:18 +0200, Rafa Griman wrote:

> Got some problems with aclocal :( When running:
> 
>     emerge -avDuN --with-bdeps=y world
> 
> I get a whole bunch of packages who won't install nor upgrade with the
> following error:
> 
>      Failed Running aclocal !
> 
> Looking through the Forums I saw I've got to mask autoconf. So I added autoconf to:
> 
>      /etc/portage/package.mask

That's what you get with the forums, aclocal isn't even part of autoconf,
it is provided by automake-wrapper.

> And now I get a whole bunch of errors saying autoconf is masked and I
> have to unmask it ... which takes me back to step 1 ...

There have been issues with automake-1.13. I have seen a similar error on
one package and worked around it with

WANT_AUTOMAKE=1.12 emerge -1 cat/package


-- 
Neil Bothwick

BING But It's Not Google

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Problems with aclocal

[Jackie]

在 Thu, 02 May 2013 06:39:02 +0800，Neil Bothwick <neil@digimed.co.uk>  
写道:

> On Wed, 1 May 2013 23:05:18 +0200, Rafa Griman wrote:
>
>> Got some problems with aclocal :( When running:
>>
>>     emerge -avDuN --with-bdeps=y world
>>
>> I get a whole bunch of packages who won't install nor upgrade with the
>> following error:
>>
>>      Failed Running aclocal !
>>
>> Looking through the Forums I saw I've got to mask autoconf. So I added  
>> autoconf to:
>>
>>      /etc/portage/package.mask
>
> That's what you get with the forums, aclocal isn't even part of autoconf,
> it is provided by automake-wrapper.
>
>> And now I get a whole bunch of errors saying autoconf is masked and I
>> have to unmask it ... which takes me back to step 1 ...
>
> There have been issues with automake-1.13. I have seen a similar error on
> one package and worked around it with
>
> WANT_AUTOMAKE=1.12 emerge -1 cat/package


Also get the same problem here two days ago when I was trying to emerge  
bootchart2.After searching through the Internet I also noticed that it had  
sth to do with automake-1.13,I masked it and problem solved.

Re: [gentoo-user] Problems with aclocal

[J. Roeleveld]

Jackie <jiangjun12321@gmail.com> wrote:

>在 Thu, 02 May 2013 06:39:02 +0800，Neil Bothwick <neil@digimed.co.uk>  
>写道:
>
>> On Wed, 1 May 2013 23:05:18 +0200, Rafa Griman wrote:
>>
>>> Got some problems with aclocal :( When running:
>>>
>>>     emerge -avDuN --with-bdeps=y world
>>>
>>> I get a whole bunch of packages who won't install nor upgrade with
>the
>>> following error:
>>>
>>>      Failed Running aclocal !
>>>
>>> Looking through the Forums I saw I've got to mask autoconf. So I
>added  
>>> autoconf to:
>>>
>>>      /etc/portage/package.mask
>>
>> That's what you get with the forums, aclocal isn't even part of
>autoconf,
>> it is provided by automake-wrapper.
>>
>>> And now I get a whole bunch of errors saying autoconf is masked and
>I
>>> have to unmask it ... which takes me back to step 1 ...
>>
>> There have been issues with automake-1.13. I have seen a similar
>error on
>> one package and worked around it with
>>
>> WANT_AUTOMAKE=1.12 emerge -1 cat/package
>
>
>Also get the same problem here two days ago when I was trying to emerge
> 
>bootchart2.After searching through the Internet I also noticed that it
>had  
>sth to do with automake-1.13,I masked it and problem solved.

Hit this a few weeks ago.

I ended up unmasking new revisions as fixes for the packages having issues were already in the tree.

--
Joost
-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

Re: [gentoo-user] Problems with aclocal

[Rafa Griman]

Hi !!

On Thu, May 2, 2013 at 6:18 AM, Jackie <jiangjun12321@gmail.com> wrote:
> 在 Thu, 02 May 2013 06:39:02 +0800，Neil Bothwick <neil@digimed.co.uk> 写道:
>
>
>> On Wed, 1 May 2013 23:05:18 +0200, Rafa Griman wrote:
>>
>>> Got some problems with aclocal :( When running:
>>>
>>>     emerge -avDuN --with-bdeps=y world
>>>
>>> I get a whole bunch of packages who won't install nor upgrade with the
>>> following error:
>>>
>>>      Failed Running aclocal !
>>>
>>> Looking through the Forums I saw I've got to mask autoconf. So I added
>>> autoconf to:
>>>
>>>      /etc/portage/package.mask
>>
>>
>> That's what you get with the forums, aclocal isn't even part of autoconf,
>> it is provided by automake-wrapper.
>>
>>> And now I get a whole bunch of errors saying autoconf is masked and I
>>> have to unmask it ... which takes me back to step 1 ...
>>
>>
>> There have been issues with automake-1.13. I have seen a similar error on
>> one package and worked around it with
>>
>> WANT_AUTOMAKE=1.12 emerge -1 cat/package
>
>
>
> Also get the same problem here two days ago when I was trying to emerge
> bootchart2.After searching through the Internet I also noticed that it had
> sth to do with automake-1.13,I masked it and problem solved.
>


Masked 1.13 and portage installs 2.69 ... still have the same error.
This is what I've got:

 # equery list '*' | grep -iE "(automake|autoconf)"
sys-devel/autoconf-2.69
sys-devel/autoconf-wrapper-13
sys-devel/automake-1.13.1
sys-devel/automake-wrapper-8


This is ONE of the package I'm trying to install (with the included
error), there are another 75:
# emerge  app-text/libpaper

 * IMPORTANT: 4 news items need reading for repository 'gentoo'.
 * Use eselect news to read news items.

Calculating dependencies... done!

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) app-text/libpaper-1.1.24-r1
 * libpaper_1.1.24.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ...

        [ ok ]
>>> Unpacking source...
>>> Unpacking libpaper_1.1.24.tar.gz to /var/tmp/portage/app-text/libpaper-1.1.24-r1/work
>>> Source unpacked in /var/tmp/portage/app-text/libpaper-1.1.24-r1/work
>>> Preparing source in /var/tmp/portage/app-text/libpaper-1.1.24-r1/work/libpaper-1.1.24 ...
 * Running eautoreconf in
'/var/tmp/portage/app-text/libpaper-1.1.24-r1/work/libpaper-1.1.24'
...
 * Running libtoolize --install --copy --force --automake ...

        [ ok ]
 * Running aclocal ...

        [ !! ]

 * Failed Running aclocal !
 *
 * Include in your bugreport the contents of:
 *
 *   /var/tmp/portage/app-text/libpaper-1.1.24-r1/temp/aclocal.out

 * ERROR: app-text/libpaper-1.1.24-r1 failed (prepare phase):
 *   Failed Running aclocal !
 *
 * Call stack:
 *     ebuild.sh, line   93:  Called src_prepare
 *   environment, line 2826:  Called eautoreconf
 *   environment, line  764:  Called eaclocal
 *   environment, line  667:  Called autotools_run_tool '--at-m4flags' 'aclocal'
 *   environment, line  537:  Called die
 * The specific snippet of code:
 *           die "Failed Running $1 !";
 *
 * If you need support, post the output of `emerge --info
'=app-text/libpaper-1.1.24-r1'`,
 * the complete build log and the output of `emerge -pqv
'=app-text/libpaper-1.1.24-r1'`.
/usr/lib/portage/bin/isolated-functions.sh: line 215: wait: `Failed
Running aclocal !': not a pid or valid job spec
 * The complete build log is located at
'/var/tmp/portage/app-text/libpaper-1.1.24-r1/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/app-text/libpaper-1.1.24-r1/temp/environment'.
 * Working directory:
'/var/tmp/portage/app-text/libpaper-1.1.24-r1/work/libpaper-1.1.24'
 * S: '/var/tmp/portage/app-text/libpaper-1.1.24-r1/work/libpaper-1.1.24'

>>> Failed to emerge app-text/libpaper-1.1.24-r1, Log file:

>>>  '/var/tmp/portage/app-text/libpaper-1.1.24-r1/temp/build.log'




Checking  /var/tmp/portage/app-text/libpaper-1.1.24-r1/temp/aclocal.out we see:

 # cat  /var/tmp/portage/app-text/libpaper-1.1.24-r1/temp/aclocal.out
***** aclocal *****
***** PWD: /var/tmp/portage/app-text/libpaper-1.1.24-r1/work/libpaper-1.1.24
***** aclocal

configure.ac:6: error: 'AM_CONFIG_HEADER': this macro is obsolete.
    You should use the 'AC_CONFIG_HEADERS' macro instead.
/usr/share/aclocal-1.13/obsolete-err.m4:12: AM_CONFIG_HEADER is expanded from...
configure.ac:6: the top level
autom4te-2.69: /usr/bin/m4 failed with exit status: 1
aclocal-1.13: error: echo failed with exit status: 1


More info, I have just installed this system with the base Gentoo
system installed. I'm trying to get all the rest (X, KDE, ...)
installed.

Thanks

   Rafa

Re: [gentoo-user] Problems with aclocal

[Jackie]

在 Thu, 02 May 2013 20:22:26 +0800，Rafa Griman <rafagriman@gmail.com>  
写道:

> Hi !!
>
> On Thu, May 2, 2013 at 6:18 AM, Jackie <jiangjun12321@gmail.com> wrote:
>> 在 Thu, 02 May 2013 06:39:02 +0800，Neil Bothwick <neil@digimed.co.uk>  
>> 写道:
>>
>>
>>> On Wed, 1 May 2013 23:05:18 +0200, Rafa Griman wrote:
>>>
>>>> Got some problems with aclocal :( When running:
>>>>
>>>>     emerge -avDuN --with-bdeps=y world
>>>>
>>>> I get a whole bunch of packages who won't install nor upgrade with the
>>>> following error:
>>>>
>>>>      Failed Running aclocal !
>>>>
>>>> Looking through the Forums I saw I've got to mask autoconf. So I added
>>>> autoconf to:
>>>>
>>>>      /etc/portage/package.mask
>>>
>>>
>>> That's what you get with the forums, aclocal isn't even part of  
>>> autoconf,
>>> it is provided by automake-wrapper.
>>>
>>>> And now I get a whole bunch of errors saying autoconf is masked and I
>>>> have to unmask it ... which takes me back to step 1 ...
>>>
>>>
>>> There have been issues with automake-1.13. I have seen a similar error  
>>> on
>>> one package and worked around it with
>>>
>>> WANT_AUTOMAKE=1.12 emerge -1 cat/package
>>
>>
>>
>> Also get the same problem here two days ago when I was trying to emerge
>> bootchart2.After searching through the Internet I also noticed that it  
>> had
>> sth to do with automake-1.13,I masked it and problem solved.
>>
>
>
> Masked 1.13 and portage installs 2.69 ... still have the same error.
> This is what I've got:
>
>  # equery list '*' | grep -iE "(automake|autoconf)"
> sys-devel/autoconf-2.69
> sys-devel/autoconf-wrapper-13
> sys-devel/automake-1.13.1
> sys-devel/automake-wrapper-8
>
>
> This is ONE of the package I'm trying to install (with the included
> error), there are another 75:
> # emerge  app-text/libpaper
>
>  * IMPORTANT: 4 news items need reading for repository 'gentoo'.
>  * Use eselect news to read news items.
>
> Calculating dependencies... done!
>
>>>> Verifying ebuild manifests
>
>>>> Emerging (1 of 1) app-text/libpaper-1.1.24-r1
>  * libpaper_1.1.24.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ...
>
>         [ ok ]
>>>> Unpacking source...
>>>> Unpacking libpaper_1.1.24.tar.gz to  
>>>> /var/tmp/portage/app-text/libpaper-1.1.24-r1/work
>>>> Source unpacked in /var/tmp/portage/app-text/libpaper-1.1.24-r1/work
>>>> Preparing source in  
>>>> /var/tmp/portage/app-text/libpaper-1.1.24-r1/work/libpaper-1.1.24 ...
>  * Running eautoreconf in
> '/var/tmp/portage/app-text/libpaper-1.1.24-r1/work/libpaper-1.1.24'
> ...
>  * Running libtoolize --install --copy --force --automake ...
>
>         [ ok ]
>  * Running aclocal ...
>
>         [ !! ]
>
>  * Failed Running aclocal !
>  *
>  * Include in your bugreport the contents of:
>  *
>  *   /var/tmp/portage/app-text/libpaper-1.1.24-r1/temp/aclocal.out
>
>  * ERROR: app-text/libpaper-1.1.24-r1 failed (prepare phase):
>  *   Failed Running aclocal !
>  *
>  * Call stack:
>  *     ebuild.sh, line   93:  Called src_prepare
>  *   environment, line 2826:  Called eautoreconf
>  *   environment, line  764:  Called eaclocal
>  *   environment, line  667:  Called autotools_run_tool '--at-m4flags'  
> 'aclocal'
>  *   environment, line  537:  Called die
>  * The specific snippet of code:
>  *           die "Failed Running $1 !";
>  *
>  * If you need support, post the output of `emerge --info
> '=app-text/libpaper-1.1.24-r1'`,
>  * the complete build log and the output of `emerge -pqv
> '=app-text/libpaper-1.1.24-r1'`.
> /usr/lib/portage/bin/isolated-functions.sh: line 215: wait: `Failed
> Running aclocal !': not a pid or valid job spec
>  * The complete build log is located at
> '/var/tmp/portage/app-text/libpaper-1.1.24-r1/temp/build.log'.
>  * The ebuild environment file is located at
> '/var/tmp/portage/app-text/libpaper-1.1.24-r1/temp/environment'.
>  * Working directory:
> '/var/tmp/portage/app-text/libpaper-1.1.24-r1/work/libpaper-1.1.24'
>  * S: '/var/tmp/portage/app-text/libpaper-1.1.24-r1/work/libpaper-1.1.24'
>
>>>> Failed to emerge app-text/libpaper-1.1.24-r1, Log file:
>
>>>>  '/var/tmp/portage/app-text/libpaper-1.1.24-r1/temp/build.log'
>
>
>
>
> Checking  /var/tmp/portage/app-text/libpaper-1.1.24-r1/temp/aclocal.out  
> we see:
>
>  # cat  /var/tmp/portage/app-text/libpaper-1.1.24-r1/temp/aclocal.out
> ***** aclocal *****
> ***** PWD:  
> /var/tmp/portage/app-text/libpaper-1.1.24-r1/work/libpaper-1.1.24
> ***** aclocal
>
> configure.ac:6: error: 'AM_CONFIG_HEADER': this macro is obsolete.
>     You should use the 'AC_CONFIG_HEADERS' macro instead.
> /usr/share/aclocal-1.13/obsolete-err.m4:12: AM_CONFIG_HEADER is expanded  
> from...
> configure.ac:6: the top level
> autom4te-2.69: /usr/bin/m4 failed with exit status: 1
> aclocal-1.13: error: echo failed with exit status: 1
>
>
> More info, I have just installed this system with the base Gentoo
> system installed. I'm trying to get all the rest (X, KDE, ...)
> installed.
>
> Thanks
>
>    Rafa
>


My problem was similiar to Rafa's,though I was compiling  
dev-python/pygtk-2.24.0-r3.But I also got same autom4te & aclcal error as  
Rafa.But I just masked automake-1.13.1 downgraded to automake-1.12.6 and  
the compilation went through,then I unmasked automake-1.31.1 and upgraded  
it back again.Maybe you can try it,too.Just to solve the problem for  
now.(After I upgradeed automake to 1.13.1,I compiled   
dev-python/pygtk-2.24.0-r3,the same error appeared again,so it seemed that  
sth might be wrong with automake-1.13.1)

Jackie

Re: [gentoo-user] Problems with aclocal

[Alan McKinnon]

On 02/05/2013 17:09, Jackie wrote:
> My problem was similiar to Rafa's,though I was compiling
> dev-python/pygtk-2.24.0-r3.But I also got same autom4te & aclcal error
> as Rafa.But I just masked automake-1.13.1 downgraded to automake-1.12.6
> and the compilation went through,then I unmasked automake-1.31.1 and
> upgraded it back again.Maybe you can try it,too.Just to solve the
> problem for now.(After I upgradeed automake to 1.13.1,I compiled 
> dev-python/pygtk-2.24.0-r3,the same error appeared again,so it seemed
> that sth might be wrong with automake-1.13.1)

The easiest way to deal with that if it's just a single package failing is

WANT_AUTOMAKE=<version> emerge ....

It tells portage to not try autodetect stuff but rather to use the SLOT
specified by you.
In this case though, the breakage seems to be somewhat more than just a
few packages, which probably requires masking till automake is fixed
properly.

The whole thing is rather a scathing comment at whoever committed the
automake change, as quite obviously the correct answer to "How much
testing did you do?" is "very little if any"

-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Problems with aclocal

[Rafa Griman]

Yo Alan !!

On Thu, May 2, 2013 at 5:15 PM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> On 02/05/2013 17:09, Jackie wrote:
>> My problem was similiar to Rafa's,though I was compiling
>> dev-python/pygtk-2.24.0-r3.But I also got same autom4te & aclcal error
>> as Rafa.But I just masked automake-1.13.1 downgraded to automake-1.12.6
>> and the compilation went through,then I unmasked automake-1.31.1 and
>> upgraded it back again.Maybe you can try it,too.Just to solve the
>> problem for now.(After I upgradeed automake to 1.13.1,I compiled
>> dev-python/pygtk-2.24.0-r3,the same error appeared again,so it seemed
>> that sth might be wrong with automake-1.13.1)
>
> The easiest way to deal with that if it's just a single package failing is
>
> WANT_AUTOMAKE=<version> emerge ....
>
> It tells portage to not try autodetect stuff but rather to use the SLOT
> specified by you.
> In this case though, the breakage seems to be somewhat more than just a
> few packages, which probably requires masking till automake is fixed
> properly.


That's what I was trying but I guess I was masking blindly. As you
say, WANT_AUTOMAKE is useful when you've got just a handful of
packages. In my case ... let's say you've got big hands and both of
them are full ;)

I'll try to figure out what has to me masked. I'll check what Jackie
says in his e-mail and see if I get it working.


> The whole thing is rather a scathing comment at whoever committed the
> automake change, as quite obviously the correct answer to "How much
> testing did you do?" is "very little if any"


Well ... I'm testing right now ;) So if the developer/maintainer is
reading this thread ... hope it helps in some way. I can send him all
the info he might need/want.

Thanks guys !!

   Rafa

Re: [gentoo-user] Problems with aclocal

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 431 bytes --]

On Thu, 02 May 2013 17:15:15 +0200, Alan McKinnon wrote:

> The whole thing is rather a scathing comment at whoever committed the
> automake change, as quite obviously the correct answer to "How much
> testing did you do?" is "very little if any"

Look at the number of bugs depending on this :-O

https://bugs.gentoo.org/show_bug.cgi?id=451744


-- 
Neil Bothwick

30 minutes of begging is not considered foreplay.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Problems with aclocal

[Rafa Griman]

On Thu, May 2, 2013 at 7:10 PM, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Thu, 02 May 2013 17:15:15 +0200, Alan McKinnon wrote:
>
>> The whole thing is rather a scathing comment at whoever committed the
>> automake change, as quite obviously the correct answer to "How much
>> testing did you do?" is "very little if any"
>
> Look at the number of bugs depending on this :-O
>
> https://bugs.gentoo.org/show_bug.cgi?id=451744

Wow !!!

Re: [gentoo-user] Problems with aclocal

[Rafa Griman]

Jackie !!

On Thu, May 2, 2013 at 5:09 PM, Jackie <jiangjun12321@gmail.com> wrote:

[...]

> My problem was similiar to Rafa's,though I was compiling
> dev-python/pygtk-2.24.0-r3.But I also got same autom4te & aclcal error as
> Rafa.But I just masked automake-1.13.1 downgraded to automake-1.12.6 and the
> compilation went through,then I unmasked automake-1.31.1 and upgraded it
> back again.Maybe you can try it,too.Just to solve the problem for now.(After
> I upgradeed automake to 1.13.1,I compiled  dev-python/pygtk-2.24.0-r3,the
> same error appeared again,so it seemed that sth might be wrong with
> automake-1.13.1)


I'll try this with a bit more time. I guess I was masking "wrongly"
and I was missing something.

Thanks for your help !!

   Rafa

Re: [gentoo-user] Problems with aclocal

[Rafa Griman]

Hi Neil,

On Thu, May 2, 2013 at 12:39 AM, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Wed, 1 May 2013 23:05:18 +0200, Rafa Griman wrote:
>
>> Got some problems with aclocal :( When running:
>>
>>     emerge -avDuN --with-bdeps=y world
>>
>> I get a whole bunch of packages who won't install nor upgrade with the
>> following error:
>>
>>      Failed Running aclocal !
>>
>> Looking through the Forums I saw I've got to mask autoconf. So I added autoconf to:
>>
>>      /etc/portage/package.mask
>
> That's what you get with the forums, aclocal isn't even part of autoconf,
> it is provided by automake-wrapper.


I know, that's why I posted in another mail the automake and
automake-wrapper versions I've got installed.


>> And now I get a whole bunch of errors saying autoconf is masked and I
>> have to unmask it ... which takes me back to step 1 ...
>
> There have been issues with automake-1.13. I have seen a similar error on
> one package and worked around it with
>
> WANT_AUTOMAKE=1.12 emerge -1 cat/package


Tried this too, still get errors :(

Thanks for your time,

   Rafa

Re: [gentoo-user] Problems with aclocal

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 701 bytes --]

On Thu, 2 May 2013 13:59:07 +0200, Rafa Griman wrote:

> > There have been issues with automake-1.13. I have seen a similar
> > error on one package and worked around it with
> >
> > WANT_AUTOMAKE=1.12 emerge -1 cat/package  
> 
> 
> Tried this too, still get errors :(

The same errors? I just tried rebuilding libpaper and got the aclocal
errors (more specifically, the error about AM_CONFIG_HEADER being
obsolete). But it worked with

WANT_AUTOMAKE=1.12 emerge -1a libpaper

Alternatively, there is a patch at
https://bugs.gentoo.org/show_bug.cgi?id=466952


-- 
Neil Bothwick

I stayed up all night playing poker with tarot cards. I got a full
house and four people died.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Problems with aclocal

[Rafa Griman]

On Thu, May 2, 2013 at 3:06 PM, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Thu, 2 May 2013 13:59:07 +0200, Rafa Griman wrote:
>
>> > There have been issues with automake-1.13. I have seen a similar
>> > error on one package and worked around it with
>> >
>> > WANT_AUTOMAKE=1.12 emerge -1 cat/package
>>
>>
>> Tried this too, still get errors :(
>
> The same errors?


Yup, same errors :( Posted them in response to Jackie's e-mail.


> I just tried rebuilding libpaper and got the aclocal
> errors (more specifically, the error about AM_CONFIG_HEADER being
> obsolete). But it worked with
>
> WANT_AUTOMAKE=1.12 emerge -1a libpaper


Can you list the autoconf, automake and automake-wrapper versions
you've got installed? Just to ckech your versions with mine.


> Alternatively, there is a patch at
> https://bugs.gentoo.org/show_bug.cgi?id=466952


I'll take a look. Thanks !!!

   Rafa

Re: [gentoo-user] Problems with aclocal

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 948 bytes --]

On Thu, 2 May 2013 16:43:05 +0200, Rafa Griman wrote:

> > I just tried rebuilding libpaper and got the aclocal
> > errors (more specifically, the error about AM_CONFIG_HEADER being
> > obsolete). But it worked with
> >
> > WANT_AUTOMAKE=1.12 emerge -1a libpaper  

> Can you list the autoconf, automake and automake-wrapper versions
> you've got installed? Just to ckech your versions with mine.

The latest testing release of each, I've nothing masked.

% qlist -ICv auto
sys-devel/autoconf-2.13
sys-devel/autoconf-2.69
sys-devel/autoconf-wrapper-13
sys-devel/autogen-5.17.3
sys-devel/automake-1.10.3
sys-devel/automake-1.11.6
sys-devel/automake-1.12.6
sys-devel/automake-1.13.1
sys-devel/automake-1.9.6-r3
sys-devel/automake-wrapper-8
sys-fs/zfs-auto-snapshot-9999


-- 
Neil Bothwick

Programming Language: (n.) a shorthand way of describing a series of bugs
                      to a computer or a programmer.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Problems with aclocal

[Rafa Griman]

Hi Neil,

On Thu, May 2, 2013 at 4:48 PM, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Thu, 2 May 2013 16:43:05 +0200, Rafa Griman wrote:
>
>> > I just tried rebuilding libpaper and got the aclocal
>> > errors (more specifically, the error about AM_CONFIG_HEADER being
>> > obsolete). But it worked with
>> >
>> > WANT_AUTOMAKE=1.12 emerge -1a libpaper
>
>> Can you list the autoconf, automake and automake-wrapper versions
>> you've got installed? Just to ckech your versions with mine.
>
> The latest testing release of each, I've nothing masked.
>
> % qlist -ICv auto
> sys-devel/autoconf-2.13
> sys-devel/autoconf-2.69
> sys-devel/autoconf-wrapper-13
> sys-devel/autogen-5.17.3
> sys-devel/automake-1.10.3
> sys-devel/automake-1.11.6
> sys-devel/automake-1.12.6
> sys-devel/automake-1.13.1
> sys-devel/automake-1.9.6-r3
> sys-devel/automake-wrapper-8
> sys-fs/zfs-auto-snapshot-9999


OK, unmasked what I had masked. And emerged autoconf and automake to
be at the same level as you :) Now I've got:

# qlist -ICv auto
sys-devel/autoconf-2.13
sys-devel/autoconf-2.69
sys-devel/autoconf-wrapper-13
sys-devel/autogen-5.17.3
sys-devel/automake-1.10.3
sys-devel/automake-1.11.6
sys-devel/automake-1.12.6
sys-devel/automake-1.13.1
sys-devel/automake-1.9.6-r3
sys-devel/automake-wrapper-8

And ... YES !!! Now it works !!!

Thanks a bunch Neil !!! Now I've got to do it with the other 70+
packages with the same error ;)

   Rafa

Re: [gentoo-user] Problems with aclocal

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 372 bytes --]

On Thu, 2 May 2013 18:08:45 +0200, Rafa Griman wrote:

> Thanks a bunch Neil !!! Now I've got to do it with the other 70+
> packages with the same error ;)

export WANT_AUTOMAKE=1.12
emerge @everything-that-needs-emerging

Don't forget to unset WANT_AUTOMAKE, or close the shell, when you're done.


-- 
Neil Bothwick

Runtime Error: Out of funny taglines!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Problems with aclocal

[Andre Lucas Falco]

[-- Attachment #1: Type: text/plain, Size: 623 bytes --]

2013/5/2 Neil Bothwick <neil@digimed.co.uk>

> On Thu, 2 May 2013 18:08:45 +0200, Rafa Griman wrote:
>
> > Thanks a bunch Neil !!! Now I've got to do it with the other 70+
> > packages with the same error ;)
>
> export WANT_AUTOMAKE=1.12
> emerge @everything-that-needs-emerging
>
> Don't forget to unset WANT_AUTOMAKE, or close the shell, when you're done.
>
>
> --
> Neil Bothwick
>
> Runtime Error: Out of funny taglines!
>

It's possible to use the package.env, described here:
http://wiki.gentoo.org/wiki//etc/portage/env.

I use this for 2 packages (ghostscript-gpl and orbit), runs flawlessly.

--
Andre Lucas Falco

[-- Attachment #2: Type: text/html, Size: 1250 bytes --]

Re: [gentoo-user] Problems with aclocal

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 798 bytes --]

On Thu, 2 May 2013 14:15:40 -0300, Andre Lucas Falco wrote:

> > export WANT_AUTOMAKE=1.12
> > emerge @everything-that-needs-emerging
> >
> > Don't forget to unset WANT_AUTOMAKE, or close the shell, when you're
> > done.

> It's possible to use the package.env, described here:
> http://wiki.gentoo.org/wiki//etc/portage/env.
> 
> I use this for 2 packages (ghostscript-gpl and orbit), runs flawlessly.

You could, but then you need to remove the settings when automake or the
ebuilds are fixed. Since a fixed ebuild won't necessarily have a version
bump, you'd continue using the old version after you don't have to.


-- 
Neil Bothwick

WORM: (n.) acronym for Write Once, Read Mangled. Used to describe a
      normally-functioning computer disk of the very latest design.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Problems with aclocal

[Andre Lucas Falco]

[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]

2013/5/2 Neil Bothwick <neil@digimed.co.uk>

> On Thu, 2 May 2013 14:15:40 -0300, Andre Lucas Falco wrote:
>
> > > export WANT_AUTOMAKE=1.12
> > > emerge @everything-that-needs-emerging
> > >
> > > Don't forget to unset WANT_AUTOMAKE, or close the shell, when you're
> > > done.
>
> > It's possible to use the package.env, described here:
> > http://wiki.gentoo.org/wiki//etc/portage/env.
> >
> > I use this for 2 packages (ghostscript-gpl and orbit), runs flawlessly.
>
> You could, but then you need to remove the settings when automake or the
> ebuilds are fixed. Since a fixed ebuild won't necessarily have a version
> bump, you'd continue using the old version after you don't have to.
>
>
> --
> Neil Bothwick
>
> WORM: (n.) acronym for Write Once, Read Mangled. Used to describe a
>       normally-functioning computer disk of the very latest design.
>

Ok, but for me, it's a perspective stuff, the bug (
https://bugs.gentoo.org/show_bug.cgi?id=451744) has 4 months, and the
packages those i need to compile won't solved.
I choose to manage my installations of Gentoo using package.env, but always
exists other solutions/corrections.


--
Andre Lucas Falco

[-- Attachment #2: Type: text/html, Size: 1966 bytes --]

[gentoo-user] Re: Problems with aclocal

[Steven J. Long]

Andre Lucas Falco wrote:
> > > It's possible to use the package.env, described here:
> > > http://wiki.gentoo.org/wiki//etc/portage/env.
> > >
> > > I use this for 2 packages (ghostscript-gpl and orbit), runs flawlessly.
> 2013/5/2 Neil Bothwick <neil@digimed.co.uk>
> >
> > You could, but then you need to remove the settings when automake or the
> > ebuilds are fixed. Since a fixed ebuild won't necessarily have a version
> > bump, you'd continue using the old version after you don't have to.

> Ok, but for me, it's a perspective stuff, the bug (
> https://bugs.gentoo.org/show_bug.cgi?id=451744) has 4 months, and the
> packages those i need to compile won't solved.

The linked url[1] states that the issue is automake-1.13.1 (and .0).
For the fix mentioned, i imagine it's the deprecation warning with -Werror, as
the feature is not removed til automake-1.14, which isn't in-tree.

I think 1.13.1 should be hard-masked, since it's clearly buggy, and 1.13.2 should
be here soon. In any event masking 1.13.1 yourself should be sufficient, for others
if not you, as you only have 2 packages failing.

Then again, that's what you get for running ~arch ;p

Still it's only compilation errors, not broken installs. Not sure what the brouhaha
is about: Gentoo users tend to react to compile problems like other distro users
react to broken libs, which gives the wrong impression to others (who thus think
Gentoo is really unstable in their terms, when the true issue is that some
software won't build.) Still, we're only human.

Regards,
steveL

[1] http://www.flameeyes.eu/autotools-mythbuster/forwardporting/automake.html
-- 
#friendly-coders -- We're friendly, but we're not /that/ friendly ;-)

Re: [gentoo-user] Problems with aclocal

[Rafa Griman]

Yo !!

On Thu, May 2, 2013 at 7:12 PM, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Thu, 2 May 2013 18:08:45 +0200, Rafa Griman wrote:
>
>> Thanks a bunch Neil !!! Now I've got to do it with the other 70+
>> packages with the same error ;)
>
> export WANT_AUTOMAKE=1.12
> emerge @everything-that-needs-emerging
>
> Don't forget to unset WANT_AUTOMAKE, or close the shell, when you're done.


I prefer to add it to make.conf (works well, I'm compiling right now)
and then comment it out. The only reason for this is that if this ever
happens again ... I just have to uncomment what I have in make.conf.
My memory is not that good and I know I'll forget as soon as
compilation finishes ;)

Thanks a bunch !!

   Rafa

Re: [gentoo-user] Problems with aclocal

[Alan McKinnon]

On 02/05/2013 13:59, Rafa Griman wrote:
> Hi Neil,
> 
> On Thu, May 2, 2013 at 12:39 AM, Neil Bothwick <neil@digimed.co.uk> wrote:
>> On Wed, 1 May 2013 23:05:18 +0200, Rafa Griman wrote:
>>
>>> Got some problems with aclocal :( When running:
>>>
>>>     emerge -avDuN --with-bdeps=y world
>>>
>>> I get a whole bunch of packages who won't install nor upgrade with the
>>> following error:
>>>
>>>      Failed Running aclocal !
>>>
>>> Looking through the Forums I saw I've got to mask autoconf. So I added autoconf to:
>>>
>>>      /etc/portage/package.mask
>>
>> That's what you get with the forums, aclocal isn't even part of autoconf,
>> it is provided by automake-wrapper.
> 
> 
> I know, that's why I posted in another mail the automake and
> automake-wrapper versions I've got installed.
> 
> 
>>> And now I get a whole bunch of errors saying autoconf is masked and I
>>> have to unmask it ... which takes me back to step 1 ...
>>
>> There have been issues with automake-1.13. I have seen a similar error on
>> one package and worked around it with
>>
>> WANT_AUTOMAKE=1.12 emerge -1 cat/package



This works for me too when emerging libpaper, I'm running ~amd64

Obviously first thing to check is that you ran the correct command
(typos being so easy to make), and did remove all the maskings you added
whilst debugging. If it then still fails, you should probably join the
fun at bugs.gentoo.org and provide full info there so the devs can deal
with it correctly.





> 
> 
> Tried this too, still get errors :(
> 
> Thanks for your time,
> 
>    Rafa
> 


-- 
Alan McKinnon
alan.mckinnon@gmail.com