I figured out myself what caused the problem mentioned in my last post.
I'd like to share this information just in case someone else stumbles
across it. The problem was:
I'm facing a problem now with running fossil using a CGI script using
the small web server
http://www.sqlite.org/docsrc/artifa
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
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
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
May be you should specify the "-Bstatic" from the makfile, to be sure
static version of every libs are used.
On Fri, Apr 22, 2011 at 7:06 PM, Martin Gagnon wrote:
> Normally, libssl is disponible as a static library (libssl.a). This
> would simplify everything.
>
> What distro are you using ?
>
>
Normally, libssl is disponible as a static library (libssl.a). This
would simplify everything.
What distro are you using ?
- -
Martin
On Fri, Apr 22, 2011 at 3:04 PM, Felix Wolfheimer
wrote:
> True, but the libssl of my distro depends on a whole bunch of other
> libs. Many of them just offered
On Thu, Apr 21, 2011 at 5:14 PM, Felix Wolfheimer
wrote:
> Thanks for your answer. To be more specific: It is no problem to write
> the download page manually. I don't expect fossil to do this for me. But
> when I have the download.html file plus the packages/installers/source
> archives or whatev
True, but the libssl of my distro depends on a whole bunch of other
libs. Many of them just offered as .so in the repos. So it was simpler
for me to copy the shared libs to the chroot jail. However, if switching
off the dependency on libssl for fossil it works with -static.
Am Freitag, den 22.04.
On Fri, Apr 22, 2011 at 07:57:16PM +0200, Felix Wolfheimer wrote:
> However, it took me a while to figure out that I need to copy all the
> dependencies (shared libraries) fossil depends on into the file
> structure accessed by the webserver.
make LDFLAGS=-static
Joerg
___
I tried the approach with the small one-file web server suggested in one
of the replies to my question and it works fine. Fossil is started via
cgi script and I can host all the stuff now using this small webserver.
However, it took me a while to figure out that I need to copy all the
dependencie
The http://www.fossil-scm.org/ site runs off of CGI. (The source code
for the server there can be seen at
http://www.sqlite.org/docsrc/artifact/0f78441e2de25641b0) So the
download files are just plain old content files that the server
delivers.
---> Thanks for this information. I think I underst
On Fri, Apr 22, 2011 at 3:47 AM, Richard Hipp wrote:
> It never occurred to me to make the built-in server of Fossil have the
> ability of serve separate files. I figured that anybody who wanted to do
> that would use a "real" web server like Apache or Nginx or even something
> like the "althttp
On Thu, Apr 21, 2011 at 5:14 PM, Felix Wolfheimer <
f.wolfhei...@googlemail.com> wrote:
> Thanks for your answer. To be more specific: It is no problem to write
> the download page manually. I don't expect fossil to do this for me. But
> when I have the download.html file plus the packages/install
Personally, I'd use the wiki for that. If you want to autogenerate a
download wiki page, you can do that, too, and then have your script update
the Download wiki page.
Bill
On Thu, Apr 21, 2011 at 4:14 PM, Felix Wolfheimer <
f.wolfhei...@googlemail.com> wrote:
> Thanks for your answer. To be
Thanks for your answer. To be more specific: It is no problem to write
the download page manually. I don't expect fossil to do this for me. But
when I have the download.html file plus the packages/installers/source
archives or whatever things I would like to provide to the users: Where
should I pla
On Thu, Apr 21, 2011 at 1:15 PM, Bill Burdick wrote:
> It looks to me like DRH runs that by hand when he makes a new release and
> it's not run automatically from the fossil server on a web request.
That's correct.
>
>
> Bill
>
>
> On Thu, Apr 21, 2011 at 1:43 AM, Felix Wolfheimer <
> f.wolfhe
It looks to me like DRH runs that by hand when he makes a new release and
it's not run automatically from the fossil server on a web request.
Bill
On Thu, Apr 21, 2011 at 1:43 AM, Felix Wolfheimer <
f.wolfhei...@googlemail.com> wrote:
> Dear Fossil Experts,
>
> first of all I would like to tha
Dear Fossil Experts,
first of all I would like to thank you for providing this great
software! I was really amazed when I found it. I searched for a simple
bug tracking/ticketing solution for a small software project and before
I found fossil I played around with some of the "bigger" bug tracking
18 matches
Mail list logo
