wineinstall fails after cvs update

[degs]

Hi,

I find tools/wineinstall frequently fails in ./configure when trying to 
rebuild Wine after a "cvs update". I only seem to be able to fix this by 
blowing away the whole tree and re-fetching it with "cvs checkout". Is 
wineinstall the Right Way to build Wine when one is trying to hack on it?

thanks
-- degs

PS: I know hardly anything about autoconf (shudder) and absolutely *zero* 
about CVS :-(

[Andriy Palamarchuk]

Hi Degs,

--- degs <degs(a)giantblob.com> wrote:
> Hi,
>
> I find tools/wineinstall frequently fails in
> ./configure when trying to 
> rebuild Wine after a "cvs update". I only seem to be
> able to fix this by 
> blowing away the whole tree and re-fetching it with
> "cvs checkout". Is 
> wineinstall the Right Way to build Wine when one is
> trying to hack on it?

Wineinstall not only installs wine, but also
configures it. Usually you do not need to reconfigure
wine each time you refreshed source from CVS, so
simply run in the Wine root dorectory:
./configure
make depend
make install

or in one line:
./configure && make depend && make install

"make install" will refresh the Wine binaries, but
won't do anything with your existing configuration.

BTW, question about installation belongs to
wine-users, look forward for your questions about
hacking ;-)

Andriy Palamarchuk


__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Mother's Day is May 12th!
http://shopping.yahoo.com

[degs]

On Friday 10 May 2002 21:03, Andriy Palamarchuk wrote:
> Hi Degs,
>
> --- degs <degs(a)giantblob.com> wrote:
> > Hi,
> >
> > I find tools/wineinstall frequently fails in
> > ./configure when trying to
> > rebuild Wine after a "cvs update". I only seem to be
> > able to fix this by
> > blowing away the whole tree and re-fetching it with
> > "cvs checkout". Is
> > wineinstall the Right Way to build Wine when one is
> > trying to hack on it?
>
> Wineinstall not only installs wine, but also
> configures it. Usually you do not need to reconfigure
> wine each time you refreshed source from CVS, so
> simply run in the Wine root dorectory:
> ./configure
> make depend
> make install
>
> or in one line:
> ./configure && make depend && make install
>
> "make install" will refresh the Wine binaries, but
> won't do anything with your existing configuration.
>
> BTW, question about installation belongs to
> wine-users, look forward for your questions about
> hacking ;-)
> Hi,

Sorry I wasn't very clear - its not really a wine-users question per se - I 
want to be able to hack on Wine whilst keeping up-to-date with the 
cvs.winehq.com version and need to know how to build it. I'm aware 
wineinstall runs configure - its configure that fails for me. It fails 
regardless of whether I run configure manually or through wineinstall so 
wineinstall is probably a red herring.

So, my question is: what is the correct way to rebuild Wine after 'cvs update' 
so that the configure *doesn't* fail? preferably without having to blow away 
the whole tree, re-check out and re-merge any changes which I've made to it?

I'm sure this must be a common problem but I can't figure out how to get 
around it - if anyone can tell me the right way to do this it would be really 
handly.

BTW I know its not my changes to my local Wine tree which break configure as 
I've changed nothing in that area (I've only added debug code to some bits of 
GDI which are giving me jip)

thanks
-- degs
> Andriy Palamarchuk
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Shopping - Mother's Day is May 12th!
> http://shopping.yahoo.com

[Dustin Navea]

--- degs <degs(a)giantblob.com> wrote:
> On Friday 10 May 2002 21:03, Andriy Palamarchuk
> wrote:
> > Hi Degs,
> >
> > --- degs <degs(a)giantblob.com> wrote:
> > > Hi,
> > >
> > > I find tools/wineinstall frequently fails in
> > > ./configure when trying to
> > > rebuild Wine after a "cvs update". I only seem
> > > to be
> > > able to fix this by
> > > blowing away the whole tree and re-fetching it
> > > with
> > > "cvs checkout". Is
> > > wineinstall the Right Way to build Wine when one
> > > is
> > > trying to hack on it?
> >
> > Wineinstall not only installs wine, but also
> > configures it. Usually you do not need to
> > reconfigure
> > wine each time you refreshed source from CVS, so
> > simply run in the Wine root dorectory:
> > ./configure
> > make depend
> > make install
> >
> > or in one line:
> > ./configure && make depend && make install
> >
> > "make install" will refresh the Wine binaries, but
> > won't do anything with your existing
> > configuration.
> >
> > BTW, question about installation belongs to
> > wine-users, look forward for your questions about
> > hacking ;-)
> > Hi,
>
> Sorry I wasn't very clear - its not really a
> wine-users question per se - I 
> want to be able to hack on Wine whilst keeping
> up-to-date with the 
> cvs.winehq.com version and need to know how to build
> it. I'm aware 
> wineinstall runs configure - its configure that
> fails for me. It fails 
> regardless of whether I run configure manually or
> through wineinstall so 
> wineinstall is probably a red herring.
>
> So, my question is: what is the correct way to
> rebuild Wine after 'cvs update' 
> so that the configure *doesn't* fail? preferably
> without having to blow away 
> the whole tree, re-check out and re-merge any
> changes which I've made to it?
>
> I'm sure this must be a common problem but I can't
> figure out how to get 
> around it - if anyone can tell me the right way to
> do this it would be really 
> handly.
>
> BTW I know its not my changes to my local Wine tree
> which break configure as 
> I've changed nothing in that area (I've only added
> debug code to some bits of 
> GDI which are giving me jip)
>
> thanks
> -- degs

are you downloading on windows and then copying over
to linux?  if so, you will probably need a tool like
uxcook95, which fixes problems with files downloaded
in ascii (windows' preferred method of storage, even
for binary files), google search will probably bring
up a few hits...

-Dustin

__________________________________________________
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
http://launch.yahoo.com

[degs]

On Saturday 11 May 2002 02:24, Dustin Navea wrote:
> > Hi,
> >
> > Sorry I wasn't very clear - its not really a
> > wine-users question per se - I
> > want to be able to hack on Wine whilst keeping
> > up-to-date with the
> > cvs.winehq.com version and need to know how to build
> > it. I'm aware
> > wineinstall runs configure - its configure that
> > fails for me. It fails
> > regardless of whether I run configure manually or
> > through wineinstall so
> > wineinstall is probably a red herring.
> >
> > So, my question is: what is the correct way to
> > rebuild Wine after 'cvs update'
> > so that the configure *doesn't* fail? preferably
> > without having to blow away
> > the whole tree, re-check out and re-merge any
> > changes which I've made to it?
> >
> > I'm sure this must be a common problem but I can't
> > figure out how to get
> > around it - if anyone can tell me the right way to
> > do this it would be really
> > handly.
> >
> > BTW I know its not my changes to my local Wine tree
> > which break configure as
> > I've changed nothing in that area (I've only added
> > debug code to some bits of
> > GDI which are giving me jip)
> >
> > thanks
> > -- degs
>
> are you downloading on windows and then copying over
> to linux?  if so, you will probably need a tool like
> uxcook95, which fixes problems with files downloaded
> in ascii (windows' preferred method of storage, even
> for binary files), google search will probably bring
> up a few hits...

No - nothing like that - its basically recent CVS of Wine tree on pretty 
vanilla SuSE 7.3. Source is on an ext3 partition. I run cvs update and build 
wine as the same user. What happens is this:

cvs checkout wine
while(1) {
	./configure && make all install
	sleep(days)
	cvs update wine
}

eventually configure fails. (some way in - in makefile generation I think). I 
suspect I cvs is leaving stuff behind which should be removed. Next time it 
happens I'll post the output of configure. I'm probably doing something daft 
- I just haven't figured out what it is yet...

-- degs
> -Dustin
>
> __________________________________________________
> Do You Yahoo!?
> LAUNCH - Your Yahoo! Music Experience
> http://launch.yahoo.com

[Sylvain Petreolle]

degs,
please post your messages when configure fails...
that will be better than only words...
> cvs checkout wine
> while(1) {
>   ./configure && make all install
>   sleep(days)
>   cvs update wine
> }
>
> eventually configure fails. (some way in - in
> makefile generation I think). I 
> suspect I cvs is leaving stuff behind which should
> be removed. Next time it 
> happens I'll post the output of configure. I'm
> probably doing something daft 
> - I just haven't figured out what it is yet...

___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail : http://fr.mail.yahoo.com

[Ove Kaaven]

On Sat, 11 May 2002, degs wrote:
> cvs checkout wine
> while(1) {
>   ./configure && make all install
>   sleep(days)
>   cvs update wine

cvs update -Pd wine
(as the instructions on www.winehq.com tells you)
> }

[Dustin Navea]

--- degs <degs(a)giantblob.com> wrote:
> On Saturday 11 May 2002 02:24, Dustin Navea wrote:
> > > Hi,
> > >
> > > Sorry I wasn't very clear - its not really a
> > > wine-users question per se - I
> > > want to be able to hack on Wine whilst keeping
> > > up-to-date with the
> > > cvs.winehq.com version and need to know how to
> >
> > build
> > > it. I'm aware
> > > wineinstall runs configure - its configure that
> > > fails for me. It fails
> > > regardless of whether I run configure manually
> > > or
> > > through wineinstall so
> > > wineinstall is probably a red herring.
> > >
> > > So, my question is: what is the correct way to
> > > rebuild Wine after 'cvs update'
> > > so that the configure *doesn't* fail? preferably
> > > without having to blow away
> > > the whole tree, re-check out and re-merge any
> > > changes which I've made to it?
> > >
> > > I'm sure this must be a common problem but I
> > > can't
> > > figure out how to get
> > > around it - if anyone can tell me the right way
> > > to
> > > do this it would be really
> > > handly.
> > >
> > > BTW I know its not my changes to my local Wine
> > > tree
> > > which break configure as
> > > I've changed nothing in that area (I've only
> > > added
> > > debug code to some bits of
> > > GDI which are giving me jip)
> > >
> > > thanks
> > > -- degs
> >
> > are you downloading on windows and then copying
> > over
> > to linux?  if so, you will probably need a tool
> > like
> > uxcook95, which fixes problems with files
> > downloaded
> > in ascii (windows' preferred method of storage,
> > even
> > for binary files), google search will probably
> > bring
> > up a few hits...
>
> No - nothing like that - its basically recent CVS of
> Wine tree on pretty 
> vanilla SuSE 7.3. Source is on an ext3 partition. I
> run cvs update and build 
> wine as the same user. What happens is this:
>
> cvs checkout wine
> while(1) {
>   ./configure && make all install
>   sleep(days)
>   cvs update wine
> }
>
> eventually configure fails. (some way in - in
> makefile generation I think). I 
> suspect I cvs is leaving stuff behind which should
> be removed. Next time it 
> happens I'll post the output of configure. I'm
> probably doing something daft 
> - I just haven't figured out what it is yet...

try doing cvs update -RdP wine

and see if configure fails after that...

__________________________________________________
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
http://launch.yahoo.com

[Francois Gouget]

On Fri, 10 May 2002, degs wrote:
> Hi,
>
> I find tools/wineinstall frequently fails in ./configure when trying to
> rebuild Wine after a "cvs update". I only seem to be able to fix this by
> blowing away the whole tree and re-fetching it with "cvs checkout". Is
> wineinstall the Right Way to build Wine when one is trying to hack on it?

The only reason I can think of is that you changed something in
configure.in and then regenerated the configure script. But then when
you did the cvs update you got tons of conflicts in the configure script
so it does not work anymore.

The solution to this is to resolve any conflicts you may have in the
configure.in file, and the run autoconf again to update the configure
script.

If that does not help, then you will have to tell us more about what
configure says when it fails and possibly post the config.log file.



--
Francois Gouget         fgouget(a)free.fr        http://fgouget.free.fr/
            "Lotto: A tax on people who are bad at math." -- unknown
          "Windows: Microsoft's tax on computer illiterates." -- WE7U