On 05/01/2010 05:47 PM, Rob Landley wrote:
On Friday 23 April 2010 09:29:10 Austin Foxley wrote:
Since it seems that ld.so soname is hardcoded in GCC. If you want to
use something else than /lib/ld-uClibc.so.0 as dynamic linker, you also
need to update GCC default configration, create alternate
Rob Landley wrote:
You're saying you want to support having two installations of uClibc the same
system. Starting from separate dynamic linkers, and going through segregated
library search paths. Because nothing says "lightweight and embedded" like
installing two or three complete copies of y
Temporary file name template passed to __gen_tempname had no "XX" in it,
so __gen_tempname returned EINVAL which led to sem_open failure.
Fixes NPTL tests tst-sem4, tst-sem7, tst-sem8, tst-sem9.
Signed-off-by: Roman I Khimov
---
libpthread/nptl/sem_open.c |3 ++-
1 files changed, 2 inse
On Sun, 2 May 2010, Timo wrote:
> And yes, it's not full solution. Deep library wise dependencies can be
> temporarily broken.
The problem is that just one level of shared library other than the C
library, is sufficient to break side-by-side execution based *only* on C
library soname changes. Tha
On Sunday 02 May 2010 14:23:29 Timo Teräs wrote:
> Rob Landley wrote:
> > You're saying you want to support having two installations of uClibc the
> > same system. Starting from separate dynamic linkers, and going through
> > segregated library search paths. Because nothing says "lightweight and
Rob Landley wrote:
No, the idea is not to have two versions installed all the time. The idea
is to allow the coexistance temporarily while package manager is upgrading
system.
Isn't this what static linking is for?
If we targeted flashable upgrade, then this would not be needed as
everything
