Re: [Freetype] Slow FT_Set_Pixel_Sizes function on amd64

[Roman Bednarek]

On Tue, 22 Jun 2004, Werner LEMBERG wrote:

> >     I have compiled it with -O0 option and nothing has changed. I
> > tried to compile it with -Wall flag, but it outputs everything to
> > /dev/null and I do not know where to change it.  Can you suggest how
> > to get rid of the /dev/null redirection?
>
> This is very strange behaviour and probably a misconfiguration of your
> compiler.  Normally, warning messages are sent to stderr.  What about
>
>    make &> make.log
>
> to save both stdout and stderr?
>
  I am not familiar with freetype build process, the configure adds
/dev/null redirection to makefiles example:
gcc -pedantic -ansi 
-I/var/tmp/portage/freetype-2.1.5-r1/work/freetype-2.1.5/objs
-I/var/tmp/portage/freetype-2.1.5-r1/work/freetype-2.1.5/builds/unix
-I/var/tmp/portage/freetype-2.1.5-r1/work/freetype-2.1.5/include -c -Wall
-pipe -O2 -DTT_CONFIG_OPTION_BYTECODE_INTERPRETER
-DFT_CONFIG_OPTION_SYSTEM_ZLIB -DDARWIN_NO_CARBON
-I/var/tmp/portage/freetype-2.1.5-r1/work/freetype-2.1.5/src/base
/var/tmp/portage/freetype-2.1.5-r1/work/freetype-2.1.5/src/base/ftbase.c
-o /var/tmp/portage/freetype-2.1.5-r1/work/freetype-2.1.5/objs/ftbase.o
>/dev/null 2>&1

  so redirecting make output does not help.

   In the meantime I have tried the example on suse 9.1 on amd64 and it
works fine, it has freetype 2.1.7(currently not available as gentoo
package). So it may be a problem with gentoo configuration or the problem
was fixed in new freetype version. I can make some more tests to find out
way it does not work on amd64 gentoo.

   Roman