Closed GoogleCodeExporter closed 9 years ago
Hi,
We don't use explicitly FreeType, I think Pidgin does. What is the output from
./configure? And what is your Linux distribution?
Stefan
Original comment by stefan.i...@gmail.com
on 17 Nov 2009 at 6:13
I use Ubuntu Lucid Lynx (full updated today):
$ uname -a
Linux otorion 2.6.32-2-generic #2-Ubuntu SMP Sat Oct 31 17:07:12 UTC 2009 i686
GNU/Linux
./configure
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... none
checking whether gcc and cc understand -c and -o together... yes
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for GLIB... yes
checking for PIDGIN... yes
checking for WEBKIT... yes
checking for LIBCURL... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/websites/Makefile
config.status: executing depfiles commands
config.status: executing libtool commands
Original comment by shaka...@gmail.com
on 17 Nov 2009 at 6:18
I've installed this Ubuntu version and everything seems okay. I'm a little
puzzled the
compilation process needs FreeType from /usr/local/lib. How did you install
Pidgin?
From official repositories or from sources?
As a side note: maybe the new .deb packages we've build could work for you.
Stefan
Original comment by stefan.i...@gmail.com
on 18 Nov 2009 at 9:11
I have this freetype.so files. I thinks that some path is wrong or something
like that.
$ locate freetype.so
/opt/cxchromium/lib/libcxfreetype.so
/opt/cxchromium/lib/libcxfreetype.so.6
/opt/cxchromium/lib/libcxfreetype.so.6.3.7
/usr/lib/libfreetype.so
/usr/lib/libfreetype.so.6
/usr/lib/libfreetype.so.6.3.22
/usr/lib/osgPlugins-2.8.1/osgdb_freetype.so
/usr/local/lib/libfreetype.so.6
/usr/local/lib/libfreetype.so.6.3.16
The last file is .so.6.3.16 an the other es .so.6
I have the developers ppa for pidgin.
I install your .deb and works! But I cant compile yet. Also I have a flicker
effect
when I do scrool on pidgin.
Original comment by shaka...@gmail.com
on 18 Nov 2009 at 11:34
It appears you have multiple versions of libfreetype installed on your
computer, but
one of them is missing a file. Do
ln -s /usr/local/lib/libfreetype.so.6 /usr/local/lib/libfreetype.so
and then try to compile our plugin again. I think this should work fine.
The flicker effect is because of the flash plugin. Most of the times I get this
issue
in Firefox too.
Original comment by stefan.i...@gmail.com
on 25 Nov 2009 at 2:52
Original comment by stefan.i...@gmail.com
on 8 Feb 2010 at 2:38
Original issue reported on code.google.com by
shaka...@gmail.com
on 17 Nov 2009 at 5:29