Jan. 5th, 2017

sawyl: (A self portrait)
Another intriguing Darshan gotcha, this time related to file locations and packaging problems. Trying to bundle the software up into an RPM, I encountered continual problems with one of the pkg-config config files not being recognised by the package, despite appearing the the RPM spec file manifest.

After a certain amount of bafflement, I noticed the problem file wasn't being installed in the correct location within the RPM build-root; instead it was being installed in a subdirectory of the build-root whose structure doubled the build-root tree.

Examining the Makefile.am more closely, I quickly located the source of the problem:

bindir = $(DESTDIR)@bindir@
libdir = $(DESTDIR)@libdir@
pkgconfigdir = $(DESTDIR)$(libdir)/pkgconfig

Since $(DESTDIR), which is set to the build-root by RPM, has been added to the path of the libdir macro, including it for a second time in the pkgconfigdir macro has the effect of duplicating the build-root hierarchy, causing the manifest match to fail.

Fortunately all it took was a quick patch to snip out the extra reference, and everything built as expected — it's just annoying it took me as long as it did to notice the problem...

Profile

sawyl: (Default)
sawyl

September 2017

S M T W T F S
      1 2
3 456 78 9
10111213141516
17181920212223
24252627282930

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Sep. 26th, 2017 02:33 pm
Powered by Dreamwidth Studios