On Tue, 2 Mar 1999, Doug Rabson wrote: > That was put in extremely recently. The reason it doesn't build a shared > library by default is to avoid potential conflict with the system > libstdc++. > > If you enable it, the port will install the shared lib in > /usr/lib/gcc-lib/.../libstdc++.so. You may need to add a runpath option > to your link to point the executable at the directory.
Doug, my egcs (when I tell it to --enable-shared) installs: libstdc++.so libstdc++.so.2.9 and libstdc++.so.2.9.0 How about I just keep the first one, kill the middle one, and make the real file libstdc++.so.3 (so it keeps our numbering). I'm not sure about the rules for this, since elf ... will stuff looking for libstdc++.so.2 find my new libstdc++.so.3, or will the new one (with it's incompatible format, like you said) be safe? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chu...@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
