UpdatingPorts
Hi, I was updating my ports and got this error, help.. unable to execute -fno-strict-aliasing: No such file or directory -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd - fno-common -fno-common -dynamic -DNDEBUG -g -O3 -Wall -Wstrict- prototypes -I/opt/local/Library/Frameworks/Python.framework/Versions/ 2.4/include/python2.4 -c conftest.c -o conftest.o unable to execute -fno-strict-aliasing: No such file or directory building 'twisted.protocols._c_urlarg' extension creating build/temp.macosx-10.3-ppc-2.4 creating build/temp.macosx-10.3-ppc-2.4/twisted creating build/temp.macosx-10.3-ppc-2.4/twisted/protocols -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd - fno-common -fno-common -dynamic -DNDEBUG -g -O3 -Wall -Wstrict- prototypes -I/opt/local/Library/Frameworks/Python.framework/Versions/ 2.4/include/python2.4 -c twisted/protocols/_c_urlarg.c -o build/ temp.macosx-10.3-ppc-2.4/twisted/protocols/_c_urlarg.o unable to execute -fno-strict-aliasing: No such file or directory error: command '-fno-strict-aliasing' failed with exit status 1 Error: Unable to upgrade port: 1 Mack Johnson [EMAIL PROTECTED] http//macknezjohnson.com ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: UpdatingPorts
On Apr 20, 2008, at 4:37 PM, Mack Johnson wrote: Hi, I was updating my ports and got this error, help.. unable to execute -fno-strict-aliasing: No such file or directory -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused- madd -fno-common -fno-common -dynamic -DNDEBUG -g -O3 -Wall - Wstrict-prototypes -I/opt/local/Library/Frameworks/Python.framework/ Versions/2.4/include/python2.4 -c conftest.c -o conftest.o unable to execute -fno-strict-aliasing: No such file or directory building 'twisted.protocols._c_urlarg' extension creating build/temp.macosx-10.3-ppc-2.4 creating build/temp.macosx-10.3-ppc-2.4/twisted creating build/temp.macosx-10.3-ppc-2.4/twisted/protocols -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused- madd -fno-common -fno-common -dynamic -DNDEBUG -g -O3 -Wall - Wstrict-prototypes -I/opt/local/Library/Frameworks/Python.framework/ Versions/2.4/include/python2.4 -c twisted/protocols/_c_urlarg.c -o build/temp.macosx-10.3-ppc-2.4/twisted/protocols/_c_urlarg.o unable to execute -fno-strict-aliasing: No such file or directory error: command '-fno-strict-aliasing' failed with exit status 1 Error: Unable to upgrade port: 1 Are you running Mac OS X 10.5 Leopard? If so, this may be the well- known but not yet fully-understood problem that Guido and I have been talking about on the list today. If so, a workaround is to simply try the upgrade again and it should work. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: UpdatingPorts
On Sun, 20 Apr 2008, Ryan Schmidt wrote: Are you running Mac OS X 10.5 Leopard? If so, this may be the well-known but not yet fully-understood problem that Guido and I have been talking about on the list today. If so, a workaround is to simply try the upgrade again and it should work. i get this relatively often, too. I think what happens is that some make prerequisite is missing, but not added to the autoconf configuration. For example: Say, you do something like $(RM) -f foo.bar in your makefile and assume that every sane environment has $(RM) defined as rm or something else. Then, RM is for some reason undefined - what command will make see? -f foo.bar So you have to look for undefined variables in the makefiles. Most of the time they should be more or less easy to find for the rest of the parametera following... -- peter koellner [EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: UpdatingPorts
On Apr 20, 2008, at 7:18 PM, Peter Koellner wrote: On Sun, 20 Apr 2008, Ryan Schmidt wrote: Are you running Mac OS X 10.5 Leopard? If so, this may be the well- known but not yet fully-understood problem that Guido and I have been talking about on the list today. If so, a workaround is to simply try the upgrade again and it should work. i get this relatively often, too. I think what happens is that some make prerequisite is missing, but not added to the autoconf configuration. For example: Say, you do something like $(RM) -f foo.bar in your makefile and assume that every sane environment has $(RM) defined as rm or something else. Then, RM is for some reason undefined - what command will make see? -f foo.bar So you have to look for undefined variables in the makefiles. Most of the time they should be more or less easy to find for the rest of the parametera following... You don't have to look in the Makefiles for anything. You just have to do whatever MacPorts command you issued a second time and it should work. Guido has suggested a reason why this is causing problems for Leopard users, but I don't yet understand it or how to turn it into a fix that we can apply in MacPorts: http://lists.macosforge.org/pipermail/macports-users/2008-April/ 009986.html ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
