Re: [gnome-slackware]Compiling GNOME2

[Blackguard666 <blackguard666 vibros-land net>]

Le Samedi 4 Mai 2002 13:53, vous avez écrit :
> Hi!
>
> Well, I've tried compiling GNOME2 on my Slackware Current (8.1 beta2)
> using vicious-build-scripts and GARNOME 0.9.5. Both failed :(
>
> GARNOME 0.9.5.
> ==============
>
> I get the same error which someone posted a few days ago. But the posted
> solutions weren't successful. As I mentioned, I'm already using
> Slackware current and didn't install the old freetype.
>
> [...]/garnome/lib/libpangoxft-1.0.so: undefined reference to
> 'FT_Get_Next_Char'
> [...]/garnome/lib/libpangoxft-1.0.so: undefined reference to
> 'FT_Get_First_Char'
> collect2: ld returned 1 exit status
>

This is typicly a lib missing error, and when i see the references that are 
missing, i deduce that is the FreeType2 lib. Ok ok, you know that ;)
On my computer, i have the TWO freetype libs. I think we MUST have v1 and v2 
for compatibility reasons (ex:ttmkfntdir). I have compiled and intalled v1 
and v2 without ANY problem. They coexist perfectly. FreeType1 lib is 
libttf.so and FreeType2 lib is libfreetype.so. Includes coexist perfectly 
too.

Ok, return to your bug.
1- verify your freetype2 and freetype1 path are in /etc/ld.so.conf.
2- verify your have NOT two versions of same version freetype libs (ex : one 
ver2 in /usr/X11R6 and another ver2 in /usr or /usr/local). It can be sources 
of bugs. In that case remove the older one (bin, lib and includes). NB : If 
you have compiled XFree86 manualy, you may have a freetype2 version installed 
in /usr/X11R6.
3- So, at this point, all appears OK. Let's continue : See carefuly if, at 
the compilation stage of your error, the GCC line include "-lfreetype" and 
"-L<path_to_your_freetype2_lib>" (ex: "-L/usr/X11R6/lib -lfreetype"). If it 
not mentioned, gcc cant know what is some ref (aka FT_Get_Next_Char) and you 
may correct the problem by hand in the good makefile. But if there is too 
many problem of that type, see 4- section.

4- I have compiled Pango with GCC-3.0.4, freetype2 and freetype1. There was 
no problem. So maybee some configurations have not been detected at the 
./configure stage. I haved some detection problems with some product who 
detect ELF capability of LD with an english console result sentence. My 
system was not speak in english. So ./configure detect i haved a 
"i686-linux-gnuold". Funny isn't it ? My system was entierly made by my hands 
1-2 months ago. Just language problem, remove LANG and LANGUAGE environnement 
variables and all was good. Ahahah, that always killed me.
So, my piece of advice is to see what is REALY detected by ./configure. You 
may try this : "./configure --prefix=...etc 2>&1 | less". With that you will 
see if a problem occurs. And if it don't work You may try 5- section.

5- No lucky you are. You must try to have all freetype libs by hands. So 
deinstall it from your dist with pkgtool and install it manualy. If don't 
work, go 6- section

6- May the linux force be with you, mwouahaahahahah !

bye.

> This occurs while compiling in
> "(garnomedir)/gnome/gtk+/work/gtk+-2.0.2/gtk"
>
>
> vicious-build-scripts
> =====================
>
> "Build failed on libgtop"
>
> It's a make problem:
>  no target "all-no- BUILD_INCLUDED_LIBINTL@"
>  in "(compiledir)/cvs/libgtop/intl"
>
> Any ideas?
>
>
> Cu, Gunnar
> _______________________________________________
> Gnome-slackware mailing list
> Gnome-slackware gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-slackware