Re: [fossil-users] Errors during compile in Windows 7 x64
> Windows users - please try this on your machines and let me know if you have > problems. Thanks everyone for your help in fixing this problem. Makefile.mingw Works for me in Win7+MSYS+MINGW. I think it will be very difficult to make a VS2008 or VS2010 solution that will do the build in the IDE. I have worked with at least one project that builds with a makefile project in the IDE - http://ta-lib.org/ - the ta_libc project is done with NMake. That's about the extent of my ability to contribute on this. Sorry. BTW since makefile.win32 is now removed from the repository, the build wiki needs to be updated to remove references to it. RW Ron Wilson, Engineering Project Lead (o) 434.455.6453, (m) 434.851.1612, www.harris.com HARRIS CORPORATION | RF Communications Division assuredcommunicationsT ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Errors during compile in Windows 7 x64
On Thu, Dec 30, 2010 at 7:07 AM, Kohn Bernhard wrote: > Hello > > > I can try to contribute a VS2010 solution. But I need some information > regarding the tool. As I am not firm in reading/understanding makefiles, can > you explain me, in which order I have to call the mkindex, translate and > makeheader programs. As I understand, on every *.c file should be applied > the three programs? Also I would like to know which version of zlib should > be linked (I have found version 1.2.5 in the net). > I just added build documentation that should give you all the information you need:' http://www.fossil-scm.org/fossil/doc/trunk/www/makefile.wiki > I would create a directory called vs2010, in which the solution file will > be placed (at the same dir level as the src directory), which subdirectories > for the project files. Also I will include the zlib library and include file > there, if this is ok. > > Regarding the awk script, I will search for a windows version available, > which I will also place in the vs2010 directory, so everything should be in > place. The test project which uses tcl I won’t create, as I have no > relation/experience which tcl. > There is a C program in the source tree that does the work of AWK for you. The new build documentation describes how that works. > > > Best regards > > Bernhard > > > > > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Errors during compile in Windows 7 x64
Hello >I also have a brand new copy of VS2010 on my brand new win7 box. Does anybody >have any suggestions on how we might get VS2010 to >compile Fossil? Recognize >that (as with most of the software I write) the "source code" is not really C >code, but rather text that looks a lot >like C but which gets additional >processing prior to being input to the C compiler. In the case of Fossil, the >"C-source-modules" are first >processed by a program (source code included) >called "mkindex", then another program called "translate", then a third >program called >"makeheaders". Then there is an AWK script that runs to >generate some additional header information. Finally, the output of all of >the above >is ready to go into the C compiler. But VS2010 seems to be of the >opinion that all "source code" should be plain and simple C code (or C# or >>whatever) and not require any preprocessing by other utilities. Somebody >correct me if I'm wrong. Is there any (reasonable) way to get >VS2010 to >compile preprocessor programs then run them over source text in order to >generate the C code for input to the compiler? It isn't >like that is a novel >technique or anything - programmers have been doing that sort of thing for a >least 4 decades now (that I know of) and >probably much longer. Would anybody >care to contribute a VS2010 "project" or "solution" that will compile Fossil? > Your input would be >greatly appreciated. I can try to contribute a VS2010 solution. But I need some information regarding the tool. As I am not firm in reading/understanding makefiles, can you explain me, in which order I have to call the mkindex, translate and makeheader programs. As I understand, on every *.c file should be applied the three programs? Also I would like to know which version of zlib should be linked (I have found version 1.2.5 in the net). I would create a directory called vs2010, in which the solution file will be placed (at the same dir level as the src directory), which subdirectories for the project files. Also I will include the zlib library and include file there, if this is ok. Regarding the awk script, I will search for a windows version available, which I will also place in the vs2010 directory, so everything should be in place. The test project which uses tcl I won't create, as I have no relation/experience which tcl. Best regards Bernhard ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Errors during compile in Windows 7 x64
At 10:43 AM 12/23/2010, Richard Hipp wrote: >I had to install zlib in \mingw\include and \mingw\lib but >otherwise no changes were made to the MinGW installation. > >Windows users - please try this on your machines and let me know >if you have problems. Thanks everyone for your help in fixing >this problem. It works over all, but I tweaked a couple of nits: 1. I don't like to modify mingw/lib or mingw/include because they can get rebuilt from scratch when fussing with new releases of MinGW. Since I got my build of zlib from GnuWin32 and installed it with their installer, I changed Makefile.mingw to use a macro to point at the GnuWin32 install folder, and used that macro to construct the -I and -L options to GCC. ZLIBDIR = C:/Programs/GnuWin32 ZLIB = -L$(ZLIBDIR)/lib -I$(ZLIBDIR)/include 2. You shouldn't need to name the Mingw include and lib folders to GCC. The MinGW release of GCC will already know about those locations. 3. The clean target uses a unix-style path name on the DEL command line. I changed clean to look like: del /q $(OBJDIR) del $(APPNAME) This works because a folder name is implicitly a wild-card for all files in that folder, and the /Q option silences the query about acting on that wildcard. I assume that typing "make clean" is intent enough, and I don't need to be asked for more confirmation. 4. The install target still has an mv command, and names the undefined macro INSTALLDIR as the destination. A reasonable substitute on Windwos for mv is MOVE. There is no obviously ideal default location to set for INSTALLDIR, however. I used a fairly stale GCC (3.4.5 mingw special), but I wouldn't expect to see any issues with a newer MinGW release. Ross Berteig r...@cheshireeng.com Cheshire Engineering Corp. http://www.CheshireEng.com/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Errors during compile in Windows 7 x64
And on 64-bit Win7 This is fossil version [4ba6a2c96f] 2010-12-23 18:26:37 UTC From: Clark Christensen To: fossil-users@lists.fossil-scm.org Sent: Thu, December 23, 2010 12:33:26 PM Subject: Re: [fossil-users] Errors during compile in Windows 7 x64 Worked here on 32-bit Win7. I'll see if it does the same for me on 64-bit Win7. But I don't have mingw or msys on that box yet. -Clark From: Richard Hipp To: fossil-users@lists.fossil-scm.org Sent: Thu, December 23, 2010 10:43:53 AM Subject: Re: [fossil-users] Errors during compile in Windows 7 x64 I now have the build working using mingw on my windows7 box. Using the latest Fossil sources: \mingw\msys\1.0\bin\make -f win/Makefile.mingw I had to install zlib in \mingw\include and \mingw\lib but otherwise no changes were made to the MinGW installation. Windows users - please try this on your machines and let me know if you have problems. Thanks everyone for your help in fixing this problem. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Errors during compile in Windows 7 x64
Worked here on 32-bit Win7. I'll see if it does the same for me on 64-bit Win7. But I don't have mingw or msys on that box yet. -Clark From: Richard Hipp To: fossil-users@lists.fossil-scm.org Sent: Thu, December 23, 2010 10:43:53 AM Subject: Re: [fossil-users] Errors during compile in Windows 7 x64 I now have the build working using mingw on my windows7 box. Using the latest Fossil sources: \mingw\msys\1.0\bin\make -f win/Makefile.mingw I had to install zlib in \mingw\include and \mingw\lib but otherwise no changes were made to the MinGW installation. Windows users - please try this on your machines and let me know if you have problems. Thanks everyone for your help in fixing this problem. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Errors during compile in Windows 7 x64
On Thu, Dec 23, 2010 at 09:24:46PM +0100, Lluís Batlle i Rossell wrote: > You can build fossil with any Express (free) edition of Visual Studio (with > the > Visual C compiler). VS2010 Express is just fine. > It comes with a batch script that will put all its programs in the PATH. It > also > puts an icon in "Programs" to start a CMD shell calling that batch script. > From > that on, you have on PATH: > cl.exe - the compiler > link.exe - the linker I forgot to mention... whether to build in i386 for i386, or in i386 for amd64 (cross build), or in amd64 for amd64, it only depends on what is on the PATH (and some other environment variables, like the Windows SDK version). There are batch scripts that place whatever toolchain you need ready to be used in the PATH. Regards again, Lluís. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Errors during compile in Windows 7 x64
On Wed, Dec 22, 2010 at 07:29:13PM -0500, Richard Hipp wrote:
> I spent a very frustrating morning on Monday, downloading mingw and trying
> to get the makefile to work on a new windows7 box I have sitting off to
> might right. It appears that getting the makefile to work on win7 will be
> very hard indeed. If anybody has any hints, I would like to hear them. At
> the moment, the only thing I can think to do is to completely rework the
> entire build process to not depend on standard unix tools like "make" and
> "awk" and "sed" since they just do not work or do not exist on
> mingw/windows7.
mingw is only about the toolchain, and you require more than that. MSYS is a
small collection of unix tools built with the mingw toolchain. They don't
coincide exactly with the current GNU unix tools, so its 'sed' will work a bit
different for example. They can be a bit special on the end of lines too
(CR/CRLF).
The MSYS prebuilt packages you may find can be very outdated. I don't know who
is responsible of maintaining that up to date.
What I'd do is to setup a cygwin environment, simply putting the MINGW toolchain
in the PATH variable previous to the rest of gnu cygwin pieces (its binutils,
gcc, ...), but make your program use the cygwin awk, cygwin sed, ... You can use
the GNU make coming with cygwin too. That will give you an OS environment very
much like what you would get in GNU/linux.
> I also have a brand new copy of VS2010 on my brand new win7 box. Does
> anybody have any suggestions on how we might get VS2010 to compile Fossil?
> Recognize that (as with most of the software I write) the "source code" is
> not really C code, but rather text that looks a lot like C but which gets
> additional processing prior to being input to the C compiler. In the case
> of Fossil, the "C-source-modules" are first processed by a program (source
> code included) called "mkindex", then another program called "translate",
> then a third program called "makeheaders". Then there is an AWK script that
> runs to generate some additional header information. Finally, the output of
> all of the above is ready to go into the C compiler. But VS2010 seems to be
> of the opinion that all "source code" should be plain and simple C code (or
> C# or whatever) and not require any preprocessing by other utilities.
You can build fossil with any Express (free) edition of Visual Studio (with the
Visual C compiler). VS2010 Express is just fine.
It comes with a batch script that will put all its programs in the PATH. It also
puts an icon in "Programs" to start a CMD shell calling that batch script. From
that on, you have on PATH:
cl.exe - the compiler
link.exe - the linker
They require few parameters to go on, and if I recall correctly, with good
defaults. You have to learn how they generate ".obj" from ".c" ("cl file.c" may
be enough). And "link /output:fossil.exe a.obj b.obj ..." can also go on fine.
The MSVC tools come with 'nmake' (their implementation of 'make', with a syntax
slightly different than GNU make, but very close; but it does not like slashes
for paths, for example, iirc).
They come with 'vcbuild' (It can build vcproj files). 'vcproj' files are XML
descriptions on how to build ONE target from a group of source files. People
usually create it with the devenv.exe (the GUI frontend to all those things,
editor included).
They come also with 'msbuild', to build "solutions". Solutions group multiple
vcproj files (so multiple targets), so for example you can have a solution that
builds a Library and a Program linked to that library, whereas with 'vcproj
files' alone you would only be able to build one target.
If you want to use the MSVC compiler, I'd go with cygwin too. Then you have
gnumake, and other current gnu unix tools. Simply prepare your compiler
instructions to issue a "cl file.c /out:file.obj" or however that is done
instead of "gcc -c file.c", and you are done.
Personally, I barely use windows other than through cygwin's bash and rxvt or
sshd. Then I always prefer to have tools like 'fossil' built on cygwin instead
of raw Windows.
I may be able to answer in more detail, on questions about more detail.
Regards,
Lluís.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Errors during compile in Windows 7 x64
__ > Od: "Richard Hipp" > Komu: fossil-users@lists.fossil-scm.org > Datum: 23.12.2010 19:44 > Předmět: Re: [fossil-users] Errors during compile in Windows 7 x64 > >I now have the build working using mingw on my windows7 box. Using the >latest Fossil sources: > > mingwmsys1.0binmake -f win/Makefile.mingw > >I had to install zlib in mingwinclude and mingwlib but otherwise no >changes were made to the MinGW installation. > >Windows users - please try this on your machines and let me know if you have >problems. Thanks everyone for your help in fixing this problem. > >-- >D. Richard Hipp >d...@sqlite.org Recipe in win/Makefile.mingw works for me on XP box under msys and mingw. Thanks. Peter ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Errors during compile in Windows 7 x64
I now have the build working using mingw on my windows7 box. Using the latest Fossil sources: \mingw\msys\1.0\bin\make -f win/Makefile.mingw I had to install zlib in \mingw\include and \mingw\lib but otherwise no changes were made to the MinGW installation. Windows users - please try this on your machines and let me know if you have problems. Thanks everyone for your help in fixing this problem. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Errors during compile in Windows 7 x64
On Thu, 23 Dec 2010 13:49:39 + (GMT) mailer-dae...@sqlite.org (Mail Delivery System) wrote: > This is the mail system at host sqlite.org. > > I'm sorry to have to inform you that your message could not > be delivered to one or more recipients. It's attached below. > > For further assistance, please send mail to postmaster. > > If you do so, please include this problem report. You can > delete your own text from the attached returned message. > >The mail system > > (expanded from ): host > gmail-smtp-in.l.google.com[74.125.45.27] said: 552-5.7.0 Our > system detected an illegal attachment on your message. Please > 552-5.7.0 visit > http://mail.google.com/support/bin/answer.py?answer=6590 to 552 5.7.0 > review our attachment guidelines. g9si13724882ybn.2 (in reply to end > of DATA command) D'oh. That was silly of me. You will find the script at https://dreamtrack.dnsalias.com/downloads/do.cmd.txt instead. Sorry for the noise. signature.asc Description: PGP signature ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Errors during compile in Windows 7 x64
At 06:34 PM 12/22/2010, altufa...@mail.com wrote: >Hi Ross, >I face this issue even on Win32 XP SP2. It used to build >successfully before recent commit [e084092a07]. > >Were you successful to build it after above commit? I don't know (yet). The last build I built myself was probably [6fd2ff1b09] from last August. I should have some time to look into this over the coming weekend. It looks like I probably used MinGW with make, sed and awk from GnuWin32, based on the Makefile.w32 that was in the source kit then. Ross Berteig r...@cheshireeng.com Cheshire Engineering Corp. http://www.CheshireEng.com/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Errors during compile in Windows 7 x64
Hi Ross, I face this issue even on Win32 XP SP2. It used to build successfully before recent commit [e084092a07]. Were you successful to build it after above commit? - Altu -Original Message- From: Ross Berteig To: fossil-users@lists.fossil-scm.org; fossil-users@lists.fossil-scm.org Sent: Thu, Dec 23, 2010 7:04 am Subject: Re: [fossil-users] Errors during compile in Windows 7 x64 At 04:29 PM 12/22/2010, Richard Hipp wrote: >I spent a very frustrating morning on Monday, downloading mingw >and trying to get the makefile to work on a new windows7 box I >have sitting off to might right. It appears that getting the >makefile to work on win7 will be very hard indeed. If anybody >has any hints, I would like to hear them. At the moment, the >only thing I can think to do is to completely rework the entire >build process to not depend on standard unix tools like "make" >and "awk" and "sed" since they just do not work or do not exist >on mingw/windows7. >This ought to work "out of the box" if you add MSYS to your MinGWinstallation. Alternatively, there are builds of most of thecommon *nix utilities available from the GnuWin32 project(gnuwin32.sourceforge.net). I know that they provide builds ofboth sed and awk. Assuming you use Gnu Make built natively forWindows (also available from GnuWin32), then it ought to bepossible to get it to build from a CMD prompt without the MSYSport of bash and friends. I have built fossil here under WinXPusing some combination of the above tricks, but that PC is nowretired and I haven't had a reason to build fossil myself since Ireplaced it with a new Win 7 Pro machine.If your Win 7 is either Professional or Ultimate (but not HomePremium) then another approach is to install Virtual PC and thehighly integrated XP Mode. That gets you a virtual machinerunning a fully licensed XP SP3. (With Home Premium, you canstill use Virtual PC, but you don't get an XP license to run init so you'd have to provide one separately.)This is a useful thing to do if you want and need to test thingsin 32-bit XP as well as under Win 7 64-bit, or if you have toolsthat cannot run in Win 7 for some obscure reason. If you had aknown to work build recipe for XP, then this might be an approach.I will take some time "soon" to work out what the build recipefor MinGW on Win7Pro 64-bit can be, and specifically whatpackages other than MinGW are required to get it to build. I'llreport back to the list if someone doesn't beat me to it.Ross Berteig r...@cheshireeng.comcheshire Engineering Corp. http://www.CheshireEng.com/___fossil-users mailing listfossil-us...@lists.fossil-scm.orghttp://lists.fossil-scm.org:8080/cgi -bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Errors during compile in Windows 7 x64
At 04:29 PM 12/22/2010, Richard Hipp wrote: >I spent a very frustrating morning on Monday, downloading mingw >and trying to get the makefile to work on a new windows7 box I >have sitting off to might right. It appears that getting the >makefile to work on win7 will be very hard indeed. If anybody >has any hints, I would like to hear them. At the moment, the >only thing I can think to do is to completely rework the entire >build process to not depend on standard unix tools like "make" >and "awk" and "sed" since they just do not work or do not exist >on mingw/windows7. > This ought to work "out of the box" if you add MSYS to your MinGW installation. Alternatively, there are builds of most of the common *nix utilities available from the GnuWin32 project (gnuwin32.sourceforge.net). I know that they provide builds of both sed and awk. Assuming you use Gnu Make built natively for Windows (also available from GnuWin32), then it ought to be possible to get it to build from a CMD prompt without the MSYS port of bash and friends. I have built fossil here under WinXP using some combination of the above tricks, but that PC is now retired and I haven't had a reason to build fossil myself since I replaced it with a new Win 7 Pro machine. If your Win 7 is either Professional or Ultimate (but not Home Premium) then another approach is to install Virtual PC and the highly integrated XP Mode. That gets you a virtual machine running a fully licensed XP SP3. (With Home Premium, you can still use Virtual PC, but you don't get an XP license to run in it so you'd have to provide one separately.) This is a useful thing to do if you want and need to test things in 32-bit XP as well as under Win 7 64-bit, or if you have tools that cannot run in Win 7 for some obscure reason. If you had a known to work build recipe for XP, then this might be an approach. I will take some time "soon" to work out what the build recipe for MinGW on Win7Pro 64-bit can be, and specifically what packages other than MinGW are required to get it to build. I'll report back to the list if someone doesn't beat me to it. Ross Berteig r...@cheshireeng.com Cheshire Engineering Corp. http://www.CheshireEng.com/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Errors during compile in Windows 7 x64
I spent a very frustrating morning on Monday, downloading mingw and trying to get the makefile to work on a new windows7 box I have sitting off to might right. It appears that getting the makefile to work on win7 will be very hard indeed. If anybody has any hints, I would like to hear them. At the moment, the only thing I can think to do is to completely rework the entire build process to not depend on standard unix tools like "make" and "awk" and "sed" since they just do not work or do not exist on mingw/windows7. I finally gave up in frustration and just did a new build, hoping that would satisfy the needs of windows users for the time being. See http://www.fossil-scm.org/download.html for the new build. Note that the win32 builds on the website are generated by running mingw configured as a cross-compiler and running on Linux. So "make" works as advertised and I have "awk" and "sed" and all the usual tools that make life so easy and pleasant and stress-free on unix. I also have a brand new copy of VS2010 on my brand new win7 box. Does anybody have any suggestions on how we might get VS2010 to compile Fossil? Recognize that (as with most of the software I write) the "source code" is not really C code, but rather text that looks a lot like C but which gets additional processing prior to being input to the C compiler. In the case of Fossil, the "C-source-modules" are first processed by a program (source code included) called "mkindex", then another program called "translate", then a third program called "makeheaders". Then there is an AWK script that runs to generate some additional header information. Finally, the output of all of the above is ready to go into the C compiler. But VS2010 seems to be of the opinion that all "source code" should be plain and simple C code (or C# or whatever) and not require any preprocessing by other utilities. Somebody correct me if I'm wrong. Is there any (reasonable) way to get VS2010 to compile preprocessor programs then run them over source text in order to generate the C code for input to the compiler? It isn't like that is a novel technique or anything - programmers have been doing that sort of thing for a least 4 decades now (that I know of) and probably much longer. Would anybody care to contribute a VS2010 "project" or "solution" that will compile Fossil? Your input would be greatly appreciated. On Tue, Dec 21, 2010 at 9:00 AM, wrote: > OBJDIR = ./wobj in Makefile.w32 > > > -Original Message----- > From: Richard Hipp > To: fossil-users@lists.fossil-scm.org > Sent: Tue, Dec 21, 2010 5:40 pm > Subject: Re: [fossil-users] Errors during compile in Windows 7 x64 > > > > > > On Mon, Dec 20, 2010 at 6:11 PM, Arnel Legaspi > 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 ".\wobj\add_.c;.\wobj\add.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? > > > Checking the "wobj" folder, there are no files ending in *.h. > I am using MinGW for this with GCC v4.5.1. > > There are instructions on the Fossil wiki regarding using Pelles-C > instead of MinGW - should I try that instead? > > Thanks, > Arnel > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > > > > -- > D. Richard Hipp > d...@sqlite.org > > > ___fossil-users mailing > listfossil-us...@lists.fossil-scm.orghttp://lists.fossil-scm.org:8080/cgi > -bin/mailman/listinfo/fossil-users > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Errors during compile in Windows 7 x64
> Od: "Arnel Legaspi" > 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 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
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 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 ".\wobj\add_.c;.\wobj\add.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. Thanks, Arnel ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Errors during compile in Windows 7 x64
OBJDIR = ./wobj in Makefile.w32 -Original Message- From: Richard Hipp To: fossil-users@lists.fossil-scm.org Sent: Tue, Dec 21, 2010 5:40 pm Subject: Re: [fossil-users] Errors during compile in Windows 7 x64 On Mon, Dec 20, 2010 at 6:11 PM, Arnel Legaspi 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 ".\wobj\add_.c;.\wobj\add.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? Checking the "wobj" folder, there are no files ending in *.h. I am using MinGW for this with GCC v4.5.1. There are instructions on the Fossil wiki regarding using Pelles-C instead of MinGW - should I try that instead? Thanks, Arnel ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- D. Richard Hipp d...@sqlite.org ___fossil-users mailing listfossil-us...@lists.fossil-scm.orghttp://lists.fossil-scm.org:8080/cgi -bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Errors during compile in Windows 7 x64
On Mon, Dec 20, 2010 at 6:11 PM, Arnel Legaspi 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 ".\wobj\add_.c;.\wobj\add.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? > > Checking the "wobj" folder, there are no files ending in *.h. > I am using MinGW for this with GCC v4.5.1. > > There are instructions on the Fossil wiki regarding using Pelles-C > instead of MinGW - should I try that instead? > > Thanks, > Arnel > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Errors during compile in Windows 7 x64
Oops, posted local link there. http://www.fossil-scm.org/index.html/info/e084092a07 -Original Message- From: altufa...@mail.com To: fossil-users@lists.fossil-scm.org Sent: Tue, Dec 21, 2010 9:18 am Subject: Re: [fossil-users] Errors during compile in Windows 7 x64 Me too get this error, compiling on XP (MinGW). Looks like one of the side effects of http://localhost/fossil/fossil/info/e084092a07.-Original Message-From: Arnel Legaspi To: fossil-us...@lists.fossil-scm.orgsent: Tue, Dec 21, 2010 4:41 amSubject: [fossil-users] Errors during compile in Windows 7 x64Hello,Compiling Fossil in 64-bit Windows 7 appears to stop after the "makeheaders" step. It produces the following error:Can't read input file ".\wobj\add_.c;.\wobj\add.h" // and so on...Checking the "wobj" folder, there are no files ending in *.h.I am using MinGW for this with GCC v4.5.1.There are instructions on the Fossil wiki regarding using Pelles-C instead of MinGW - should I try that instead?Thanks,Arnel___fossil -users mailing listfossil-us...@lists.fossil-scm.orghttp://lists.fossil-scm.org:8080/cgi -bin/mailman/listinfo/fossil-users ___fossil-users mailing listfossil-us...@lists.fossil-scm.orghttp://lists.fossil-scm.org:8080/cgi -bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Errors during compile in Windows 7 x64
Me too get this error, compiling on XP (MinGW). Looks like one of the side effects of http://localhost/fossil/fossil/info/e084092a07. -Original Message- From: Arnel Legaspi To: fossil-users@lists.fossil-scm.org Sent: Tue, Dec 21, 2010 4:41 am Subject: [fossil-users] Errors during compile in Windows 7 x64 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 ".\wobj\add_.c;.\wobj\add.h" // and so on...Checking the "wobj" folder, there are no files ending in *.h.I am using MinGW for this with GCC v4.5.1.There are instructions on the Fossil wiki regarding using Pelles-C instead of MinGW - should I try that instead?Thanks,Arnel___fossil -users mailing listfossil-us...@lists.fossil-scm.orghttp://lists.fossil-scm.org:8080/cgi -bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
