| Summary: | nano crashes under uClibc | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Matteo Sasso <matteo.sasso> |
| Component: | [OLD] Core system | Assignee: | Embedded Gentoo Team <embedded> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Matteo Sasso
2006-05-15 04:47:27 UTC
Somehow you have two libc's installed. Thats for sure incorrect. I upgraded my uClibc and portage didn't unmerge the old version. I tried to do that manually but it destroyed my system :( Anyway, my system was functioning properly before that. I compiled vanilla nano and it ran flawlessly. nano really works fine when using the current uclibc-0.9.28 I think the result of the nano crashing for you is based on your messed up system. I tried again and I encountered the same problem. Unfortunately it seems I cannot upgrade uClibc to 0.9.28 without leaving two versions installed. It probabily has to do with the fact that I'm using an old uClibc stage3 (based on 2005.0). I couldn't find anything else to get a full uClibc-based gentoo; I'd appreciate if you could give me some pointers. I mark this bug as invalid since it probably affects only me and it cannot be confirmed. Thanks for your help anyway. ;) Oddly enough I noticed when going from 2005.1 stage1-ppc-uclibc with a current tree that every pkg wants to slot itself. Including libc/portage/bash etc. Is that more or less how you got into the mess of two libc's installed? No, I DID manage to upgrade other packages. Not so for uClibc. I think the problem lies in uClibc's infamous binary incompatibility. An upgrade should force a world rebuild. Also, portage, python, gcc etc. should be compiled statically. Mhmmm... Btw, you have a 2005.1 uclibc stage? Where did you get it? I could only find 2005.0 stages (under experimental/embedded). Sorry I ment. 2005.0 I've been maintaining several binary repos for several uclibc arches. http://tinderbox.x86.dev.gentoo.org/html/uclibc/ What I do is point my portage at it and run from there. PORTAGE_BINHOST=http://tinderbox.x86.dev.gentoo.org/uclibc/i386 It greatly speeds up install/upgrade times for me. Current uclibc stages are delayed due to a coreutils/sandbox bug. Oh and I figured out why we are seeing every pkg get sloted on fresh installs. http://planet.gentoo.org/developers/solar/2006/05/16/before_i_go_to_sleep |