Re: [fossil-users] Linux 2.6 :-(

2014-08-09 Thread Andy Bradford
Thus said Steve Bennett on Fri, 08 Aug 2014 15:55:51 +1000:

 Are you sure you just changed /home to 711? 
 Worked OK for me:

I did some  more testing and despite the errors,  it does actually build
jimsh0:

$ ls -l autosetup/jimsh0
ls: autosetup/jimsh0: No such file or directory
$ ./autosetup/find-tclsh 
No installed jimsh or tclsh, building local bootstrap jimsh0
Runtime Error: stdlib.tcl:87: Failed to get pwd
in procedure 'info nameofexecutable' called at file ./autosetup/test-tclsh, 
line 11
at file stdlib.tcl, line 87
Runtime Error: stdlib.tcl:87: Failed to get pwd
in procedure 'info nameofexecutable' called at file ./autosetup/test-tclsh, 
line 11
at file stdlib.tcl, line 87
No working C compiler found. Tried cc and gcc.
false
$ ls -l autosetup/jimsh0
-rwxr-xr-x  1 amb  amb  229487 Aug  9 10:40 autosetup/jimsh0*

Andy
-- 
TAI64 timestamp: 400053e64f70


___
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] Linux 2.6 :-(

2014-08-08 Thread Steve Bennett
On 8 Aug 2014, at 2:34 pm, Andy Bradford amb-fos...@bradfords.org wrote:

 Thus said Joe Mistachkin on Thu, 07 Aug 2014 21:14:56 -0700:
 
 Yeah, it appears the net change  was that Jim Tcl was updated. There
 are quite a  lot of changes to  it since the last  version. However, I
 think it should be fine merging it to trunk? Any conflicting opinions?
 
 No, looks fine now (as far as the merge is concerned).
 
 I tried to test  it by making my /home unreadable  (chmod 711 /home) but
 then  Fossil couldn't  even  update,  and all  other  kinds of  problems
 happened:
 
 $ fossil up
 cannot find current working directory; Permission denied
 $ ./configure --disable-lineedit
 No installed jimsh or tclsh, building local bootstrap jimsh0
 Runtime Error: stdlib.tcl:87: Failed to get pwd
 in procedure 'info nameofexecutable' called at file ./autosetup/test-tclsh, 
 line 11
 at file stdlib.tcl, line 87
 Runtime Error: stdlib.tcl:87: Failed to get pwd
 in procedure 'info nameofexecutable' called at file ./autosetup/test-tclsh, 
 line 11
 at file stdlib.tcl, line 87
 No working C compiler found. Tried cc and gcc.
 $ which tclsh
 /usr/local/bin/tclsh
 $ pwd
 /home/src/fossil
 
 $ cd /home
 $ pwd
 /home
 $ ls
 ls: .: Permission denied
 $ cd src
 $ ls 
 fossil
 
 So  clearly it's  possible to  navigate, but  configure doesn't  like it
 much. I  tried with --debug and  didn't get any other  useful info. It's
 also odd that it didn't think it  could find tclsh (yes I forgot to make
 tclsh disappear, but it thought it was gone already).

Are you sure you just changed /home to 711? 
Worked OK for me:

$ stat /home
  File: `/home'
  Size: 4096Blocks: 8  IO Block: 4096   directory
Device: 801h/2049d  Inode: 164626433   Links: 8
Access: (0711/drwx--x--x)  Uid: (0/root)   Gid: (0/root)
Access: 2013-04-18 13:27:17.195385388 +1000
Modify: 2012-08-10 14:46:50.0 +1000
Change: 2014-08-08 15:52:14.586170436 +1000
 Birth: -

$ ./autosetup/find-tclsh
No installed jimsh or tclsh, building local bootstrap jimsh0
/home/steveb/src/fossil/autosetup/jimsh0
$ ./configure --disable-lineedit
Host System...i686-pc-linux-gnu
Build System...i686-pc-linux-gnu
C compiler...ccache cc -g -O2
...


--
Embedded Systems Specialists - http://workware.net.au/
WorkWare Systems Pty Ltd
W: www.workware.net.au  P: +61 434 921 300
E: ste...@workware.net.au   F: +61 7 3391 6002






___
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] Linux 2.6 :-(

2014-08-08 Thread Andy Bradford
Thus said Steve Bennett on Fri, 08 Aug 2014 15:55:51 +1000:

 Are you sure you just changed /home to 711?

Yes, I did ``chmod  711 /home'' (as root). That was it.  Then I tried to
configure and got the errors. I see you are on Linux. I'm on OpenBSD, so
perhaps things work a little differently (for whatever reason):

$ ls -ld /home
drwxr-xr-x  13 root  wheel  512 Jul 30  2013 /home/
$ sudo chmod 711 /home
$ ls -ld /home
drwx--x--x  13 root  wheel  512 Jul 30  2013 /home/
$ ./configure
No installed jimsh or tclsh, building local bootstrap jimsh0
Runtime Error: stdlib.tcl:87: Failed to get pwd
in procedure 'info nameofexecutable' called at file ./autosetup/test-tclsh, 
line 11
at file stdlib.tcl, line 87
Runtime Error: stdlib.tcl:87: Failed to get pwd
in procedure 'info nameofexecutable' called at file ./autosetup/test-tclsh, 
line 11
at file stdlib.tcl, line 87
No working C compiler found. Tried cc and gcc.
$ which tclsh
/usr/local/bin/tclsh
$ which cc
/usr/bin/cc

Andy
-- 
TAI64 timestamp: 400053e4e3ea


___
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] Linux 2.6 :-(

2014-08-07 Thread Stephan Beal
On Wed, Aug 6, 2014 at 1:29 AM, Warren Young war...@etr-usa.com wrote:

 That has more to do with contemporaneity.  When you talk about Linux 3.x,
 you also necessarily imply recent versions of glibc and such, which is the
 true dependency.


+1


  I seriously doubt Fossil actually makes any syscalls added to Linux 3.x,
 not present in Linux 2.6.  (If there are any such calls, they're probably
 nonportable.)


Correct. The only system-level APIs we use anywhere (off the top of my
head):

- networking, but those are standard APIs which don't randomly change from
glibc version A to B.

- system(), fork(), exec(), but those are also age-old and don't just
randomly change.

- Windows and (IIRC) Mac: native-to/from-unicode string conversions ('Nix
platforms do not do these).

i'm pretty certain (not 100%) that that's it, but i know we don't use any
Linux-specific calls which might depend on a newer glibc version, except
possibly indirectly via the fuse module (its public API does not expose any
such dependencies, but it almost certainly has low-level deps on the OS).

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do. -- Bigby Wolf
___
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] Linux 2.6 :-(

2014-08-07 Thread Sean Woods

 Or you could ask me, since I wrote autosetup :-)

I appreciate your assistance and responsiveness.

 glob.tcl is bundled up in the jimsh0 executable, but you can find it because
 the source code is there - autosetup/jimsh0.c
 
 Some part of the autosetup/configure process is failing because of these odd 
 permissions.
 
 Try running ./configure --debug and look at or send the resulting config.log

My guess is that it's not the actual `glob.tcl` file, but rather the path 
that this program is trying to stat().  It would be nice to drop down to an 
interactive prompt during debugging and examine the program's state.  Since the 
fossil application is supposed to be self-contained, it seems like it can do 
its job looking only at the current folder and not have to go elsewhere.  But 
then again, maybe I don't know.

swoods@web75:Fossil-e0199bfc43$ ./configure --debug
glob.tcl:13: Error: Permission denied
in procedure 'main' called at file ./autosetup/autosetup, line 1908
in procedure 'glob' called at file ./autosetup/autosetup, line 123
in procedure 'glob.glob' called at file glob.tcl, line 174
in procedure 'glob.glob' called at file glob.tcl, line 85
in procedure 'glob.glob' called at file glob.tcl, line 85
in procedure 'glob.glob' called at file glob.tcl, line 85
in procedure 'glob.glob' called at file glob.tcl, line 85
in procedure 'glob.globdir' called at file glob.tcl, line 97
at file glob.tcl, line 13

___
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] Linux 2.6 :-(

2014-08-07 Thread Warren Young

On 8/7/2014 01:26, Stephan Beal wrote:


i'm pretty certain (not 100%) that that's it, but i know we don't use
any Linux-specific calls which might depend on a newer glibc version,


After I posted that, I went out and looked for a list of Linux syscalls 
that included the point where they were introduced.  It turns out that 
recent versions of syscalls(2) include such a table:


http://man7.org/linux/man-pages/man2/syscalls.2.html

I went through that list; Fossil has no business using any of the Linux 
3.0+ calls.  They're kernel module loading enhancements, virtualization 
improvements, etc.  Some of them aren't even exposed by glibc.  Not a 
one is portable, not even by way of cloning a BSD feature.


The only thing Fossil *could* really make use of is sendmmsg(2), which 
for TCP sockets is just a non-portable version of writev(2).  It only 
provides real value for datagram (e.g. UDP) sockets.

___
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] Linux 2.6 :-(

2014-08-07 Thread Steve Bennett
On 8 Aug 2014, at 12:52 am, Sean Woods s...@seanwoods.com wrote:

 
 Or you could ask me, since I wrote autosetup :-)
 
 I appreciate your assistance and responsiveness.
 
 glob.tcl is bundled up in the jimsh0 executable, but you can find it because
 the source code is there - autosetup/jimsh0.c
 
 Some part of the autosetup/configure process is failing because of these odd 
 permissions.
 
 Try running ./configure --debug and look at or send the resulting config.log
 
 My guess is that it's not the actual `glob.tcl` file, but rather the path 
 that this program is trying to stat().  It would be nice to drop down to an 
 interactive prompt during debugging and examine the program's state.  Since 
 the fossil application is supposed to be self-contained, it seems like it can 
 do its job looking only at the current folder and not have to go elsewhere.  
 But then again, maybe I don't know.
 
 swoods@web75:Fossil-e0199bfc43$ ./configure --debug
 glob.tcl:13: Error: Permission denied
 in procedure 'main' called at file ./autosetup/autosetup, line 1908
 in procedure 'glob' called at file ./autosetup/autosetup, line 123
 in procedure 'glob.glob' called at file glob.tcl, line 174
 in procedure 'glob.glob' called at file glob.tcl, line 85
 in procedure 'glob.glob' called at file glob.tcl, line 85
 in procedure 'glob.glob' called at file glob.tcl, line 85
 in procedure 'glob.glob' called at file glob.tcl, line 85
 in procedure 'glob.globdir' called at file glob.tcl, line 97
 at file glob.tcl, line 13

Thanks. Looks like this commit 
(https://github.com/msteveb/jimtcl/commit/7bf43eb589f738b7bdb3b4837bc0dde304046a2d)
means that Jim Tcl now requires read access to each element of the path.

I'll take a look at fixing this. In the meantime, you can install Tcl
(and remove autosetup/jimsh0), or change the permissions.

Cheers,
Steve

--
Embedded Systems Specialists - http://workware.net.au/
WorkWare Systems Pty Ltd
W: www.workware.net.au  P: +61 434 921 300
E: ste...@workware.net.au   F: +61 7 3391 6002






___
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] Linux 2.6 :-(

2014-08-07 Thread Steve Bennett
On 8 Aug 2014, at 10:58 am, Steve Bennett ste...@workware.net.au wrote:

 On 8 Aug 2014, at 12:52 am, Sean Woods s...@seanwoods.com wrote:
 
 
 Or you could ask me, since I wrote autosetup :-)
 
 I appreciate your assistance and responsiveness.
 
 glob.tcl is bundled up in the jimsh0 executable, but you can find it because
 the source code is there - autosetup/jimsh0.c
 
 Some part of the autosetup/configure process is failing because of these 
 odd permissions.
 
 Try running ./configure --debug and look at or send the resulting config.log
 
 My guess is that it's not the actual `glob.tcl` file, but rather the path 
 that this program is trying to stat().  It would be nice to drop down to an 
 interactive prompt during debugging and examine the program's state.  Since 
 the fossil application is supposed to be self-contained, it seems like it 
 can do its job looking only at the current folder and not have to go 
 elsewhere.  But then again, maybe I don't know.
 
 swoods@web75:Fossil-e0199bfc43$ ./configure --debug
 glob.tcl:13: Error: Permission denied
 in procedure 'main' called at file ./autosetup/autosetup, line 1908
 in procedure 'glob' called at file ./autosetup/autosetup, line 123
 in procedure 'glob.glob' called at file glob.tcl, line 174
 in procedure 'glob.glob' called at file glob.tcl, line 85
 in procedure 'glob.glob' called at file glob.tcl, line 85
 in procedure 'glob.glob' called at file glob.tcl, line 85
 in procedure 'glob.glob' called at file glob.tcl, line 85
 in procedure 'glob.globdir' called at file glob.tcl, line 97
 at file glob.tcl, line 13
 
 Thanks. Looks like this commit 
 (https://github.com/msteveb/jimtcl/commit/7bf43eb589f738b7bdb3b4837bc0dde304046a2d)
 means that Jim Tcl now requires read access to each element of the path.
 
 I'll take a look at fixing this. In the meantime, you can install Tcl
 (and remove autosetup/jimsh0), or change the permissions.

I have fixed Jim Tcl, updated autosetup, and pushed a new version to the 
'autosetup' branch.

Please test. If it looks ok, perhaps someone can pull it into trunk.

Cheers,
Steve

--
Embedded Systems Specialists - http://workware.net.au/
WorkWare Systems Pty Ltd
W: www.workware.net.au  P: +61 434 921 300
E: ste...@workware.net.au   F: +61 7 3391 6002






___
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] Linux 2.6 :-(

2014-08-07 Thread Sean Woods
 I have fixed Jim Tcl, updated autosetup, and pushed a new version to the
 'autosetup' branch.
 
 Please test. If it looks ok, perhaps someone can pull it into trunk.

Woo hoo!  It works!  Bonzer!!

swoods@web75:Fossil-93fb7c774f$ ./fossil version
This is fossil version 1.25 [93fb7c774f] 2014-08-08 02:26:54 UTC
___
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] Linux 2.6 :-(

2014-08-07 Thread Andy Bradford
Thus said Steve Bennett on Fri, 08 Aug 2014 12:30:52 +1000:

 I have fixed  Jim Tcl, updated autosetup, and pushed  a new version to
 the 'autosetup' branch.

Did you intend  for the branch to  split off of such an  old revision of
trunk?

Thanks,

Andy
-- 
TAI64 timestamp: 400053e44780


___
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] Linux 2.6 :-(

2014-08-07 Thread Steve Bennett
On 8 Aug 2014, at 1:43 pm, Andy Bradford 
amb-sendok-1410061405.efmchampahhhjobco...@bradfords.org wrote:

 Thus said Steve Bennett on Fri, 08 Aug 2014 12:30:52 +1000:
 
 I have fixed  Jim Tcl, updated autosetup, and pushed  a new version to
 the 'autosetup' branch.
 
 Did you intend  for the branch to  split off of such an  old revision of
 trunk?

No. Not sure why that happened. I'm out of practice with fossil.

--
Embedded Systems Specialists - http://workware.net.au/
WorkWare Systems Pty Ltd
W: www.workware.net.au  P: +61 434 921 300
E: ste...@workware.net.au   F: +61 7 3391 6002






___
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] Linux 2.6 :-(

2014-08-07 Thread Andy Bradford
Thus said Steve Bennett on Fri, 08 Aug 2014 14:00:02 +1000:

 No. Not sure why that happened. I'm out of practice with fossil.

Well, it looks  like Joe decided to  merge trunk into the  branch, so it
may not be  anything to worry about.  I started to look at  it and there
were a lot of  conflicts, but maybe he's more familiar  with the code in
question and could simply resolve  the conflicts easily (or just ignored
them and updated with the latest jimsh sources).

Andy
-- 
TAI64 timestamp: 400053e44dcc


___
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] Linux 2.6 :-(

2014-08-07 Thread Andy Bradford
Thus said Joe Mistachkin on Thu, 07 Aug 2014 21:14:56 -0700:

 Yeah, it appears the net change  was that Jim Tcl was updated. There
 are quite a  lot of changes to  it since the last  version. However, I
 think it should be fine merging it to trunk? Any conflicting opinions?

No, looks fine now (as far as the merge is concerned).

I tried to test  it by making my /home unreadable  (chmod 711 /home) but
then  Fossil couldn't  even  update,  and all  other  kinds of  problems
happened:

$ fossil up
cannot find current working directory; Permission denied
$ ./configure --disable-lineedit
No installed jimsh or tclsh, building local bootstrap jimsh0
Runtime Error: stdlib.tcl:87: Failed to get pwd
in procedure 'info nameofexecutable' called at file ./autosetup/test-tclsh, 
line 11
at file stdlib.tcl, line 87
Runtime Error: stdlib.tcl:87: Failed to get pwd
in procedure 'info nameofexecutable' called at file ./autosetup/test-tclsh, 
line 11
at file stdlib.tcl, line 87
No working C compiler found. Tried cc and gcc.
$ which tclsh
/usr/local/bin/tclsh
$ pwd
/home/src/fossil

$ cd /home
$ pwd
/home
$ ls
ls: .: Permission denied
$ cd src
$ ls 
fossil

So  clearly it's  possible to  navigate, but  configure doesn't  like it
much. I  tried with --debug and  didn't get any other  useful info. It's
also odd that it didn't think it  could find tclsh (yes I forgot to make
tclsh disappear, but it thought it was gone already).

Andy
-- 
TAI64 timestamp: 400053e45372


___
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] Linux 2.6 :-(

2014-08-07 Thread Steve Bennett
On 8 Aug 2014, at 2:14 pm, Joe Mistachkin sql...@mistachkin.com wrote:

 
 Andy Bradford wrote:
 
 Well, it looks  like Joe decided to  merge trunk into the  branch, so it
 may not be  anything to worry about.  
 
 
 Yeah, it appears the net change was that Jim Tcl was updated.  There are
 quite a lot of changes to it since the last version.  However, I think it
 should be fine merging it to trunk?  Any conflicting opinions?

Yes. Looks fine. There's no magic.
All I did was check out the latest autosetup and then run:

.../autosetup --install

I pulled your changes, did the same thing, and it is identical.
So looks good to me.

--
Embedded Systems Specialists - http://workware.net.au/
WorkWare Systems Pty Ltd
W: www.workware.net.au  P: +61 434 921 300
E: ste...@workware.net.au   F: +61 7 3391 6002






___
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] Linux 2.6 :-(

2014-08-06 Thread Steve Bennett
On 6 Aug 2014, at 2:08 pm, Warren Young war...@etr-usa.com wrote:

 On 8/5/2014 18:50, Sean Woods wrote:
 
 I saw that jimsh references glob.tcl, so I removed all my local Tcl/Tk
 stuff -- I wasn't really using it -- and rebuilt Fossil clean from tip,
 to force it to use jimsh, and it still doesn't happen.
 
 How did you do this?  My knowledge of the TCL ecosystem isn't that
 great.
 
 I tugged on loose bits of yarn until the sweater unraveled.  It didn't all 
 come to me in a blinding flash of revelation.
 
 it's trying to stat `/home` which on my system has restricted
 access (not readable or writable by others).
 
 Do you realize that *you* are one of those others in this context?
 
 Your stat(1) output says all you've done is chmod 711 /home relative to the 
 stock CentOS 5 /home permissions, which are 755 root.root.  Since you are 
 neither root nor a member of group root, the only reason you can even cd into 
 your own home directory is the o+x permission.  chmod 710 /home would lock 
 you out of the system entirely.
 
 I suggest that you add yourself to the stock users group, then log out and 
 back in again, then chgrp users /home  chmod 750 /home.
 
 An even better solution to others crawling around in /home is SELinux.
 
 Not that any of this actually solves the problem.  I chmodded my CentOS 5 
 box's /home to 711, too, and Fossil still builds.  The real problem is this 
 glob.tcl file, which isn't present on my system, anywhere.  Why you have one 
 is a complete mystery to me.  You're seeing jimsh0 reading it, then 
 complaining when it hits line 13 in that file.
 
 I see two ways to fix it:
 
 1. Find this glob.tcl file, and move it out of the way, at least temporarily.
 
 2. Install tcl to get tclsh, and forget about jimsh0's confusion.

Or you could ask me, since I wrote autosetup :-)

glob.tcl is bundled up in the jimsh0 executable, but you can find it because
the source code is there - autosetup/jimsh0.c

Some part of the autosetup/configure process is failing because of these odd 
permissions.

Try running ./configure --debug and look at or send the resulting config.log

Cheers,
Steve

--
Embedded Systems Specialists - http://workware.net.au/
WorkWare Systems Pty Ltd
W: www.workware.net.au  P: +61 434 921 300
E: ste...@workware.net.au   F: +61 7 3391 6002






___
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] Linux 2.6 :-(

2014-08-05 Thread Warren Young

On 8/3/2014 15:01, Sean Woods wrote:

What is the latest version of Fossil that will run on the 2.6.x line of
Linux kernels?


I regularly run Fossil on CentOS 5, which still ships kernel 2.6.18.


Can't compile off trunk and I don't know why.


We don't know why, either, since you didn't include the error message 
you got.


The kernel you're running on almost certainly is not the problem.  Most 
likely, you're missing some local userspace facility: a library, header 
file, tool, etc.


(A good example is the Case of the Missing Zip(1) in Stephen Beal's post 
on June 28 in the Fossil on Raspberry Pi thread.)

___
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] Linux 2.6 :-(

2014-08-05 Thread Sean Woods
  What is the latest version of Fossil that will run on the 2.6.x line of
  Linux kernels?
 
 I regularly run Fossil on CentOS 5, which still ships kernel 2.6.18.

As do I.

  Can't compile off trunk and I don't know why.
 
 We don't know why, either, since you didn't include the error message 
 you got.

That error message was pasted in another thread.  When I type
./configure, I get an error message about permissions for `glob.tcl`.  I
responded to Richard's question about it and though he didn't bite on
that one he did help me later by telling me the Makefile trick for which
I'm grateful.  I probably could have re-read the document about
building fossil in the Wiki and spared the discussion on the mailing
list, but hopefully this thread will be useful anyway.

The glob.tcl permissions error seems like an autosetup issue.  I must
admit that I don't understand Fossil's need for autosetup -- at least
for Linux.  It's probably there for Windows or other inferior OS. 
(autosetup does look like it could be a snazzy Autotools replacement)

 The kernel you're running on almost certainly is not the problem.  Most 
 likely, you're missing some local userspace facility: a library, header 
 file, tool, etc

I agree with your reasoning, but here's the thing.  On the Fossil
Downloads page (the one with the staticly linked binaries that just
work) it specifically mentions Linux 3.x as the platform.  When you
try to run one of these binaries on a Linux 2.6 system you get a message
that the binary is not supported by that version of Linux.

If you want to run a static binary on Linux  3.0 without compiling,
there's no obvious way to do that on the Fossil web page.  I'm
comfortable with compiling and don't care, but others may not be in the
same situation.
___
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] Linux 2.6 :-(

2014-08-05 Thread Sean Woods
   $ mkdir skull # fossil head, get it?  Ahahaha.
   $ cd skull
   $ fossil open /museum/fossil.fossil   # where fossils live

Clever!

 I saw that jimsh references glob.tcl, so I removed all my local Tcl/Tk 
 stuff -- I wasn't really using it -- and rebuilt Fossil clean from tip, 
 to force it to use jimsh, and it still doesn't happen.

How did you do this?  My knowledge of the TCL ecosystem isn't that
great.

 I see from your other thread that you are using tarball checkouts.  Now 
 that you have a fossil binary built, what happens if you check out 
 Fossil tip and build from that?

Same result when I try it from a fresh checkout.

[ 8 some other stuff from `fossil open` omitted 8 ]

project-name: Fossil
repository:   /home/swoods/tmp/fossil-tip/../fossil.fossil
local-root:   /home/swoods/tmp/fossil-tip/
config-db:/home/swoods/.fossil
project-code: CE59BB9F186226D80E49D1FA2DB29F935CCA0333
checkout: b6a5023faefffefacfbda986853aa5a845715137 2014-08-05
17:27:43 UTC
parent:   b9b3ce3b3907823d298816149c83b3e3f88c812b 2014-08-05
10:52:57 UTC
leaf: open
tags: trunk
comment:  Updates to the help text for the tarball command. Add
  hyperlinks for accessing content on the /cachestat
  webpage.
  (user: drh)
checkins: 7262

swoods@web75:fossil-tip$ ./configure
No installed jimsh or tclsh, building local bootstrap jimsh0
glob.tcl:13: Error: Permission denied

I ran this through `strace` to see if that gave me any clues.  Looks
like it's trying to stat `/home` which on my system has restricted
access (not readable or writable by others).

stat64(/, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
open(/, O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 3
fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
getdents(3, /* 29 entries */, 32768)= 532
getdents(3, /* 0 entries */, 32768) = 0
close(3)= 0
stat64(/home, {st_mode=S_IFDIR|0751, st_size=12288, ...}) = 0
open(/home, O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = -1 EACCES
(Permission denied)
write(2, glob.tcl:13: Error: Permission d..., 37glob.tcl:13: Error:
Permission denied) = 37
write(2, \n, 1
)   = 1
exit_group(1)   = ?

swoods@web75:fossil-tip$ stat /home
  File: `/home'
  Size: 12288 Blocks: 32 IO Block: 4096   directory
Device: 803h/2051d  Inode: 259522561   Links: 274
Access: (0751/drwxr-x--x)  Uid: (0/root)   Gid: (0/root)
Access: 2014-08-05 13:19:26.0 +
Modify: 2014-08-04 19:17:09.0 +
Change: 2014-08-04 19:17:09.0 +
swoods@web75:fossil-tip$ ls /home
ls: /home: Permission denied
___
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] Linux 2.6 :-(

2014-08-05 Thread Warren Young

On 8/5/2014 18:50, Sean Woods wrote:



I saw that jimsh references glob.tcl, so I removed all my local Tcl/Tk
stuff -- I wasn't really using it -- and rebuilt Fossil clean from tip,
to force it to use jimsh, and it still doesn't happen.


How did you do this?  My knowledge of the TCL ecosystem isn't that
great.


I tugged on loose bits of yarn until the sweater unraveled.  It didn't 
all come to me in a blinding flash of revelation.



it's trying to stat `/home` which on my system has restricted
access (not readable or writable by others).


Do you realize that *you* are one of those others in this context?

Your stat(1) output says all you've done is chmod 711 /home relative 
to the stock CentOS 5 /home permissions, which are 755 root.root.  Since 
you are neither root nor a member of group root, the only reason you can 
even cd into your own home directory is the o+x permission.  chmod 710 
/home would lock you out of the system entirely.


I suggest that you add yourself to the stock users group, then log out 
and back in again, then chgrp users /home  chmod 750 /home.


An even better solution to others crawling around in /home is SELinux.

Not that any of this actually solves the problem.  I chmodded my CentOS 
5 box's /home to 711, too, and Fossil still builds.  The real problem is 
this glob.tcl file, which isn't present on my system, anywhere.  Why you 
have one is a complete mystery to me.  You're seeing jimsh0 reading it, 
then complaining when it hits line 13 in that file.


I see two ways to fix it:

1. Find this glob.tcl file, and move it out of the way, at least 
temporarily.


2. Install tcl to get tclsh, and forget about jimsh0's confusion.
___
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] Linux 2.6 :-(

2014-08-03 Thread David Given
On 8/3/14, 11:01 PM, Sean Woods wrote:
 What is the latest version of Fossil that will run on the 2.6.x line of
 Linux kernels?  I need this in order to run Fossil on my shared host. 
 See yesterday's conversation about filenames with a question mark in
 them.  Can't compile off trunk and I don't know why.

What's the error you're getting? Fossil ought to be pretty vanilla...

(And are you sure it's a kernel issue and not a compiler issue? If you
have a 2.6.x kernel, you might have an old compiler which doesn't do
C99; Fossil should be C89 but I have seen a few C99isms sneak through in
the past.)

-- 
┌─── dg@cowlark.com ─ http://www.cowlark.com ─
│ Feminism encourages women to leave their husbands, kill their
│ children, practice withcraft, destroy capitalism and become lesbians.
│ --- Rev. Pat Robertson



signature.asc
Description: OpenPGP digital 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] Linux 2.6 :-(

2014-08-03 Thread Andy Bradford
Thus said Sean Woods on Sun, 03 Aug 2014 17:01:41 -0400:

 Can't compile off trunk and I don't know why.

What about compiling a release version?

http://www.fossil-scm.org/index.html/timeline?t=release

The latest is 1.29.

If  that compiles  while  trunk  does not,  then  there's  a problem  to
investigate. :-)

Thanks,

Andy
-- 
TAI64 timestamp: 400053deb45c


___
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] Linux 2.6 :-(

2014-08-03 Thread Sean Woods
 If ./configure isn't working for you, then make a copy of Makefile.classic
 into Makefile and hand-edit that file to get it to do what you want.  It 
 isn't hard.

Excellent, that did the trick.  Now everything is as it should be.

Thank you!
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users