From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: Libreoffice building (sort of)
Date: Mon, 24 Nov 2014 19:03:58 +0100
Message-ID: <87tx1obhm9.fsf@gnu.org>
References: <20141124171933.GA8722@jocasta.intra>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:49583)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1Xsxzc-0000QS-57
	for guix-devel@gnu.org; Mon, 24 Nov 2014 13:04:14 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1XsxzW-00066b-4r
	for guix-devel@gnu.org; Mon, 24 Nov 2014 13:04:08 -0500
Received: from hera.aquilenet.fr ([2a01:474::1]:38573)
	by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from <ludo@gnu.org>)
	id 1XsxzV-00066J-UB
	for guix-devel@gnu.org; Mon, 24 Nov 2014 13:04:02 -0500
In-Reply-To: <20141124171933.GA8722@jocasta.intra> (John Darrington's message
	of "Mon, 24 Nov 2014 18:19:33 +0100")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org

John Darrington <john@darrington.wattle.id.au> skribis:

> Well currently the libreoffice package in wip-libreoffice branch, builds,=
 installs and=20
> seems to work ok.

Wo0t!  Excellent!

> Slightly worrying is that the first few builds crashed in one of LO's uni=
ttests.  I added
> the line (setenv "CPPUNITTRACE" "gdb --args") which I expected just to gi=
ve me a backtrace
> to help me diagnose the problem.  I was very surprised doing this, caused=
 the package to=20
> build, test and install without error! -- A Heisenbug.

How is $CPPUNITTRACE used exactly?  If it=E2=80=99s used as in:

  sh -c $CPPUNITTRACE test-program

then I=E2=80=99m surprised it works at all, because =E2=80=98gdb --args tes=
t-program=E2=80=99
just spawns an interactive GDB session.

Any idea what happens?

> Anyway, like I say, the  package works, but is a bit rough.   I suggest t=
hat some of the
> dependencies are tidied up, reviewed and pushed to master,  and the deepe=
r issues investigated
> later.  Help doing this is welcome.

Sounds like a good plan!

Ludo=E2=80=99.