On 5/2/19 2:12 PM, Darshit Shah wrote: > * Tim Rühsen <[email protected]> [190502 10:21]: >> On 5/2/19 10:02 AM, Jeffrey Walton wrote: >>> On Thu, May 2, 2019 at 4:00 AM Tim Rühsen <[email protected]> wrote: >>>> >>>> Hi Jeff, >>>> >>>> On 5/1/19 11:38 PM, Jeffrey Walton wrote: >>>>> On Wed, May 1, 2019 at 3:51 PM Tim Rühsen <[email protected]> wrote: >>>>>> >>>>>> could you post e.g. the content of tests/Test-504.log ? >>>>> >>>>> Yes, attached. >>>>> >>>>> Do you want an account on the box. I keep it around for testing, and I >>>>> can make you admin. You can connect to it with 'ssh >>>>> [email protected]'. If so, send over your authorized_keys. >>>> >>>> thanks for the offer, but this issue is not Solaris specific. >>>> But if the need arises, I have access to the OpenCSW Solaris boxes :-) >>>> >>>> Please check README.checkout which lists python3 as requirement for >>>> running the tests in testenv/ (as Darshit also pointed out). >>> >>> Ack, thanks. >>> >>> Since I got you on the line, how do I disable them. There is no need >>> to run them if all they are going to do is fail. I did not see a >>> configure option. >> >> Maybe the easiest way is before you bootstrap / autoconf (in the project >> main dir): >> >> sed -i 's/ testenv//g' Makefile.am >> >> Regards, Tim >> > > The easiest way right now would be to install Python3. If that is not > possible, > the easiest workaround is as Tim suggested. > > However, this _is_ a bug. Since if you see testenv/Makefile.am, we have a > `HAVE_PYTHON3` conditional block. And configure also checks for it. > > This is why I am interested in seeing the contents of your config.log file. I > would like to see what went wrong causing configure to believe that you indeed > have Python3 installed.
Darshit, just temporarily rename your python3 binary to reproduce the issue. It's really not a Solaris issue. Regards, Tim
signature.asc
Description: OpenPGP digital signature
