From owner-freebsd-stable@FreeBSD.ORG Mon Mar 11 11:59:59 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 288B6303 for ; Mon, 11 Mar 2013 11:59:59 +0000 (UTC) (envelope-from greglmiller@gmail.com) Received: from mail-oa0-f42.google.com (mail-oa0-f42.google.com [209.85.219.42]) by mx1.freebsd.org (Postfix) with ESMTP id D43DBBE6 for ; Mon, 11 Mar 2013 11:59:58 +0000 (UTC) Received: by mail-oa0-f42.google.com with SMTP id i18so4434862oag.29 for ; Mon, 11 Mar 2013 04:59:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=mkjnnRFM0wNn2eh3MrAjkJPCcKsEs/hm5+S7pgxzyo4=; b=d0WJw4iai+316AJbIGVIsQUuHXltePiEpiAh+YLQxU42O3+NFhsHA1ev7qtO1xt5da /RwQgpEzOu34mfM+fO9Fmd+LNZNW+RZSzFam1WKcqScaLXMU6wdieI4HcC8vXdNktJ6d 1XJQoMTh7g0Vx2B0RDfpqkRmbVixnEjZhM5KbQMkEaltP9/3b1roMFaytnxqeMDW4gH3 Xe7nq6HmfU4bsIvt0s7ZsshBpCwpUYQTJFQxHIis7/6ocYYd/hDKCio0cqx4Ck3XFNeu jCFDQx08zhRZoRzdxzbMfY++JPwVrm/ZpdhsXmKTN+HvXXv3OvtR7lVAZhT0iyoK5Fm9 NrjA== MIME-Version: 1.0 X-Received: by 10.60.25.138 with SMTP id c10mr8315504oeg.12.1363003198023; Mon, 11 Mar 2013 04:59:58 -0700 (PDT) Received: by 10.60.50.73 with HTTP; Mon, 11 Mar 2013 04:59:57 -0700 (PDT) In-Reply-To: <44mwuxo5a8.fsf@lowell-desk.lan> References: <511CED39.2010909@aldan.algebra.com> <51238AE9.20205@aldan.algebra.com> <5123ADEC.2040103@aldan.algebra.com> <5123BE8E.2080209@aldan.algebra.com> <1361297952.1164.83.camel@revolution.hippie.lan> <5123CA4C.90703@aldan.algebra.com> <51250E61.8080209@gmx.de> <51260364.5040104@digsys.bg> <44mwuxo5a8.fsf@lowell-desk.lan> Date: Mon, 11 Mar 2013 06:59:57 -0500 Message-ID: Subject: Re: Why can't gcc-4.2.1 build usable libreoffice? From: Greg Miller To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 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: Mon, 11 Mar 2013 11:59:59 -0000 On 2/21/13, Lowell Gilbert wrote: > Greg Miller writes: > >> On 2/21/13, Daniel Kalchev wrote: >>> >>> >>> On 21.02.13 04:23, Greg Miller wrote: >>>> I can't speak for the OP, but I tried it because clang, gcc46, and >>>> gcc47 wouldn't produce a working executable at all for a long time >>>> (and continue to fail) on my 9.0 and 9.1 systems. There's been so much >>>> libreoffice breakage that I don't even bother reporting it or making >>>> much effort to fix it. I just reboot to Windows for the cases where I >>>> need a working libreoffice. I don't much care whether gcc 4.2 produces >>>> a working libreoffice; I just wish something did. >>> >>> Did you build the Windows version yourself from source? >>> >>> If not, why you just don't get the binary WhateverOffice for FreeBSD and >>> be done with this "problem"? That will surely save you the reboots. At >>> least. >> >> One reason I moved from Linux to FreeBSD many years ago was to get >> away from binary dependency hell, so I've been reluctant to try any >> large binary packages in quite a while. >> >> In any case, some people in the thread wanted to know why others try >> to build with something other than the default compiler, and one of >> the answers is "it doesn't build with the default compiler, at least >> for some of us." If you have a problem with that, you'll just have to >> live with it. > > The port of libreoffice doesn't build with the system default > compiler (if it's gcc; looks like clang will work), and won't do so > even if you ask it to. The original poster thinks this is a problem, > but since you didn't notice (or at least mention) the distinction, > I'm not sure what position your argument is supporting. > > No compiler will build all of the programs in the ports collection, > but as long as the ports infrastructure supports that fact, it isn't > a problem. [In my opinion.] When I said "default compiler", I meant the default for the port (which was clang 3.1 from base on my system at the I sent that email), not the system compiler. That seems to be fixed now with the latest version of the libreoffice port, which pulls in lang/clang, which does seem to get the job done nicely.