These files have a .hash section even when my LDFLAGS tell the linker not to generate it:
Upstream? Or can it be fixed in the ebuild?
That depends on the build system. Usually, a patch to the build system is required, as in this case. Looking at src/gapcmon/Makefile.in, the link rule for gapcmon is:
$(LD) -o $@ $(gapcmon_OBJS) @GAPCMON_LIBS@ -lX11 -lXext $(X_LIBS) $(X_EXTRA_LIBS)
The fix should be to add $(LDFLAGS) right after $(LD). Do not be misled by the use of $(LD) as the variable name. Based on the configure script, $(LD) is usually set to gcc. It might be different on a non-Linux system.
Taking over. Michael you let this package rot so much, since I need it, I'm going to take it over and take care.
Please don't say I didn't give you enough notice, last year I already asked you this much and now I'm simply tired.
Upstream's new buildsystem is fun. Why people reinvent the wheel? :(
The only version of sys-power/apcupsd I see in the tree right now is 3.14.7, and its Makefile appears to honor LDFLAGS for gapcmon now.
Looks like fixed to me...
Both version in tree (3.14.7 3.14.8) respect LDFLAGS. Closing...