| Re: [AD] mingw, static, tls |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Sat, 2009-07-18 at 10:22 -0600, Trent Gamblin wrote:
> On Sat, July 18, 2009 9:48 am, Matthew Leverton said:
> > On Sat, Jul 18, 2009 at 10:04 AM, Trent Gamblin<trent@xxxxxxxxxx> wrote:
> >> If you're using gcc < 4 you can't compile a static lib with MinGW.
> >> It doesn't support native TLS.
> >>
> > What does that mean? I did see it buried in the a5_readme.txt as I was
> > looking for some info on OS X after the fact.
> >
> > I built it with my horrible hack, and it "worked." What features
> > cannot work properly? Is there no way to support it, or has nobody
> > felt like supporting it?
>
> Your hack will only work for single threaded programs.
>
> > And if it cannot be made to work, then cmake ought to detect MinGW's
> > version and tell the user instead of letting him build it, only to
> > find out that it crashes.
>
> Yes it probably should.
>
I guess it should be possible to create TLS "manually", by using the
current thread id to return the right value in all the tls functions.
--
Elias Pschernig <elias@xxxxxxxxxx>