unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Fixing LibreOffice on ‘core-updates’
Date: Sun, 25 Nov 2018 17:11:22 +0100	[thread overview]
Message-ID: <20181125171122.1c74a542@lepiller.eu> (raw)
In-Reply-To: <87y39hw7vm.fsf@gnu.org>

Le Sun, 25 Nov 2018 15:26:37 +0100,
ludo@gnu.org (Ludovic Courtès) a écrit :

> Heya,
> 
> Marius Bakke <mbakke@fastmail.com> skribis:
> 
> > ludo@gnu.org (Ludovic Courtès) writes:
> >  
> >> Hello Guix,
> >>
> >> As briefly discussed with Marius on IRC, we both tried to fix
> >> LibreOffice on ‘core-updates’.  The initial problem is that some
> >> of the libraries it depends on fail to build with the new Boost.
> >>
> >> I started upgrading the whole shebang but eventually got stuck with
> >> LibreOffice itself, which fails to build like this:
> >>
> >> --8<---------------cut here---------------start------------->8---
> >> [build PAG] writer
> >> [build MOD] embedserv
> >> [build CUS] extras/glade
> >> [build XSL] Classy_Red/styles.xml
> >> make[1]: *** No rule to make target
> >> '/tmp/guix-build-libreoffice-6.2.0.0.alpha1.drv-0/libreoffice-6.2.0.0.alpha1/external/tarballs/49a64f3bcf20a7909ba2751349231d6652ded9cd2840e961b5164d09de3ffa63-opens___.ttf',
> >> needed by
> >> '/tmp/guix-build-libreoffice-6.2.0.0.alpha1.drv-0/libreoffice-6.2.0.0.alpha1/workdir/CustomTarget/extras/fonts/opens___.ttf'.
> >> Stop. make[1]: *** Waiting for unfinished jobs.... make: ***
> >> [Makefile:286: build] Error 2 --8<---------------cut
> >> here---------------end--------------->8---
> >>
> >> Below is what I have so far.  Help welcome!  
> >
> > I am currently building libreoffice with this patch (along with the
> > package updates you mentioned):
> >
> > From a89c47bf5ea6850d15735d262a2497f7df20896e Mon Sep 17 00:00:00
> > 2001 From: Marius Bakke <mbakke@fastmail.com>
> > Date: Fri, 23 Nov 2018 22:00:42 +0100
> > Subject: [PATCH] gnu: libreoffice: Fix build with MDDS 1.4 and
> > Orcus 0.14.
> >
> > * gnu/packages/libreoffice.scm (libreoffice)[source](patches): Add
> > two patches from Arch Linux.
> > [arguments]: Add substitutions so the libraries are found.  
> 
> Looks promising.  :-)  Did it eventually work?
> 
> Thanks!
> 
> Ludo’.

libreoffice 6.2.0.alpha1 is not available anymore at
https://download.documentfoundation.org/libreoffice/src/6.2.0/

The patches do not apply directly on the beta1, but I haven't
investigated more than that.

  reply	other threads:[~2018-11-25 16:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-18 22:23 Fixing LibreOffice on ‘core-updates’ Ludovic Courtès
2018-11-23 21:16 ` Marius Bakke
2018-11-25 14:26   ` Ludovic Courtès
2018-11-25 16:11     ` Julien Lepiller [this message]
2018-11-25 16:31     ` Marius Bakke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181125171122.1c74a542@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).