glibc versions

Are there any issues with more recent glibc?

I am looking to what has changed on my system since I had wine working  
nicely a few months back.

It occured to me that I probably have updated glibc at some point possibly  
later then the wine build that worked to well until I foolishly tried to  
update it.

Is there anything here we need to be aware of?

TIA for any detail.

Regareds

[Jesse Allen]

On 9/24/05, [e-mail]  wrote:
> Are there any issues with more recent glibc?
>
> I am looking to what has changed on my system since I had wine working
> nicely a few months back.
>
> It occured to me that I probably have updated glibc at some point possibly
> later then the wine build that worked to well until I foolishly tried to
> update it.
>
> Is there anything here we need to be aware of?
>
> TIA for any detail.
>
> Regareds

I just found out two days ago that Wine built with GCC 4.0 breaks
SecuRom protected games -- probably in signal handling.  It's deja vu
all over again to what happened with the kernel.  Debian (unstable?)
just happened to switch to GCC 4.0.  We need to identify the problem
before the GCC 4.0 migration progresses.  Don't know if this is your
problem but who knows?

Thanks,

I've been a bit slow to think if this but I do keep this system fairly  
upto date, although not madly so.

I am currently running  gcc-3.4.3.20050110-r2  and glibc-2.3.4.20041102-r1

Is there any recommended cutoff versions for these work with wine-cvs or  
recent wine?

TIA

On Sun, 25 Sep 2005 02:04:49 +0200, Jesse Allen   
wrote:
> On 9/24/05, [e-mail]  wrote:
> > Are there any issues with more recent glibc?
> >
> > I am looking to what has changed on my system since I had wine working
> > nicely a few months back.
> >
> > It occured to me that I probably have updated glibc at some point  
> > possibly
> > later then the wine build that worked to well until I foolishly tried to
> > update it.
> >
> > Is there anything here we need to be aware of?
> >
> > TIA for any detail.
> >
> > Regareds
>
> I just found out two days ago that Wine built with GCC 4.0 breaks
> SecuRom protected games -- probably in signal handling.  It's deja vu
> all over again to what happened with the kernel.  Debian (unstable?)
> just happened to switch to GCC 4.0.  We need to identify the problem
> before the GCC 4.0 migration progresses.  Don't know if this is your
> problem but who knows?

[Jesse Allen]

On 9/24/05, [e-mail]  wrote:
> Thanks,
>
> I've been a bit slow to think if this but I do keep this system fairly
> upto date, although not madly so.
>
> I am currently running  gcc-3.4.3.20050110-r2  and glibc-2.3.4.20041102-r1
>
> Is there any recommended cutoff versions for these work with wine-cvs or
> recent wine?
>
> TIA

According to my slackware system:
glibc-2.3.5-i486-5
gcc-3.3.6-i486-1

Wine CVS works fine for me.  Despite the problems with GCC 4.0 --
which will be fixed surely -- I don't believe there are any cutoffs. 
Any modern enough setup should work.

OK thanks for the info , if no-one else posts any warning or conflicting  
info I guess it should be ok.

I may just rebuild with 3.3.6 just to see but having different compiler  
versions mixed is not a good idea

Thanks again

On Sun, 25 Sep 2005 07:30:49 +0200, Jesse Allen   
wrote:
> On 9/24/05, [e-mail]  wrote:
> > Thanks,
> >
> > I've been a bit slow to think if this but I do keep this system fairly
> > upto date, although not madly so.
> >
> > I am currently running  gcc-3.4.3.20050110-r2  and  
> > glibc-2.3.4.20041102-r1
> >
> > Is there any recommended cutoff versions for these work with wine-cvs or
> > recent wine?
> >
> > TIA
>
> According to my slackware system:
> glibc-2.3.5-i486-5
> gcc-3.3.6-i486-1
>
> Wine CVS works fine for me.  Despite the problems with GCC 4.0 --
> which will be fixed surely -- I don't believe there are any cutoffs.
> Any modern enough setup should work.