Re: RFC: libc6 policy supplement 2nd try

1997-06-15 Thread David Engel
On Jun 14, Rob Browning wrote > Helmut Geyer <[EMAIL PROTECTED]> writes: > > - compile the library using -D_RENTRANT or -D_THREAD_SAFE > > There was some talk about adding -D_REENTRANT to the list of flags > that are automatically included by gcc/g++. I don't recall what the > resulting decis

Re: RFC: libc6 policy supplement 2nd try

1997-06-14 Thread joost witteveen
> packages as follows [1]. Some packages (mostly from base) may use > locations in /lib. > >based on | package name | library location > > libc6 | libfoo | /usr/lib/libfoo.so. > libc5 | libfoo-g |

Re: RFC: libc6 policy supplement 2nd try

1997-06-14 Thread Rob Browning
Helmut Geyer <[EMAIL PROTECTED]> writes: > - compile the library using -D_RENTRANT or -D_THREAD_SAFE There was some talk about adding -D_REENTRANT to the list of flags that are automatically included by gcc/g++. I don't recall what the resulting decision was, if there was one. > - there

RFC: libc6 policy supplement 2nd try

1997-06-14 Thread Helmut Geyer
Here is a reworked proposal: -=-=-=-=-=-=-=-=-=-=-= SNIP -=-=-=-=-=-=-=-=-=-=-=-=-=- Debian library policy supplement draft for libc5->libc6 migration This document is meant to tell what a Debian package providing a library should do to support both libc6 (glibc2) and libc5. Note