I have not attempted this build yet, however.... The report-gnome.go file appears to be a build file, not a system file. You are encountering a processing error for the .scm file, which results in a build file not getting generated. Later on the build system goes back and cannot find file that it failed to generate. This is why your google search returns nothing, its a temp build file.
Which version of guile is installed, and compare to packages.slackware.com. Apologies in advance, gmail app on android sucks -Ben On Aug 31, 2017 5:04 PM, "Rich Shepard" <rshep...@appl-ecosys.com> wrote: On Thu, 31 Aug 2017, Tomas Kuchta wrote: > You can pass additional search path to ./configure on the command line see > help/comments inside ./configure to see what options. Or run ./configure > --help Tom, First I need to figure out what search path is being used. My current approach is building 2.6.17 on the 32-bit Dell Latitude 2100, re-directing stdout and stderr to the build.log file. Then I'll run 'diff -y <good-file> <failed-file>' and see where they differ. This should tell me what's different between a system that upgraded from 14.1 to 14.2 and a system with 14.2 installed on a new disk. Thanks, Rich _______________________________________________ PLUG mailing list PLUG@lists.pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug _______________________________________________ PLUG mailing list PLUG@lists.pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
