From: Daniel J. <dr...@fa...> - 2003-05-07 02:28:47
|
On Wed, May 07, 2003 at 11:18:00AM +0900, kaz Kojima wrote: > Daniel Jacobowitz <dr...@fa...> wrote: > >> But some shared libraries can be made without libc, can't be? > >> -z defs issue remains for them. > > > > They shouldn't be; it causes all sorts of problems with for instance > > prelinking. > > I agree with you, though my point is can/cannot. I want to add that moving it to libc wouldn't hurt that case: they'd get a unique copy when loaded. > >> Of course, we can treat them as the exceptions, but it seems to me > >> it's not essentially different with the current crt1.o implementation. > > > > I'd have to think about it... I think it makes more sense in libc. > > I have no strong sense about where it is placed if it's unique. > Once Niibe-san proposed libfpscr.so-like which is an "always linked" > shared library as an another possibility. Do you mind if I ask libc-alpha for opinions? Roland, Jakub, et al. are a lot more on top of this than I am. I can just force -z nodefs for now, but I'm not happy with that as a solution. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer |