On Wed, 30 Jan 2013, Jan Nijtmans wrote:
2013/1/29 Stephan Beal:
On Tue, Jan 29, 2013 at 9:00 AM, K. Fossil user wrote:
Latest stable release or dev release does not compile with option:
--static
...
Like networking libs, it will produce warnings like:
warning: Using 'dlopen' in
2013/1/30 Sergei Gavrikov sergei.gavri...@gmail.com:
[FYI]
An optimized (-O2) default build with entered substitution
-Dstrcmp=fossil_strcmp fails (SIGSEG) on i686 GNU/Linux
...
Program received signal SIGSEGV, Segmentation fault.
...
Thanks! That's fully explainable: When setting
On Wed, Jan 30, 2013 at 11:10 AM, Jan Nijtmans jan.nijtm...@gmail.comwrote:
Fossil's TCL support also appears to use dlopen()
- The link flag -ldl is missing on Linux. That's the shared library
containing dlopen,so - indeed - without it, Tcl support will not work.
Which flavour of linux
On Wed, Jan 30, 2013 at 12:54 AM, David Given d...@cowlark.com wrote:
(How does one go about submitting a contributor agreement?)
Hi!
http://www.fossil-scm.org/fossil/doc/trunk/www/copyright-release.html
That needs to be printed out, filled out, and snail-mailed to the address
at the bottom
2013/1/30 Stephan Beal sgb...@googlemail.com:
On Wed, Jan 30, 2013 at 11:10 AM, Jan Nijtmans jan.nijtm...@gmail.com
wrote:
Fossil's TCL support also appears to use dlopen()
- The link flag -ldl is missing on Linux. That's the shared library
containing dlopen,so - indeed - without it, Tcl
On Wed, Jan 30, 2013 at 8:11 AM, Jan Nijtmans jan.nijtm...@gmail.comwrote:
2013/1/30 Sergei Gavrikov sergei.gavri...@gmail.com:
[FYI]
An optimized (-O2) default build with entered substitution
-Dstrcmp=fossil_strcmp fails (SIGSEG) on i686 GNU/Linux
...
Program received signal
On Wed, Jan 30, 2013 at 5:10 AM, Jan Nijtmans jan.nijtm...@gmail.comwrote:
2013/1/29 Stephan Beal sgb...@googlemail.com:
On Tue, Jan 29, 2013 at 9:00 AM, K. Fossil user
ticketpersonnal-fos...@yahoo.fr wrote:
Latest stable release or dev release does not compile with option:
--static
While I agree that the -Dstrcmp... solution is inadequate, strcmp is
subject to the system locale setting. While it might default to the C
locale (giving the expected binary comparison behavior), it might not.
One may not consider locale the same as localization, but whatever you
choose to call
And never mind, I guess I was wrong. Not sure why I couldn't have
checked that *before* clicking send, but c'est la vie.
SDR
On Wed, Jan 30, 2013 at 8:19 AM, Richard Hipp d...@sqlite.org wrote:
On Wed, Jan 30, 2013 at 8:11 AM, Jan Nijtmans jan.nijtm...@gmail.com
wrote:
2013/1/30 Sergei
2013/1/30 Richard Hipp d...@sqlite.org:
I'm uncomfortable with this change. If we need to use fossil_strcmp()
everywhere (which surprises me, since strcmp() should *not* be subject to
localization) then we should do so explicitly, and not depend on
preprocessor magic, as the preprocessor
I'm not yet convinced this is a problem that needs fixing.
D. Richard Hipp - d...@sqlite.org
Sent from phone - pardon brevity
On Jan 30, 2013 11:00 AM, Jan Nijtmans jan.nijtm...@gmail.com wrote:
2013/1/30 Richard Hipp d...@sqlite.org:
I'm uncomfortable with this change. If we need to use
On Wed, 30 Jan 2013, Jan Nijtmans wrote:
2013/1/30 Richard Hipp wrote:
I'm uncomfortable with this change. If we need to use fossil_strcmp()
everywhere (which surprises me, since strcmp() should *not* be subject to
localization) then we should do so explicitly, and not depend on
On Wed, Jan 30, 2013 at 11:10:46AM +0100, Jan Nijtmans wrote:
and encountered 2 minor problems on Linux:
- strcmp from the static C library cannot be used, it should be
replaced by fossil_strcmp everywhere. (that's a good idea
anyway, as strcmp is locale-dependant)
No, it isn't. That's
-DLL = Windows.
I do not use window$
-Warning does not stop compiling... :-)
-Why do I ask for --static compilation to succeed
Don't forget that if you would like Fossil to be used, it must be easy to
compile, especially with option --static.
People would like to use a DVCS everywhere with any
On Wed, Jan 30, 2013 at 12:30 PM, K. Fossil user
ticketpersonnal-fos...@yahoo.fr wrote:
People would like to use a DVCS everywhere with any distro with the SAME
binary, not the one specific to a distro.
I concur. Unfortunately, this is a function of the distro more than of the
application.
On Wed, 30 Jan 2013, K. Fossil user wrote:
People would like to use a DVCS everywhere with any distro with the
SAME binary, not the one specific to a distro.
First, I do not say that build process for a static executable should
fail. But at least such process is not trivial (it was given a lot
On Wed, Jan 30, 2013 at 8:45 PM, Sergei Gavrikov
sergei.gavri...@gmail.comwrote:
Incidentally, there is another opinion, Never use static linking!
http://www.akkadia.org/drepper/no_static_linking.html
On a related note, Solaris 10 removed static versions of their system
libraries, due to a
Hi
[The below is thanking -static issue]
I search through the list for /Fabrice Bellard/ and found nothing. His
famous Tiny C Compiler (http://en.wikipedia.org/wiki/Tiny_C_Compiler
http://bellard.org/tcc/) is well-known in Tcl community and they know
its strengths.
I want to share here my
On Wed, Jan 30, 2013 at 10:29 PM, Sergei Gavrikov sergei.gavri...@gmail.com
wrote:
I search through the list for /Fabrice Bellard/ and found nothing. His
famous Tiny C Compiler (http://en.wikipedia.org/wiki/Tiny_C_Compiler
http://bellard.org/tcc/) is well-known in Tcl community and they know
2013/1/30 Jan Nijtmans jan.nijtm...@gmail.com:
The $tclconfig(TCL_LIBS) contains the -ldl, but
$tclconfig(TCL_STUB_LIB_SPEC) does not, which is
OK. (the stub library doesn't use dlopen, fossil does)
Somehow, fossil should add -ldl here, such that the
--with-tcl-stubs option works in
Hello -
Yesterday I needed to revert back a commit involving 2 files to its parent
commit.
The working copy was at the tip (1255785c96) and I needed to get back to
revision 4002407825.
When I tried running fossil revert -r 4002407825 I got the following
error:
fossil: the --revision option does
On Wed, Jan 30, 2013 at 02:48:33PM -0800, Arnel Legaspi wrote:
Hello -
Yesterday I needed to revert back a commit involving 2 files to its parent
commit.
The working copy was at the tip (1255785c96) and I needed to get back to
revision 4002407825.
When I tried running fossil revert -r
On Wed, Jan 30, 2013 at 10:46 PM, Stephan Beal sgb...@googlemail.com wrote:
i've written the tcc team expressing my amazement at this type of result,
but they respond to my excitement with a sober, but the runtime code is not
as fast as gcc's. (Also, tcc's warning/error messages are, in
23 matches
Mail list logo
