Pike-devel

pike-devel@lists.lysator.liu.se

4 participants
3044 discussions

doc building
by Peter Bortas ＠ Pike developers forum 19 Dec '03

19 Dec '03

7.5 loops forever trying to build the documentation: /pkg/pike/src/Pike/7.5/src/intel-rh9/pike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/pkg/pike/src/Pike/7.5/src/intel-rh9/master.pike -x extract_autodoc -q --srcdir=/pkg/pike/src/Pike/7.5/src \ --imgsrc=/pkg/pike/src/Pike/7.5/refdoc/src_images --builddir=doc_build/src \ --imgdir=doc_build/images % find . -name "intel-*" | grep src /pkg ./pike/src/Pike/7.5/src/intel-rh9 ./pike/src/Pike/7.5/src/intel-rh9/doc_build/src/intel-rh9 ./pike/src/Pike/7.5/src/intel-rh9/doc_build/src/intel-rh9/doc_build/src/intel-rh9 ./pike/src/Pike/7.5/src/intel-rh9/doc_build/src/intel-rh9/doc_build/src/intel-rh9/doc_build/src/intel-rh9 ./pike/src/Pike/7.5/src/intel-rh9/doc_build/src/intel-rh9/doc_build/src/intel-rh9/doc_build/src/intel-rh9/doc_build/src/intel-rh9 ./pike/src/Pike/7.5/src/intel-rh9/doc_build/src/intel-rh9/doc_build/src/intel-rh9/doc_build/src/intel-rh9/doc_build/src/intel-rh9/doc_build/src/intel-rh9 *snip* ... And it goes on and on ... Not that I care to build the documentation at all. What's the configure flag to turn it off?

1 0

Re: SQL
by Martin Nilsson (saturator) ＠ Pike (-) developers forum 19 Dec '03

19 Dec '03

I will not find the solution for you over this 33K modem... Read Sql.pike. / Martin Nilsson (saturator) Previous text: >2003-12-19 23:36: >Subject: Re: SQL >-------------------------------------------------------------------- >ok, so what do i need to do to have sqlite be a supported "protocol"? > >I have a sqlite.pike and sqlite_result.pike in the Sql.pmod directory, >each inheriting the proper files, but still no workie... > >any thoughts? > >bill > >On Fri, 19 Dec 2003, Martin Nilsson (saturator) @ Pike (-) developers forum wrote: > >> And Sql.Sql does that for you when you call its big_query and the lower >> level has no big_query method. >> >> / Martin Nilsson (saturator) >> >> Previous text: >> >2003-12-19 21:41: >> >Subject: Re: SQL >> >-------------------------------------------------------------------- >> >>you could just fake big_query() by executing the query at once, storing >> >>it in an array inside the object returned, and then have the methods >> >>access the array. >> > >> >This is exactly what Sql.sql_result does. You can do >> > >> > Sql.sql_result(xxx->query("blah")) >> > >> >to convert a normal query result to a big_query result. >> > >> > / Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) >> > >> > > > > / Brevbäraren >

1 0

Re: fork()ing into background (was Pike 7.6)
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 19 Dec '03

19 Dec '03

That makes sense. Maybe there should be some provision to be able to remove defines (as well as adding new ones). / Martin Stjernholm, Roxen IS Previous text: >2003-12-19 03:43: >Subject: Re: fork()ing into background (was Pike 7.6) >-------------------------------------------------------------------- >How about arguments like module paths and defines? Should these be part >of the "environment" passed on to the newly started Pike? > >Any thoughts? > >Bill > >On Wednesday, December 17, 2003, at 07:15 PM, Martin Stjernholm, Roxen >IS @ Pike developers forum wrote: > >>> Would it be necessary to put this in master(), as that's where the >>> easiest access to agv/c would be? >> >> Some support in the master is necessary, but the function itself >> probably belongs in the Process module. There are already two >> variables _pike_file_name and _master_file_name in the master for >> this. >> >> / Martin Stjernholm, Roxen IS > > > > / Brevbäraren >

1 0

Re: fork()ing into background (was Pike 7.6)
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 17 Dec '03

17 Dec '03

> Would it be necessary to put this in master(), as that's where the > easiest access to agv/c would be? Some support in the master is necessary, but the function itself probably belongs in the Process module. There are already two variables _pike_file_name and _master_file_name in the master for this. / Martin Stjernholm, Roxen IS Previous text: >2003-12-17 03:30: >Subject: Re: fork()ing into background (was Pike 7.6) >-------------------------------------------------------------------- >Yes, on SunOS 5.9 > >> Good. I think the problem with threads at startup was on e.g. Solaris. >> Did you test there? >> > >Would it be necessary to put this in master(), as that's where the >easiest access to agv/c would be? > >> It doesn't. It's useful to start new pike scripts at any time in a >> multithreaded application. fork only works at startup before any >> threads are started. >> > > > > / Brevbäraren >

1 0

Re: fork()ing into background (was Pike 7.6)
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 17 Dec '03

17 Dec '03

Did it work to start threads in the subprocess? / Henrik Grubbström (Lysator) Previous text: >2003-12-17 03:30: >Subject: Re: fork()ing into background (was Pike 7.6) >-------------------------------------------------------------------- >Yes, on SunOS 5.9 > >> Good. I think the problem with threads at startup was on e.g. Solaris. >> Did you test there? >> > >Would it be necessary to put this in master(), as that's where the >easiest access to agv/c would be? > >> It doesn't. It's useful to start new pike scripts at any time in a >> multithreaded application. fork only works at startup before any >> threads are started. >> > > > > / Brevbäraren >

2 1

Pike 7.6
by Martin Nilsson (saturator) ＠ Pike (-) developers forum 16 Dec '03

16 Dec '03

So what are the items for the Pike 7.6 todo check list?

5 7

mcpcom
by Mirar ＠ Pike developers forum 16 Dec '03

16 Dec '03

What does mcpcom do? PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 17260 xenofarm 39 19 222m 208m 7720 R 99.9 20.6 0:21.60 mcpcom ^^^^^^^^^ ^^^^

2 2

completing the reference
by Martin Bähr 16 Dec '03

16 Dec '03

hi, again and again i find it hard to locate certain pieces of documentation. problems as far as i can see them are: the chapterized reference manual contains a lot of stuff also found in the tree reference. (the module stuff (chapters 9-17)) the tutorial contains stuff that is not in the manual. (notably the definition of static) some things from the tutorial better fit into the reference: Terminology / Glossary Expressions (a tutorial should only explain things needed at that point) any objections to me trying to move things around and mess them up? :-) greetings, martin.

1 0

interesting
by Mirar ＠ Pike developers forum 14 Dec '03

14 Dec '03

I think we have an interesting resolver problem: | Pike v7.5 release 15 running Hilfe v3.5 (Incremental Pike Frontend) | > Protocols.Bittorrent.Port; | ...Torrent.pike:377:Too many arguments to clone call. | ...Torrent.pike:377:Expected: function( : object(is 65691)) | ...Torrent.pike:377:Got : function(object(implements 65692) : void | mixed) | ...Torrent.pike:517:Must return a value for a non-void function. | ...Torrent.pike:654:Must return a value for a non-void function. | ...Torrent.pike:868:Must return a value for a non-void function. | ...Torrent.pike:906:Must return a value for a non-void function. | ...Torrent.pike:914:Must return a value for a non-void function. | ...Torrent.pike:917:Must return a value for a non-void function. | ...Torrent.pike:985:Must return a value for a non-void function. | ...Torrent.pike:1060:Class definition failed. | ...Torrent.pike:1070:Must return a value for a non-void function. | ...Torrent.pike:1123:Must return a value for a non-void function. | ...Port.pike:6:Error looking up 'Torrent' in module '.'. | ...Port.pike:27:Must return a value for a non-void function. | Compiler Error: 1:Error looking up 'Port' in module 'Bittorrent'. | Pike v7.5 release 15 running Hilfe v3.5 (Incremental Pike Frontend) | > Protocols.Bittorrent.Torrent; | (1) Result: Protocols.Bittorrent.Torrent | > Protocols.Bittorrent.Port; | (2) Result: Protocols.Bittorrent.Port Any clues how to fix that?

1 0

Freetype2
by Peter Bortas ＠ Pike developers forum 14 Dec '03

14 Dec '03

The Freetype people seems to have invented a new way of handling their headers. Is this solved in any of the trees? From the package available in latest Debian testing combined with 7.4-HEAD: conftest -g -mcpu=i686 -I/usr/include/freetype2 conftest.c -lfreetype -lz -ldl -lrt -lnsl -lm -lpthread -lcrypt 1>&5 In file included from configure:1104: /usr/include/freetype2/freetype/freetype.h:20:2: #error "`ft2build.h' hasn't been included yet!" /usr/include/freetype2/freetype/freetype.h:21:2: #error "Please always use macros to include FreeType header files." /usr/include/freetype2/freetype/freetype.h:22:2: #error "Example:" /usr/include/freetype2/freetype/freetype.h:23:2: #error " #include <ft2build.h>" /usr/include/freetype2/freetype/freetype.h:24:2: #error " #include FT_FREETYPE_H"

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pike-devel