From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 25484@debbugs.gnu.org
Subject: bug#25484: QEMU depends on two different version of libjpeg
Date: Thu, 19 Jan 2017 15:24:25 +0100 [thread overview]
Message-ID: <idj4m0v6sbq.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <idj60lb6tfg.fsf@bimsb-sys02.mdc-berlin.net>
[-- Attachment #1: Type: text/plain, Size: 989 bytes --]
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> writes:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> While building ‘qemu’ as of 840f38ba37af1d09eb1e896a6350d6ab7f6532d0, we
>> see:
>>
>> --8<---------------cut here---------------start------------->8---
>> ld: warning: libjpeg.so.62, needed by /gnu/store/9a3r8wjnfyxfc912i6inlw8k6pw3rlxy-spice-0.12.8/lib/libspice-server.so, may conflict with libjpeg.so.8
>> --8<---------------cut here---------------end--------------->8---
>>
>> Indeed, ‘guix graph -t references qemu’ shows ‘libjpeg’ and
>> ‘libjpeg-turbo’ as indirect dependencies.
>>
>> Any idea how to fix that?
>
> “libjpeg-turbo” is used by “spice” but I just built “spice” successfully
> with “libjpeg-8” instead of “libjpeg-turbo”. This seems to be okay.
Attached is a patch. I successfully built “spice” and “qemu” and
confirmed with “guix graph -t references qemu -b d3js > graph.html” that
libjpeg-turbo has disappeared.
[-- Attachment #2: 0001-gnu-spice-Build-with-libjpeg-8.patch --]
[-- Type: text/x-patch, Size: 1075 bytes --]
From b277b1a282a91ab236f8a5ed7c7a47a46c8de279 Mon Sep 17 00:00:00 2001
From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Date: Thu, 19 Jan 2017 15:22:06 +0100
Subject: [PATCH] gnu: spice: Build with libjpeg-8.
* gnu/packages/spice.scm (spice)[inputs]: Replace libjpeg-turbo with
libjpeg-8.
---
gnu/packages/spice.scm | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/gnu/packages/spice.scm b/gnu/packages/spice.scm
index 805f47a60..4d7c96e53 100644
--- a/gnu/packages/spice.scm
+++ b/gnu/packages/spice.scm
@@ -1,5 +1,6 @@
;;; GNU Guix --- Functional package management for GNU
;;; Copyright © 2016 David Craven <david@craven.ch>
+;;; Copyright © 2017 Ricardo Wurmus <rekado@elephly.net>
;;;
;;; This file is part of GNU Guix.
;;;
@@ -217,7 +218,7 @@ which allows users to view a desktop computing environment.")
(inputs
`(("cyrus-sasl" ,cyrus-sasl)
("glib" ,glib)
- ("libjpeg-turbo" ,libjpeg-turbo)
+ ("libjpeg" ,libjpeg-8)
("lz4" ,lz4)
("opus" ,opus)
("zlib" ,zlib)))
--
2.11.0
next prev parent reply other threads:[~2017-01-19 14:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 13:19 bug#25484: QEMU depends on two different version of libjpeg Ludovic Courtès
2017-01-19 14:00 ` Ricardo Wurmus
2017-01-19 14:24 ` Ricardo Wurmus [this message]
2017-01-19 16:11 ` Ludovic Courtès
2020-04-28 7:28 ` bug#25484: Closing #25484? Brice Waegeneire
2020-04-28 12:19 ` Marius Bakke
2020-04-28 20:46 ` Ludovic Courtès
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=idj4m0v6sbq.fsf@bimsb-sys02.mdc-berlin.net \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=25484@debbugs.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).