Solved: Problems with nut and python build / fink

Bernhard Heinz <[email protected]>
Newsgroups gmane.os.apple.fink.beginners
Organization (priv)
Message-ID <[email protected]>
Hi Hans-Peter,

your python fix worked great, thanks for your quick response

Bernhard

Am 09.06.20 um 02:22 schrieb Hanspeter Niederstrasser:
> On 2020-06-08 16:16, Bernhard Heinz wrote:
>> Hi there,
>>
>> I am getting the follwing error trying to build nut on my Mac OS
>> 10.14.6 Mac mini (End 2014).
>> Same also happens when I build python.
>> I ran fink selfupdate, updated packages, reduced number of build jobs
>> to 1 and looked in FAQ - no match.
>> Please help.
>>
>> Thanks and greetings from Germany
>> Bernhard
>>
>> Bernhard HEINZ
>> Germany
>>
>> Mobile:+49 (0) 171-420-6621
>> Email:[email protected]
>>
>> FaceTime:[email protected]
>> Skype:b.a.heinz
>> Facebook:http://facebook.com/bernhard.a.heinz
>> _______________________________________
>> Von meinem Mac Mini gesendet
>>
>> Extract from log starting with last gcc (Full Logfiles of nut and
>> python build attached):
>>
>> gcc -L/opt/sw/lib -bundle
>> /opt/sw/src/fink.build/python27-2.7.18-1/Python-2.7.18/libpython2.7.dylib 
>>
>> -L/opt/sw/lib -L/opt/sw/lib -fno-strict-aliasing
>> -Wno-nullability-completeness -DNDEBUG -g -fwrapv -fwrapv -O3 -Wall
>> -Wstrict-prototypes -I. -IInclude -I./Include -I/opt/sw/include
>> -I/opt/sw/include/ncursesw
>> -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/usr/include 
>>
>> build/temp.macosx-10.14-x86_64-2.7/opt/sw/src/fink.build/python27-2.7.18-1/Python-2.7.18/Modules/_ctypes/_ctypes.o 
>>
>> build/temp.macosx-10.14-x86_64-2.7/opt/sw/src/fink.build/python27-2.7.18-1/Python-2.7.18/Modules/_ctypes/callbacks.o 
>>
>> build/temp.macosx-10.14-x86_64-2.7/opt/sw/src/fink.build/python27-2.7.18-1/Python-2.7.18/Modules/_ctypes/callproc.o 
>>
>> build/temp.macosx-10.14-x86_64-2.7/opt/sw/src/fink.build/python27-2.7.18-1/Python-2.7.18/Modules/_ctypes/stgdict.o 
>>
>> build/temp.macosx-10.14-x86_64-2.7/opt/sw/src/fink.build/python27-2.7.18-1/Python-2.7.18/Modules/_ctypes/cfield.o 
>>
>> build/temp.macosx-10.14-x86_64-2.7/opt/sw/src/fink.build/python27-2.7.18-1/Python-2.7.18/Modules/_ctypes/malloc_closure.o 
>>
>> build/temp.macosx-10.14-x86_64-2.7/opt/sw/src/fink.build/python27-2.7.18-1/Python-2.7.18/Modules/_ctypes/darwin/dlfcn_simple.o 
>>
>> -L/opt/sw/lib -L. -lffi -ldl -o
>> build/lib.macosx-10.14-x86_64-2.7/_ctypes.so
>>
>> Python build finished, but the necessary bits to build these modules
>> were not found:
>> bsddb185           dl                 imageop
>> linuxaudiodev      ossaudiodev        spwd
>> sunaudiodev
>> To find the necessary bits, look in setup.py in detect_modules() for
>> the module's name.
>> (Fink package build should have 7 missing)
>>
>>
>> Failed to build these modules:
>> _scproxy           readline
>
> Please download the python27.info and python27.patch files from 
> https://github.com/fink/fink-distributions/pull/540 and save them to 
> /opt/sw/fink/dists/local/main/finkinfo
>
> Then try rebuilding python27 (the version should now show as 
> 2.7.18-2). This should definitely take care of the failing readline 
> module. The _scproxy sometimes fails from a broken Command Line Tools 
> install.
>
> See this message
> https://sourceforge.net/p/fink/mailman/message/37031093/
>
> about running the command (one line):
>
> /bin/ls -Fl /Library/Developer/CommandLineTools/SDKs
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs 
>
>
> And what the output is supposed to look like. Your output is supposed 
> to look like the bits at the bottom. If you have a MacOSX10.14.sdk in 
> the command line tools as a separate directory (not a link), then 
> fixing that should deal with the _scproxy error.
>
> Hanspeter


_______________________________________________
Fink-beginners mailing list
[email protected]
List archive:
https://sourceforge.net/p/fink/mailman/fink-users/
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-beginners
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.