Re: SGI mips3 and thread safe

[David Turner]

Hi Harley,

Harley Blumenfeld a écrit :
> 
> I am not getting the error messages in the ttmutex file.
> The error messages are in arch/unix/ttmmap.c. The compile errors
> are happening in a part of the memory mapped file that within a
> #ifdef TT_CONFIG_OPTION_THREAD_SAFE block. I've been looking
> through the threads and porting documentation to see how the file
> component works, and what could be the problem. Possibly some
> macro argument isn't expanding correctly or something.
> 
> Any ideas, anyone?
> 

Well, simply put it, some files were incorrect and didn't compile properly
when TT_CONFIG_OPTION_THREAD_SAFE is defined, due to trivial buts (how
embarassing :-).

I've just commited some changes to the CVS repository. Please check it
now and tell us about any problems you might encounter..

Best Regards,

- David

PS: For those interested, the files were:

         lib/arch/unix/ttmmap.c
         lib/extend/ftxsbit.c
         lib/extend/ftxgdef.c
         lib/extend/ftxgsub.c
         lib/extend/ftxgpos.c

   If you don't use extensions (the "ftx*" files), the library itself
   compiled properly in thread-safe mode on non-Unix platforms..

> Thanks,
> Harley Blumenfeld
> 
> >From: Werner LEMBERG <address@hidden>
> >Reply-To: Werner LEMBERG <address@hidden>
> >To: address@hidden
> >CC: address@hidden
> >Subject: Re: mjps3 and Freetype
> >Date: Thu, 11 May 2000 07:50:05 +0000 (GMT)
> >
> >
> > > Thanks for the reply.  I am now trying to compile a thread safe
> > > version of freetype and am not having much success.  I have done a
> > > dist clean in the freetype directory. Then I modified the
> > > ft_conf.h.in file to define TT_CONFIG_OPTION_THREAD_SAFE.  I then
> > > set up the build to use my own ttmutex.c file, which implements
> > > using POSIX mutexes.
> > >
> > > When I try to build freetype I get these error messages:
> > > [...]
> > > cc-1148 cc: ERROR File = ./file.c, Line = 266
> > >   Expression must have "struct" or "union" type.
> > >
> > >      engine.file_component = NULL;
> > >      ^
> > > [...]
> >
> >I think this is a bug.  Unfortunately, I don't have time currently to
> >check it (and, admittedly, I don't fully understand the thread
> >stuff :-)
> >
> >Can someone on the list check this, please?  Maybe it is helpful if
> >you can provide your ttmutex.c together with hints which thread
> >implementation you use.
> >
> >
> >     Werner
> 
> ________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com