From owner-freebsd-current Tue Mar 2 19: 9:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id DFDEF14E23 for ; Tue, 2 Mar 1999 19:09:24 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id WAA80990; Tue, 2 Mar 1999 22:06:12 -0500 (EST) Date: Tue, 2 Mar 1999 22:06:12 -0500 (EST) From: Chuck Robey To: Doug Rabson Cc: Thomas Dean , mark@grondar.za, freebsd-current@freebsd.org Subject: Re: egcs and gcc In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 chuckr@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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message