Re: [fossil-users] Fossil on cygwin64

On 7/26/2013 01:15, Jan Nijtmans wrote: For your other remarks, I suggest that you become a fossil code committer. I've yet to step beyond evaluating Fossil for use here. I like its features and how it works, but I think I'm going to be forced to use git for interoperability reasons. (We'r

Re: [fossil-users] Fossil on cygwin64

2013/7/26 Warren Young : > db.c, db_open(): Wrong. Fix or remove. > > First, hard-coding a conversion to "/cygdrive/%c/%s" will break if the user > has changed the cygdrive mount point in /etc/fstab. This is more common > than you may realize. If you mount cygdrive at the root, you can use > sho

Re: [fossil-users] Fossil on cygwin64

Some of what I wrote was based on wrong assumptions due to being stuck here on a February branch of Fossil's repo. Now that I've looked at the __CYGWIN__ blocks in an up-to-date Fossil trunk, I understand your post better, Jan. Updated commentary inline below. On 7/25/2013 15:59, Warren You

Re: [fossil-users] Fossil on cygwin64

On 7/24/2013 05:06, Warren Young wrote: On 7/24/2013 02:33, Jan Nijtmans wrote: Just wait on the Cygwin64 people to bring out a new Sqlite package with the same fixes already done in Cygwin32. Um, it's the same people. Me. :) Oh, I see what you mean. I forgot that I didn't release 3.7.17-3

Re: [fossil-users] Fossil on cygwin64

On 7/25/2013 16:52, Joe Mistachkin wrote: Warren Young wrote: I guess they already got taken out of the trunk. I did my spelunking in a current pull of the tree. I'm simply searching trunk for "__CYGWIN__". I was stuck on a branch from February. Now that I'm actually looking at the trun

Re: [fossil-users] Fossil on cygwin64

Warren Young wrote: > > I guess they already got taken out of the trunk. I did my spelunking in > a current pull of the tree. > I'm simply searching trunk for "__CYGWIN__". -- Joe Mistachkin ___ fossil-users mailing list fossil-users@lists.fossil-

Re: [fossil-users] Fossil on cygwin64

On 7/25/2013 16:03, Joe Mistachkin wrote: Warren Young wrote: I'm up for some spelunking. Let's go: What about all the __CYGWIN__ blocks in the following files? I guess they already got taken out of the trunk. I did my spelunking in a current pull of the tree. That explains why Richa

Re: [fossil-users] Fossil on cygwin64

On 7/25/2013 04:29, Richard Hipp wrote: Native, pure-blooded windows binaries run just fine on cygwin, right? Mostly, yes. There are exceptions. The Windows console infrastructure isn't as general and as easy to hook into a the Unix TTY equivalent, so there are programs that only work prope

Re: [fossil-users] Fossil on cygwin64

Warren Young wrote: > > I'm up for some spelunking. Let's go: > What about all the __CYGWIN__ blocks in the following files? 1. add.c 2. blob.c 3. checkin.c 4. db.c 5. file.c 6. utf8.c Frankly, I'm not convinced of how many of these are actually necessary. -- Joe Mistachkin _

Re: [fossil-users] Fossil on cygwin64

On 7/25/2013 07:46, Jan Nijtmans wrote: 2013/7/25 Richard Hipp : If it does work, then I move for the immediate banishment of all __CYGWIN__ macros. Doing that will break four things: - Accessing a check-out repository on Cygwin, while the previous check-out was done in win32. Are you mer

Re: [fossil-users] Fossil on cygwin64

On Thu, Jul 25, 2013 at 02:42:23PM -0600, Warren Young wrote: > On 7/25/2013 06:24, Jan Danielsson wrote: > >So .. we used the __CYGWIN__ macro to explicitly break fossil on > >cygwin? That seems unnecessarily creative to me. > > It is well known that the creators of Cygwin do this sort of thi

Re: [fossil-users] Fossil on cygwin64

On 7/25/2013 06:24, Jan Danielsson wrote: So .. we used the __CYGWIN__ macro to explicitly break fossil on cygwin? That seems unnecessarily creative to me. It is well known that the creators of Cygwin do this sort of thing because They're Just Mean. Maybe Fossil's creators are the same wa

Re: [fossil-users] Fossil on cygwin64

On Thu, Jul 25, 2013 at 03:46:21PM +0200, Jan Nijtmans wrote: > 2013/7/25 Richard Hipp : > > If it does work, then I move for the immediate banishment of all __CYGWIN__ > > macros. > > Doing that will break four things: > - Accessing a check-out repository on Cygwin, while the previous check-out >

Re: [fossil-users] Fossil on cygwin64

2013/7/25 Richard Hipp : > If it does work, then I move for the immediate banishment of all __CYGWIN__ > macros. Doing that will break four things: - Accessing a check-out repository on Cygwin, while the previous check-out was done in win32. - Allow usage of win32 paths (possibly coming from WIN

Re: [fossil-users] Fossil on cygwin64

On 7/25/13 2:10 PM, Richard Hipp wrote: > Move to banish __CYGWIN__ from both Fossil and SQLite sources. Do I have a > second? Seconded. /Jan ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bi

Re: [fossil-users] Fossil on cygwin64

On 7/25/13 2:05 PM, Lluís Batlle i Rossell wrote: [---] >> "grep" tells me that there are 33 instances of the __CYGWIN__ macro in >> Fossil, in 8 different files. So if you use "sed" to change them all to >> __CYGWIN_OFF_ (or something else harmless) and then do "./configure; make", >> does it wor

Re: [fossil-users] Fossil on cygwin64

On Thu, Jul 25, 2013 at 8:05 AM, Lluís Batlle i Rossell wrote: > On Thu, Jul 25, 2013 at 07:59:38AM -0400, Richard Hipp wrote: > > On Thu, Jul 25, 2013 at 7:44 AM, Martin Gagnon wrote: > > > > > In Theory, fossil should build and work on fossil like on any other > unix > > > like Operating syste

Re: [fossil-users] Fossil on cygwin64

On Thu, Jul 25, 2013 at 07:59:38AM -0400, Richard Hipp wrote: > On Thu, Jul 25, 2013 at 7:44 AM, Martin Gagnon wrote: > > > In Theory, fossil should build and work on fossil like on any other unix > > like Operating system (like linux/*bsd etc..) That's what cygwin is for. > > > > "grep" tells

Re: [fossil-users] Fossil on cygwin64

On Thu, Jul 25, 2013 at 7:44 AM, Martin Gagnon wrote: > In Theory, fossil should build and work on fossil like on any other unix > like Operating system (like linux/*bsd etc..) That's what cygwin is for. > "grep" tells me that there are 33 instances of the __CYGWIN__ macro in Fossil, in 8 diffe

Re: [fossil-users] Fossil on cygwin64

On Thu, Jul 25, 2013 at 07:44:16AM -0400, Martin Gagnon wrote: > Le 2013-07-25 06:43, Jan Nijtmans a écrit : > >2013/7/25 Richard Hipp : > >> Native, pure-blooded windows binaries run just fine on cygwin, > right? So > >> why are we complicating the code with exceptions, special cases, > and hack

Re: [fossil-users] Fossil on cygwin64

Le 2013-07-25 06:43, Jan Nijtmans a écrit : 2013/7/25 Richard Hipp : >> Native, pure-blooded windows binaries run just fine on cygwin, right? So >> why are we complicating the code with exceptions, special cases, and hacks >> for cygwin? > > There are three things that a windows fossil binar

Re: [fossil-users] Fossil on cygwin64

2013/7/25 Richard Hipp : > Native, pure-blooded windows binaries run just fine on cygwin, right? So > why are we complicating the code with exceptions, special cases, and hacks > for cygwin? There are three things that a windows fossil binary can never do in the Cygwin environment: 1) handle Cygw

Re: [fossil-users] Fossil on cygwin64

Native, pure-blooded windows binaries run just fine on cygwin, right? So why are we complicating the code with exceptions, special cases, and hacks for cygwin? -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-s

Re: [fossil-users] Fossil on cygwin64

2013/7/24 Warren Young : > The bundled SQLite is almost certainly broken with that patch because it > probably isn't using the Cygwin 1.7.20+ F_LCK_MANDATORY feature, so it won't > cooperate properly with any program based on native Windows SQLite. Agreed. It was just an experiment. Closed now. >

Re: [fossil-users] Fossil on cygwin64

On 7/24/2013 05:30, Jan Nijtmans wrote: It looks like SQLite is doing something wrong here: That patch is fine on Cygwin as long as you build Fossil with the external SQLite, rather than the bundled SQLite. The bundled SQLite is a

Re: [fossil-users] Fossil on cygwin64

On Wed, Jul 24, 2013 at 08:01:47AM -0400, Martin Gagnon wrote: > Le 24 juil. 2013 06:06, "Lluís Batlle i Rossell" a > écrit : > > > > On Wed, Jul 24, 2013 at 11:53:02AM +0200, Jan Nijtmans wrote: > > > 2013/7/24 Lluís Batlle i Rossell : > > > > I think our main usage for a cygwin fossil is that we

Re: [fossil-users] Fossil on cygwin64

Le 24 juil. 2013 06:06, "Lluís Batlle i Rossell" a écrit : > > On Wed, Jul 24, 2013 at 11:53:02AM +0200, Jan Nijtmans wrote: > > 2013/7/24 Lluís Batlle i Rossell : > > > I think our main usage for a cygwin fossil is that we develop using a cygwin > > > terminal with bash and vim. And we want fossi

Re: [fossil-users] Fossil on cygwin64

2013/7/24 Warren Young > > Just wait on the Cygwin64 people to bring out a new Sqlite package with >> the same fixes already done in Cygwin32. >> > > Um, it's the same people. Me. :) > > Both packages are generated from the same source, with the same build > options. If they behave differently,

Re: [fossil-users] Fossil on cygwin64

On 7/24/2013 02:33, Jan Nijtmans wrote: SQLITE_CANTOPEN: os_win.c:34063: (3) winOpen(/var/tmp/etilqs_FoaHNBQa56cVGrh\etilqs_PXfZEjH5dBl8Cm5) - The system cannot find the path specified. I'm not sure whether this is a SQLite 3.7.17 thing or if it is due to one of the build option changes i

Re: [fossil-users] Fossil on cygwin64

On Wed, Jul 24, 2013 at 11:53:02AM +0200, Jan Nijtmans wrote: > 2013/7/24 Lluís Batlle i Rossell : > > I think our main usage for a cygwin fossil is that we develop using a cygwin > > terminal with bash and vim. And we want fossil to spawn vim properly on > > commit. > > That should work, only yo

Re: [fossil-users] Fossil on cygwin64

On Wed, Jul 24, 2013 at 11:53:02AM +0200, Jan Nijtmans wrote: > 2013/7/24 Lluís Batlle i Rossell : > > I think our main usage for a cygwin fossil is that we develop using a cygwin > > terminal with bash and vim. And we want fossil to spawn vim properly on > > commit. > > That should work, only yo

Re: [fossil-users] Fossil on cygwin64

2013/7/24 Lluís Batlle i Rossell : > I think our main usage for a cygwin fossil is that we develop using a cygwin > terminal with bash and vim. And we want fossil to spawn vim properly on > commit. That should work, only you should do something like: export EDITOR="C:/Cygwin64/bin/bash.exe -c

Re: [fossil-users] Fossil on cygwin64

On Wed, Jul 24, 2013 at 11:16:19AM +0200, Jan Nijtmans wrote: > 2013/7/24 Lluís Batlle i Rossell : > > Do you happen to know if I can build and run programs for cygwin32, in a > > cygwin64 installation? or I should run two cygwin setups in orthogonally, > > 32 and > > 64? > > I would recommend to

Re: [fossil-users] Fossil on cygwin64

2013/7/24 Lluís Batlle i Rossell : > Do you happen to know if I can build and run programs for cygwin32, in a > cygwin64 installation? or I should run two cygwin setups in orthogonally, 32 > and > 64? I would recommend to compile fossil using: make -f win/Makefile.mingw PREFIX=x86_64-w64-ming

Re: [fossil-users] Fossil on cygwin64

Great! Very informative. Thank you. Do you happen to know if I can build and run programs for cygwin32, in a cygwin64 installation? or I should run two cygwin setups in orthogonally, 32 and 64? On Wed, Jul 24, 2013 at 10:33:38AM +0200, Jan Nijtmans wrote: > On Mon, Jul 22, 2013 at 09:21:57PM +020

Re: [fossil-users] Fossil on cygwin64

On Mon, Jul 22, 2013 at 09:21:57PM +0200, Lluís Batlle i Rossell wrote: > Hello, > > today I built fossil on cygwin64, and it built but "it didn't work". Cloning, > a > line in os_win.c complained about not having permission to create a file (a > tmp > file with some kind of random string) in C:/

Re: [fossil-users] Fossil on cygwin64

On Mon, Jul 22, 2013 at 09:21:57PM +0200, Lluís Batlle i Rossell wrote: > Hello, > > today I built fossil on cygwin64, and it built but "it didn't work". Cloning, > a > line in os_win.c complained about not having permission to create a file (a > tmp > file with some kind of random string) in C:

Re: [fossil-users] Fossil on cygwin64

On Mon, Jul 22, 2013 at 9:21 PM, Lluís Batlle i Rossell wrote: > I've been using happily fossil in cygwin 32-bit since years, and only > today I > tried this cygwin64 (completely new for me). Has anyone tried it? Maybe I > am > doing something very wrong. > Speculation: i _suspect_ that the C mac

[fossil-users] Fossil on cygwin64

Hello, today I built fossil on cygwin64, and it built but "it didn't work". Cloning, a line in os_win.c complained about not having permission to create a file (a tmp file with some kind of random string) in C:/windows. I wonder... why is it running any os_win code? shouldn't cygwin look like uni