From owner-freebsd-stable@FreeBSD.ORG Tue Feb 19 17:35:39 2013 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D9356D66; Tue, 19 Feb 2013 17:35:39 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from duck.symmetricom.us (duck.symmetricom.us [206.168.13.214]) by mx1.freebsd.org (Postfix) with ESMTP id 7F8A2868; Tue, 19 Feb 2013 17:35:39 +0000 (UTC) Received: from damnhippie.dyndns.org (daffy.symmetricom.us [206.168.13.218]) by duck.symmetricom.us (8.14.6/8.14.6) with ESMTP id r1JHZWkj006813; Tue, 19 Feb 2013 10:35:38 -0700 (MST) (envelope-from ian@FreeBSD.org) Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r1JHZJMP050038; Tue, 19 Feb 2013 10:35:19 -0700 (MST) (envelope-from ian@FreeBSD.org) Subject: Re: Why can't gcc-4.2.1 build usable libreoffice? From: Ian Lepore To: Adrian Chadd In-Reply-To: References: <511CED39.2010909@aldan.algebra.com> <51238AE9.20205@aldan.algebra.com> <5123ADEC.2040103@aldan.algebra.com> Content-Type: text/plain; charset="us-ascii" Date: Tue, 19 Feb 2013 10:35:18 -0700 Message-ID: <1361295318.1164.70.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Chris Rees , "Mikhail T." , office@FreeBSD.org, stable@FreeBSD.org, Chris Rees X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Feb 2013 17:35:39 -0000 On Tue, 2013-02-19 at 09:23 -0800, Adrian Chadd wrote: > Hi, > > The base compiler is supposed to compile base and bootstrap whatever > else you need to compile other software. > > It's not supposed to be continuously updated to new, major versions. :-) > > I bet *office just uses a bunch of either horrible syntax that breaks > things, or newer C/C++ features that are buggy in older compilers. > They could've made their code compile on older compilers.. they just > haven't bothered. > > In any case, why hasn't that port been blessed with the "requires gcc > 4.6+" port option/dependency? I thought that's why we _have_ that. It has been. The OP stated the he disabled that and forced use of gcc 4.2.1, and is now complaining that it doesn't work after specifically taking steps to make it not-work. -- Ian