Package: libroxen-guestbook
Version: 1.4-9
Severity: normal

guestbook.pike does not compile as a caudium module.  Here is the
relevant piece of /var/log/caudium/debug/default.1:

----------
Considering guestbook.pike -  compilation failed
Compilation errors found while scanning modules in /usr/share/roxen/modules/:
/usr/lib/pike/7.2.580/lib/include/simulate.h:5  Error: Module is neither 
mapping nor object
/usr/share/roxen/modules/guestbook.pike:252     Error: Must return a value for 
a non-void function.
/usr/share/roxen/modules/guestbook.pike:362     Error: Duplicate local variable 
'result', previous declaration on line 358

/usr/share/roxen/modules/guestbook.pike:366     Error: Duplicate local variable 
'result', previous declaration on line 362
----------

I have never programmed pike, but the last three errors were easy to fix
based on experience with other languages (remove "return;" at 252; add
"string result;" above switch at 356; remove "string" from beginning of
lines 358, 362, and 366).  Fixing the first error requires more specific
knowledge of pike, and I didn't spend much time on it.  Apparently
simulate.h (from pike7.2 package) is included to get the function
explode from /usr/lib/pike/7.2.580/lib/7.0/modules/Simulate.pmod (import
Simulate on line 5), but what it takes to make Simulate.pmod a mapping
or an object requires more knowledge of pike than I have; perhaps this
one is a bug in pike7.2?

$ dpkg -l pike7.2
ii  pike7.2             7.2.580-3           Powerful interpreted programming 
language

Although libroxen-guestbook does not explicitly say it is intended to
work as a caudium module, this is implied by

Depends: roxen (>= 1.3.122-10) | roxen2 | caudium

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-2um
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages libroxen-guestbook depends on:
ii  caudium                     2:1.2.35.1-1 An extensible WWW server written i

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to