Hello!
In relation to bug 354395 [1] I would like to downgrade my glibc back to
2.12.2. Portage doesn't allow me to do that:
* Sanity check to keep you from breaking your system:
* Downgrading glibc is not supported and a sure way to destruction
* ERROR: sys-libs/glibc-2.12.2 failed (setup
A little update from my side:
I was abe to downgrade glibc to 2.12.2 and my sound problem [1] is now
gone again! If it's not glibc itself, it's one of the packages
re-installed after (again, see [1] for the list).
If anyone considers masking glibc 2.13 for now: please take my vote.
Best,
On 2/11/11 10:55 AM, Michael Haubenwallner wrote:
what do you think of working around the memcpy troubles with glibc-2.13 by
simply redirecting memcpy to memmove within glibc, either unconditionally or
optional/temporary (via USE-flag?) until everyone uses memmove where
necessary?
I'm not a
On 2/11/11 1:06 PM, Sebastian Pipping wrote:
I was abe to downgrade glibc to 2.12.2 and my sound problem [1] is now
gone again!
Just curious, what downgrade method did you use? Just untaring an older
glibc package?
signature.asc
Description: OpenPGP digital signature
On 02/11/11 13:26, Paweł Hajdan, Jr. wrote:
Just curious, what downgrade method did you use? Just untaring an older
glibc package?
This is what I did:
0) Log out of X, log in to root console
1) Collect packages emerged after previous update to glibc from
files in PORT_LOGDIR (using
On 02/11/2011 01:20 PM, Paweł Hajdan, Jr. wrote:
On 2/11/11 10:55 AM, Michael Haubenwallner wrote:
what do you think of working around the memcpy troubles with glibc-2.13 by
simply redirecting memcpy to memmove within glibc, either unconditionally or
optional/temporary (via USE-flag?) until
