From: dawnbreez <casco...@gmail.com>
To: voidlinux <void...@googlegroups.com>
Subject: Re: OpenGL?
Date: Fri, 4 Sep 2015 13:27:21 -0700 (PDT) [thread overview]
Message-ID: <6fd0df85-e008-4812-b6c1-3fa9b986bf2f@googlegroups.com> (raw)
In-Reply-To: <2f14aa83-2cf8-4475-b817-b88c13c73480@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 1051 bytes --]
I tried to install SDL2-devel, and got this output:
dbus-1.8.18_2 broken, needs `dbus-libs-1.10.0_1'
eudev-libgudev-3.1.2_1 broken, needs `eudev-libudev-3.1.2_2'
pulseaudio-6.0_6 broken, needs `libpulseaudio-6.0_9'
libblkid-2.26.2_5 broken, needs `libuuid-2.26.2_7'
libfdisk-2.26.2_5 broken, needs `libuuid-2.26.2_7'
libmount-2.26.2_5 broken, needs `libuuid-2.26.2_7'
util-linux-2.26.2_5 broken, needs `libuuid-2.26.2_7'
Transaction aborted due to unresolved dependencies.
Any idea how to fix this?
On Friday, September 4, 2015 at 12:39:06 PM UTC-5, Stefan Mühlinghaus wrote:
>
> It depends on what exactly is missing. The SDL libraries are installed to
> /usr/lib and that should be in your library path. Maybe you need the
> corresponding devel package (SDL-devel or SDL2-devel)? Or maybe even the
> 32bit versions? It could also be possible that the software looks for the
> libraries or header-files in a wrong directory. In that case you would
> probably need to modify the build process and/or the source code.
>
[-- Attachment #1.2: Type: text/html, Size: 1399 bytes --]
next prev parent reply other threads:[~2015-09-04 20:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 17:01 OpenGL? dawnbreez
2015-09-04 1:11 ` OpenGL? JD Robinson
2015-09-04 12:44 ` OpenGL? dawnbreez
2015-09-04 5:52 ` OpenGL? Juan RP
2015-09-04 12:45 ` OpenGL? dawnbreez
2015-09-04 16:52 ` OpenGL? dawnbreez
2015-09-04 17:39 ` OpenGL? Stefan Mühlinghaus
2015-09-04 20:27 ` dawnbreez [this message]
2015-09-04 22:47 ` OpenGL? dawnbreez
2015-09-15 7:35 ` OpenGL? Juan RP
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6fd0df85-e008-4812-b6c1-3fa9b986bf2f@googlegroups.com \
--to="casco..."@gmail.com \
--cc="void..."@googlegroups.com \
/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.
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 NNTP newsgroup(s).