On 9/19/2016 4:12 PM, jungle Boogie wrote:
> On 19 September 2016 at 13:16, Tony Papadimitriou wrote:
>> Usually do just FOSSIL UPDATE and then run make.
>
> Best to do fossil up trunk as you may inadvertently follow a branch.
Indeed, this happens when your checkout version, or a predecessor, ge
On 19 September 2016 at 13:16, Tony Papadimitriou wrote:
> Usually do just FOSSIL UPDATE and then run make.
Best to do fossil up trunk as you may inadvertently follow a branch.
--
---
inum: 883510009027723
sip: [email protected]
___
fossi
On Sep 19, 2016, at 2:16 PM, Tony Papadimitriou wrote:
>
> Usually do just FOSSIL UPDATE and then run make.
Me, too, on *ix type platforms, but every once in a long while, a “make clean”
seems to be necessary before it will build cleanly.
Checking out a fresh copy is just a more extreme versio
Usually do just FOSSIL UPDATE and then run make. Now re-opened checkout and
tried again, no problems! Thanks.
-Original Message-
From: Richard Hipp
Sent: Monday, September 19, 2016 9:41 PM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] Compilation error with l
On 9/19/16, Tony Papadimitriou wrote:
> manifest_.c:2631: extra '#endif'.
> tar_.c:708: Unterminated "{"
> Errors while processing "tar_.c"
> NMAKE : fatal error U1077: '.\makeheaders.exe' : return code '0x2'
> Stop.
I'm unable to reproduce the problem on Windows10.
* Fresh Fossil checkout
* cd
manifest_.c:2631: extra '#endif'.
tar_.c:708: Unterminated "{"
Errors while processing "tar_.c"
NMAKE : fatal error U1077: '.\makeheaders.exe' : return code '0x2'
Stop.___
fossil-users mailing list
[email protected]
http://lists.fossil-scm
6 matches
Mail list logo
