From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Glibc Update Breaks Open/LibreOffice -- Can't Downgrade
Date: Wed, 06 Jul 2011 19:40:58 +0200 [thread overview]
Message-ID: <1569579.6MFKAECpi5@localhost> (raw)
In-Reply-To: <20110706120845.6f111797.frank.peters@comcast.net>
On Wednesday 06 July 2011 12:08:45 Frank Peters wrote:
> On Wed, 6 Jul 2011 00:22:33 -0500
> Paul Hartman <paul.hartman+gentoo@gmail.com> wrote:
> > Take a look at this page:> http://en.gentoo-wiki.com/wiki/Downgrade_Glibc>
> > And also this forum topic:> http://forums.gentoo.org/viewtopic-t-845000-
start-0.html
> Thanks for these links.
> What a mess! In my case there would be no problem becauseabsolutely nothing
was built against the new glibc.
> However, I found another solution. I did not realize thatGentoo offers a
binary OpenOffice package. Installingthis openoffice-bin package now gives me
an OpenOfficethat starts with the new glibc update.
> So the new question is why does the binary from OO/LOfail to start while the
Gentoo binary shows no problem?AFAIK they are the same package, but the
directory structuresare different.
> Anyway, I'm glad to have OO running.
> Frank Peters
one is compiled by the ooo guys for some setup they consider 'standard'. The
other compiled against gentoo stable tree.
Huge differences. Really.
--
#163933
next prev parent reply other threads:[~2011-07-06 18:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 1:31 [gentoo-amd64] Glibc Update Breaks Open/LibreOffice -- Can't Downgrade Frank Peters
2011-07-06 2:28 ` Volker Armin Hemmann
2011-07-06 3:11 ` Frank Peters
2011-07-06 5:22 ` Paul Hartman
2011-07-06 16:08 ` Frank Peters
2011-07-06 17:26 ` Barry Schwartz
2011-07-06 17:40 ` Volker Armin Hemmann [this message]
2011-07-06 18:57 ` Frank Peters
2011-07-06 22:20 ` Benny Pedersen
2011-07-08 21:06 ` James Cloos
2011-07-06 3:10 ` Barry Schwartz
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=1569579.6MFKAECpi5@localhost \
--to=volkerarmin@googlemail.com \
--cc=gentoo-amd64@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