public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: walt <w41ter@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Anyone compiled libreoffice-3.6.0.4 yet?
Date: Sun, 12 Aug 2012 11:01:19 -0700	[thread overview]
Message-ID: <k08r1f$34m$1@dough.gmane.org> (raw)
In-Reply-To: <20120812174439.GD2883@ca.inter.net>

On 08/12/2012 10:44 AM, Philip Webb wrote:
> 120812 Philip Webb wrote:
>> 120812 v_2e@ukr.net wrote:
>>>   Looks like developers have already caught this issue.
>>> https://bugs.gentoo.org/show_bug.cgi?id=428328#c8
>> I'll try merging again with  USE="xmlsec" , as the bug fix recommends.
> 
> Yes, it compiled with that flag.
> While it used less memory than  2  emerges ago,
> it used more disk space ( 4 GB ) & took much longer ( 3 h 2 m ).
> OTOH it also opens almost at once, so I'll take the trade-offs.

I'm glad to hear that because I'm still failing to build it on three
machines :(

Did you add xmlsec to your make.conf, or use it in the command line when
emerging libreoffice?



  reply	other threads:[~2012-08-12 18:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-09 20:19 [gentoo-user] Anyone compiled libreoffice-3.6.0.4 yet? walt
2012-08-09 20:36 ` Alex Schuster
2012-08-09 20:58   ` Stefan G. Weichinger
2012-08-09 21:07     ` Jacques Montier
2012-08-09 22:43 ` Paul Hartman
2012-08-10 13:02 ` [gentoo-user] Re: Anyone compiled libreoffice-3.6.0.4 yet? [SOLVED, maybe] walt
2012-08-12  8:50 ` [gentoo-user] Anyone compiled libreoffice-3.6.0.4 yet? v_2e
2012-08-12 10:53   ` v_2e
2012-08-12 14:33     ` Philip Webb
2012-08-12 17:44       ` Philip Webb
2012-08-12 18:01         ` walt [this message]
2012-08-12 22:24           ` [gentoo-user] " Philip Webb
2012-08-18 13:46 ` [gentoo-user] Re: Anyone compiled libreoffice-3.6.0.4 yet? [WORKAROUND] walt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='k08r1f$34m$1@dough.gmane.org' \
    --to=w41ter@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox