Re: Segmentation fault on x86_64
Peter Nixon <[email protected]>
| Newsgroups | gmane.comp.mobile.kannel.devel |
|---|---|
| Message-ID | <[email protected]> |
Current CVS head does appear to work ok on x86_64. Thanks for you help Regards Peter On Sun 30 Jul 2006 15:44, Alexander Malysh wrote: > Hi, > > 1.4.0 is known to crash on x86_64. So please use CVS head and it should > work on 64bit just fine. > and yes kannel is mantained but progress goes a bit slower at this point > int time ;) > > Thanks, > Alex > > Am 29.07.2006, 23:26 Uhr, schrieb Peter Nixon <[email protected]>: > > Hi Alex > > > > It is 1.4.0. The latest rpm I have built is: > > > > http://software.opensuse.org/download/home:/peternixon/SUSE_Linux_10.0/x8 > >6_64/kannel-1.4.0-22.1.x86_64.rpm > > > > Please note that as I am currently working on the spec file to clean it > > up it > > is being rebuilt quite often so you may need to look for a new version > > under: > > > > http://software.opensuse.org/download/home:/peternixon/SUSE_Linux_10.0/x8 > >6_64/ > > > > I will test CVS HEAD on Monday to see if it works on x86_64 and report > > back to > > the list. > > In the mean time I have installed the 32bit compatibility libs that SUSE > > so > > thoughtfully provides for x86_64 releases and 32bit kannel and it seems > > to be > > working ok. > > > > I notice that a stable release hasn't been made in a LONG time. Is work > > proceeding on kannel? Is it being maintained at all? > > > > Regards > > > > Peter > > > > On Sat 29 Jul 2006 15:12, Alexander Malysh wrote: > >> Hi, > >> > >> which version do you use? please try CVS HEAD. > >> > >> Thanks, > >> Alex > >> > >> Am 27.07.2006, 16:40 Uhr, schrieb Peter Nixon <[email protected]>: > >> > Hi Guys > >> > > >> > I have packaged kannel for SUSE Linux (All versions from 9.3 - 10.1 > >> > including > >> > Enterprise 9 and 10). The packages will be available from the > >> > opensuse.org > >> > > >> > Unfortunately when I try to start kannel on a 64bit machine the > >> > >> following > >> > >> > happens: > >> > > >> > # bearerbox -v 1 /etc/kannel/kannel.conf > >> > 2006-07-27 17:09:28 [9308] [0] INFO: Debug_lvl = 1, log_file = <none>, > >> > log_lvl > >> > = 0 > >> > 2006-07-27 17:09:28 [9308] [0] WARNING: DLR: using default 'internal' > >> > >> for > >> > >> > storage type. > >> > 2006-07-27 17:09:28 [9308] [0] INFO: DLR using storage type: internal > >> > Segmentation fault > >> > > >> > > >> > The same package, compiled for 32bit on the same SUSE version (32bit) > >> > with the > >> > same kannel.conf works fine: > >> > > >> > # bearerbox -v 1 /etc/kannel.conf > >> > 2006-07-27 17:51:51 [3621] [0] INFO: Debug_lvl = 1, log_file = <none>, > >> > log_lvl = 0 > >> > 2006-07-27 17:51:51 [3621] [0] WARNING: DLR: using default 'internal' > >> > for storage type. > >> > 2006-07-27 17:51:51 [3621] [0] INFO: DLR using storage type: internal > >> > 2006-07-27 17:51:51 [3621] [0] INFO: Added logfile > >> > `/var/log/bearerbox.log' with level `2'. > >> > 2006-07-27 17:51:51 [3621] [0] INFO: HTTP: Opening server at port > >> > >> 13000. > >> > >> > 2006-07-27 17:51:51 [3621] [0] INFO: Adding interface * > >> > 2006-07-27 17:51:51 [3621] [0] ERROR: Missing wapbox-port variable, > >> > cannot start WAP > >> > 2006-07-27 17:51:51 [3621] [0] INFO: > >> > ---------------------------------------- > >> > 2006-07-27 17:51:51 [3621] [0] INFO: Kannel bearerbox II version 1.4.0 > >> > starting > >> > 2006-07-27 17:51:51 [3621] [0] INFO: MAIN: Start-up done, entering > >> > mainloop > >> > >> ------------------------------------------------------------------------ > >>- > >> > >> > Does anyone else have kannel working successfully on a 64bit machine? > >> > We have had 32bit kannel in operation for over a year at one location > >> > with no > >> > problems. > >> > > >> > Regards -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (GNU/Linux) iD8DBQBE0fSPAcdsUt9pJjwRAtjhAKDXSBQWuFV06oJGYgNaX/yaegeXPwCfbCtL aWeFewreBtyhKipipZkDmoo= =Rh7k -----END PGP SIGNATURE-----