In bug #130895 the swi-prolog install failed in src_install. See attached log for the src_install output. This output raises two issues: 1) the swi-prolog ebuild does not honour $libdir, thus breaking multilib-strict compliance. I've committed a patch to honour /usr/$libdir, rather than /usr/lib. Can the amd64 team please test in order to see if swi-prolog is now multilib-strict compliant. 2) the output shows a perplexing sequence of events, summarized as: run 'make -C src install': mkdir -p $(DESTDIR)/usr/lib64/pl-5.6.8/include run 'make -C packages install': install SWI-cpp.h $(DESTDIR)/usr/lib/pl-5.6.8/include mkdir -p $(DESTDIR)/usr/lib/pl-5.6.8/include The second call to mkdir is failing as $(DESTDIR)/usr/lib/pl-5.6.8/include is a file created by the 'install' command. This is somewhat confusing as the first call to mkdir (from src/Makefile) is defined by: mkdir -p $(DESTDIR)$(PLBASE) and $PLBASE is defined as: PLBASE=$(prefix)/lib/pl-5.6.8 But the install log is showing PLBASE expanded to $(prefix)/lib64/pl-5.6.8 instead. The ebuild does not override PLBASE when calling 'make install' and it does not call 'make -e install', so we don't have errant environment variables sneaking into the build. Can the amd64 arch team please attempt to install swi-prolog-5.6.8 *without* swi-prolog-PLBASE.patch being applied in order to see if the output in the install log is reproduceable.
Created attachment 88398 [details] src_install.log
This bug is fixed with application of swi-prolog-PLBASE.patch. Closing.
