Fontconfig - Apr 2006 - Portability questions & 2.4.0 release plans

Hi all,

I''ve committed a number of portability fixes to the fc-2_4_branch of
fontconfig in the past few days.  I''d like to know whether it breaks
anything, and what platforms you can get fontconfig running on.

I''m particularly interested in reports about MinGW, HP-UX, and Solaris.
 Please reply to me or the list and let me know if things work.

If things look good, I''d like to release 2.3.95 in a week, let it bake
for two weeks, and then release 2.4.0 with the same code.

pat

On 4/7/06, Patrick Lam <plam@mit.edu> wrote:
> Hi all,
>
> I''ve committed a number of portability fixes to the fc-2_4_branch
of
> fontconfig in the past few days.  I''d like to know whether it
breaks
> anything, and what platforms you can get fontconfig running on.
>
> I''m particularly interested in reports about MinGW, HP-UX, and
Solaris.
>  Please reply to me or the list and let me know if things work.
>
> If things look good, I''d like to release 2.3.95 in a week, let it
bake
> for two weeks, and then release 2.4.0 with the same code.
>
> pat
> _______________________________________________
> Fontconfig mailing list
> Fontconfig@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/fontconfig
>
MinGW:

autoconfiguration failed:

$ ./autogen.sh
I am going to run ./configure with no arguments - if you wish
to pass any to it, please specify them on the ./autogen.sh command line.
Running aclocal
Running autoheader
'' is already registered with AC_CONFIG_FILES.
autoconf/status.m4:844: AC_CONFIG_FILES is expanded from...
configure.in:513: the top level
autom4te: /bin/m4 failed with exit status: 1
autoheader: /usr/bin/autom4te failed with exit status: 1

Fortunately I could run it on a linux machine, so I finally got the
configure script generated.

Compilation went fine, but the included test failed:

$ ./run-test.sh
*** Test failed: Basic check
*** output is in ''out'', expected output in
''out.expected''

the "out" file is attached.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: out
Type: application/octet-stream
Size: 4 bytes
Desc: not available
Url :
http://lists.freedesktop.org/archives/fontconfig/attachments/20060422/68df7cf0/out.obj

On 4/22/06, Patrick Lam <plam@mit.edu> wrote:
> There are many different tests, please send out.expected as well.
>
> pat
>
>
Here is the out.expected file.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: out.expected
Type: application/octet-stream
Size: 115 bytes
Desc: not available
Url :
http://lists.freedesktop.org/archives/fontconfig/attachments/20060422/57290435/out.obj

Christian Prochaska wrote:
> Compilation went fine, but the included test failed:
> 
> $ ./run-test.sh
> *** Test failed: Basic check
> *** output is in ''out'', expected output in
''out.expected''
> 
> the "out" file is attached.
It seems to be a libtool incompatibility with respect to make distcheck.
 It doesn''t seem to actually have any bad effects, though.

pat