lawrence@garland.uk.co.btrl (03/07/91)
----- News saved at 7 Mar 91 10:58:57 GMT We are trying to use Objectworks for C++ (ParcPlace) Release 2 in conjunction with the NIHCL library (dev by Keith E. Gorlen et al) on Sun SPARCstations. We run into a problem with multiply defined _main.o objects in the libC.a and the libnihcl.a libraries during linkage. We are using the AT&T R2.1 C++ compiler. Is there a way of combining/eliminating the two _main.o objects? Both OWC and NIHCL seem to generate their own _main.o. Any solutions?? Are there any other potential problems we might run into by using these two products together? Many Thanks. Lawrence Lordanich lawrence@garland.bt.co.uk From: lawrence@garland.uk.co.btrl () Path: garland.uk.co.btrl!lawrence Newsgroups: lang.comp.c++ Subject: OWC++ and NIHCL library compatibility Expires: References: Sender: Reply-To: lawrence@garland.uk.co.btrl.uk.co.btrl () Followup-To: Distribution: Organization: RT4253, BTRL Keywords: ObjectWorks_for_C++ NIHCL Library_Compatibility Solutions? We are trying to use Objectworks for C++ (ParcPlace) Release 2 in conjunction with the NIHCL library (dev by Keith E. Gorlen et al) on Sun SPARCstations. We run into a problem with multiply defined _main.o objects in the libC.a and the libnihcl.a libraries during linkage. We are using the AT&T R2.1 C++ compiler. Is there a way of combining/eliminating the two _main.o objects? Both OWC and NIHCL seem to generate their own _main.o. Any solutions?? Are there any other potential problems we might run into by using these two products together? Many Thanks. Lawrence Lordanich lawrence@garland.bt.co.uk