[MacPorts] #14582: mod_python-3.3.1 Build fails with "unable to execute -fno-strict-aliasing: No such file or directory"
#14582: mod_python-3.3.1 Build fails with "unable to execute -fno-strict-aliasing: No such file or directory" --------------------------------------------+------------------------------- Reporter: mark@mwilden.com | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Keywords: mod_python fno-strict-aliasing | --------------------------------------------+------------------------------- {{{ ~/twistage/src/rails/twistage/trunk$ sudo port clean --work mod_python ---> Cleaning mod_python ~/twistage/src/rails/twistage/trunk$ sudo port install mod_python ---> Fetching mod_python ---> Verifying checksum(s) for mod_python ---> Extracting mod_python ---> Configuring mod_python ---> Building mod_python with target all Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_mod_python/work/mod_python-3.3.1" && make all " returned error 2 Command output: creating build/lib.macosx-10.3-i386-2.4/mod_python copying /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_mod_python/work/mod_python-3.3.1/lib/python/mod_python/__init__.py -> build/lib.macosx-10.3-i386-2.4/mod_python copying /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_mod_python/work/mod_python-3.3.1/lib/python/mod_python/apache.py -> build/lib.macosx-10.3-i386-2.4/mod_python copying /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_mod_python/work/mod_python-3.3.1/lib/python/mod_python/cache.py -> build/lib.macosx-10.3-i386-2.4/mod_python copying /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_mod_python/work/mod_python-3.3.1/lib/python/mod_python/cgihandler.py -> build/lib.macosx-10.3-i386-2.4/mod_python copying /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_mod_python/work/mod_python-3.3.1/lib/python/mod_python/Cookie.py -> build/lib.macosx-10.3-i386-2.4/mod_python copying /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_mod_python/work/mod_python-3.3.1/lib/python/mod_python/importer.py -> build/lib.macosx-10.3-i386-2.4/mod_python copying /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_mod_python/work/mod_python-3.3.1/lib/python/mod_python/psp.py -> build/lib.macosx-10.3-i386-2.4/mod_python copying /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_mod_python/work/mod_python-3.3.1/lib/python/mod_python/publisher.py -> build/lib.macosx-10.3-i386-2.4/mod_python copying /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_mod_python/work/mod_python-3.3.1/lib/python/mod_python/python22.py -> build/lib.macosx-10.3-i386-2.4/mod_python copying /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_mod_python/work/mod_python-3.3.1/lib/python/mod_python/Session.py -> build/lib.macosx-10.3-i386-2.4/mod_python copying /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_mod_python/work/mod_python-3.3.1/lib/python/mod_python/testhandler.py -> build/lib.macosx-10.3-i386-2.4/mod_python copying /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_mod_python/work/mod_python-3.3.1/lib/python/mod_python/util.py -> build/lib.macosx-10.3-i386-2.4/mod_python running build_ext building 'mod_python._psp' extension creating build/temp.macosx-10.3-i386-2.4 creating build/temp.macosx-10.3-i386-2.4/opt creating build/temp.macosx-10.3-i386-2.4/opt/local creating build/temp.macosx-10.3-i386-2.4/opt/local/var creating build/temp.macosx-10.3-i386-2.4/opt/local/var/macports creating build/temp.macosx-10.3-i386-2.4/opt/local/var/macports/build creating build/temp.macosx-10.3-i386-2.4/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_mod_python creating build/temp.macosx-10.3-i386-2.4/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_mod_python/work creating build/temp.macosx-10.3-i386-2.4/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_mod_python/work/mod_python-3.3.1 creating build/temp.macosx-10.3-i386-2.4/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_mod_python/work/mod_python-3.3.1/src -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/_opt_local_var_macports_sources_rsync.macports.org_release_ports_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/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_mod_python/work/mod_python-3.3.1/src/psp_string.c -o build/temp.macosx-10.3-i386-2.4/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_mod_python/work/mod_python-3.3.1/src/psp_string.o unable to execute -fno-strict-aliasing: No such file or directory error: command '-fno-strict-aliasing' failed with exit status 1 make[1]: *** [build] Error 1 make: *** [do_dso] Error 2 Error: Status 1 encountered during processing. }}} -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14582> MacPorts </projects/macports> Ports system for Mac OS
#14582: mod_python-3.3.1 Build fails with "unable to execute -fno-strict-aliasing: No such file or directory" -------------------------------+-------------------------------------------- Reporter: mark@mwilden.com | Owner: mww@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@macports.org): * cc: mww@macports.org (removed) * owner: macports-tickets@lists.macosforge.org => mww@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
#14582: mod_python-3.3.1 Build fails with "unable to execute -fno-strict-aliasing: No such file or directory" -------------------------------+-------------------------------------------- Reporter: mark@mwilden.com | Owner: mww@macports.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: mod_python fno-strict-aliasing -------------------------------+-------------------------------------------- Comment (by reiffert@macports.org): Please attach the file "config.log" to this ticket. It can be found in the build directory. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14582#comment:2> MacPorts </projects/macports> Ports system for Mac OS
#14582: mod_python-3.3.1 Build fails with "unable to execute -fno-strict-aliasing: No such file or directory" -------------------------------+-------------------------------------------- Reporter: mark@mwilden.com | Owner: mww@macports.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: mod_python fno-strict-aliasing -------------------------------+-------------------------------------------- Comment (by mark@mwilden.com): Nothing jumped out at me from looking at the build debug output, except for the warning about my blood pressure (which I believe to be in error). -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14582#comment:3> MacPorts </projects/macports> Ports system for Mac OS
#14582: mod_python-3.3.1 Build fails with "unable to execute -fno-strict-aliasing: No such file or directory" -------------------------------+-------------------------------------------- Reporter: mark@mwilden.com | Owner: mww@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@macports.org): * cc: ryandesign@macports.org (added) Comment: Looking through the differences between our config.logs, the significant difference appears to be that mine says: {{{ ECHO_C='' ECHO_N='-n' }}} While yours says: {{{ ECHO_C='ECHO_N='' }}} Is something the matter with your /bin/echo, or do you have another different echo binary somewhere? -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14582#comment:4> MacPorts </projects/macports> Ports system for Mac OS
#14582: mod_python-3.3.1 Build fails with "unable to execute -fno-strict-aliasing: No such file or directory" -------------------------------+-------------------------------------------- Reporter: mark@mwilden.com | Owner: mww@macports.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: mod_python fno-strict-aliasing -------------------------------+-------------------------------------------- Comment (by mark@mwilden.com): Bearing in mind that I'm an OS X/Unix newbie, my /bin/echo seems to work fine. I was able to build "manually" from the source found in /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_mod_python/work/mod_python-3.3.1 using the instructions in README, but apachectl -t told me it was the wrong architecture. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14582#comment:5> MacPorts </projects/macports> Ports system for Mac OS
#14582: mod_python-3.3.1 Build fails with "unable to execute -fno-strict-aliasing: No such file or directory" -------------------------------+-------------------------------------------- Reporter: mark@mwilden.com | Owner: mww@macports.org Type: defect | Status: closed Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: duplicate | Keywords: mod_python fno-strict-aliasing -------------------------------+-------------------------------------------- Changes (by jmr@macports.org): * status: new => closed * resolution: => duplicate Comment: I remember reading somewhere that the behaviour of `echo -n` did in fact change in Leopard. Anyway, this is a duplicate of #13856. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14582#comment:6> MacPorts </projects/macports> Ports system for Mac OS
participants (1)
-
MacPorts