Re: error building python24 on mac os x
I put this fix into the portfile, and it seems to work fine. Boey Maun Suang wrote: On 11/05/2007, at 15:02, Jann Röder wrote: I just found something interesting in Mac/OSX/Dist/build : # If the filesystem is case-sensitive then python will be built, but # some parts of the install expect python.exe which is what is built # on a case-insensitive filesystem. Make a link just in case it is # needed. if [ ! -e python.exe ]; then ln -s python python.exe fi So it is a case-sensitve vs. not case sensitive filesystem, but this code should fix it... Why isn't it working then ? The README file in Mac/OSX/ says that that Mac/OSX/Dist/build is only used for creating binary distributions, and grepping for \Dist\ and /build\ through the source after the configure step indicates to me that it is never called by anything else. By the way, has anybody reported this problem upstream? I imagine that it would be easy for them to fix. Kind regards, Maun Suang ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: python24 upgrade fails?
No, not at all. Which version of Mac OS X are you using ? Does it work if you uninstall the python port first (with the -f flag) and then try to install the new version ? Jann paul beard wrote: On May 9, 2007, at 3:34 PM, Weissmann Markus wrote: we already received this error report from another user, but not with the hint about the actual version of the python interpreter in $worksrcpath; neither Jann nor Elias nor I did encounter this particular error and we have been unable to reproduce it so far. We're investigating; please throw any hints my way! any idea why I would see this? /bin/sh: line 1: ../../python.exe: No such file or directory -- Paul Beard words: http://paulbeard.org/wordpress pictures: http://www.flickr.com/photos/pdb206/ Are you trying to win an argument or solve a problem? ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: qt4-mac port
You should contact the maintainer ([EMAIL PROTECTED]) and/or create a patch for that issue and put it on the bugtracker. Jann Jochen Küpper wrote: Hi, I was quite happy to find out that there is a port of Qt4. However, when compiling (my own) Unix program against it using autotools/libtool I found the following error: libtool: link: cannot find the library `' or unhandled argument `Carbon' This is due to the -framwork options in the .la files installed in /opt/local/lib. Removing all /opt/local/lib/libQt*.la files solves the problem (as documented elsewhere), but maybe MacPorts should take care o that, not? Greetings, Jochen ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: cleaning up older versions?
I regularly do a sudo port -f uninstall inactive Jann Ryan Schmidt schrieb: On Jan 22, 2007, at 13:26, Avi Carmi wrote: Hi all, I try to keep up to date, and I upgrade my packages on a regular basis (usually as new versions come out) however, even though the old version are deactivated they are still around: $ port installed apr-util The following ports are currently installed: apr-util @1.2.7_1 apr-util @1.2.8_0 apr-util @1.2.8_1 (active) port will not let me remove the older version, and claims that other packages are dependent on them... $ sudo port -v uninstall apr-util @1.2.7_1 --- Unable to uninstall apr-util 1.2.7_1, the following ports depend on it: ---apache2 ---subversion ---apache2 ---apache2 Error: port uninstall failed: Please uninstall the ports that depend on apr-util first. how do I clean up and remove the older versions??? Since you already have a new version of apr-util installed, you can ignore the warning and force the uninstall: $ sudo port -f uninstall apr-util @1.2.7_1 In the future, you can tell MacPorts to automatically uninstall the old version when you upgrade: $ sudo port -cu upgrade apr-util If, after configuring and compiling, you get a message that ports depend on that port, then you execute it a second time, using the -f (force) and -n (no dependencies) switches: $ sudo port -fncu upgrade apr-util (If you don't use -n, it will also force the recompilation of all dependencies of that port, which is probably not necessary and will just waste time.) ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
