Re: [Fink-users] [EXTERNAL] python27build error

[Luigi E. Z. <Lui...@mi...>]

On 31/05/2020 15:55, Derek Homeier wrote:
> Dear Jianxin and Luigi,
>
> thanks for your further reports.
>
>> On 31 May 2020, at 12:09 pm, Luigi Ernesto Zanotti <lui...@mi...> wrote:
>>
>> disappearance of 'readline' from the 'Failed to build these modules: 'list.
>> I assume that the list of the log file provided by Jianxin to Derek will be the same (if required, I'll go for it).
>> There is also another point that I don't understand; the issue under examination is going on on my iMac, that I couldn't use for a couple of months (lock-down effect); on the contrary, on my MacbookAir, which has a Fink installation that should be 'almost' the same as on iMac, the update to python27_2.7.18-1 went smoothly on May 6, with quite different .info and .patch files; so what changed going to python27_2.7.18-2? As for now, I didn't get any notification for an update to python27_2.7.18-2 on my MacbookAir.
> You have not got a notification on the update as it is not merged yet, so the only way to test it ahead of
> merging is to manually get the files as described earlier by Hanspeter:
>
>> Can you go to <https://github.com/fink/fink-distributions/pull/540/>
>> and download these two files:
>>
>> https://raw.githubusercontent.com/fink/fink-distributions/159d62662c0d6351ca75ed47124a541889f2dfdb/10.9-libcxx/stable/main/finkinfo/languages/python27.info
>>
>> https://raw.githubusercontent.com/fink/fink-distributions/159d62662c0d6351ca75ed47124a541889f2dfdb/10.9-libcxx/stable/main/finkinfo/languages/python27.patch
>>
>> and save them to /sw/fink/dists/local/main/finkinfo/languages (make the directory if not present)https://github.com/fink/fink-distributions/raw/159d62662c0d6351ca75ed47124a541889f2dfdb/10.9-libcxx/stable/main/finkinfo/languages/python27.info
> But in any case this does not seem to resolve the second build error.
>
> Did I understand that on that iMac building the same original python27_2.7.18-1 succeeded on 10.14 without
> any errors with either readline or _scproxy? That makes things even more confusing, but it would reflect
> Hanspeter’s results described in
> https://github.com/fink/fink-distributions/issues/624#issuecomment-629419708
>
> Not sure how to proceed with such inconsistent behaviour, and searching the web for information related
> to the _scproxy error brings up somewhat contradictory results as well. It looks like this may require a
> fix to the compiler itself.
>
> Cheers,
> 					Derek
Derek,
just to make the history clearer:

- both computers are with OS 10.14.5, Xcode and CLT 11.3.1
- python27_2.7.18-1 built on MacbookAir on May 6, starting from a 
previous version that I don't know, without any error, but no attempt 
has been made so far to go up to python27_2.7.18-2.

- iMac was all the time, during lock-down with python27_2.7.17-1, and 
only after May 25, out of lock-down, I could work on it and I was asked 
to update to python27_2.7.17-2, with failure reported in my first mail. 
After Hanspeter's suggestions the build failed again, but in this case 
'readline' disappeared from the 'Failed to build these modules: ' list. 
Cheers to you too, Luigi


-- 
Prof. Luigi Ernesto Zanotti (retired)

Physics Department "G. Occhialini"
University of Milano Bicocca

Piazza della Scienza 3. 20126 Milano Italy
E-Mail: lui...@mi...