> Od: "Arnel Legaspi" <jalespr...@gmail.com>
> Komu: fossil-users@lists.fossil-scm.org
> Datum: 22.12.2010 20:21
> Předmět: Re: [fossil-users] Errors during compile in Windows 7 x64
>
>On 12/22/2010 5:35 PM, fossil-users-requ...@lists.fossil-scm.org wrote:
>> On Mon, Dec 20, 2010 at 6:11 PM, Arnel Legaspi<jalespr...@gmail.com>  wrote:
>>
>>> Hello,
>>>
>>> Compiling Fossil in 64-bit Windows 7 appears to stop after the
>>> "makeheaders" step. It produces the following error:
>>>
>>> Can't read input file ".wobjadd_.c;.wobjadd.h" // and so on...
>>>
>>
>> What do you have OBJDIR set to in your toplevel makefile?  Are you using 
>> instead of /?  Have you tried changing the s to /s to see if that fixes the
>> problem?
>
>It's the same as altufaltu had:
>
>SRCDIR = ../src
>OBJDIR = ./wobj
>
>This Makefile has worked previously on 32-bit versions of Windows XP and 
>7. Even if it does put all the *.h files inside the "wobj" folder, I'm 
>able to build Fossil without any issues.
>
>In the meantime, I'm using a box with 32-bit Windows to build Fossil, 
>but if there are other ideas, I'd love to hear them.

There seems to be no way of clearing/replacing "/" with something 
which would allow successful execution of main.mk (by means of  make -f 
Makefile.w32), 
as there is a construct in form of:

SRC = 
  $(SRCDIR)/add.c 
...

which expands into:
./wobj/makeheaders  ./wobj/add_.c:./wobj/add.h

ad subsequently fails as seen from examples of execution of fragments
under msys on windows XP execution of a fragment of build command:
u...@wrk ~/fossil
$ ./wobj/makeheaders  ./wobj/add_.c:./wobj/add.h
fails with error
Can't read input file ".wobjadd_.c;.wobjadd.h"

while crafted fragment in form of:
u...@wrk ~/fossil
$ ./wobj/makeheaders  .\wobjadd_.c:.\wobjadd.h

or
u...@wrk ~/fossil
$ .\wobjmakeheaders  .\wobjadd_.c:.\wobjadd.h

executes successfuly.


Peter
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to