Re: [gentoo-user] Problems with aclocal
Hi Neil, On Thu, May 2, 2013 at 12:39 AM, Neil Bothwick n...@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
Hi !! On Thu, May 2, 2013 at 6:18 AM, Jackie jiangjun12...@gmail.com wrote: 在 Thu, 02 May 2013 06:39:02 +0800，Neil Bothwick n...@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
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. signature.asc Description: PGP signature
Re: [gentoo-user] Problems with aclocal
On 02/05/2013 13:59, Rafa Griman wrote: Hi Neil, On Thu, May 2, 2013 at 12:39 AM, Neil Bothwick n...@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.mckin...@gmail.com
Re: [gentoo-user] Problems with aclocal
On Thu, May 2, 2013 at 3:06 PM, Neil Bothwick n...@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
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- -- Neil Bothwick Programming Language: (n.) a shorthand way of describing a series of bugs to a computer or a programmer. signature.asc Description: PGP signature
Re: [gentoo-user] Problems with aclocal
在 Thu, 02 May 2013 20:22:26 +0800，Rafa Griman rafagri...@gmail.com 写道: Hi !! On Thu, May 2, 2013 at 6:18 AM, Jackie jiangjun12...@gmail.com wrote: 在 Thu, 02 May 2013 06:39:02 +0800，Neil Bothwick n...@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
Re: [gentoo-user] Problems with aclocal
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.mckin...@gmail.com
Re: [gentoo-user] Problems with aclocal
Hi Neil, On Thu, May 2, 2013 at 4:48 PM, Neil Bothwick n...@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- 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
Yo Alan !! On Thu, May 2, 2013 at 5:15 PM, Alan McKinnon alan.mckin...@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
Jackie !! On Thu, May 2, 2013 at 5:09 PM, Jackie jiangjun12...@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
[gentoo-user] Delays while building Libre Office.
Hi, Gentoo. I've just built libreoffice-3.6.6.2 and it took 2 hours 10 minutes on my 2.6 GHz quad core Athlon 2. It used to take about an hour. Watching the build, it became evident that the first 50 minutes or so was taken up by several hundred mkdir operations (more precisely, mkdir -p long path). Some of these mkdir's would take, perhaps, a minute to execute. All the while, top showed make taking 100% of one core. There seems to be something suboptimal here. Has anybody else seen this, or does anybody have any ideas how to fix the problem? -- Alan Mackenzie (Nuremberg, Germany).
Re: [gentoo-user] Delays while building Libre Office.
On 05/02/2013 12:27 PM, Alan Mackenzie wrote: Hi, Gentoo. I've just built libreoffice-3.6.6.2 and it took 2 hours 10 minutes on my 2.6 GHz quad core Athlon 2. It used to take about an hour. Watching the build, it became evident that the first 50 minutes or so was taken up by several hundred mkdir operations (more precisely, mkdir -p long path). Some of these mkdir's would take, perhaps, a minute to execute. All the while, top showed make taking 100% of one core. There seems to be something suboptimal here. Has anybody else seen this, or does anybody have any ideas how to fix the problem? Long delays suggest a timeout of some sort. First thing I'd look at is the filesystem underneath, and the disk underneath that. Second thing I'd look at is to see if permissions checks might be bouncing through something like kerberos, samba or ldap. Do you have any single-signon things configured on that machine? signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] Delays while building Libre Office.
130502 Alan Mackenzie wrote: I've just built libreoffice-3.6.6.2 and it took 2 hours 10 minutes on my 2.6 GHz quad core Athlon 2. It used to take about an hour. I've been using 4.0.0.1 w/o problems since 130113 : 4.0.2.2 is in testing. It took 1 h 10 m used c 3,5 GB for temporary storage. You might try it report the result. You have to be careful if you mix stable/testing for system pkgs, but using the testing version of something well-maintained, like LO or KDE, shouldn't cause problems normally. -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
Re: [gentoo-user] Delays while building Libre Office.
On Thu, May 02, 2013 at 12:33:37PM -0400, Michael Mol wrote: On 05/02/2013 12:27 PM, Alan Mackenzie wrote: Hi, Gentoo. I've just built libreoffice-3.6.6.2 and it took 2 hours 10 minutes on my 2.6 GHz quad core Athlon 2. It used to take about an hour. Watching the build, it became evident that the first 50 minutes or so was taken up by several hundred mkdir operations (more precisely, mkdir -p long path). Some of these mkdir's would take, perhaps, a minute to execute. All the while, top showed make taking 100% of one core. There seems to be something suboptimal here. Has anybody else seen this, or does anybody have any ideas how to fix the problem? Long delays suggest a timeout of some sort. OK. As a matter of interest, some of the mkdirs executed relatively quickly - perhaps in 0.5 seconds. I never saw the screen whizzing by as I ought to have done, though. First thing I'd look at is the filesystem underneath, and the disk underneath that. My /var is an ext3 LVM partition, doubled up on a RAID-1 disk array. In the middle of the mkdiring, I checked there were enough inodes free (there were). I've no reason to suspect the disk drives might be flaky. Second thing I'd look at is to see if permissions checks might be bouncing through something like kerberos, samba or ldap. Do you have any single-signon things configured on that machine? I've not got kerberos or samba installed. I appear to have ldap (whatever that might be ;-). ls -lurt /usr/bin/ldap* shows these binaries were last accessed (?used) on 2012-03-14. What exactly do you mean by single-signon? -- Alan Mackenzie (Nuremberg, Germany).
Re: [gentoo-user] Problems with aclocal
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. signature.asc Description: PGP signature
Re: [gentoo-user] Problems with aclocal
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! signature.asc Description: PGP signature
Re: [gentoo-user] Problems with aclocal
2013/5/2 Neil Bothwick n...@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
Re: [gentoo-user] Delays while building Libre Office.
On 05/02/2013 12:58 PM, Alan Mackenzie wrote: On Thu, May 02, 2013 at 12:33:37PM -0400, Michael Mol wrote: On 05/02/2013 12:27 PM, Alan Mackenzie wrote: Hi, Gentoo. I've just built libreoffice-3.6.6.2 and it took 2 hours 10 minutes on my 2.6 GHz quad core Athlon 2. It used to take about an hour. Watching the build, it became evident that the first 50 minutes or so was taken up by several hundred mkdir operations (more precisely, mkdir -p long path). Some of these mkdir's would take, perhaps, a minute to execute. All the while, top showed make taking 100% of one core. There seems to be something suboptimal here. Has anybody else seen this, or does anybody have any ideas how to fix the problem? Long delays suggest a timeout of some sort. OK. As a matter of interest, some of the mkdirs executed relatively quickly - perhaps in 0.5 seconds. I never saw the screen whizzing by as I ought to have done, though. Hm. First thing I'd look at is the filesystem underneath, and the disk underneath that. My /var is an ext3 LVM partition, doubled up on a RAID-1 disk array. How full is the ext3 partition? What options do you have enabled on it? (e.g. dir indexing?) In the middle of the mkdiring, I checked there were enough inodes free (there were). I've no reason to suspect the disk drives might be flaky. Well, you kinda do, now; you have evidence that at least some disk access is unusually slow. Check dmesg for disk I/O errors (unlikely to be reported at this point; I'm sure you checked whether your RAID was in a degraded state), and run commanded smartctl tests on the disks. Second thing I'd look at is to see if permissions checks might be bouncing through something like kerberos, samba or ldap. Do you have any single-signon things configured on that machine? I've not got kerberos or samba installed. I appear to have ldap (whatever that might be ;-). ls -lurt /usr/bin/ldap* shows these binaries were last accessed (?used) on 2012-03-14. It would be more a question of whether they were tied into PAM. What exactly do you mean by single-signon? Well, that was a slip of the tongue. More central auth. I was wondering if there were any features installed on your system that are designed to check authorization against a server somewhere. (i.e. you can use an LDAP directory to centrally manage things like users, groups, etc.) Technically, single-signon combines authorization checks with persistent authentication checks. Examples of this include kerberos, web session cookies and some uses of OAuth; once you're authenticated, the mechanism ensures you don't need to authenticate to another server in the same auth realm so long as your existing session hasn't expired. But this is less likely to be related to your problem than something seeking to ask a server if you have authorization to access something. signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] Problems with aclocal
On Thu, May 2, 2013 at 7:10 PM, Neil Bothwick n...@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
Yo !! On Thu, May 2, 2013 at 7:12 PM, Neil Bothwick n...@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
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. signature.asc Description: PGP signature
Re: [gentoo-user] Problems with aclocal
2013/5/2 Neil Bothwick n...@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
[gentoo-user] Postfixadmin Vacation (and maybe other perl based mailers) broken with Mail-Sender-0.8.22
Hi all, In case anyone else bumps into this (and I'm surprised no one noticed this before now)... One of our employees just reported that they didn't get a vacation response when they should have (ugh, I know, but the boss has mandated that we have a working vacation message capability), and upon investigation, it is definitely broken. I went back through the logs, and discovered that it stopped working on April 7th, right after I updated a bunch of perl stuff, among them the Mail-Sender (updated to 0.8.22). Reverting it to 0.8.21 fixes it. Not sure if this is an upstream bug or something with the ebuild. Bug reported: https://bugs.gentoo.org/show_bug.cgi?id=468316
Re: [gentoo-user] Delays while building Libre Office.
On Thu, May 02, 2013 at 01:15:58PM -0400, Michael Mol wrote: On 05/02/2013 12:58 PM, Alan Mackenzie wrote: On Thu, May 02, 2013 at 12:33:37PM -0400, Michael Mol wrote: On 05/02/2013 12:27 PM, Alan Mackenzie wrote: Hi, Gentoo. I've just built libreoffice-3.6.6.2 and it took 2 hours 10 minutes on my 2.6 GHz quad core Athlon 2. It used to take about an hour. Watching the build, it became evident that the first 50 minutes or so was taken up by several hundred mkdir operations (more precisely, mkdir -p long path). Some of these mkdir's would take, perhaps, a minute to execute. All the while, top showed make taking 100% of one core. There seems to be something suboptimal here. Has anybody else seen this, or does anybody have any ideas how to fix the problem? Long delays suggest a timeout of some sort. OK. As a matter of interest, some of the mkdirs executed relatively quickly - perhaps in 0.5 seconds. I never saw the screen whizzing by as I ought to have done, though. Hm. First thing I'd look at is the filesystem underneath, and the disk underneath that. My /var is an ext3 LVM partition, doubled up on a RAID-1 disk array. How full is the ext3 partition? What options do you have enabled on it? (e.g. dir indexing?) root@acm ~ # df /var Filesystem 1K-blocksUsed Available Use% Mounted on /dev/mapper/vg-var 12385456 1959860 9796580 17% /var In the middle of the mkdiring, I checked there were enough inodes free (there were). I've no reason to suspect the disk drives might be flaky. Well, you kinda do, now; The reason I say this is that building the last ?one/two/three versions of libreoffice also gave me this grief, but I haven't noticed anything else amiss. you have evidence that at least some disk access is unusually slow. Check dmesg for disk I/O errors (unlikely to be reported at this point; Nothing awry in dmesg. I'm sure you checked whether your RAID was in a degraded state), cat /proc/mdstat shows everything in order. and run commanded smartctl tests on the disks. That I haven't done, yet. Second thing I'd look at is to see if permissions checks might be bouncing through something like kerberos, samba or ldap. Do you have any single-signon things configured on that machine? I've not got kerberos or samba installed. I appear to have ldap (whatever that might be ;-). ls -lurt /usr/bin/ldap* shows these binaries were last accessed (?used) on 2012-03-14. It would be more a question of whether they were tied into PAM. OK. I'm sadly ignorant about PAM. :-( What exactly do you mean by single-signon? Well, that was a slip of the tongue. More central auth. I was wondering if there were any features installed on your system that are designed to check authorization against a server somewhere. (i.e. you can use an LDAP directory to centrally manage things like users, groups, etc.) Not that I know of. My machine is a mere desktop connected via a router/modem to the net. I'd have no reason to install any auth stuff. Technically, single-signon combines authorization checks with persistent authentication checks. Examples of this include kerberos, web session cookies and some uses of OAuth; once you're authenticated, the mechanism ensures you don't need to authenticate to another server in the same auth realm so long as your existing session hasn't expired. But this is less likely to be related to your problem than something seeking to ask a server if you have authorization to access something. If this were the case, what would libreoffice's build need to ask that no other package stumbles over? -- Alan Mackenzie (Nuremberg, Germany).
Re: [gentoo-user] Delays while building Libre Office.
On 05/02/2013 02:47 PM, Alan Mackenzie wrote: On Thu, May 02, 2013 at 01:15:58PM -0400, Michael Mol wrote: On 05/02/2013 12:58 PM, Alan Mackenzie wrote: On Thu, May 02, 2013 at 12:33:37PM -0400, Michael Mol wrote: On 05/02/2013 12:27 PM, Alan Mackenzie wrote: Hi, Gentoo. I've just built libreoffice-3.6.6.2 and it took 2 hours 10 minutes on my 2.6 GHz quad core Athlon 2. It used to take about an hour. Watching the build, it became evident that the first 50 minutes or so was taken up by several hundred mkdir operations (more precisely, mkdir -p long path). Some of these mkdir's would take, perhaps, a minute to execute. All the while, top showed make taking 100% of one core. There seems to be something suboptimal here. Has anybody else seen this, or does anybody have any ideas how to fix the problem? Long delays suggest a timeout of some sort. OK. As a matter of interest, some of the mkdirs executed relatively quickly - perhaps in 0.5 seconds. I never saw the screen whizzing by as I ought to have done, though. Hm. First thing I'd look at is the filesystem underneath, and the disk underneath that. My /var is an ext3 LVM partition, doubled up on a RAID-1 disk array. How full is the ext3 partition? What options do you have enabled on it? (e.g. dir indexing?) root@acm ~ # df /var Filesystem 1K-blocksUsed Available Use% Mounted on /dev/mapper/vg-var 12385456 1959860 9796580 17% /var In the middle of the mkdiring, I checked there were enough inodes free (there were). I've no reason to suspect the disk drives might be flaky. Well, you kinda do, now; The reason I say this is that building the last ?one/two/three versions of libreoffice also gave me this grief, but I haven't noticed anything else amiss. you have evidence that at least some disk access is unusually slow. Check dmesg for disk I/O errors (unlikely to be reported at this point; Nothing awry in dmesg. I'm sure you checked whether your RAID was in a degraded state), cat /proc/mdstat shows everything in order. and run commanded smartctl tests on the disks. That I haven't done, yet. Second thing I'd look at is to see if permissions checks might be bouncing through something like kerberos, samba or ldap. Do you have any single-signon things configured on that machine? I've not got kerberos or samba installed. I appear to have ldap (whatever that might be ;-). ls -lurt /usr/bin/ldap* shows these binaries were last accessed (?used) on 2012-03-14. It would be more a question of whether they were tied into PAM. OK. I'm sadly ignorant about PAM. :-( If you've just got a single box, it's very unlikely this is your problem. What exactly do you mean by single-signon? Well, that was a slip of the tongue. More central auth. I was wondering if there were any features installed on your system that are designed to check authorization against a server somewhere. (i.e. you can use an LDAP directory to centrally manage things like users, groups, etc.) Not that I know of. My machine is a mere desktop connected via a router/modem to the net. I'd have no reason to install any auth stuff. Technically, single-signon combines authorization checks with persistent authentication checks. Examples of this include kerberos, web session cookies and some uses of OAuth; once you're authenticated, the mechanism ensures you don't need to authenticate to another server in the same auth realm so long as your existing session hasn't expired. But this is less likely to be related to your problem than something seeking to ask a server if you have authorization to access something. If this were the case, what would libreoffice's build need to ask that no other package stumbles over? My presumption there was that this was a very recent thing, and LO's time-to-build makes it easier to observe. Anyway, floor's open to anyone else who might have an idea. signature.asc Description: OpenPGP digital signature
[gentoo-user] texlive-basic
Hello,
have someone run the texlive update succesfully? I have problems with
building.
The message:
###
fmtutil: Error! Not all formats have been built successfully.
Visit the log files in directory
/var/tmp/portage/dev-texlive/texlive-basic-2012/work/texmf-var/web2c
for details.
###
This is a summary of all `failed' messages:
`luatex -ini -jobname=dviluatex -progname=dviluatex dviluatex.ini' failed
`luatex -ini -jobname=luatex -progname=luatex luatex.ini' failed
* ERROR: dev-texlive/texlive-basic-2012 failed (compile phase):
* failed to build format texmf/fmtutil/format.texlive-basic.cnf
*
* Call stack:
* ebuild.sh, line 93: Called src_compile
* environment, line 2195: Called texlive-module_src_compile
* environment, line 2834: Called die
* The specific snippet of code:
* VARTEXFONTS=${T}/fonts
TEXMFHOME=${S}/texmf:${S}/texmf-dist:${S}/texmf-var env -u TEXINPUTS fmtutil
--cnffile ${i} --fmtdir ${S}/texmf-var/web2c --all || die failed to build
format ${i};
*
* If you need support, post the output of `emerge --info
'=dev-texlive/texlive-basic-2012'`,
* the complete build log and the output of `emerge -pqv
'=dev-texlive/texlive-basic-2012'`.
* The complete build log is located at
'/var/tmp/portage/dev-texlive/texlive-basic-2012/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp/portage/dev-texlive/texlive-basic-2012/temp/environment'.
* Working directory: '/var/tmp/portage/dev-texlive/texlive-basic-2012/work'
* S: '/var/tmp/portage/dev-texlive/texlive-basic-2012/work'
Failed to emerge dev-texlive/texlive-basic-2012, Log file:
gentoo-mobile siefke # emerge -pqv =dev-texlive/texlive-basic-2012
[ebuild U ] dev-texlive/texlive-basic-2012 [2011-r1] USE=-doc -source
emerge --info =dev-texlive/texlive-basic-2012
http://nopaste.info/09608209ae.html
Thank you Greetings
Silvio
Re: [gentoo-user] texlive-basic
Hello Silvio,
Silvio Siefke wrote:
Hello,
have someone run the texlive update succesfully? I have problems with
building.
The message:
###
fmtutil: Error! Not all formats have been built successfully.
Visit the log files in directory
/var/tmp/portage/dev-texlive/texlive-basic-2012/work/texmf-var/web2c
for details.
###
This is a summary of all `failed' messages:
`luatex -ini -jobname=dviluatex -progname=dviluatex dviluatex.ini' failed
`luatex -ini -jobname=luatex -progname=luatex luatex.ini' failed
* ERROR: dev-texlive/texlive-basic-2012 failed (compile phase):
* failed to build format texmf/fmtutil/format.texlive-basic.cnf
*
* Call stack:
* ebuild.sh, line 93: Called src_compile
* environment, line 2195: Called texlive-module_src_compile
* environment, line 2834: Called die
* The specific snippet of code:
* VARTEXFONTS=${T}/fonts
TEXMFHOME=${S}/texmf:${S}/texmf-dist:${S}/texmf-var env -u TEXINPUTS
fmtutil --cnffile ${i} --fmtdir ${S}/texmf-var/web2c --all || die failed
to build format ${i};
*
* If you need support, post the output of `emerge --info
'=dev-texlive/texlive-basic-2012'`,
* the complete build log and the output of `emerge -pqv
'=dev-texlive/texlive-basic-2012'`.
* The complete build log is located at
'/var/tmp/portage/dev-texlive/texlive-basic-2012/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp/portage/dev-texlive/texlive-basic-2012/temp/environment'.
* Working directory: '/var/tmp/portage/dev-texlive/texlive-basic-2012/work'
* S: '/var/tmp/portage/dev-texlive/texlive-basic-2012/work'
That error occurred on my 32-Bit systems, too (interestingly, not on any
amd64 system). Was easily solved by recompiling luatex, it had some
broken dependency not detected by revdep-rebuild.
To check that, maybe try running luatex on the console, it crashed
instantly on my boxes until it was re-emerged...
Thank you Greetings Silvio
Regards,
Felix
Re: [gentoo-user] Re: GSettings-to-GConf problem
On Tue, Apr 30, 2013 at 09:02:04PM -0700, Grant wrote I see your thread on gentoo-dev. Many thanks for taking this to the right place. The solution seems to be keywording a bunch of ~arch gnome stuff. I don't know if my solution will be your solution. As per my sig, I don't run the fullblown GNOME DE. I use ICEWM. I happen to run a few GNOME apps (ABIWORD/GIMP/GNUMERIC). According to Alexandre... But if you are running IceWM, this should not be a problem. To get gsettings working, you only need 4 things: dbus, glib, dconf, and gsettings-desktop-schemas. And the latest stable versions of them would be sufficient. That'll be the way I go if Openoffice doesn't pan out. If you want to go testing on the fullblown GNOME, see... http://git.overlays.gentoo.org/gitweb/?p=proj/gnome.git;a=blob;f=status/portage-configs/package.keywords.gnome3 ...for a list of ebuilds to keyword. And I hope you enjoy PulseaudioG. -- Walter Dnes waltd...@waltdnes.org I don't run desktop environments; I run useful applications
Re: [gentoo-user] texlive-basic
On Thu, 2 May 2013 21:57:26 +0200
Silvio Siefke siefke_lis...@web.de wrote:
Hello,
have someone run the texlive update succesfully? I have
problems with building.
The message:
###
fmtutil: Error! Not all formats have been built
successfully. Visit the log files in directory
/var/tmp/portage/dev-texlive/texlive-basic-2012/work/texmf-var/web2c
for details.
###
This is a summary of all `failed' messages:
`luatex -ini -jobname=dviluatex -progname=dviluatex
dviluatex.ini' failed `luatex -ini -jobname=luatex
-progname=luatex luatex.ini' failed
* ERROR: dev-texlive/texlive-basic-2012 failed (compile
phase):
* failed to build format
texmf/fmtutil/format.texlive-basic.cnf
*
* Call stack:
* ebuild.sh, line 93: Called src_compile
* environment, line 2195: Called
texlive-module_src_compile
* environment, line 2834: Called die
* The specific snippet of code:
* VARTEXFONTS=${T}/fonts
TEXMFHOME=${S}/texmf:${S}/texmf-dist:${S}/texmf-var env
-u TEXINPUTS fmtutil --cnffile ${i} --fmtdir
${S}/texmf-var/web2c --all || die failed to build
format ${i};
*
* If you need support, post the output of `emerge --info
'=dev-texlive/texlive-basic-2012'`,
* the complete build log and the output of `emerge -pqv
'=dev-texlive/texlive-basic-2012'`.
* The complete build log is located at
'/var/tmp/portage/dev-texlive/texlive-basic-2012/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp/portage/dev-texlive/texlive-basic-2012/temp/environment'.
* Working directory:
'/var/tmp/portage/dev-texlive/texlive-basic-2012/work'
* S:
'/var/tmp/portage/dev-texlive/texlive-basic-2012/work'
Failed to emerge dev-texlive/texlive-basic-2012, Log
file:
gentoo-mobile siefke # emerge -pqv
=dev-texlive/texlive-basic-2012 [ebuild U ]
dev-texlive/texlive-basic-2012 [2011-r1] USE=-doc
-source emerge --info
=dev-texlive/texlive-basic-2012
http://nopaste.info/09608209ae.html
Thank you Greetings
Silvio
Hello Silvio
I had the same errors and needed to add -O2 to my CFLAGS.
I did edit /etc/make.conf and changed
CFLAGS=-march=native
to
CFLAGS=-O2 -march=native
I am running mostly stable on an old 32-bit laptop with
Intel(R) Core(TM) Duo CPU T2250 @ 1.73GHz processor. Hope
that helps.
Urs
