[Bulk] Re: py-wxpython build failure

[Kevin Horton]

The version info for gcc claims it is for powerpc.  It certainly has  
been building packages for Fink on a daily basis without complaint.

% gcc --version
powerpc-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc.  
build 5367)

  "About XCode Tools.pdf" found in /Developer seems to say that XCode  
2.4.1 can build software for either PowerPC or Intel.  So, I believe  
that I have the correct XCode.  What other evidence should I look for  
to confirm?

Jyrki Wahlstedt  suggested that my problem looked like ones he had  
seen that were caused by a wrong symbolic link for wx-config.  This  
turned out to the be the case.  The package built once I corrected  
that link.

Kevin Horton



On 20 Jan 2007, at 09:05, Altoine Barker wrote:

> You sure you are running the correct Xcode for your box? I think you
> have the intel Xcode and not the powerpc Xcode. Is this your case?
>
> HTH
>
> -Altoine
>
> Kevin Horton wrote:
>> I'm a new MacPorts user with my first build failure.  I'm running  
>> OS X
>> 10.4.8 on a G4. I believe I have the latest XCode:
>>
>> % gcc --version
>> powerpc-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc.  
>> build
>> 5367)
>>
>> I did a port selfupdate today, then a port install py-wxpython.  It
>> failed like:
>>
>> Error: Target com.apple.build returned: shell command "cd
>> "/opt/local/var/db/dports/build/ 
>> _Volumes_Maxtor_300_opt_local_var_db_dports_sources_rsync.rsync.darwi 
>> nports.org_dpupdate_dports_python_py-wxpython/work/wxPython- 
>> src-2.8.0.1/wxPython"
>> && WX_CONFIG="/opt/local/bin/wx-config" UNICODE="1" WXPORT="mac"
>> /opt/local/bin/python2.5 setup.py build" returned error 1
>> Command output: src/helpers.cpp:2894: error: 'bool
>> wxPyImageHandler::LoadFile' is not a static member of 'class
>> wxPyImageHandler'
>> src/helpers.cpp:2894: error: 'wxImage' was not declared in this scope
>> src/helpers.cpp:2894: error: 'image' was not declared in this scope
>> src/helpers.cpp:2894: error: 'wxInputStream' was not declared in  
>> this scope
>> src/helpers.cpp:2894: error: 'stream' was not declared in this scope
>> src/helpers.cpp:2895: error: expected primary-expression before  
>> 'bool'
>> src/helpers.cpp:2895: error: expected primary-expression before 'int'
>> src/helpers.cpp:2895: error: initializer expression list treated as
>> compound expression
>> src/helpers.cpp:2895: error: expected ',' or ';' before '{' token
>> src/helpers.cpp:2919: error: 'bool wxPyImageHandler::SaveFile' is  
>> not a
>> static member of 'class wxPyImageHandler'
>> src/helpers.cpp:2919: error: 'wxImage' was not declared in this scope
>> src/helpers.cpp:2919: error: 'image' was not declared in this scope
>> src/helpers.cpp:2919: error: 'wxOutputStream' was not declared in  
>> this
>> scope
>> src/helpers.cpp:2919: error: 'stream' was not declared in this scope
>> src/helpers.cpp:2920: error: expected primary-expression before  
>> 'bool'
>> src/helpers.cpp:2920: error: initializer expression list treated as
>> compound expression
>> src/helpers.cpp:2920: error: expected ',' or ';' before '{' token
>> src/helpers.cpp:2942: error: 'int wxPyImageHandler::GetImageCount' is
>> not a static member of 'class wxPyImageHandler'
>> src/helpers.cpp:2942: error: 'wxInputStream' was not declared in  
>> this scope
>> src/helpers.cpp:2942: error: 'stream' was not declared in this scope
>> src/helpers.cpp:2942: error: expected ',' or ';' before '{' token
>> src/helpers.cpp: In function 'bool wxPyCheckForApp()':
>> src/helpers.cpp:752: warning: control reaches end of non-void  
>> function
>> src/helpers.cpp: In member function 'bool wxPyInputStream::eof()':
>> src/helpers.cpp:1094: warning: control reaches end of non-void  
>> function
>> src/helpers.cpp: In member function 'int wxPyInputStream::tell()':
>> src/helpers.cpp:1241: warning: control reaches end of non-void  
>> function
>> src/helpers.cpp: In function 'bool wxPyTestDisplayAvailable()':
>> src/helpers.cpp:3016: warning: control reaches end of non-void  
>> function
>> error: command '/usr/bin/gcc-4.0' failed with exit status 1
>>
>> Error: Status 1 encountered during processing.
>> ============================
>>
>> I repeated again with port -v install py-wxpython, and noted that  
>> there
>> may be signs that it thinks it is building for 10.3.  There is also a
>> strange cc1plus: warning buried in there:
>>
>> cc1plus: warning: command line option "-Wstrict-prototypes" is  
>> valid for
>> C/ObjC but not for C++
>>
>> ...
>> ls: wx*-2.4-config: No such file or directory
>> ls: wx*-2.4-config: No such file or directory
>>
>>   Warning: No config found to match: /usr/bin/wx-config --toolkit=mac
>> --unicode=yes --version=2.8 --libs gl
>>            in /usr/lib/wx/config
>>   If you require this configuration, please install the desired
>>   library build.  If this is part of an automated configuration
>>   test and no other errors occur, you may safely ignore it.
>>   You may use wx-config --list to see all configs available in
>>   the default prefix.
>>
>> Found wx-config: /usr/bin/wx-config
>>     Using flags:  --toolkit=mac --unicode=yes --version=2.8
>> Preparing CORE...
>> Preparing GLCANVAS...
>> Preparing STC...
>> Preparing GIZMOS...
>> running build
>> running build_py
>> copying wx/__version__.py -> build.unicode/lib.macosx-10.3-ppc-2.5/wx
>> copying wx/build/build_options.py ->
>> build.unicode/lib.macosx-10.3-ppc-2.5/wx/build
>> running build_ext
>> building '_core_' extension
>> /usr/bin/gcc-4.0 -fno-strict-aliasing -Wno-long-double -no-cpp- 
>> precomp
>> -mno-fused-madd -DNDEBUG -g -O3 -Wall -Wstrict-prototypes
>> -DSWIG_TYPE_TABLE=_wxPython_table -DSWIG_PYTHON_OUTPUT_TUPLE
>> -DWXP_USE_THREAD=1 -UNDEBUG -Iinclude -Isrc
>> -I/opt/local/include/python2.5 -c src/helpers.cpp -o
>> build.unicode/temp.macosx-10.3-ppc-2.5/src/helpers.o -O2
>> cc1plus: warning: command line option "-Wstrict-prototypes" is  
>> valid for
>> C/ObjC but not for C++
>> In file included from src/helpers.cpp:16:
>> include/wx/wxPython/wxPython_int.h:19:19: error: wx/wx.h: No such  
>> file
>> or directory
>> ...
>>
>> What other info will help troubleshooting?