please unsubscribe me...
please do the needful...
On Fri, May 13, 2016 at 5:19 PM, SimuAWIPS <simuawips@xxxxxxxxxxxxx> wrote:
> You will need to fix these files by adding the line in my note below, and
> recompiling:
>
> FIX BROKEN DECODERS
>
> ----------------------------------------------------------------------------------
>
> https://gcc.gnu.org/onlinedocs/gfortran/Read_002fWrite-after-EOF-marker.html
> http://www.unidata.ucar.edu/software/gempak/tutorial/runtime_errors.html
>
>
> At line 74 of file wnout.f (unit = 11, file =
> '/home/gempak/data/warn/2015052902_warn.gem')
> Fortran runtime error: Sequential READ or WRITE not allowed after EOF
> marker, possibly use REWIND or BACKSPACE
>
> vi /home/gempak/GEMPAK7/gempak/source/bridge/sv/svout.f
> vi /home/gempak/GEMPAK7/gempak/source/bridge/nc/ncout.f
> vi /home/gempak/GEMPAK7/gempak/source/bridge/is/isout.f
> vi /home/gempak/GEMPAK7/gempak/source/bridge/hc/hcout.f
> vi /home/gempak/GEMPAK7/gempak/source/bridge/cs/csout.f
> vi /home/gempak/GEMPAK7/gempak/source/bridge/am/amout.f
> vi /home/gempak/GEMPAK7/gempak/source/bridge/wp/wpout.f
> vi /home/gempak/GEMPAK7/gempak/source/bridge/ws/wsout.f
> vi /home/gempak/GEMPAK7/gempak/source/bridge/fa/faout.f
> vi /home/gempak/GEMPAK7/gempak/source/bridge/ww/wwout.f
> vi /home/gempak/GEMPAK7/gempak/source/bridge/wo/woout.f
> vi /home/gempak/GEMPAK7/gempak/source/bridge/wc/wcout.f
> vi /home/gempak/GEMPAK7/gempak/source/bridge/wn/wnout.f
>
> -AJO
>
> SimuAWIPS Lead Developer
> The Oldaker Group, LLC
> Facebook - Twitter - Latest News Updates
>
>
>
>
>
> -----Original Message-----
> From: gembud-bounces@xxxxxxxxxxxxxxxx [mailto:
> gembud-bounces@xxxxxxxxxxxxxxxx] On Behalf Of
> gembud-request@xxxxxxxxxxxxxxxx
> Sent: Thursday, May 12, 2016 13:00
> To: gembud@xxxxxxxxxxxxxxxx
> Subject: gembud Digest, Vol 86, Issue 4
>
> Send gembud mailing list submissions to
> gembud@xxxxxxxxxxxxxxxx
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mailman.unidata.ucar.edu/mailman/listinfo/gembud
> or, via email, send a message with subject or body 'help' to
> gembud-request@xxxxxxxxxxxxxxxx
>
> You can reach the person managing the list at
> gembud-owner@xxxxxxxxxxxxxxxx
>
> When replying, please edit your Subject line so it is more specific than
> "Re: Contents of gembud digest..."
>
>
> Today's Topics:
>
> 1. Re: GEMPAK 7.2.3 on CentOS 7 with gcc-gfortran 4.8.5
> (Ryan Hickman)
> 2. libmotif4/libxm4 dependency conflict (Kevin Lux)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 11 May 2016 15:27:40 -0600
> From: Ryan Hickman <ryan@xxxxxxxxxxxxxxxx>
> To: gembud@xxxxxxxxxxxxxxxx
> Cc: support-gempak@xxxxxxxxxxxxxxxx
> Subject: Re: [gembud] GEMPAK 7.2.3 on CentOS 7 with gcc-gfortran 4.8.5
> Message-ID:
> <
> CANTuNuMOyEnru2-r9cXjXNBp46rLzTOJRSc35rYYJy4iFk9NPA@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="utf-8"
>
> GEMPAK 7.3.0 has not fixed the issues I am having related to `dcwou` on
> CentOS 7.
>
> I've tried both with and without the "-fno-whole-file" modification
> recommended at http://www.unidata.ucar.edu/software/gempak
> /tutorial/runtime_errors.html. It appears that option is only included by
> default in the Fedora version of the Makeinc configuration.
> ("$NAWIPS/config/Makeinc.linux64_gfortran_fedora") Neither the default nor
> "-fno-whole-file" approach seems to work.
>
> Fortran compiler remains 4.8.5-4, the default offered by the stable
> repository. No G77 on CentOS 7, as far as I know.
>
> One noticeable difference with 7.3.0 vs. 7.2.3 is that there are no longer
> any errors related to "sleep.h".
>
>
>
> On Wed, Mar 16, 2016 at 10:15 AM, Ryan Hickman <ryan@xxxxxxxxxxxxxxxx>
> wrote:
>
> > We've been running Gempak on CentOS 6 without issue for many years. We
> recently rebuilt our entire infrastructure and made the decision to move
> forward with CentOS 7. Now I'm beginning to see issues related to decoding
> watch outlines (`dcwou`) and seemingly any other function which
> reads/writes in a similar manner.
> >
> > [ldm@ldm-central1-b root]$ cat /data/gempak/storm/wou/1.wous |
> > /home/gempak/NAWIPS/os/linux64/bin/dcwou -e
> > GEMTBL=/home/gempak/NAWIPS/gempak/tables /data/gempak/storm/wou/1.wou
> >>
> >> At line 96 of file woout.f (unit = 11, file =
> >> '/data/gempak/storm/wou/1.wou')
> >>
> >> Fortran runtime error: Sequential READ or WRITE not allowed after EOF
> >> marker, possibly use REWIND or BACKSPACE
> >>
> > The file 1.wou is created but is 0 bytes.
> >
> > I've seen the instructions at
> http://www.unidata.ucar.edu/software/gempak/tutorial/runtime_errors.html
> for modifications to $NAWIPS/config/Makeinc.linux64_gfortran but these have
> made no difference, even when doing a fresh installation.
> >
> > I've also observed a fatal error at the completion of `make all` which
> references sleep.h. The file exists at $NAWIPS/gempak/include/sleep.h.
> >
> > In file included from vgf2xml.c:2:0:
> >>
> >> gemprm.h:173:79: fatal error: sleep.h: No such file or directory
> >>
> >> #include <sleep.h> /* added for U. Albany mod for semaphore in
> >> message queue*/
> >>
> > [gempak@ldm-central1-b ~]$ ls -al $NAWIPS/gempak/include/sleep.h
> >
> > -rw-r--r-- 1 gempak users 482 Mar 11 23:03
> > /home/gempak/NAWIPS/gempak/include/sleep.h
> > The output of `gfortran -v`
> >
> > Using built-in specs.
> >> COLLECT_GCC=gfortran
> >> COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/4.8.5/lto-wr
> >> apper
> >> Target: x86_64-redhat-linux
> >> Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
> >> --infodir=/usr/share/info
> >> --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap
> >> --enable-shared --enable-threads=posix --enable-checking=release
> >> --with-system-zlib --enable-__cxa_atexit
> >> --disable-libunwind-exceptions --enable-gnu-unique-object
> >> --enable-linker-build-id --with-linker-hash-style=gnu
> >> --enable-languages=c,c++,objc,obj-c++,java,fortran,ada,go,lto
> >> --enable-plugin --enable-initfini-array --disable-libgcj
> >> --with-isl=/builddir/build/BUILD/gcc-4.8.5-20150702/obj-x86_64-redhat
> >> -linux/isl-install
> >> --with-cloog=/builddir/build/BUILD/gcc-4.8.5-20150702/obj-x86_64-redh
> >> at-linux/cloog-install --enable-gnu-indirect-function
> >> --with-tune=generic --with-arch_32=x86-64 --build=x86_64-redhat-linux
> >> Thread model: posix gcc version 4.8.5 20150623 (Red Hat 4.8.5-4)
> >> (GCC)
> >
> >
> > I've attached the make.out log output from `make all`.
> >
> > Any ideas are welcome and appreciated.
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://mailman.unidata.ucar.edu/mailing_lists/archives/gembud/attachments/20160511/fc8bdae6/attachment.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Thu, 12 May 2016 12:26:39 -0500
> From: Kevin Lux <stormpilgrim@xxxxxxxxx>
> To: gembud@xxxxxxxxxxxxxxxx
> Subject: [gembud] libmotif4/libxm4 dependency conflict
> Message-ID:
> <
> CA+Xcn34EO0iW198gcnSC9YQkUUP0C8e+W4PFzPuxGvFf3ZrLoQ@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="utf-8"
>
> I just built a brand-spanking-new Ubuntu 16.04 partition and downloaded
> the GEMPAK 7.2 debian package. I had to install the OpenMotif libraries,
> which was no big deal, but when I go to install gempak, it errors out and
> says I need libxm4. Okay, no problem. However, when I go to install libxm4,
> Synaptic removes libmotif4. If I have libxm4 installed and go to install
> libmotif4, Synaptic removes libxm4! I can't win. What is it about these two
> packages that make them not get along? Can I do a shotgun wedding somehow?
>
> Kevin
>
> ----
> Shoot for the moon--at least if you miss, you'll end up among the stars.
> And there you'll remain. A frozen corpse floating in space for eternity.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://mailman.unidata.ucar.edu/mailing_lists/archives/gembud/attachments/20160512/86961f77/attachment.html
> >
>
> ------------------------------
>
> _______________________________________________
> NOTE: All exchanges posted to Unidata maintained email lists are recorded
> in the Unidata inquiry tracking system and made publicly available through
> the web. Users who post to any of the lists we maintain are reminded to
> remove any personal information that they do not to be made public.
>
>
> gembud mailing list
> gembud@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe, visit:
> http://www.unidata.ucar.edu/mailing_lists/
>
> End of gembud Digest, Vol 86, Issue 4
> *************************************
>
> _______________________________________________
> NOTE: All exchanges posted to Unidata maintained email lists are
> recorded in the Unidata inquiry tracking system and made publicly
> available through the web. Users who post to any of the lists we
> maintain are reminded to remove any personal information that they
> do not want to be made public.
>
>
> gembud mailing list
> gembud@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe, visit:
> http://www.unidata.ucar.edu/mailing_lists/
>
