On Wednesday 3 October 2018 14:03, Rich Shepard <rshep...@appl-ecosys.com> put forth the proposition: > On Wed, 3 Oct 2018, David Woodfall wrote: > > > Could you please make a build log and attach it to a reply here? > > Dave, > > An xzipped build log is attached. I'm really interested in learning what > insights are hidden from me in the log. > > Thanks, > > Rich
After doing some building and diffing what sticks out is that in your log make is including /usr/lib/glib-2.0/include/glibconfig.h Whereas my log shows /usr/lib64/glib-2.0/include/glibconfig.h This is also on a 14.2 multilib system. Can you test the following change in the slackbuild just after the CFLAGS= and CXXFLAGS= lines add: GLIB_CFLAGS="-I/usr/lib$LIBDIRSUFFIX/glib-2.0/include" \ If that doesn't work you could try exporting the variable and remove the '\' on the end. It's a bit of a long shot but it may help. Something in your environment seems to be causing the build process to think it's not x86_64 for some reason. As others have said, you may want to think about building packages in a non-multilib VM when this kind of thing happens. I tend to use a chrooted installation for this because it takes no extra software and you don't need to boot anything to use it either. -- Dave "I'm not under the alkafluence of inkahol that some thinkle peep I am. It's just the drunker I sit here the longer I get." .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~'
signature.asc
Description: PGP signature
_______________________________________________ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/