From: Barry Schwartz <chemoelectric@chemoelectric.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Glibc Update Breaks Open/LibreOffice -- Can't Downgrade
Date: Wed, 6 Jul 2011 12:26:46 -0500 [thread overview]
Message-ID: <20110706172646.GA18733@crud> (raw)
In-Reply-To: <20110706120845.6f111797.frank.peters@comcast.net>
Frank Peters <frank.peters@comcast.net> skribis:
> What a mess! In my case there would be no problem because
> absolutely nothing was built against the new glibc.
And the difference between versions may have been trivial, anyway.
> So the new question is why does the binary from OO/LO
> fail to start while the Gentoo binary shows no problem?
> AFAIK they are the same package, but the directory structures
> are different.
Was one x86 and the other amd64?
next prev parent reply other threads:[~2011-07-06 18:05 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 [this message]
2011-07-06 17:40 ` Volker Armin Hemmann
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=20110706172646.GA18733@crud \
--to=chemoelectric@chemoelectric.org \
--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