From owner-freebsd-questions Wed Apr 14 1:26:35 1999 Delivered-To: freebsd-questions@freebsd.org Received: from ixion.honeywell.com (ixion.honeywell.com [129.30.4.80]) by hub.freebsd.org (Postfix) with ESMTP id 7E9E114C8A for ; Wed, 14 Apr 1999 01:26:33 -0700 (PDT) (envelope-from sleas@ixion.honeywell.com) Received: by ixion.honeywell.com (1.40.112.8/16.2) id AA250078252; Wed, 14 Apr 1999 03:24:12 -0500 Date: Wed, 14 Apr 1999 03:24:12 -0500 From: Shawn Leas To: questions@FreeBSD.ORG Subject: Re: Cannot get egcs 1.1.1 port to build me a shared libstdc++!!!!!!! (MICO SAGA SOLVED (sort of)) Message-Id: <19990414032412.A24352@ixion.honeywell.com> References: <19990414014531.A16377@ixion.honeywell.com> <19990414020418.A18180@ixion.honeywell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <19990414020418.A18180@ixion.honeywell.com>; from Shawn Leas on Wed, Apr 14, 1999 at 02:04:18AM -0500 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Apr 14, 1999 at 02:04:18AM -0500, Shawn Leas wrote: > Now I know it isn't how egc is configured, but mico's > configure script must be wierd... Can someone help > me build a shared mico on 3.1R? OK, is I just got this working by changing the configure script in two places and by adding -lstdc++ in mico-shld.def.in so mico-shld always links with -lstdc++. This is a hack. Is anyone familiar with my problem? you must be, because KDE is suposed to be used by a lot of BSD users, and building a snapshot requires MICO. Furthurmore, is anyone interested in my hack? -- Shawn <=========== America Held Hostage ===========> Day 2275 for the poor and the middle class. Day 2294 for the rich and the dead. 647 days remaining in the Raw Deal. <============================================> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message