-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[resend after joining list]
I'm trying to install kde4, but I keep on hitting my head against a missing
symbol. Starting with kdelibs4, that needs a binary, /usr/local/bin/automoc4,
but that binary is missing this symbol:
_Z7qstrcmpRK10QByteArrayPKc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck Robey wrote:
> [resend after joining list]
>
> I'm trying to install kde4, but I keep on hitting my head against a missing
> symbol. Starting with kdelibs4, that needs a binary, /usr/local/bin/automoc4,
> but that binary is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bartosz Fabianowski wrote:
>>> _Z7qstrcmpRK10QByteArrayPKc : qstrcmp(QByteArray const&, char
>>> const*)
>> I can't locate any library having such a symbol (after a LOT of
>> searching)
>
> nm /usr/local/lib/qt4/libQtCore.so | grep _Z7qstrcmpRK10QByte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am I seeing something incorrect? The distinfo in the kdelibs4 directory has
only references to version 4.2.0, which the Mk/bsd.kde.mk tells me that the
version is 4.2.1, so actually having that distinfo in place breaks the buiold
for me.
Either I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt wrote:
> On Wed, Mar 11, 2009 at 3:12 PM, Chuck Robey wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Am I seeing something incorrect? The distinfo in the kdelibs4 directory has
>> only referenc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I don't really want to delete my existing kde, in order to upgrade, that seems
pretty extreme, so I'm doing it manually. Right now, I'm trying to update my
kdelibs, which is stuck on doing kdeaccessibility. Kdeaccessibility (in
ports/accessibility) i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bartosz Fabianowski wrote:
> As bsd.cmake.mk says, setting CMAKE_VERBOSE in the port's Makefile
> should do what you want. Also, the way cmake works, it is a replacement
> for the autotools. It spits out a Makefile that is then run through BSD
> make.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hit a new problem, I want to ask help again. Also, look for the utility at the
end here, I hope some find it useful.
I'm still working on upgrading my kde4 to 4.2, without removing my old kde
because I won't remove all of my old kde, both because I d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck Robey wrote:
> Hit a new problem, I want to ask help again. Also, look for the utility at
> the
> end here, I hope some find it useful.
>
Darnit, I left in some stupid leftovers from when I had it requiring a target
file for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I just spent a long while trying to hunt down the qt4-dbus port, only to find
that the archive directory is, for some reason, named dbus-qt4. If you build
it, it sanely announces it's building qt4-dbus, but try to find this evil beast,
and you'll be p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just so you understand, all these problems I'm having, they probably all come
from my stubborn refusal to delete my previous kde3.5 setup until I had a new
one in place. I saw that instructions in the UPGRADE, but it seemed too
draconian, when I wasn'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Max Brazhnikov wrote:
> On Mon, 16 Mar 2009 18:00:15 -0400, Chuck Robey wrote:
>> Just so you understand, all these problems I'm having, they probably all
>> come from my stubborn refusal to delete my previous kde3.5 setup until
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I finally have kde4 working. I fixed everything excepting strigi, which I
cheated on, and got a package from a friend. I may post some questions later
on, after I get thigs working a bit more smoothly, but I want to read all of the
mail on this that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Johnson wrote:
>> Heya
>>
>> I was wondering what the ETA is on Qt 4.5. I am planning to do some work
>> that requires 4.5 and I am wondering whether I should wait for that to
>> hit the ports or install a local copy in my home directory. If 4.5
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I need to amplify the question I asked about setting the desktop switching keys,
because I'm now aware of what's really causing it. You know the block of keys
on the far right-hand side? The 2, 4, 6, and 8 keys can stand in for the arrow
keys, but th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bartosz Fabianowski wrote:
> Chuck, you succeeded in installing KDE4 and Qt 4.4.3 while Qt 3.5.10 was
> installed. That's known to work.
>
> What David pointed out is that Qt 4.5 cannot be installed that way -
> Nokia/Trolltech seem to have b0rked it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Johnson wrote:
>> Would like to ask 1 question, tho, right now. I didn't get kde working
>> for the
>> first while, because I wasn't aware of x11/kdebase4-workspace. It seems
>> that
>> nothing pulls that package in, as far as depends go, so wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Johnson wrote:
>> Your advice isn't wrong, really, but I wanted to say that I personally
>> found
>> that you CAN keep your old kde3.5/qt3 installation, merely installing qt4
>> and
>> kde4 over the top of it.
>
> There should be zero problems
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I need some advice here, on phonon.The various differing kde and qt4 phonon
dependencies are confusing me.
I see 4 ports. I've installed only the phonon-gstreamer and phonon (base?)
ports. I installed those ports because it seems that there are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt wrote:
> On Tue, Mar 24, 2009 at 2:37 PM, Chuck Robey wrote:
>> Anyone know which version(s) of phonon are really needed, and if phonon-xine
>> is
>> needed, if anyone knows why it won't recognize the instal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bartosz Fabianowski wrote:
> Phonon is KDE's multimedia framework. Trolltech/Nokia liked it and
> decided to import it into Qt. They did that a while ago and hence have a
> pre-KDE-4.2 version of Photon in the toolkit. You *can* install the
> other com
I want to try to use the Umbrello UML modeler, which is part of the kdesdk4
port. The problem is that, after I built that huge list of dependencies (all
bringing me up to 4.5.3), kdesdk fails to build, it gets a "C++ error". I'm
using portupgrade, my OS is Freebsd-current, and I am guessing now t
I found a PR which seems to very precisely describe exactly the same problem I'm
seeing, in trying to unsuccessfully upgrade to kde-4.5.3. The dbus-qt4 ports
fails with that precise error message. The only resolution I see is to delte
the older port the reinstall, I tried to delete the older exis
I finally got all of the various qt4 things built, and now I'm working on
kdelibs4, but it wants phonon. This is a problem because it doesn't seem to be
directly brought in as a dependency (portupgrade doesn't seem to know about it)
and since there are multiple phonon ports which are actively host
Matt wrote:
> On Tue, Jan 12, 2010 at 3:24 PM, Chuck Robey wrote:
>> I finally got all of the various qt4 things built, and now I'm working on
>> kdelibs4, but it wants phonon. This is a problem because it doesn't seem to
>> be
>> directly brought in as a de
Alberto Villa wrote:
> On Tuesday 12 January 2010 22:26:33 Matt wrote:
>> Building and installing kdelibs4 from my tinderbox results in the
>> following phonon ports being installed (this is from the CFT for Qt
>> 4.6.0, thus the 4.6 version of Qt):
>> phonon-xine-4.3.1_3
>> qt4-phonon-4.6.0
>>
OK, this set of notes is mostly because I can't find a paper notepad,
but also because it's probably going to need action by someone dealing
with the KDE3 ports. I am going to describe what I was trying to do,
and what I found in trying to fix it.
I was using portmanager to build things, and t
27 matches
Mail list logo
