- Original Message -
From: "Dustin Navea" <[EMAIL PROTECTED]>
> --- Jon Brandenburg <[EMAIL PROTECTED]> wrote:
> > On Sat, 2003-09-06 at 16:36, Ian Goldby wrote:
> >
> > > and occurs 2-3 hours into the build. Thanks for any further
suggestions.
> >
> Well on my old 1.2 ghz athlon (when
--- Jon Brandenburg <[EMAIL PROTECTED]> wrote:
> On Sat, 2003-09-06 at 16:36, Ian Goldby wrote:
>
> > and occurs 2-3 hours into the build. Thanks for any further suggestions.
> >
>
> Speaking of compile times.. what are the average/min/max times for
> compiling the complete system? I was surpri
Jon Brandenburg <[EMAIL PROTECTED]> wrote:
>On Sat, 2003-09-06 at 16:36, Ian Goldby wrote:
>>
>> and occurs 2-3 hours into the build. Thanks for any further suggestions.
>
>Speaking of compile times.. what are the average/min/max times for
>compiling the complete system? I was surprise when it to
Jon Brandenburg wrote:
On Sat, 2003-09-06 at 16:36, Ian Goldby wrote:
and occurs 2-3 hours into the build. Thanks for any further suggestions.
Speaking of compile times.. what are the average/min/max times for
compiling the complete system? I was surprise when it took my system 12
minut
Thank you. That patch worked for me. It now fully compiles without errors.
On Sunday 07 Sep 2003 03:45, Steven Edwards wrote:
> Here is a patch for this. I also included some changes to help the
> MS_VC/Mingw build
>
> Changelog:
> include and porting fix (reported by Ian Goldby)
>
>
> Index: gdbp
Here is a patch for this. I also included some changes to help the MS_VC/Mingw build
Changelog:
include and porting fix (reported by Ian Goldby)
Index: gdbproxy.c
===
RCS file: /home/wine/wine/programs/winedbg/gdbproxy.c,v
retrievi
On Sat, 2003-09-06 at 16:36, Ian Goldby wrote:
> and occurs 2-3 hours into the build. Thanks for any further suggestions.
>
Speaking of compile times.. what are the average/min/max times for
compiling the complete system? I was surprise when it took my system 12
minutes to do it do a full cvs '
On Saturday 06 Sep 2003 06:32, Sylvain Petreolle wrote:
> Thanks, that fixed the problem.
> I see that you added the dependancy to re-generate testlist.c. :)
>
> > You can remove the testlist.c files and they will be regenerated
> > correctly. Or simply do a make clean.
Didn't work for me. I trie
Thanks, that fixed the problem.
I see that you added the dependancy to re-generate testlist.c. :)
> You can remove the testlist.c files and they will be regenerated
> correctly. Or simply do a make clean.
=
Sylvain Petreolle (spetreolle_at_users_dot_sourceforge_dot_net)
ICQ #170597259
Say
I was noticing something similar for myself, but I can't explain why the
difference is occurring other than to say that it must be a newbie error
on my part. But I downloaded the latest cvs earlier this afternoon.
Ran
./configure
./make depend && make
./make install
and now when I try to run wine
Sylvain Petreolle <[EMAIL PROTECTED]> writes:
> After updating to the latest CVS via cvs update (the only patch involved was the
> header dependancies fix), wine doesnt compile.I tried to rerun './configure' but
> there is no change.What I get is : (make depend runs fine.)[EMAIL PROTECTED] tests
After updating to the latest CVS via cvs update (the only patch involved was the header dependancies fix), wine doesnt compile.
I tried to rerun './configure' but there is no change.
What I get is : (make depend runs fine.)
[EMAIL PROTECTED] tests]$ LANG=en_US make
gcc -c -I. -I. -I../../../inclu
12 matches
Mail list logo
