public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Graham Murray <graham@gmurray.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] parrot & openoffice failures
Date: Thu, 09 Nov 2006 11:24:40 +0000	[thread overview]
Message-ID: <87ac30zwuf.fsf@newton.gmurray.org.uk> (raw)
In-Reply-To: <7573e9640611080904j9378eefn43151fc262dde568@mail.gmail.com> (Richard Fish's message of "Wed\, 8 Nov 2006 10\:04\:44 -0700")

"Richard Fish" <bigfish@asmallpond.org> writes:

> Now if openoffice fails to build against the new icu, then _that_ is a bug. :-)

The rebuild of openoffice-2.04 to build against the new icu failed for
me, but the emerge also download something. But I have not yet had
time to look and see why the build failed.

But I have noticed this before with openoffice. A new version comes
out and it builds fine. But later when revdep-rebuild wants to rebuild
it, or I have run 'emerge -e world' (for example after an upgrade to
gcc/libstdc++), the build has failed and each time it has also
downloaded a new patch or something even though the version has not
changed.
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2006-11-09 11:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-08 16:20 [gentoo-user] parrot & openoffice failures Vladimir G. Ivanovic
2006-11-08 17:04 ` Richard Fish
2006-11-09  1:13   ` Vladimir G. Ivanovic
2006-11-09  1:47     ` Richard Fish
2006-11-09  3:25       ` Vladimir G. Ivanovic
2006-11-09 11:24   ` Graham Murray [this message]
2006-11-09 11:42     ` Novensiles divi Flamen

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=87ac30zwuf.fsf@newton.gmurray.org.uk \
    --to=graham@gmurray.org.uk \
    --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