On Thu, Dec 15, 2011 at 5:57 AM, Dmitry Chestnykh <[email protected]>wrote:
> On Thu, 15 Dec 2011 01:43:42 +0100 BohwaZ wrote: > > > Server: https://[email protected]/garradin/ > > Bytes Cards Artifacts Deltas > > Sent: 279 4 0 0 > > waiting for server...fossil: relocation > > error: /lib/libnss_mdns4_minimal.so.2: symbol strlen, version > > GLIBC_2.0 not defined in file libc.so.6 with link time reference > > It seems like it was a bad decision to put statically linked Fossil > on /downloads.html. Linux binaries cannot be statically linked > reliably -- they depend on the particular version of glibc for DNS > resolution and other things. GCC even shows a warning about this: > > ./bld/shell.o: In function `find_home_dir': > /home/dchest/src/fossil/./src/shell.c:2547: warning: Using 'getpwuid' > in statically linked applications requires at runtime the shared > libraries from the glibc version used for linking ./bld/http_socket.o: > In function > `socket_open': /home/dchest/src/fossil/./bld/http_socket_.c:151: > warning: Using 'gethostbyname' in statically linked applications > requires at runtime the shared libraries from the glibc version used > for linking > > Richard, can we go back to the dynamically linked one? > Dynamic linking means going without SSL, which many Linux systems do not have installed. I did the current build on a circa 2006 32-bit SuSE linux system that has never been upgraded. And I can run the resulting binary on the very latest Ubuntu install on a 64-bit I7. Presumably it also works on everything in between. So I think the incompatibility warning is overstated. > > -- > Dmitry Chestnykh > http://www.codingrobots.com > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
