Thank you Michael for your suggestion on patches. I updated two of the patches for the new source and the others seemed to have been included in the new source.
As suggested, one of the patches corrected the problem of the startup script not finding the executables. I have also added udns and libgsasl to the Makefile as the build originally failed showing these were required. However I have not yet been able to fix the problem with c2s and sm as outlined below. -----Original Message----- From: Michael McConville [mailto:mm...@mykolab.com] Sent: Saturday, February 6, 2016 5:06 PM To: Stephen Graf <s_g...@telus.net> Subject: Re: jabberd out of date Hi, Stephen. It looks like patches/patch-tools_jabberd_in addressed this in the existing port. When updating a port, always be sure to consider every patch. Reports like this should almost always go to ports@openbsd.org so that everyone can help. It's sometimes best to discuss privately if you're going into great detail on something with the maintainer, though. Thanks for working on this! It looks like you're pretty close to having a functional port that we can commit. Best, Michael Stephen Graf wrote: > I am not doing very well and without help am not going anywhere. > Between not knowing the application and never having worked within > ports, there is just too much to learn and at my age there are too few > brain cells left > > So far I have built the new port by: > - starting with an empty port and adding the Makefile from the old port. > - changing the name and source of the application > - removing references to a module that is no longer used (resolver) > - using the step by step procedure to build > > Two of the four modules seem to start and run (router, s2s) and two do not > with errors that are probably due to the build procedure. > A startup script (jabberd) fails because the executable modules are put into > /usr/local/libexe/jabberd and the new script seems to want them in > /usr/local/sbin. The modules can be run without the startup script so a > workaround is available. > > The PLIST only generates samples for the config files and does not put them > into /etc. The PLIST from the old system puts the config files into > /etc/jabberd. I can work around this also. > > The c2s module fails as follows: > # /usr/local/libexec/jabberd/c2s -D > Sat Feb 6 16:35:56 2016 [notice] modules search path: > /usr/local/lib/jabberd Sat Feb 6 16:35:56 2016 [info] loading 'mysql' > authreg module Sat Feb 6 16:35:56 2016 [error] failed loading authreg > module 'mysql' (File not found) Segmentation fault (core dumped) > > The /usr/local/lib/jabberd does not exist. > > The sm module fails as follows: > # /usr/local/libexec/jabberd/sm -D > /usr/local/libexec/jabberd/sm: error: `/usr/local/libexec/jabberd/.libs/sm' > does not exist. > > As the error states, the directory does not exist. > > > -----Original Message----- > From: Michael McConville [mailto:mm...@mykolab.com] > Sent: Tuesday, February 2, 2016 11:49 AM > To: Stephen Graf <s_g...@telus.net> > Subject: Re: jabberd out of date > > Stephen Graf wrote: > > I'll give it a shot. It looks like the repository of the code has > > changed. > > Nice! Be sure to use the current CVS repo and to test on -current. >
jabberd-test.tar.gz
Description: GNU Zip compressed data
