Date: Sat, 20 Feb 2010 22:00:10 -0600 From: Programmer In Training <pit@joseph-a-nagy-jr.us> To: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Problems With K3b Message-ID: <4B80AFCA.50404@joseph-a-nagy-jr.us>
next in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF03D6D5B3DDC859FFE3E7610 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I'm trying to install k3b from ports so I might use my DVD super multi format drive (an HP 1040i; I've already added the necessary line to /boot/default/loader.conf for enabling dma) with either the gui or cli but during the install of libthai (which is a dependency of kimproxy which is a dependency of k3b) the configure script infinitely loops. Is anyone else having this issue? I was able to add it via pkg_add -r but encountered other problems. Apparently I hadn't compiled Qt with thread support and another required part of kdelibs failed on that part, so I deinstalled qt33 and began recompiling it with the intention of enabling thread support. The compile of Qt than proceeded to fail (I've long since closed the window but could retry it to get the specific messages if needed). I need Qt back because I have quite a few apps that require Qt installed (though I'm wanting to get rid of qwit, if anyone can recommend a /good/ Twitter client for FreeBSD, I'd appreciate a private mail with the recommendation). Using pkg_add for k3b isn't working because I'm using a newer version of some of it's dependencies and that apparently is causing problems (I should have never installed Xv, I had to upgrade jpeg from jpeg-7 to jpeg-8 and that upgrade has caused nothing but problems). I can really do without k3b since I do have the cli tools, but I'd like to resolve these issues (when I asked for help with flash, I was able to update my ports collection so I have the latest available as of yesterday) so that they aren't problems further on down the road. I realize now that I'm going to have to learn to use the port management tools to help prevent problems like this in the future and that's ok. This install is supposed to be a learning experience (even if this box has become my primary machine, unlike I had intended) and I am trying to learn. --=20 Yours In Christ, PIT Emails are not formal business letters, whatever businesses may want. --------------enigF03D6D5B3DDC859FFE3E7610 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iQEcBAEBAgAGBQJLgK/dAAoJEENZQ8DH7rW0FyIIAJu4Zjn4cpjkwu+DWvUJgFiY zJ8KiaPioQ0bE71XCxFJ5MLxwtqmIK94XvxMiN/nISsu+yOdF9E5Jr7bvVPlfltG p4TYD7Sftke6N+f7a6YhoURJIh6W09rfXZLtKpRWOuJKbOvjMicvw9Dewlvi7oKP NgsNA04vsnN55qNR68J4vfSBP11LNDfLMbzuc6wWWQQXESoCvls1zPk8FsCMvB7u 40b94Ju7l9lhaWNzv5lzKbBaqWlNCF3ovDn9GhNbJLNfziypmCPPCFi/yTwyBiFk uA+ecC3K79vmcUbnO3Uga6mnh1fnsWJWhGHjg5su+qwlPxT0EcwbBk77WRwziwo= =holU -----END PGP SIGNATURE----- --------------enigF03D6D5B3DDC859FFE3E7610--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B80AFCA.50404>