[quoted lines by Gwyn Ciesla on 2017/06/16 at 12:29 -0500] >I'm unsure why those differ.
But that may be at least part of the answer to the puzzle. Someone specifically made that change to the spec file, so there must be a reason why, and, of course, it could be (maybe just partially) wrong. What I'd do is insert the invocation of an interactive shell into the build, just before the actual install, and have a look at what has actually been built. >What I do see is that the configure script doesn't pick up the PYTHON* env >variables the way it does for python 2.7. It should, since the code is the very same. This one may be a precedence issue. It looks to me like you're setting it as a configure or make argument. In that case I'd expect it to have a lower precedence than an actual environment setting. In other words, if the environment already contains a setting then overriding it with a make argument won't change it. -- Dave Mielke | 2213 Fox Crescent | http://Mielke.cc/ Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/ EMail: [email protected] | Canada K2A 1H7 | The Bible is the very Word of God. _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [email protected] For general information, go to: http://brltty.com/mailman/listinfo/brltty
