From owner-cvs-gnu Mon Mar 13 02:30:55 1995 Return-Path: cvs-gnu-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA00337 for cvs-gnu-outgoing; Mon, 13 Mar 1995 02:30:55 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA00309; Mon, 13 Mar 1995 02:30:38 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id OAA21760; Mon, 13 Mar 1995 14:39:48 +1000 Date: Mon, 13 Mar 1995 14:39:48 +1000 From: Bruce Evans Message-Id: <199503130439.OAA21760@godzilla.zeta.org.au> To: CVS-commiters@freefall.cdrom.com, ache@freefall.cdrom.com, bde@zeta.org.au, cvs-gnu@freefall.cdrom.com, nate@trout.sri.MT.net Subject: Re: cvs commit: src/gnu/usr.bin/cc/cc_int Makefile Sender: cvs-gnu-owner@freebsd.org Precedence: bulk >> >> Modified: gnu/usr.bin/cc/cc_int Makefile >> >> Log: >> >> Bump SHLIB_MAJOR to 263 to match ../Makefile.inc >> ... >> Er, there is no point in making libgcc.so.263.0. >Umm, the library he changed is the library shared by the different gcc >programs (cc1plus, cc1obj if we made it) we no longer make since it >slows down builds considerably. However, if we *do* make it, Andrew >made sure the major # was correct. Oops. OK, I'll object to the shared cc_int :-). If you have to keep old libcc_int.so's around, then the disk space "saved" by sharing will be negative. The shared library numbering doesn't really apply to gcc. The library interface will probably change for every new version so you are unlikely to want to keep old libcc_int.so's. The install step should probably know about this and always install new shared libraries and nuke the old ones. Bruce