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

List:       kde-devel
Subject:    Re: [kde-freebsd] wrong include order for custom KDEDIR(S)
From:       Thiago Macieira <thiago.macieira () kdemail ! net>
Date:       2004-12-24 15:19:10
Message-ID: 200412241319.10836.thiago.macieira () kdemail ! net
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Raphael Langerhorst wrote:
>On Friday 24 December 2004 11:24, Raphael Langerhorst wrote:
>As you can see the at the compile line, -I/usr/local/include comes
>BEFORE -I/usr/home/kdedev/local/kde-head/include (which is
>$KDEDIR/include). The stable KDE header files are located
>in /usr/local/include.
>
>This leads to including wrong headers. As long as the headers are
>fairly compatible, this doesn't matter much of course, but in this
>case the visibility patch was applied AFTER the 3.3 release, so this
>leads to failure because wrong headers are used.
>
>If I compile this file by hand and move -I/usr/local/include after the
>KDE includes, then it compiles fine.

It looks like the configure scripts found your libfreetype/libXft includes 
in /usr/local/include. That's why you get wrongly ordered includes.

The line in Makefile.am is:

AM_CPPFLAGS= $(LIBFREETYPE_CFLAGS) $(LIBFONTCONFIG_CFLAGS) 
$(all_includes)-D_LARGEFILE64_SOURCE

What happens if you move $(all_includes) to the beginning of the line?

-- 
  Thiago Macieira  -  thiago (AT) macieira (DOT) info
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

4. And æfter se scieppend ingelogode, he wrát "cenn", ac eala! se 
rihtendgesamnung andswarode "cenn: ne wát hú cennan 'eall'. Ástynt."

[Attachment #5 (application/pgp-signature)]

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


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