From owner-freebsd-current Wed Jul 3 13:33:59 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6292F37B400; Wed, 3 Jul 2002 13:33:56 -0700 (PDT) Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AD1343E09; Wed, 3 Jul 2002 13:33:50 -0700 (PDT) (envelope-from reg@shale.csir.co.za) Received: (from reg@localhost) by shale.csir.co.za (8.11.6/8.11.6) id g63KXjI05782; Wed, 3 Jul 2002 22:33:45 +0200 (SAT) (envelope-from reg) Date: Wed, 3 Jul 2002 22:33:45 +0200 From: Jeremy Lea To: "David O'Brien" , Garance A Drosihn , Sheldon Hearn , Maxim Sobolev , current@FreeBSD.org Subject: Re: gcc 3.1 can't compile XFree86-4-Server Message-ID: <20020703223345.B4834@shale.csir.co.za> References: <200207031426.g63EQo802988@vega.vega.com> <20020703092727.B8178@dragon.nuxi.com> <20020703180748.GJ769@starjuice.net> <20020703205602.A4834@shale.csir.co.za> <20020703131008.A10840@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020703131008.A10840@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Wed, Jul 03, 2002 at 01:10:08PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, On Wed, Jul 03, 2002 at 01:10:08PM -0700, David O'Brien wrote: > Some one needs to do thru these and really deal with them. I didn't say they were right, just that they worked ;-) > * The patch to use -O0 (or remove -O) is wrong, and a test case should be > submitted to the GCC people. I think Maxim has already done this. > * The weak problem has been fixed in the FSF sources -- I could merge a > a patch to our system GCC from the FSF sources. Please, unless we are due for a complete upgrade soon... Do you know when 3.1.1 is due? > * Someone needs to talk with the XFree86 people to get them to stop using > `cc' on C++ code. This is not just a FreeBSD issue for them. They don't. They have all of the right macros in place, it's just that we didn't have a macro defined for C++ shared libraries. I don't think we're doing the right thing for the static library cases yet. At the moment I'm trying to go through all of the XFree86-4 ports and figure out: 1. What the patches actually do... 2. If we can use one shared ${WRKSRC}, since the ports build multiple copies of all of the libraries, and they use the wrong (unpatched) versions of the config files in some cases. Regards, -Jeremy -- FreeBSD - Because the best things in life are free... http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message