Ok, built from generic source, and everything completes and installs. I
still get the same error when I try a "wine --version" though. It's
really very frustrating when it seems to be working for so many others.
On Sat, 2003-03-29 at 12:23, Rob Hughes wrote:
> When I trying to build from the source rpm, I always get "make: ***
> [wine-devel.pdf] Error 1". This happens with glibc 2.3.2, or the
> previous version. I may have a go at the vanilla source.
>
> On Sat, 2003-03-29 at 08:28, Kevin DeKorte wrote:
> > Rob,
> >
> > The way I was able to make this work was this.
> >
> > Download a new wine source tar file and put in a new directory and compile
> > from there.. Or if you use CVS, then delete your current working CVS
> > directory and get a new copy.
> >
> > I tried doing a make dist-clean, but for some reason it would compile but not
> > run. But starting with a fresh working dir when compiling wine solved that
> > problem. I did not need the LD_ASSUME_KERNEL workaround when I did this.
> >
> > You also might want to clean up your /tmp dir..
> >
> > rm -rf /tmp/.wine-{uid}
> >
> > Kevin
> >
> > On Friday 28 March 2003 09:55 pm, Rob Hughes wrote:
> > > Wine was fine before upgrading glibc to 2.3.2 on RH 8. Since that time,
> > > I get
> > >
> > > $wine --version
> > > wine: lstat /tmp/.wine-<user>/server-9-ff9be/socket : No such file or
> > > directory
> > >
> > > This happens no matter what user I run wine as. This also happens using
> > > the LD_ASSUME_KERNEL work around. The only thing that changed between a
> > > working wine, and a non-working wine was glibc, so I'm positive that's
> > > it. Can anyone reproduce this, and if so, does anyone have a work around
> > > for this particular issue?
> > >
> > > Thanks,
> > > Rob
Attachment:
signature.asc
Description: This is a digitally signed message part
