> >No it's not. It's a SO problem. It relies on features in glibc-2.0.7 which
> >are not present in glibc-2.1.
>
> Which private entry points did they use?
The loader mentioned that it was unable to locate _dl_something.
> I statically link every elf program I have to use these days,
> because it's the only way to guarantee that it will work.
> It adds ~250k to each and every binary, which isn't perfect,
> but in the land of 128mb memory sticks costing US$180 is a
> lot faster than writing a completely new libc and trying to
> get other people to use it.
Probably, but I thin we've argued about this in the past - ncurses,
remember? I think even in those times of aplenty one should strive for
efficiency. Of course, with open source, you're free to do what you wish.
> How many _programs_ are in the SO suite?
Just one big program!
> ____
> david parsons \bi/ Of course a.out doesn't have this problem, because
> \/ (other) people aren't poking at the libraries anymore.
> Bummer I can't get XF3.3.3 to compile as a.out.
Why not?!
Cheers,
Alex
-- /_/\ Legalise cannabis now! ( o.o ) Grow some cannabis today! > ^ < Peace, Love, Unity and Respect to all.http://www.tahallah.demon.co.uk - *Updated* New additions in Humour section
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/