Just happened to download v1.36 Linux binary off Fossil page to a
Linux x86-32bit box and surprisingly it would not execute....
http://fossil-scm.org/index.html/uv/download/fossil-linux-x86-1.36.tar.gz
Turns out it's actually a 64bit binary:
file ./fossil
./fossil: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked (uses shared libs), for GNU/Linux 2.6.32,
BuildID[sha1]=abeae887e354f3300aa097e9380ce8acead4711d, stripped
./fossil version -v
This is fossil version 1.36 [c24373934d] 2016-10-24 14:59:33 UTC
Compiled on Oct 24 2016 17:40:35 using gcc-5.4.0 20160609 (64-bit)
SQLite 3.15.0 2016-10-14 10:20:30 707875582f
Schema version 2015-01-24
zlib 1.2.8, loaded 1.2.8
SSL (OpenSSL 1.0.1f 6 Jan 2014)
UNICODE_COMMAND_LINE
DYNAMIC_BUILD
Not sure if this is a new way going forward, if it is, then certianly
this should be noted somewhere on the download page.
Previous releases (v1.35 and v1.34) are x86 32bit, also they are STATIC_BUILD.
This brings up another issue, on 64-bit Linux a staticly-linked 32-bit
fossil binary may not be able to properly bind to 64-bit gcc
run-times, producing error like the following:
./fossil-1.35-x86-32 clone http://fossil-scm.org fossil.fossil
getaddrinfo() fails: Name or service not known
Clone done, sent: 0 received: 0 ip:
server returned an error - clone aborted
So, perhaps, there's a need to post BOTH Linux x84 binaries 32-bit and
64-bit. This way users may not need to scratch heads then tweak and
build Fossil themeselves.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
