[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20010304: can't print in nsharp (5.6a or 5.4)

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20010304: can't print in nsharp (5.6a or 5.4)
  • Date: Sun, 04 Mar 2001 18:08:48 -0700
Robert,

The printing section was re-written to use all the routines within nxmlib
and the$GEMTBL/config/printers.tbl configuration.

To build properly, the nxmlib must be copied in the makefile to local_Nxmlib.a
and one routine must be reoved so that the nsharp routine is used instead of the
GEMPAK routine. If something isn't correct, your link would be fining the wrong
routine.

cd $NAWIPS/unidata/programs/nsharp/source
make clean

verify that the local_Nxmlib.a routine has been removed.

Then attempt the build with "make all".

Note any error messages,

Steve Chiswell
Unidata User Support




>From: 10 <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200103041925.f24JPxL12915

>I am unable to print in NSHARP with either 5.4 or 5.6a.  I do not
>see an nsharp_spool file in the GEMPAK5.6 dist so I copied the
>one from 5.4.  NSHARP crashes when you select print.  I ran
>NSHARP under 5.4 (Solaris 7 Sparc) under dbx and got the following
>when I tried to print:
>
>Running: nsharp 
>(process id 5644)
>signal SEGV (no mapping at the fault address) in strrchr at 0xfedd0700
>0xfedd0700: strrchr+0x0010:     ldsb    [%g1], %o4
>(/opt/SUNWspro/bin/../WS5.0/bin/sparcv9/dbx) 
>
>I applied the latest nsharp.tar.Z that was mentioned in a previous
>support question before doing this.  I get basically the same error
>under 5.6a on Solaris 8 Sparc.
>
>Any ideas?  I do not understand what the output is telling me.
>I do not even get a print pop-up box.
>
>Thanks,
>Robert Mullenax
>