[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-ports
Subject:    Re: [kde-freebsd] New Qt-3
From:       Andy Fawcett <andy () athame ! co ! uk>
Date:       2003-01-06 10:17:52
[Download RAW message or body]

On Sunday 05 January 2003 23:57, AlanE wrote:
> On Sun, Jan 05, 2003 at 11:29:49PM +0200, Andy Fawcett wrote:
> >On Sunday 05 January 2003 23:08, Pete Fritchman wrote:
> >> ++ 05/01/03 13:06 -0800 - David Johnson:
> >> | releasing 3.1.x in a couple of weeks. The state of Qt/KDE is
> >> | "stuck" waiting the unfreeze of the ports tree (may already have
> >> | happened) and the release of KDE 3.1.
> >>
> >> The tree is thawed somewhat, but larger ports (like KDE and Qt)
> >> shouldn't be upgraded still until 5.0-R (which should be happening
> >> soon).
> >
> >If you add to this problems building Qt 3.1.1, depending on certain
> >combinations of installed X / Xft2 / fontconfig, which have not been
> >thoroughly analysed, you can effectively forget an upgrade to 3.1.1
> >right at the moment, even if a freeze wasn't in place.
>
> Andy, 3.1.1 builds fine with up-to-date X and will be committed with
> the kde 3.1 ports commits, unless there is a compelling reason not
> to. I don't consider "older X versions (4.1) don't work" a compelling
> reason.

The problem I originally heard of was on a system with up-to-date ports, 
so talking of "older X versions" is irrelevent.

I left a build running overnight. All ports required are installed, up 
to date, and the Qt build is not using any separately installed 
software (I sandbox all that). Summary below.

> It does not use Xft2, it uses Xft that comes with XF86.

It uses Xft2 if present on the system. Note the "-lXft2" in the 
following part of the build for me:

g++ -fno-exceptions -pthread -o ../../../bin/uic 
.obj/debug-shared-mt/main.o .obj/debug-shared-mt/uic.o 
.obj/debug-shared-mt/form.o .obj/debug-shared-mt/object.o 
.obj/debug-shared-mt/subclassing.o .obj/debug-shared-mt/embed.o 
.obj/debug-shared-mt/widgetdatabase.o .obj/debug-shared-mt/domtool.o 
.obj/debug-shared-mt/parser.o    -Wl,-rpath,/usr/local/lib 
-L/usr/local/lib  -Wl,-rpath,/home/tap/qt-x11-free-3.1.1/lib 
-L/home/tap/qt-x11-free-3.1.1/lib -L/usr/X11R6/lib -L/usr/X11R6/lib 
-lqt-mt -lpng -lz -lGLU -lGL -lXmu -lXrender -lXinerama -lXft2 
-lfreetype -lXext -lX11 -lm -lSM -lICE

And a build of Qt 3.1.1 from tarball breaks, if Xft-2.0_1 is installed 
from ports, with:

undefined reference to `XftFreeTypeOpen'
undefined reference to `XftPatternAddInteger'
undefined reference to `XftPatternAddString'
...

Without the Xft-2.0_1 it builds fine. 

I'll leave you to do the detective work, unless you already accounted 
for this problem with patches.

I've not actually tried building a vanilla Qt 3.1 under the same 
circumstances, so I have no idea if it builds differently.

(note, all this is on 5.0 from a week or so ago, and there is another 
small but easily fixable problem with qfiledialog.cpp wrt getpwnam_r, 
or rather the lack of it. Trolltech have been informed, and you already 
have a patch from me for it.)

Andy

-- 
Andy Fawcett                                     | andy@athame.co.uk
                                                 | tap@kde.org
"In an open world without walls and fences,      | tap@lspace.org
  we wouldn't need Windows and Gates."  -- anon  | tap@fruitsalad.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
[prev in list] [next in list] [prev in thread] [next in thread]