What distro are you using ?
---> Fedora 13
May be you should specify the "-Bstatic" from the makfile, to be sure
> static version of every libs are used.
---> Tried to put this option on the command line before the -lz -lssl
-lcrypto but the linker seems to ignore it as the shared libs (libz,
lib
You could make the release package a file in your project. Fossil
would then be able to serve the file the same as it serves any other
project file. However, this will add extraneous data to push/pull
operations.
---> That sounds like a good idea. I'll try this approach as well. It
seems even nic
Turns out it was my mistake.
After looking at the source of the created HTML page, I could see my
'class' declarations coming through (they do not get stripped out, as a
perusal of the wikiformat.c source shows). Rather, I had neglected to
"refresh" the browser so the new CSS got pulled down.
So
I saw this problem, as well. I didn't see a quick fix out there on the net.
On Sat, Apr 23, 2011 at 4:44 AM, Felix Wolfheimer <
f.wolfhei...@googlemail.com> wrote:
[...]
> When I try to use the -static flag for the linker I get a bunch of
> unresolved symbols coming from the static libssl. Here
4 matches
Mail list logo
