> On Nov 2, 2015, at 09:24, Alexander Hansen <alexanderk.han...@gmail.com> 
> wrote:
> 
> 
>> On Nov 2, 2015, at 08:16, Buz Barstow <buzbars...@gmail.com> wrote:
>> 
>> Hi fink users (Alex Hansen and Jack Rabbit are cc’d), 
>> 
>> In a follow up to the last email thread. I am continuing to try to install 
>> simplecv on MacOS X.
>> 
>> As part of this, I need to install pygame-py27. 
>> 
>> Alex was able to get a dependency of pygame: numeric-py27, to install on OS 
>> X El Capitan. However, there are still some unresolved issues with the 
>> installation of pygame-py27. 
>> 
>> Here’s my system information:
>> 
>> 
>> Also include the following system information:
>> Package manager version: 0.39.2
>> Distribution version: selfupdate-rsync Mon Nov  2 11:00:52 2015, 10.11, 
>> x86_64
>> Trees: local/main stable/main
>> Xcode.app: 7.1
>> Xcode command-line tools: 7.1.0.0.1.1444952191
>> Max. Fink build jobs:  8
>> 
>> 
>> 
>> Here’s the error message:
>> 
>> gcc -DNDEBUG -g -fwrapv -fwrapv -O3 -Wall -Wstrict-prototypes 
>> -no-integrated-as -I/usr/X11R6/include -framework CoreFoundation -framework 
>> Cocoa -I/sw/include -Ddarwin -I/sw/include/SDL -I/sw/include/SDL 
>> -I/sw/include -I/sw/include -I/sw/include/python2.7 -c src/imageext.c -o 
>> build/temp.macosx-10.11-x86_64-2.7/src/imageext.o
>> ### execution of /sw/bin/python2.7 failed, exit code 1
>> ### execution of /tmp/fink.SCFBM failed, exit code 1
>> Removing runtime build-lock...
>> Removing build-lock package...
>> /sw/bin/dpkg-lockwait -r fink-buildlock-pygame-py27-1.9.1-2
>> (Reading database ... 202455 files and directories currently installed.)
>> Removing fink-buildlock-pygame-py27-1.9.1-2 ...
>> Failed: phase compiling: pygame-py27-1.9.1-2 failed
>> 
>> 
>> Many thanks, and all the best,
>> 
>> —Buz
>> 
>> 
> 
> That doesn’t actually look like the error message.  Since you’re building 
> with multiple jobs, I’d guess that your build failed in one thread and this 
> is the last operation performed in a completely different thread.
> 
> Here is what I see when building with a single job:
> 
> ...
> gcc -DNDEBUG -g -fwrapv -fwrapv -O3 -Wall -Wstrict-prototypes 
> -no-integrated-as -I/opt/X11/include -framework CoreFoundation -framework 
> Cocoa -I/sw/include -Ddarwin -I/sw/include/SDL -I/sw/include/SDL 
> -I/sw/include -I/sw/include -I/sw/include/python2.7 -c src/imageext.c -o 
> build/temp.macosx-10.10-x86_64-2.7/src/imageext.o
> clang: warning: -framework CoreFoundation: 'linker' input unused
> clang: warning: -framework Cocoa: 'linker' input unused
> /var/folders/36/yv798ygn4n13ldn3fblgwj9w0000kr/T/imageext-38b459.s:2:Unknown 
> pseudo-op: .macosx_version_min

<snip>

> clang: error: assembler command failed with exit code 1 (use -v to see 
> invocation)
> error: command 'gcc' failed with exit status 1
> 
> Google suggest that this 
> 

Was too quick on the “send” button there.  I was going to say that Google 
suggested that this error might be a bug in the current clang.

-- 
Alexander Hansen, Ph.D.
Fink User Liaison


------------------------------------------------------------------------------
_______________________________________________
Fink-users mailing list
Fink-users@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.macosx.fink.user
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to