Your message dated Sat, 24 Mar 2007 07:17:36 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#413042: zaptel-source: AMD64 KernelFlag
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: zaptel-source
Version: 1:1.2.13~dfsg-1
Severity: normal



-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages zaptel-source depends on:
ii  bzip2                         1.0.3-6    high-quality block-sorting file co
ii  debhelper                     5.0.42     helper programs for debian/rules
ii  module-assistant              0.10.8     tool to make module package creati

Versions of packages zaptel-source recommends:
ii  zaptel                   1:1.2.11.dfsg-1 zapata telephony utilities

-- no debconf information
I think I got things working on AMD64 by adding this kernel flag This needs 
verification as I didn't go back and break it again. I found the fix at:

http://www.voip-info.org/wiki/index.php?page=zaptel-x86_64  Which said:

>I asked Digium sales support about compiling Zaptel on an AMD64 / x86_64 
/ SMP Opteron system prior to buying a card from them. Their response was:

"The only thing you'll need to do with regards to compilation is to 
add: -mcmodel=kernel to the first KFLAGS definition in the Zaptel Makefile.


--- End Message ---
--- Begin Message ---
notfound 1:1.2.13~dfsg-1

thanks

Closed at the reporter's request. Issue has been resolved in 1.2 (and
in 1.0 we had our specific patch, IIRC).

-- 
               Tzafrir Cohen       
icq#16849755                    jabber:[EMAIL PROTECTED]
+972-50-7952406           mailto:[EMAIL PROTECTED]       
http://www.xorcom.com  iax:[EMAIL PROTECTED]/tzafrir

--- End Message ---

Reply via email to