[JDEV] Jabber server on HPUX

Thu Nov 29 10:39:35 CST 2001

Hi Rick,

Oh yeah - forgot about that problem.
I was not able to build a jabberd process on HPUX
which loads the shared libraries dynamically.
The solution I used was to build a static binary.

So, in your jabber-1.4.1 directory, just type:

make static

which builds a static version and should fix this problem

james

Logica Mobile Networks,
Dublin, Ireland

-----Original Message-----
From: Rick Hickerson [mailto:richard_hickerson at agilent.com]
Sent: Thursday, November 29, 2001 3:45 PM
To: jdev at jabber.org
Subject: Re: [JDEV] Jabber server on HPUX

Many thanks, James.

Now I'm to the point where, at runtime, I'm getting an unresolved on
"debug_flag".  It's exactly the same as Vladimirr reported (see
http://mailman.jabber.org/pipermail/jdev/2000-December/004259.html ) last
December. 

To which there was apparently no reply.

Here's the output of jabberd:

Executing jsm() in ./jsm/jsm.so failed: 'Unresolved module for symbol:
debug_flag (data)  from ./jsm/jsm.so'

(there's also a reference to an "Invalid Configuration in instance
'sessions'",
but I'm guessing that the unresolved debug_flag is causing the abort, and
the
latter is a byproduct.)

To assist those who follow, here's the totality of what I've done thus far:

On my first `make` attempt I was getting unresolved messages for "dlopen"
and
"dlsym".  Installing HPUX patch PHSS_24303 fixed that, with a new libdld.sl
which includes those symbols.

Then, `make` gave an unresolved on "modf" the same as Seeniraj encountered
(see
http://mailman.jabber.org/pipermail/jdev/2001-September/008409.html ).  I
departed slightly from Seeniraj's solution by editing the platform-settings
file
and appending " -lm" to LIBS.  I then got to the same point as Seeniraj,
with
the jabberd running, not opening port 5222, and taking 100% of one of the
CPUs. 

James' fix below got me part way past this, but after running the pth
`configure`, `make`, and `make install`, the `make` of jabber gave another
unresolved on "__builtin_va_start.  A Google search turned up this note from
Russ Allbery ( 
http://mail.gnu.org/pipermail/autoconf/2001-August/011460.html ):
"... it means that gcc is picking up the system headers rather than its
own fixed headers.  The most common cause of this problem is that the
package is including -I/usr/include in the compiler flags; the second most
common cause is that the fixincludes process got botched somehow."

So I edited platform-settings again, and removed "-I/usr/include" from
CFLAGS. 
`make` now completes, but jabberd exits as indicated at the top of this
message.

I should note that I'm not a developer, just a poor schmuck trying to get
jabber
running on my company's standard *nix platform.  So I don't know much about
compiler and linker flags and such.  I've gotten other packages going on
HP-UX,
such as apache with php interfaced to the Oracle oci8, but they weren't
easy,
either.

Rick

"Brennan, James" wrote:
> 
> Hi Rick,
> 
> Yes - that's exactly what I experienced!
> 
> Although, as you say, pth compiles fine, it's actually
> the get/set/swapcontext() methods that it uses.
> 
> I found that pth just stopped 'switching' to other threads,
> grinds to a halt, takes up 100%cpu and doesn't get to spawn
> the other jabber process.
> 
> I traced it down to get/set/swapcontext() in the pth.
> You can force pth to use sigsetjmp/siglongjump instead
> and the way you do this is with the ./configure switches
> that I describe in my email at the end.
> 
> james
> 
> Logica Mobile Networks,
> Dublin, Ireland.
> 
> -----Original Message-----
> From: Rick Hickerson [mailto:richard_hickerson at agilent.com]
> Sent: Wednesday, November 28, 2001 7:51 PM
> To: jdev at jabber.org
> Subject: Re: [JDEV] Jabber server on HPUX
> 
> I get it compiled OK with pth-1.4.0, and can execute:
> ./jabberd/jabberd -D -h <my.fully.qualified.hostname>
> 
> But there everything stops. `top` shows jabberd as using 100% of one of
the
> CPUs, and any attempt to connect to port 5222 is refused.
> 
> When running in the foreground, one message comes to the console:
> Wed Nov 28 13:32:59 2001  mio.c:568 MIO is starting up
> 
> It doesn't respond to <ctrl>-c.  I have to login another session and `kill
> -9`
> to shut it down.
> 
> Rick
> 
> "Brennan, James" wrote:
> >
> > I think this is the same problem that I had.
> > The problem is the pth component which jabber uses.
> > This is the thread component part.
> >
> > You will find this component in the directory:
> > jabberd/pth-1.3.7  (I use pth-1.4.0 but this should not matter)
> >
> > You need to enter this directory and run configure with
> > the following flags:
> >
> > ./configure --with-mctx-mth=sjlj --with-mctx-dsp=sjlj
--with-mctx-stk=sas
> >
> > You then need to build the pth component.
> > Just run make in the pth-1.3.7 directory.
> >
> > Then go back out to the jabber directory and make the system.
> >
> > Get in touch with me if this doesn't make sense or work.
> >
> > james
> 
> This e-mail and any attachment is for authorised use by the intended
recipient(s) only.  It may contain proprietary material, confidential
information and/or be subject to legal privilege.  It should not be copied,
disclosed to, retained or used by, any other party.  If you are not an
intended recipient then please promptly delete this e-mail and any
attachment and all copies and inform the sender.  Thank you.
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev

-- 
Rick Hickerson        T+1(978)681-2449     Agilent Technologies
Master IT Engineer     +1(646)452-7668     IT | Information Technology
40 Shattuck Road       +1(877)868-9829
Andover, MA  01810
_______________________________________________
jdev mailing list
jdev at jabber.org
http://mailman.jabber.org/listinfo/jdev

This e-mail and any attachment is for authorised use by the intended recipient(s) only.  It may contain proprietary material, confidential information and/or be subject to legal privilege.  It should not be copied, disclosed to, retained or used by, any other party.  If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender.  Thank you.