Re: packages for 3.5 were built for 3.3 (and tahoe is up)

2013-05-31 Thread Pierre Abbat
I rebuilt the qt-libs package and still can't run a KDE program on darner. I have two DragonFly boxes, one with working KDE and one with broken KDE. How do I tell what the ABI version is, so that I can troubleshoot it? Pierre -- sei do'anai mi'a djuno puze'e noroi nalselganse srera

Re: packages for 3.5 were built for 3.3 (and tahoe is up)

2013-05-28 Thread Pierre Abbat
On Tuesday, May 28, 2013 08:44:13 Justin Sherrill wrote: > It was built on 3.3, but not just for 3.3. It should generally work. > Because pkgsrc builds take so long, the build starts before the new > release is tagged - but this was effectively 3.4, and there's no ABI > changes between 3.4 and 3.5

Re: packages for 3.5 were built for 3.3 (and tahoe is up)

2013-05-28 Thread Justin Sherrill
On Tue, May 28, 2013 at 2:24 AM, Pierre Abbat wrote: > I ran "pkg_info -BF /usr/pkg/qt4/lib/libQtNetwork.so.4" and found that the > package was built on 3.3. I then force-replaced the package and it didn't > download anything, just replaced it with the same package, still built on 3.3. > To make t

packages for 3.5 were built for 3.3 (and tahoe is up)

2013-05-27 Thread Pierre Abbat
-bash-4.2$ kwrite tahoe.cfg & [1] 91354 -bash-4.2$ /usr/lib/gcc44/libstdc++.so.9: version CXXABI_1.3 required by /usr/pkg/qt4/lib/libQtNetwork.so.4 not defined [1]+ Exit 1 kwrite tahoe.cfg (By the way, if you've had trouble running Tahoe on DragonFly, the reason is that iputil