From owner-freebsd-stable@FreeBSD.ORG Wed Feb 20 17:56:58 2013 Return-Path: Delivered-To: freebsd-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 0F376ECA for ; Wed, 20 Feb 2013 17:56:58 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by mx1.freebsd.org (Postfix) with ESMTP id 964967F1 for ; Wed, 20 Feb 2013 17:56:57 +0000 (UTC) Received: from mailout-de.gmx.net ([10.1.76.28]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0LpzgH-1Ul96K2awB-00fjz4 for ; Wed, 20 Feb 2013 18:56:51 +0100 Received: (qmail invoked by alias); 20 Feb 2013 17:56:51 -0000 Received: from f049235200.adsl.alicedsl.de (EHLO mandree.no-ip.org) [78.49.235.200] by mail.gmx.net (mp028) with SMTP; 20 Feb 2013 18:56:51 +0100 X-Authenticated: #428038 X-Provags-ID: V01U2FsdGVkX18fc70r3gcfwysT+fx4XmS87iG+fZimlMsSX6GZsX TqI98aDgb3Q8vX Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by apollo.emma.line.org (Postfix) with ESMTP id ECB6B23D52D for ; Wed, 20 Feb 2013 18:56:49 +0100 (CET) Message-ID: <51250E61.8080209@gmx.de> Date: Wed, 20 Feb 2013 18:56:49 +0100 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: Why can't gcc-4.2.1 build usable libreoffice? 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> In-Reply-To: <5123CA4C.90703@aldan.algebra.com> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 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: Wed, 20 Feb 2013 17:56:58 -0000 Am 19.02.2013 19:54, schrieb Mikhail T.: > These were, indeed, complaints, but not about the port "not working > after I broke it". My complaint is that, though the port "works" out of > the box, the office@ maintainers have given up on the base compiler too > easily -- comments in the makefile make no mention of any bug-reports > filed with anyone, for example. It sure seems, no attempts were made to > analyze the failures... I don't think, such "going with the flow" is > responsible and am afraid, the inglorious days of building a special > compiler just for the office will return... Feel free to debug MyFavouriteOffice to the point where it will build with base GCC, but don't complain if the *office teams don't look at your patches. If there are compiler bugs in gcc 4.2, there is no place where anyone will care for anyone else to file them, not upstream (abandoned 4.2.X years ago), not FreeBSD (decided to switch to clang instead). What is your point, besides getting software from the museum to build stuff from the relative future? > LibreOffice's own Native_Build page > makes no > mention of a required compiler version. Unless a compiler is documented > to not support a required feature, it is supposed to work. Thus, filing > a bug-report with LibreOffice could've been fruitful -- if it is the > code, rather than the toolchain, that are at fault... That will likely only buy you the compiler requirement you are currently missing, and it is likely to be the exact version that they used to build their official binaries, with a "newer versions may work, but no promises" attached. Feel free to query the LibreOffice developers if, and according to which conditions, they'd take your patches to make LO build with our decrepit gcc 4.2.1. > Am I really the only one here disturbed by the fact, that the compilers > shipped as cc(1) and/or c++(1) in our favorite operating system's most > recent stable versions (9.1 and 8.3) are considered buggy? Not just old > -- and thus unable to process more modern language-standards/features, > but buggy -- processing those features incorrectly? There is certainly > nothing in our errata > about it... You have not yet proven that either the base compilers or LibreOffice are at fault.