On 2/1/2013 3:15 PM, K. Fossil user wrote:
Hello,
1/ Thank you very much Edward Berner. You rock my world.
Of course, embedded system must use light libc...
I've seen that some software uses dietlibc.
In my point of view, static linking can be done in this area, so it
will be easier to spread Fossil everywhere with network support.
2/ I find that strange that a software needs manifest fix to compile
without errors.
Fossil reads "manifest" and "manifest.uuid" at build time to gather some
of the information displayed by the "fossil version" command.
I agree with you that maybe it is what I've done (fossil close) that
may did this...
3/ Could you help Fossil team with dietlibc ?
I got curious and played with musl libc. It was pretty straight
forward; I'll post a summary in another message.
I wouldn't recommend static binaries for general use, however, since
they don't work with some things, such as Pluggable Authentication
Modules and the Name Service Switch, which I feel are expected features
in modern desktop and server Linux.
4/ Crashing...
I do compile Fossil in Porteus to unsure that _if_ it is possible to
compile in Porteus, it will be possible EVERYWHERE to compile it
WITHOUT issues.
I do use Porteus 64 bit for that purpose. And I do run the resulting
binary in Porteus 64 bit either... :-)
The "Crashing" thing occur when I do compile with --static option...
5/ Question: why is it a DNS resolver issue ?
That's just a guess, based on two things: 1) It seemed to be a DNS
resolver issue when I encountered a similar problem once upon a time,
and 2) one of the warnings when building with "--static" is about the
function "gethostbyname" which is part of the DNS resolver.
--
Edward Berner
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
