Re: Error after trying to upgrade installed
On 24 Jan 2009, at 03:46, Rainer Müller wrote: Bryan Blackburn wrote: Personally, I'd like to see direct mode deprecated, and when 10.3 support is officially dropped, it can be removed entirely. Other than the old performance issues with the large number of hardlinks, I don't see any advantage to using direct over image mode. Are there other reasons for keeping it? The switch to registry2.0 which is scheduled for 1.8.0 would be a good place to drop direct mode as it is mainly implemented in the registry/receipt handling. But that means there would be no deprecation period. But as we tend to discuss development stuff on the macports-users list, there is the opportunity to ask our users: How many of you do still use direct mode and for what reasons? Rainer If you mean the end users ... I had to go and actually search in the documentation to find out what direct mode is. http://guide.macports.org/#internals.images which is the only hit for direct mode. Which I think answers your question ... Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: ASSP port testing, not getting all perl mods to work
So... :) This trickle down effect of needing A, to find it needs B and C, and that B and C need D and E, and that can go on a while. Look what I did... ( One small issue with the mysql connector still, and I have a few questions about how to chain these all together, since there is an order to install ports in, but that just seems to go from simple to complex in order. I will break out this thread into a new one for those ) What is the ETA to getting something approved and into the system? Just curious. /opt/local/bin/perl assp.pl ASSP version 1.4.3.1 (Perl 5.008009) initializing ASSP running on server: me-macbook.local (192.168.2.1) Net::LDAP module version 0.36 installed and available Net::DNS module version 0.63 installed and available Email::Valid module version 0.179 installed and available Mail::SPF::Query module version 1.999001 installed and available Mail::SPF module version 2.006 installed and available Mail::SRS module version 0.31 installed - Sender Rewriting Scheme available Compress::Zlib module version 2.015 installed - HTTP compression available Digest::MD5 module version 2.37 installed - delaying can use MD5 keys for hashes Digest::SHA1 module version 2.11 installed File::ReadBackwards module version 1.04 installed - searching of log files enabled Time::HiRes module version 1.9715 installed - CPU usage statistics available Sys::Syslog module version 0.27 installed - Unix centralized logging enabled Net::Syslog module version 0.03 installed - network Syslog logging enabled Tie::RDBM module *not* installed - mysql usage not available Net::IP::Match::Regexp module version 1.01 installed - CIDR notation for IP range available Net::CIDR::Lite module version 0.20 installed - hyphenated IP address range available Net::SenderBase module version 1.01 installed - countrycode checks available LWP::Simple module version 5.810 installed - griplist available Email::MIME::Modifier module version 1.442 installed - attachment detection available Net::SMTP module version 2.31 installed - Verify Recipients available -- Scott ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Installing Apache2 on Leopard
I have successfully accomplished this... but frankly the process just doesn't sit well with my sense of things.. I now have two complete Apache installations... and have to do work arounds to get the port installation to work (apache2ctl etc) Isn't there away to install the port version over the orginal installation? it just seems the more orderly way of doing things ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Installing Apache2 on Leopard
Jason Hirsh wrote: I have successfully accomplished this... but frankly the process just doesn't sit well with my sense of things.. I now have two complete Apache installations... and have to do work arounds to get the port installation to work (apache2ctl etc) Isn't there away to install the port version over the orginal installation? it just seems the more orderly way of doing things http://trac.macports.org/wiki/FAQ#WillMacPortslinktosystemlibrariesratherthanitsown No, it would not be okay to overwrite the system provided software. The next upgrade by Apple would remove it or would render it unusable. Rainer ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Installing Apache2 on Leopard
On Jan 24, 2009, at 5:16 AM, Jason Hirsh wrote: I have successfully accomplished this... but frankly the process just doesn't sit well with my sense of things.. I now have two complete Apache installations... and have to do work arounds to get the port installation to work (apache2ctl etc) Isn't there away to install the port version over the orginal installation? it just seems the more orderly way of doing things No, and you will get used to it as well. The first time Apple update httpd.conf you will be thankful, and they have done so in the past. Apple also runs periodic scripts that roll out your logs. Compressing them is nice, rolling them to deletion is not. Apple's kit is more in line with casual serving, not something long term and to be hit hard. Not to say it can not, but it will bite you. The main thing is, good luck getting php even moderately usable with Apple's stuff, and they will break it eventually. Ports needs some caution as well, as an upgrade, iirc, can nuke your settings as well. I too did not like the change in command I had to learn, but you quickly learn to appreciate the isolation. You can solve your issues in a few simple ways. Add /opt/local/bin and whatever /opt paths you want to your $PATH, first in order. Those commands will now take priority. You can also just move aside apachectl and symblink it to the ports version. In the end, really, how often are you restarting apache anyway. -- Scott ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Universal Binaries
2009/1/24 Ryan Schmidt ryandes...@macports.org On Jan 23, 2009, at 09:11, tim...@rochester.rr.com tim...@rochester.rr.com wrote: Joshua Root j...@macports.org wrote: Timothy Lee wrote: Do you know if its possible for me (on leopard) to build x86 code (all my macports ports) that will also run on Tiger? Short of physical access to an intel 10.4 install, is there anything I can do? I am the OSX bundle maintainer of avidemux (I maintain others too but via other ways). I build my avidemux binaries and dependent libs as universal ones on Leopard (using macports for all necessary libs) and the bundle (including binary and necessary libraries) is used on Tiger as well as Leopard. Note that avidemux is available as macports package, but I build (b)leeding edge svn bundles. I need to compile avidemux for i386 and ppc from svn trunk and lipo merge them to make them universal. The bundle contains some complicated libraries (glib, pango, cairo, gtk and they are all built universal and without X11 (so native aqua) via macports) and this works fine. (Two libs are not yet in macports and I need to make ports as soon as I have time to do so, but maintaining three packages and developing my own takes quite some spare time) Don't forget to use Reply All so the discussion goes to the list as well. There are no guarantees that this will work, but the way to do what you want would be to set universal_target to 10.4, universal_sysroot to /Developer/SDKs/MacOSX10.4u.sdk, and universal_archs to i386. Then build everything with +universal (best to add it to your variants.conf). Also set x11prefix to /usr/X11R6; Leopard's X11 prefix /usr/X11 does not exist on Tiger. Thanks for the tip! Has anyone tried this? Success/failure stories? openssl failed for me when I tried it this way on Leopard. Switching back to 10.5 and the 10.5 SDK fixed it. 90% builds OK. Some other binaries and libraries fail to build this universal way: gimp (now built as i386 aqua), sqlite3 (is a pain in the backside anyway), subversion (svn), wxwidgets (wxMac), wine, libGLEW, libOrbit, libSDL*, liba52*, libav*, libbonobo, libboost, libgnome, libpoppler and some others. I build these binaries/libraries with sudo port package -universal as I have +universal (and -x11) in my variants.conf Next to that: some libraries can be build universal as static libs, but not as dynamic libs like x264 (can't remember the other one) Also: some libs are so POSIX compliant that, when build via macports on Leopard, they can't be used on Tiger. (lib)xvid is one. I need to build that one manually. Note: I mentioned in a earlier post in this thread that I have # the SDK sysroot to use universal_sysroot /Developer/SDKs/MacOSX10.4u.sdk in my macports.conf. Technically speaking you can just as well use the 10.5 SDK as that one builds for 10.4 too as long as you set the deployment target to 10.4. I choose the 10.4 SDK as quite some packages are not yet 10.5 SDK optimized which led to some errors (pango and gtk). The 10.5 SDK uses some new stuff that works fine on Leopard but not on Tiger as most ports are actually linux based and ported to Mac. Maybe they are already fixed but I did not check yet. Harry ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Installing Apache2 on Leopard
Scott Haneda wrote: Ports needs some caution as well, as an upgrade, iirc, can nuke your settings as well. If you're thinking of this, it's been fixed: http://trac.macports.org/ticket/8605 - Josh ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: ASSP port testing, not getting all perl mods to work
Scott Haneda wrote: I think this is telling: - ERROR: Net::DNS::Resolver::Programmable is not installed - ERROR: Error is not installed - ERROR: NetAddr::IP is not installed - ERROR: version is not installed * Optional prerequisite NetAddr::IP is not installed I can probably find the first, but what is Error that is not installed, and what is version that is not installed? At a guess, p5-error and p5-version? :-) - Josh ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
apache2 fails to install
Hi folks I'm completely stuck installing apache2. No idea what exactly is going wrong. It's a clean macports install (1.700). I even ran a manual selfupdate. Installing git-core went flawless, it's just apache2 that is causing problems. Thanks for helping me out. $ sudo port install apache2 Password: --- Building db46 Error: Target org.macports.build returned: shell command cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_databases_db46/work/db-4.6.21/build_unix make all returned error 2 Command output: /bin/sh ./libtool --mode=compile /usr/bin/gcc-4.0 -c -O2 -I../dist/.. -I/opt/local/include ../dist/../db_dump185/db_dump185.c /usr/bin/gcc-4.0 -c -O2 -I../dist/.. -I/opt/local/include ../dist/../db_dump185/db_dump185.c -fno-common -DPIC -o .libs/db_dump185.o ../dist/../db_dump185/db_dump185.c: In function 'main': ../dist/../db_dump185/db_dump185.c:211: warning: assignment makes pointer from integer without a cast ../dist/../db_dump185/db_dump185.c:213: warning: assignment makes pointer from integer without a cast ../dist/../db_dump185/db_dump185.c:228: error: 'struct __db' has no member named 'seq' ../dist/../db_dump185/db_dump185.c:228: error: 'R_NEXT' undeclared (first use in this function) ../dist/../db_dump185/db_dump185.c:228: error: (Each undeclared identifier is reported only once ../dist/../db_dump185/db_dump185.c:228: error: for each function it appears in.) ../dist/../db_dump185/db_dump185.c:233: error: 'struct __db' has no member named 'seq' ../dist/../db_dump185/db_dump185.c: In function 'db_hash': ../dist/../db_dump185/db_dump185.c:261: error: 'struct __db' has no member named 'internal' ../dist/../db_dump185/db_dump185.c:263: error: 'struct __db' has no member named 'internal' ../dist/../db_dump185/db_dump185.c: In function 'db_btree': ../dist/../db_dump185/db_dump185.c:288: error: 'struct __db' has no member named 'internal' make: *** [db_dump185.lo] Error 1 Error: The following dependencies failed to build: apr-util db46 sqlite3 readline pcre Error: Status 1 encountered during processing. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Universal Binaries
Thanks for the reply Harry- I'm fairly sure that I will need to lipo together the builds for Musicbrainz' Picard. So - in your experience what are all the options that I must set after a fresh src install to have a 10.5 setup building binaries for 10.4? Also, does anyone know how UB deals with endian-specific code? Does the c-preprocessor run twice and eval all the #ifdef big_endian (or whatever the define/macro would be)? Or is there some other way to do this that wouldn't require two runs of the cpp. Thanks Tim On Jan 24, 2009, at 8:49 AM, Harry van der Wolf wrote: 2009/1/24 Ryan Schmidt ryandes...@macports.org On Jan 23, 2009, at 09:11, tim...@rochester.rr.com tim...@rochester.rr.com wrote: Joshua Root j...@macports.org wrote: Timothy Lee wrote: Do you know if its possible for me (on leopard) to build x86 code (all my macports ports) that will also run on Tiger? Short of physical access to an intel 10.4 install, is there anything I can do? I am the OSX bundle maintainer of avidemux (I maintain others too but via other ways). I build my avidemux binaries and dependent libs as universal ones on Leopard (using macports for all necessary libs) and the bundle (including binary and necessary libraries) is used on Tiger as well as Leopard. Note that avidemux is available as macports package, but I build (b)leeding edge svn bundles. I need to compile avidemux for i386 and ppc from svn trunk and lipo merge them to make them universal. The bundle contains some complicated libraries (glib, pango, cairo, gtk and they are all built universal and without X11 (so native aqua) via macports) and this works fine. (Two libs are not yet in macports and I need to make ports as soon as I have time to do so, but maintaining three packages and developing my own takes quite some spare time) Don't forget to use Reply All so the discussion goes to the list as well. There are no guarantees that this will work, but the way to do what you want would be to set universal_target to 10.4, universal_sysroot to /Developer/SDKs/MacOSX10.4u.sdk, and universal_archs to i386. Then build everything with +universal (best to add it to your variants.conf). Also set x11prefix to /usr/X11R6; Leopard's X11 prefix /usr/X11 does not exist on Tiger. Thanks for the tip! Has anyone tried this? Success/failure stories? openssl failed for me when I tried it this way on Leopard. Switching back to 10.5 and the 10.5 SDK fixed it. 90% builds OK. Some other binaries and libraries fail to build this universal way: gimp (now built as i386 aqua), sqlite3 (is a pain in the backside anyway), subversion (svn), wxwidgets (wxMac), wine, libGLEW, libOrbit, libSDL*, liba52*, libav*, libbonobo, libboost, libgnome, libpoppler and some others. I build these binaries/libraries with sudo port package - universal as I have +universal (and -x11) in my variants.conf Next to that: some libraries can be build universal as static libs, but not as dynamic libs like x264 (can't remember the other one) Also: some libs are so POSIX compliant that, when build via macports on Leopard, they can't be used on Tiger. (lib)xvid is one. I need to build that one manually. Note: I mentioned in a earlier post in this thread that I have # the SDK sysroot to use universal_sysroot /Developer/SDKs/MacOSX10.4u.sdk in my macports.conf. Technically speaking you can just as well use the 10.5 SDK as that one builds for 10.4 too as long as you set the deployment target to 10.4. I choose the 10.4 SDK as quite some packages are not yet 10.5 SDK optimized which led to some errors (pango and gtk). The 10.5 SDK uses some new stuff that works fine on Leopard but not on Tiger as most ports are actually linux based and ported to Mac. Maybe they are already fixed but I did not check yet. Harry ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Universal Binaries
On Jan 24, 2009, at 3:36 AM, Ryan Schmidt wrote: On Jan 23, 2009, at 09:11, tim...@rochester.rr.com tim...@rochester.rr.com wrote: Joshua Root j...@macports.org wrote: Timothy Lee wrote: Do you know if its possible for me (on leopard) to build x86 code (all my macports ports) that will also run on Tiger? Short of physical access to an intel 10.4 install, is there anything I can do? Don't forget to use Reply All so the discussion goes to the list as well. There are no guarantees that this will work, but the way to do what you want would be to set universal_target to 10.4, universal_sysroot to /Developer/SDKs/MacOSX10.4u.sdk, and universal_archs to i386. Then build everything with +universal (best to add it to your variants.conf). Also set x11prefix to /usr/X11R6; Leopard's X11 prefix /usr/X11 does not exist on Tiger. If I do this, how will I be able to run the executables on my 10.5 setup? Thanks for the tip! Has anyone tried this? Success/failure stories? openssl failed for me when I tried it this way on Leopard. Switching back to 10.5 and the 10.5 SDK fixed it. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Universal Binaries
Timothy Lee wrote: On Jan 24, 2009, at 3:36 AM, Ryan Schmidt wrote: On Jan 23, 2009, at 09:11, tim...@rochester.rr.com tim...@rochester.rr.com wrote: Joshua Root j...@macports.org wrote: Timothy Lee wrote: Do you know if its possible for me (on leopard) to build x86 code (all my macports ports) that will also run on Tiger? Short of physical access to an intel 10.4 install, is there anything I can do? Don't forget to use Reply All so the discussion goes to the list as well. There are no guarantees that this will work, but the way to do what you want would be to set universal_target to 10.4, universal_sysroot to /Developer/SDKs/MacOSX10.4u.sdk, and universal_archs to i386. Then build everything with +universal (best to add it to your variants.conf). Also set x11prefix to /usr/X11R6; Leopard's X11 prefix /usr/X11 does not exist on Tiger. If I do this, how will I be able to run the executables on my 10.5 setup? There's a symlink on at least some Leopard installs. If you don't have one, make one. - Josh ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Universal Binaries
2009/1/24 Timothy Lee tim...@rochester.rr.com Thanks for the reply Harry-I'm fairly sure that I will need to lipo together the builds for Musicbrainz' Picard. So - in your experience what are all the options that I must set after a fresh src install to have a 10.5 setup building binaries for 10.4? Nothing more than setting the right options in your macports.conf and then see how far you get. 2009/1/24 Timothy Lee tim...@rochester.rr.com On Jan 24, 2009, at 3:36 AM, Ryan Schmidt wrote: On Jan 23, 2009, at 09:11, tim...@rochester.rr.com tim...@rochester.rr.com wrote: Joshua Root j...@macports.org wrote: Timothy Lee wrote: Do you know if its possible for me (on leopard) to build x86 code (all my macports ports) that will also run on Tiger? Short of physical access to an intel 10.4 install, is there anything I can do? Don't forget to use Reply All so the discussion goes to the list as well. There are no guarantees that this will work, but the way to do what you want would be to set universal_target to 10.4, universal_sysroot to /Developer/SDKs/MacOSX10.4u.sdk, and universal_archs to i386. Then build everything with +universal (best to add it to your variants.conf). Also set x11prefix to /usr/X11R6; Leopard's X11 prefix /usr/X11 does not exist on Tiger. If I do this, how will I be able to run the executables on my 10.5 setup? I ran into the same issue and simply decided to make links. On Tiger I simply did sudo ln -s /usr/X11R6 /usr/X11. If you build on Tiger and bring them to Leopard you do sudo ln -s /usr/X11 /usr/X11R6. This works only on your own system off course, unless you make an installer that checks whether it runs on Tiger or Leopard and creates a softlink accordingly. Harry ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Universal Binaries
Harry- You made reference to adding the -x11 tag to your variants.conf. By doing this, do you force macports to use Apple's X11? Or is it something else entirely different? thanks On Jan 24, 2009, at 12:59 PM, Harry van der Wolf wrote: 2009/1/24 Timothy Lee tim...@rochester.rr.com Thanks for the reply Harry- I'm fairly sure that I will need to lipo together the builds for Musicbrainz' Picard. So - in your experience what are all the options that I must set after a fresh src install to have a 10.5 setup building binaries for 10.4? Nothing more than setting the right options in your macports.conf and then see how far you get. 2009/1/24 Timothy Lee tim...@rochester.rr.com On Jan 24, 2009, at 3:36 AM, Ryan Schmidt wrote: On Jan 23, 2009, at 09:11, tim...@rochester.rr.com tim...@rochester.rr.com wrote: Joshua Root j...@macports.org wrote: Timothy Lee wrote: Do you know if its possible for me (on leopard) to build x86 code (all my macports ports) that will also run on Tiger? Short of physical access to an intel 10.4 install, is there anything I can do? Don't forget to use Reply All so the discussion goes to the list as well. There are no guarantees that this will work, but the way to do what you want would be to set universal_target to 10.4, universal_sysroot to /Developer/SDKs/MacOSX10.4u.sdk, and universal_archs to i386. Then build everything with +universal (best to add it to your variants.conf). Also set x11prefix to /usr/X11R6; Leopard's X11 prefix /usr/X11 does not exist on Tiger. If I do this, how will I be able to run the executables on my 10.5 setup? I ran into the same issue and simply decided to make links. On Tiger I simply did sudo ln -s /usr/X11R6 /usr/X11. If you build on Tiger and bring them to Leopard you do sudo ln -s /usr/X11 /usr/X11R6. This works only on your own system off course, unless you make an installer that checks whether it runs on Tiger or Leopard and creates a softlink accordingly. Harry ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Universal Binaries
It is something completely different. Most linux, netbsd and freebsd packages rely on X11. MacOSX has support for x11 but the native windowing system of MacOSX is aqua. Using the -x11 option means that you don't build for X11. An increasing amount of binaries and libraries support native aqua and in that case I don't want to build for X11. It's slower, bigger (X11 takes also memory and resources next to the already available aqua) and ugglier. But the last is off course a matter of taste. Note that some binaries and libraries are still considered beta under aqua (like Gimp) but function very good. If you take a look at openoffice (not macports) you see what I mean. It has already been available for MacOSX in X11 form for a long period. Recently they also released a 3.0 beta version for Aqua which works fine. NeoOffice is an aqua spin-off of OpenOffice and has a native Aqua interface for about 1½ years now. In versioning it runs a bit behind OpenOffice (OOO 3.0.x versus NOO 2.2.5) Note also that some packages that are compiled with -x11, simply miss the X11 gui but only compile/create the command line versions. Harry 2009/1/24 Timothy Lee tim...@rochester.rr.com Harry-You made reference to adding the -x11 tag to your variants.conf. By doing this, do you force macports to use Apple's X11? Or is it something else entirely different? thanks On Jan 24, 2009, at 12:59 PM, Harry van der Wolf wrote: 2009/1/24 Timothy Lee tim...@rochester.rr.com Thanks for the reply Harry-I'm fairly sure that I will need to lipo together the builds for Musicbrainz' Picard. So - in your experience what are all the options that I must set after a fresh src install to have a 10.5 setup building binaries for 10.4? Nothing more than setting the right options in your macports.conf and then see how far you get. 2009/1/24 Timothy Lee tim...@rochester.rr.com On Jan 24, 2009, at 3:36 AM, Ryan Schmidt wrote: On Jan 23, 2009, at 09:11, tim...@rochester.rr.com tim...@rochester.rr.com wrote: Joshua Root j...@macports.org wrote: Timothy Lee wrote: Do you know if its possible for me (on leopard) to build x86 code (all my macports ports) that will also run on Tiger? Short of physical access to an intel 10.4 install, is there anything I can do? Don't forget to use Reply All so the discussion goes to the list as well. There are no guarantees that this will work, but the way to do what you want would be to set universal_target to 10.4, universal_sysroot to /Developer/SDKs/MacOSX10.4u.sdk, and universal_archs to i386. Then build everything with +universal (best to add it to your variants.conf). Also set x11prefix to /usr/X11R6; Leopard's X11 prefix /usr/X11 does not exist on Tiger. If I do this, how will I be able to run the executables on my 10.5 setup? I ran into the same issue and simply decided to make links. On Tiger I simply did sudo ln -s /usr/X11R6 /usr/X11. If you build on Tiger and bring them to Leopard you do sudo ln -s /usr/X11 /usr/X11R6. This works only on your own system off course, unless you make an installer that checks whether it runs on Tiger or Leopard and creates a softlink accordingly. Harry ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Error after trying to upgrade installed
If direct mode is removed, I will use the following to work around: port destroot foo rsync -tpogHlr /opt/local/var/macports/build/foo/work/destroot/opt/local /opt [or wherever the destroot is] This would effectively turn macports into a simple way to build packages based on the maintainer's having discovered what needs patching and which configure options there are. Unfortunately, it kills the ability to track when a port needs to be upgraded. I do not wish to proliferate thousands of hard links to old ports and such on the system. But I am not asking for permission or support. -- Dr. Robert Delius Royar Associate Professor of English Morehead State University Morehead, Kentucky ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Universal Binaries
Hmm.. thats interesting. So, does that imply that aqua provides a X11-like API (w/ libs) or does that mean that the actual people writing packages (like openoffice) need to support aqua calls conditionally compiled in on detection of the aqua include/libs? thanks On Jan 24, 2009, at 1:25 PM, Harry van der Wolf wrote: It is something completely different. Most linux, netbsd and freebsd packages rely on X11. MacOSX has support for x11 but the native windowing system of MacOSX is aqua. Using the -x11 option means that you don't build for X11. An increasing amount of binaries and libraries support native aqua and in that case I don't want to build for X11. It's slower, bigger (X11 takes also memory and resources next to the already available aqua) and ugglier. But the last is off course a matter of taste. Note that some binaries and libraries are still considered beta under aqua (like Gimp) but function very good. If you take a look at openoffice (not macports) you see what I mean. It has already been available for MacOSX in X11 form for a long period. Recently they also released a 3.0 beta version for Aqua which works fine. NeoOffice is an aqua spin-off of OpenOffice and has a native Aqua interface for about 1½ years now. In versioning it runs a bit behind OpenOffice (OOO 3.0.x versus NOO 2.2.5) Note also that some packages that are compiled with -x11, simply miss the X11 gui but only compile/create the command line versions. Harry 2009/1/24 Timothy Lee tim...@rochester.rr.com Harry- You made reference to adding the -x11 tag to your variants.conf. By doing this, do you force macports to use Apple's X11? Or is it something else entirely different? thanks On Jan 24, 2009, at 12:59 PM, Harry van der Wolf wrote: 2009/1/24 Timothy Lee tim...@rochester.rr.com Thanks for the reply Harry- I'm fairly sure that I will need to lipo together the builds for Musicbrainz' Picard. So - in your experience what are all the options that I must set after a fresh src install to have a 10.5 setup building binaries for 10.4? Nothing more than setting the right options in your macports.conf and then see how far you get. 2009/1/24 Timothy Lee tim...@rochester.rr.com On Jan 24, 2009, at 3:36 AM, Ryan Schmidt wrote: On Jan 23, 2009, at 09:11, tim...@rochester.rr.com tim...@rochester.rr.com wrote: Joshua Root j...@macports.org wrote: Timothy Lee wrote: Do you know if its possible for me (on leopard) to build x86 code (all my macports ports) that will also run on Tiger? Short of physical access to an intel 10.4 install, is there anything I can do? Don't forget to use Reply All so the discussion goes to the list as well. There are no guarantees that this will work, but the way to do what you want would be to set universal_target to 10.4, universal_sysroot to /Developer/SDKs/MacOSX10.4u.sdk, and universal_archs to i386. Then build everything with +universal (best to add it to your variants.conf). Also set x11prefix to /usr/X11R6; Leopard's X11 prefix /usr/X11 does not exist on Tiger. If I do this, how will I be able to run the executables on my 10.5 setup? I ran into the same issue and simply decided to make links. On Tiger I simply did sudo ln -s /usr/X11R6 /usr/X11. If you build on Tiger and bring them to Leopard you do sudo ln -s /usr/X11 /usr/X11R6. This works only on your own system off course, unless you make an installer that checks whether it runs on Tiger or Leopard and creates a softlink accordingly. Harry ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Universal Binaries
It's definitely not the first. I assume they added code to support aqua and it's API's. I'm not a developer. just google for answers :) Harry 2009/1/24 Timothy Lee tim...@rochester.rr.com Hmm.. thats interesting.So, does that imply that aqua provides a X11-like API (w/ libs) or does that mean that the actual people writing packages (like openoffice) need to support aqua calls conditionally compiled in on detection of the aqua include/libs? thanks On Jan 24, 2009, at 1:25 PM, Harry van der Wolf wrote: It is something completely different. Most linux, netbsd and freebsd packages rely on X11. MacOSX has support for x11 but the native windowing system of MacOSX is aqua. Using the -x11 option means that you don't build for X11. An increasing amount of binaries and libraries support native aqua and in that case I don't want to build for X11. It's slower, bigger (X11 takes also memory and resources next to the already available aqua) and ugglier. But the last is off course a matter of taste. Note that some binaries and libraries are still considered beta under aqua (like Gimp) but function very good. If you take a look at openoffice (not macports) you see what I mean. It has already been available for MacOSX in X11 form for a long period. Recently they also released a 3.0 beta version for Aqua which works fine. NeoOffice is an aqua spin-off of OpenOffice and has a native Aqua interface for about 1½ years now. In versioning it runs a bit behind OpenOffice (OOO 3.0.x versus NOO 2.2.5) Note also that some packages that are compiled with -x11, simply miss the X11 gui but only compile/create the command line versions. Harry 2009/1/24 Timothy Lee tim...@rochester.rr.com Harry-You made reference to adding the -x11 tag to your variants.conf. By doing this, do you force macports to use Apple's X11? Or is it something else entirely different? thanks On Jan 24, 2009, at 12:59 PM, Harry van der Wolf wrote: 2009/1/24 Timothy Lee tim...@rochester.rr.com Thanks for the reply Harry- I'm fairly sure that I will need to lipo together the builds for Musicbrainz' Picard. So - in your experience what are all the options that I must set after a fresh src install to have a 10.5 setup building binaries for 10.4? Nothing more than setting the right options in your macports.conf and then see how far you get. 2009/1/24 Timothy Lee tim...@rochester.rr.com On Jan 24, 2009, at 3:36 AM, Ryan Schmidt wrote: On Jan 23, 2009, at 09:11, tim...@rochester.rr.com tim...@rochester.rr.com wrote: Joshua Root j...@macports.org wrote: Timothy Lee wrote: Do you know if its possible for me (on leopard) to build x86 code (all my macports ports) that will also run on Tiger? Short of physical access to an intel 10.4 install, is there anything I can do? Don't forget to use Reply All so the discussion goes to the list as well. There are no guarantees that this will work, but the way to do what you want would be to set universal_target to 10.4, universal_sysroot to /Developer/SDKs/MacOSX10.4u.sdk, and universal_archs to i386. Then build everything with +universal (best to add it to your variants.conf). Also set x11prefix to /usr/X11R6; Leopard's X11 prefix /usr/X11 does not exist on Tiger. If I do this, how will I be able to run the executables on my 10.5 setup? I ran into the same issue and simply decided to make links. On Tiger I simply did sudo ln -s /usr/X11R6 /usr/X11. If you build on Tiger and bring them to Leopard you do sudo ln -s /usr/X11 /usr/X11R6. This works only on your own system off course, unless you make an installer that checks whether it runs on Tiger or Leopard and creates a softlink accordingly. Harry ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Boost in MacPorts Issue
and also I have in my .bash_profile this export: export CXXFLAGS=-I /opt/local/include; Usually this should go into CPPFLAGS as it is for the preprocessor. Also, check that the Makefile or build system is honoring the environment variables. Maybe you need to pass this directly to make like: make CPPFLAGS='-I /opt/local/include' Just out of interest, which software is this and if it is Open Source, would it be worth to add it to MacPorts? There must be no space between -I and the path. Regards, Simon ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Universal Binaries
Exact same settings as below (except I'm only building i386), yet I'm still seeing DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.5'. Any Ideas? Also - I'm seeing Warning: Please fix or indicate this misbehavior (if it is intended) on every install saying that /mopt/local/bin is in violation - any ideas on this? thanks On Jan 23, 2009, at 9:14 AM, Harry van der Wolf wrote: Hi, I've setup my MacPorts 1.7 to always build universal (does not always work and sometimes needs a manual change of the Portfile). To do this I configured in the macports.conf the following: # Options for Universal Binaries (+universal variant) # MACOSX_DEPLOYMENT_TARGET universal_target10.4 # the SDK sysroot to use universal_sysroot /Developer/SDKs/MacOSX10.4u.sdk # machine architectures universal_archs ppc i386 and in variants.conf: +universal Harry 2009/1/23 Joshua Root j...@macports.org Timothy Lee wrote: Hey Joshua- Thanks for the reply. Do you know if its possible for me (on leopard) to build x86 code (all my macports ports) that will also run on Tiger? Short of physical access to an intel 10.4 install, is there anything I can do? Don't forget to use Reply All so the discussion goes to the list as well. There are no guarantees that this will work, but the way to do what you want would be to set universal_target to 10.4, universal_sysroot to /Developer/SDKs/MacOSX10.4u.sdk, and universal_archs to i386. Then build everything with +universal (best to add it to your variants.conf). - Josh ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: install slib-guile hangs on activation
anyone have any luck on this? I've got the same hang, and it blocks me from
installing gnucash.
I don't know much about slib or guile, or maybe I'd look into the code
myself...
TIA-
dan
Charles Day wrote:
On Fri, Jan 16, 2009 at 1:22 PM, Bryan Blackburn b...@macports.org wrote:
On Fri, Jan 16, 2009 at 01:50:37AM -0800, Charles Day said:
I can't seem to install slib-guile without a hang during the activation
stage. Any ideas? I looked through the tickets but they all seemed to
be
focused on slib-guile16.
It appears to be hanging on the post-activate code:
post-activate {
system ${prefix}/bin/guile -c \(use-modules (ice-9 slib)) (require
'new-catalog)\
}
Why, however, I can't answer so I think we need someone who knows guile.
It hangs on the first part of the code: (use-modules (ice-9 slib))
The require part never gets executed.
I can reproduce this on the command line:
$ guile
(use-modules (ice-9 slib))
hangs...
-Charles
Bryan
Cheers,
Charles
[...]
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
--
View this message in context:
http://www.nabble.com/install-slib-guile-hangs-on-activation-tp21495903p21644431.html
Sent from the MacPorts - Users mailing list archive at Nabble.com.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
ncurses failure (5.7)
I'm failing on installing ncurses (w/ +universal variant). I tried the instructions from this old post: David, In answer to your question, yes. There is a bug that has already been reported. You will have to clean ncurses and run the following commands in this exact order: sudo port -v clean ncurses udo port -v install ncursesw sudo port -v install ncurses HTH -Altoine But I still get 'stuck' with tic owning 90% of the CPU and this screen displayed: cd misc make DESTDIR=/mopt/local/var/macports/build/ _mopt_local_var_macports_sources_rsync .macports.org_release_ports_devel_ncurses/work/destroot install DESTDIR=/mopt/local/var/macports/build/ _mopt_local_var_macports_sources_rsync .macports.org_release_ports_devel_ncurses/work/destroot \ prefix=/mopt/local/ \ exec_prefix=/mopt/local/ \ bindir=/mopt/local//bin \ top_srcdir=.. \ srcdir=. \ datadir=/mopt/local//share \ ticdir=/mopt/local//share/terminfo \ source=terminfo.tmp \ THIS_CC=/usr/bin/gcc-4.0 \ THAT_CC=/usr/bin/gcc-4.0 \ /bin/sh ./run_tic.sh ** Building terminfo database, please wait... Running tic to install /mopt/local/var/macports/build/ _mopt_local_var_macports_sources_rsync .macports.org_release_ports_devel_ncurses/work/destroot/mopt/local// share/terminfo ... You may see messages regarding extended capabilities, e.g., AX. These are extended terminal capabilities which are compiled using tic -x If you have ncurses 4.2 applications, you should read the INSTALL document, and install the terminfo without the -x option. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: install slib-guile hangs on activation
On Sat, Jan 24, 2009 at 12:15 PM, danstadler danstad...@gmail.com wrote:
anyone have any luck on this? I've got the same hang, and it blocks me
from
installing gnucash.
The gnucash port depends on slib-guile16, not slib-guile, so it should still
be installable. It works for me. Are you trying to compile GnuCash yourself
rather than port install gnucash?
I don't know much about slib or guile, or maybe I'd look into the code
myself...
TIA-
dan
Charles Day wrote:
On Fri, Jan 16, 2009 at 1:22 PM, Bryan Blackburn b...@macports.org
wrote:
On Fri, Jan 16, 2009 at 01:50:37AM -0800, Charles Day said:
I can't seem to install slib-guile without a hang during the
activation
stage. Any ideas? I looked through the tickets but they all seemed to
be
focused on slib-guile16.
It appears to be hanging on the post-activate code:
post-activate {
system ${prefix}/bin/guile -c \(use-modules (ice-9 slib)) (require
'new-catalog)\
}
Why, however, I can't answer so I think we need someone who knows guile.
It hangs on the first part of the code: (use-modules (ice-9 slib))
The require part never gets executed.
I can reproduce this on the command line:
$ guile
(use-modules (ice-9 slib))
hangs...
-Charles
Bryan
Cheers,
Charles
[...]
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
--
View this message in context:
http://www.nabble.com/install-slib-guile-hangs-on-activation-tp21495903p21644431.html
Sent from the MacPorts - Users mailing list archive at Nabble.com.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: apache2 fails to install
On Jan 24, 2009, at 10:19, Geert De Deckere wrote: I'm completely stuck installing apache2. No idea what exactly is going wrong. It's a clean macports install (1.700). I even ran a manual selfupdate. Installing git-core went flawless, it's just apache2 that is causing problems. Thanks for helping me out. $ sudo port install apache2 Password: --- Building db46 Error: Target org.macports.build returned: shell command cd /opt/ local/var/macports/ build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_datab ases_db46/work/db-4.6.21/build_unix make all returned error 2 Command output: /bin/sh ./libtool --mode=compile /usr/bin/gcc-4.0 - c -O2 -I../dist/.. -I/opt/local/include ../dist/../db_dump185/ db_dump185.c /usr/bin/gcc-4.0 -c -O2 -I../dist/.. -I/opt/local/include ../ dist/../db_dump185/db_dump185.c -fno-common -DPIC -o .libs/ db_dump185.o ../dist/../db_dump185/db_dump185.c: In function 'main': ../dist/../db_dump185/db_dump185.c:211: warning: assignment makes pointer from integer without a cast ../dist/../db_dump185/db_dump185.c:213: warning: assignment makes pointer from integer without a cast ../dist/../db_dump185/db_dump185.c:228: error: 'struct __db' has no member named 'seq' ../dist/../db_dump185/db_dump185.c:228: error: 'R_NEXT' undeclared (first use in this function) ../dist/../db_dump185/db_dump185.c:228: error: (Each undeclared identifier is reported only once ../dist/../db_dump185/db_dump185.c:228: error: for each function it appears in.) ../dist/../db_dump185/db_dump185.c:233: error: 'struct __db' has no member named 'seq' ../dist/../db_dump185/db_dump185.c: In function 'db_hash': ../dist/../db_dump185/db_dump185.c:261: error: 'struct __db' has no member named 'internal' ../dist/../db_dump185/db_dump185.c:263: error: 'struct __db' has no member named 'internal' ../dist/../db_dump185/db_dump185.c: In function 'db_btree': ../dist/../db_dump185/db_dump185.c:288: error: 'struct __db' has no member named 'internal' make: *** [db_dump185.lo] Error 1 Error: The following dependencies failed to build: apr-util db46 sqlite3 readline pcre Error: Status 1 encountered during processing. I believe you have an old version of readline in /usr/local/lib interfering with the db46 build process. Please see this ticket where the same problem was reported against db44: http://trac.macports.org/ticket/12040 Because software in /usr/local often interferes with MacPorts ports, it's a good idea to not have anything in /usr/local when using MacPorts. For now, you can rename /usr/local to /usr/local-off: sudo mv /usr/local /usr/local-off Then clean db46 and try again: sudo port clean db46 sudo port install apache2 If that works, you'll know that your software in /usr/local had interfered before. I recommend you look through everything you have in /usr/local-off, decide whether you still need it, and if you do, install the corresponding port with MacPorts. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Universal Binaries
On Jan 24, 2009, at 14:01, Timothy Lee wrote: Exact same settings as below (except I'm only building i386), yet I'm still seeing DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.5'. Any Ideas? Only building i386 -- does that mean you are not using the +universal variant? If so, the universal_target setting is not used, as I believe Josh mentioned earlier in this thread. Also - I'm seeing Warning: Please fix or indicate this misbehavior (if it is intended) on every install saying that / mopt/local/bin is in violation - any ideas on this? Did you have a slash at the end of your --prefix when you configured -- i.e. ./configure --prefix=/mopt/local/bin/? If so, reconfigure and omit the slash at the end -- i.e. ./configure --prefix=/mopt/ local/bin (and then of course make and sudo make install). This will be fixed in MacPorts 1.8.0. http://trac.macports.org/ticket/13789 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Installing Apache2 on Leopard
On Jan 24, 2009, at 07:48, Scott Haneda wrote: On Jan 24, 2009, at 5:16 AM, Jason Hirsh wrote: I have successfully accomplished this... but frankly the process just doesn't sit well with my sense of things.. I now have two complete Apache installations... and have to do work arounds to get the port installation to work (apache2ctl etc) Isn't there away to install the port version over the orginal installation? it just seems the more orderly way of doing things No, and you will get used to it as well. The first time Apple update httpd.conf you will be thankful, and they have done so in the past. Apple also runs periodic scripts that roll out your logs. Compressing them is nice, rolling them to deletion is not. Apple's kit is more in line with casual serving, not something long term and to be hit hard. Not to say it can not, but it will bite you. The main thing is, good luck getting php even moderately usable with Apple's stuff, and they will break it eventually. Ports needs some caution as well, as an upgrade, iirc, can nuke your settings as well. This is up to the individual ports. For apache2 this was recently fixed: http://trac.macports.org/ticket/8605 For other ports, please file tickets. I too did not like the change in command I had to learn, but you quickly learn to appreciate the isolation. You can solve your issues in a few simple ways. Add /opt/local/bin and whatever /opt paths you want to your $PATH, first in order. Those commands will now take priority. You can also just move aside apachectl and symblink it to the ports version. In the end, really, how often are you restarting apache anyway. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
