Fontconfig - May 2007 - fc-arch things "sparc" has the "ppc" signature

$ cd fc-arch
# ./fc-arch auto < fcarch.tmpl.h
...
#define FC_ARCHITECTURE "ppc"

So, it seems fc-arch believes Solaris/SPARC (32-bit) has the same
signature as "ppc". Ditto for HP-UX/PA and HP-UX/IA. And, for AIX,
fc-arch thinks the architecture is "m68k". And, for Tru64 UNIX,
fc-arch thinks the architecture is "x86-64".

So, is fc-arch checking too little to discern one architecture from
another?

-- 
albert chin (china at thewrittenword.com)

Albert Chin wrote:
> $ cd fc-arch
> # ./fc-arch auto < fcarch.tmpl.h
> ...
> #define FC_ARCHITECTURE "ppc"
> 
> So, it seems fc-arch believes Solaris/SPARC (32-bit) has the same
> signature as "ppc". Ditto for HP-UX/PA and HP-UX/IA. And, for
AIX,
> fc-arch thinks the architecture is "m68k". And, for Tru64 UNIX,
> fc-arch thinks the architecture is "x86-64".
> 
> So, is fc-arch checking too little to discern one architecture from
> another?
In principle if the arches have the same signature they should create
compatible cache files. Please mail the list if this isn''t the case.

pat

On Sun, May 27, 2007 at 07:37:06PM +0200, Patrick Lam
wrote:
> Albert Chin wrote:
> > $ cd fc-arch
> > # ./fc-arch auto < fcarch.tmpl.h
> > ...
> > #define FC_ARCHITECTURE "ppc"
> > 
> > So, it seems fc-arch believes Solaris/SPARC (32-bit) has the same
> > signature as "ppc". Ditto for HP-UX/PA and HP-UX/IA. And,
for AIX,
> > fc-arch thinks the architecture is "m68k". And, for Tru64
UNIX,
> > fc-arch thinks the architecture is "x86-64".
> > 
> > So, is fc-arch checking too little to discern one architecture from
> > another?
> 
> In principle if the arches have the same signature they should create
> compatible cache files. Please mail the list if this isn''t the
case.
Agreed. But it''ll seem odd to have "ppc" signature files in
~/.fontconfig on a Solaris/SPARC host. Ditto for "m68k" signature
files on a AIX host. Maybe non-platform names should be chosen
instead.

-- 
albert chin (china at thewrittenword.com)

On Sun, 2007-05-27 at 01:56 -0500, Albert Chin wrote:
> So, is fc-arch checking too little to discern one architecture from
> another?
Fontconfig checks to make sure the on-disk structures will be
compatible, which involves testing the size, alignment and byte-ordering
of several different datatypes. So, common byteorder and datatype size
will often generate common signatures.

-- 
keith.packard at intel.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url :
http://lists.freedesktop.org/archives/fontconfig/attachments/20070527/d065134d/attachment.pgp