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

[LDM #TRV-570314]: ldm-6.13.4/noaaport/Makefile.am



Richard,

Obscure errors! Thanks for sending them in.

They'll be fixed in the next release.

> I came across an automake issue with
> ldm-6.13.4/noaaport/Makefile.am
> 
> When I run autoreconf -fiv, they come up at
> lines 266, 189, 323, and 300.
> 
> Now it seems the problem at line 300
> 
> LDM_REGISTRY_DIR=../regutil $(LIBTOOL) --mode=execute valgrind \
> 
> and line 323
> 
> LDM_REGISTRY_DIR=../regutil $(LIBTOOL) --mode=execute gdb -x \
> 
> is that these are supposed to be the beginnings of
> make rules but someone mistakenly started these
> lines with 8 spaces instead of a tab.
> 
> In the case of the target definitions on
> line 266 and 189, it has to do with the fact
> that automake will not take the same target
> in an if block that is defined outside of
> any if block.  For example, while
> 
> if ENABLED_TARGET2
> all: one two
> else
> all: one
> endif
> 
> is all right,
> 
> all: one
> if ENABLED_TARGET2
> all: one two
> endif
> 
> might not run through autoconf/automake or if
> it does process through that, you might not get
> the behavior you think.
> 
> The problem is that at line 266
> 
> check-local:                  check-nbs_test
> 
> is within an an automake if block and at line 189
> 
> check-local:            check-readnoaaport check-noaaportIngester \
> check-noaaportIngester-nssl
> 
> is outside of a an automake if block.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: TRV-570314
Department: Support LDM
Priority: Normal
Status: Closed
===================
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.



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.