On Wed, 4 Feb 2004, David Schultz wrote: > On Fri, Jan 30, 2004, Scott Long wrote: > > Jacques A. Vidrine wrote: > > >On Fri, Jan 30, 2004 at 07:34:02AM -0500, Daniel Eischen wrote: > > > > > >> Until > > >> the ports system is updated to handle this change, it is > > >> recommended that folks install an /etc/libmap.conf(5) that > > >> maps libc_r to libpthread. > > > > > >Why, exactly? (curious) > > > > > >IMHO it is unacceptable to require /etc/libmap.conf to exist. I know > > >this is temporary, but I hope it is *really* temporary. > > > > We certainly are not going to ship 5.3 like this. However, given that > > HEAD is a development branch and that change does not happen > > instantly, I think that this fine for now. > > Actually, installing a libmap.conf mapping libc_r to libpthread by > default in 5.3 might be *less* painful than the alternative. > Otherwise, an application compiled after the change that links > against a multithreaded library compiled before the change might > depend on both libc_r.so and libpthread.so, which would inevitably > cause things to go wrong at runtime. Without a libmap.conf, it > would seem that users would be forced to upgrade all of their > applications and libraries that depend on libc_r simultaneously. Could mergemaster be coerced into installing a sane libmap.conf until things settle? Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/ >Received on Thu Feb 05 2004 - 10:34:38 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:41 UTC