Re: error running viewml binary

This probably isn't a problem with not running ldconfig. Usually, not running 
this will cause missing lib errors and won't even load.

Looking at the original problem, this could also be a mismatch between two 
different versions of Microwindows, where the structures have changed. I 
don't know that they have, but is another possible problem.

Hope this helps,
Jason Kingan
Century Software

On Thursday 06 February 2003 10:11 pm, you wrote:
> This is the viewml binary that I've downloaded from the site.  I copied the
> libraries to /usr/lib.  I forgot, though, to run the $ldconfig command.  Do
> you think this error has something to do with it ?  But I'm not familiar
> with ldconfig and I'm afraid that it might damage the system.  Do you also
> know where can I get a binary for arm of ldconfig ?  Or its source ?
> Thanks.
>
> Mildred
>
>
>             From: "Greg Haerr" <[email protected]>
>             Subject: Re: error running viewml binary
>             Date: Wed, 5 Feb 2003 22:13:39 -0700
>             To: "ViewML development list" <[email protected]>
>
>
>       Usually this means that the threading package isn't working properly.
>       Be sure to recompile everything from scratch.
>
>       Regards,
>
>       Greg
>         ----- Original Message -----
>         From: Mildred Frisco
>         To: ViewML development list
>         Sent: Wednesday, February 05, 2003 7:42 PM
>         Subject: error running viewml binary
>
>
>
>
>         Hi !  I've tried to run the viewml on the strongarm platform with
> embedded linux.  The platform already has nano-X running.  I've copied the
> shared libraries to /usr/lib and created the file
> /home/jasonk/projects/arm/microwin/src/bin/nano-X, since the program was
> looking for it when I first tried to run it.  then i typed the following
> commands
>
>         $ nano-X &
>         $ viewml
>
>         viewml produced the following errors:
>
>         Client 153: wrong packet type 0 (expected 3)
>         Client 153: wrong packet type 240 (expected 3)
>         Client 153: wrong packet type 1 (expected 3)
>         Client 153: wrong packet type -2048 (expected 3)
>         .
>         .
>         .
>         Client 153: wrong packet type 2016 (expected 3)
>         Client 153: wrong packet type 31 (expected 3)
>         .
>         .
>         .
>
>
>         Please reply if you know this.
>
>         Thank you very much
>
>
>         mildred

#############################################################
This message is sent to you because you are subscribed to
  the mailing list <[email protected]>.
To unsubscribe, E-mail to: <[email protected]>
To switch to the DIGEST mode, E-mail to <[email protected]>
To switch to the INDEX mode, E-mail to <[email protected]>
Send administrative queries to  <[email protected]>