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

[LDM #INT-687165]: LDM 6.13.17 will not compile under Ubuntu 22.0.4



Gilbert - took me a bit . . . and apologize for the support-in-stereo . . . but 
I have a fix for you for the time being.

In addition to the fix Steve gave you, I need you edit the file in the noaaport 
directory called "blender.c".  Line #3, which should look like:

#include "queueManager.h"

Comment that out so that it looks like:

//#include "queueManager.h"

Save, and then go at your "make install" again from the top src directory.  I 
got that to work and finish the compile and install.

Let us know if you hit upon any other snags.

Stonie

>> in reply to >>
Hi Steve,

Ha! No, you're fine. I'm crazy...

But, despite the workaround, I now get this:

libtool: link: g++ -std=c++11 -g -O2 -o .libs/blender blender.o dynabuf.o 
gini.o grib2name.o ldmProductQueue.o png_io.o process_prod.o readpdb.o 
readpdh.o readpsh.o readsbn.o redbook_header.o wgrib.o wmo_header.o 
frameWriter.o queueManager.o frameReader.o CircFrameBuf.o misc.o NbsHeaders.o 
NbsFrame2.o ../lib/.libs/libldm.so -lxml2 -lpng -lz -lm -Wl,-rpath 
-Wl,/home/ldm/ldm-6.13.17/lib
/usr/bin/ld: 
queueManager.o:/home/ldm/ldm-6.13.17/src/noaaport/queueManager.h:15: multiple 
definition of `flowDirectorThread'; 
blender.o:/home/ldm/ldm-6.13.17/src/noaaport/queueManager.h:15: first defined 
here
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:700: blender] Error 1
make[2]: Leaving directory '/home/ldm/ldm-6.13.17/src/noaaport'
make[1]: *** [Makefile:954: install] Error 2
make[1]: Leaving directory '/home/ldm/ldm-6.13.17/src/noaaport'
make: *** [Makefile:675: install-recursive] Error 1

Ticket Details
===================
Ticket ID: INT-687165
Department: Support LDM
Priority: Normal
Status: Open
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.