From owner-freebsd-office@FreeBSD.ORG Wed Feb 20 20:41:38 2013 Return-Path: Delivered-To: office@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 B4978A00; Wed, 20 Feb 2013 20:41:38 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vps.rulingia.com (host-122-100-2-194.octopus.com.au [122.100.2.194]) by mx1.freebsd.org (Postfix) with ESMTP id 2DD3D339; Wed, 20 Feb 2013 20:41:37 +0000 (UTC) Received: from server.rulingia.com (c220-239-237-213.belrs5.nsw.optusnet.com.au [220.239.237.213]) by vps.rulingia.com (8.14.5/8.14.5) with ESMTP id r1KKfE4s075031 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 21 Feb 2013 07:41:15 +1100 (EST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.14.5/8.14.5) with ESMTP id r1KKf9En055687 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Feb 2013 07:41:09 +1100 (EST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.14.5/8.14.5/Submit) id r1KKf8SD055686; Thu, 21 Feb 2013 07:41:08 +1100 (EST) (envelope-from peter) Date: Thu, 21 Feb 2013 07:41:08 +1100 From: Peter Jeremy To: "Mikhail T." Subject: Re: Why can't gcc-4.2.1 build usable libreoffice? Message-ID: <20130220204108.GA55280@server.rulingia.com> References: <511CED39.2010909@aldan.algebra.com> <51238AE9.20205@aldan.algebra.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qDbXVdCdHGoSgWSk" Content-Disposition: inline In-Reply-To: <51238AE9.20205@aldan.algebra.com> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.5.21 (2010-09-15) Cc: stable@freebsd.org, "office@freebsd.org" X-BeenThere: freebsd-office@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Office applications on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Feb 2013 20:41:38 -0000 --qDbXVdCdHGoSgWSk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2013-Feb-19 09:23:37 -0500, "Mikhail T." wro= te: >See, my understanding always was, the only possible reasons for a >compiler to produce a non-starting executable are: > > 1. The code is buggy. > 2. The compiler is buggy. > 3. Both of the above. > >My question was, which is it? You left out: 4. Code relies on language features that are not supported by the compiler. (It's not a bug that gcc 4.2.1 (eg) doesn't suppert C++11) 5. Code relies on specific compiler features Feel free to answer your own question if it's important to you. No-one else is particularly interested. >Yes, 4.6 is supposed to work and is supported by the office@ team. My >question was about 4.2.1, which happens to be the base cc/c++ in 8.x and >in 9.x as well, if world was built WITHOUT_CLANG. I too observe the >4.2.1-compiled office die at start-up -- the splash screen starts nicely >and exits after kicking off the actual soffice.bin which segfaults. As others have indicated, the toolchain provided in the base system is intended only for building the base system. If it works for you for other purposes, that's good. If you believe it has bugs, feel free to submit PRs. If the bugs don't affect the base system, they are unlikely --=20 Peter Jeremy --qDbXVdCdHGoSgWSk Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlElNOQACgkQ/opHv/APuIfzHgCcCGcqH5XBorNK98mS6JKO0PZl OsQAnRlAysKhCL34TYSWSTUui8YYPBIC =c1RB -----END PGP SIGNATURE----- --qDbXVdCdHGoSgWSk--