[gentoo-user] Re: Delays while building Libre Office.
On 05/05/2013 01:38 PM, Alan Mackenzie wrote: There doesn't appear to be any action in emerge which unpacks the build files (or even the entire source) of a package for perusal. This is a shame. You should become familiar with the 'ebuild' command, which I use very often when trying to debug a package, e.g. #ebuild /usr/portage/app-office/libreoffice/libreoffice-3.6.6.2.ebuild unpack To completely build and install a package you need to follow that command with the 'configure', 'compile', 'install', and 'qmerge' steps (man ebuild). This method allows you to resume an emerge without starting from zero. It saves a lot of pain when dealing with a package like libreoffice :)
Re: [gentoo-user] Re: Delays while building Libre Office.
Am 07.05.2013 01:22, schrieb walt: On 05/05/2013 01:38 PM, Alan Mackenzie wrote: There doesn't appear to be any action in emerge which unpacks the build files (or even the entire source) of a package for perusal. This is a shame. You should become familiar with the 'ebuild' command, which I use very often when trying to debug a package, e.g. #ebuild /usr/portage/app-office/libreoffice/libreoffice-3.6.6.2.ebuild unpack To completely build and install a package you need to follow that command with the 'configure', 'compile', 'install', and 'qmerge' steps (man ebuild). If you are lazy like my, and don't want to execute all steps manually, just use ebuild package.ebuild merge :)
[gentoo-user] Re: Delays while building Libre Office.
On 05/06/2013 04:37 PM, Michael Hampicke wrote: Am 07.05.2013 01:22, schrieb walt: On 05/05/2013 01:38 PM, Alan Mackenzie wrote: There doesn't appear to be any action in emerge which unpacks the build files (or even the entire source) of a package for perusal. This is a shame. You should become familiar with the 'ebuild' command, which I use very often when trying to debug a package, e.g. #ebuild /usr/portage/app-office/libreoffice/libreoffice-3.6.6.2.ebuild unpack To completely build and install a package you need to follow that command with the 'configure', 'compile', 'install', and 'qmerge' steps (man ebuild). If you are lazy like me, No way! I'm lazier than you :p and don't want to execute all steps manually, just use ebuild package.ebuild merge :) The reason it's nice to know the individual steps is that there can be bugs at any of those steps along the way (usually during the configure or compile phases) and if the bug is simple enough you can edit the broken files and then restart the merge. Often someone will add a patch to an existing bug report, which you can apply to a failed emerge and then restart the compile phase without starting from scratch. I'm guessing you know all of this already, but Alan and others may not know. The more debuggers, the merrier :)
[gentoo-user] Re: Delays while building Libre Office.
On 05/02/2013 09:27 AM, 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?
I've been seeing it for a long time. I even filed a bug report, which
vapier confirmed and he renamed my bug report ebuild spends too much
time polling ${obscure-socket-name}.
I just looked for the bug report but I can't find it. Eventually the
problem went away and I assumed he fixed it, but maybe not -- your
problem seems identical.
Come to think of it, maybe the problem disappeared because I've been
using libreoffice-4 for quite a while now, and lo-4 never had that
bug.
Or maybe some old update of portage fixed the problem for me, dunno.
[gentoo-user] Re: Delays while building Libre Office.
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? Just to test the file system, you may copy a large tree with cp -l within the same partition, since it creates only hard links, no data is actually copied. - Jörg
