[MacPorts] #14582: mod_python-3.3.1 Build fails with "unable to execute -fno-strict-aliasing: No such file or directory"

MacPorts trac at macosforge.org
Fri Mar 7 22:43:24 PST 2008


#14582: mod_python-3.3.1 Build fails with "unable to execute -fno-strict-aliasing:
No such file or directory"
-------------------------------+--------------------------------------------
  Reporter:  mark at mwilden.com  |       Owner:  mww at macports.org              
      Type:  defect            |      Status:  new                           
  Priority:  Normal            |   Milestone:  Port Bugs                     
 Component:  ports             |     Version:  1.6.0                         
Resolution:                    |    Keywords:  mod_python fno-strict-aliasing
-------------------------------+--------------------------------------------
Changes (by ryandesign at macports.org):

 * cc: mww at macports.org (removed)
  * owner:  macports-tickets at lists.macosforge.org => mww at macports.org
  * milestone:  => Port Bugs

Comment:

 Works for me on 10.4.11 Intel with Xcode 2.4.1. The line should read:

 {{{
 /usr/bin/gcc-4.0 -fno-strict-aliasing -Wno-long-double -no-cpp-precomp
 -fno-common -fno-common -dynamic -DNDEBUG -g -O3 -Wall -Wstrict-prototypes
 -I/opt/local/var/macports/build/_Users_rschmidt_macports_dports_www_mod_python/work/mod_python-3.3.1/src/include
 -I/opt/local/Library/Frameworks/Python.framework/Versions/2.4/include/python2.4
 -c
 /opt/local/var/macports/build/_Users_rschmidt_macports_dports_www_mod_python/work/mod_python-3.3.1/src/psp_string.c
 -o
 build/temp.macosx-10.4-i386-2.4/opt/local/var/macports/build/_Users_rschmidt_macports_dports_www_mod_python/work/mod_python-3.3.1/src/psp_string.o
 }}}

 So, in your case, the name of the compiler `/usr/bin/gcc-4.0` is missing
 but I don't know why. Assuming you do have Xcode installed and
 `/usr/bin/gcc-4.0` does exist, check the verbose output:

 {{{
 $ sudo port clean --work mod_python
 $ sudo port -dv install mod_python
 }}}

 See if anything jumps out at you in the configure phase around where I see
 this output:

 {{{
 checking for gcc... /usr/bin/gcc-4.0
 }}}

-- 
Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14582#comment:1>
MacPorts </projects/macports>
Ports system for Mac OS


More information about the macports-tickets mailing list