Re: ENV to macports
I thought choosing which version was an either/or scenario. Are you saying that its possible to choose more than one per build? On Feb 11, 2009, at 5:46 PM, Joshua Root wrote: Tim Lee wrote: This may have been answered with Josh's Ostrich Algo explanation- but, how could macports (on 10.5 darwin_9) be forced to link/ build for darwin_8? You could try selecting darwin_8 manually in addition to darwin_9, or hacking portmain.tcl to select darwin_8 instead of darwin_9. Whether either of those approaches would work, and if so, which one, would depend on each specific port. - 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: ENV to macports
So, if targeting 10.4 from 10.5, would you recommend +darwin_8 - darwin_9 in my variants.conf? Thanks Josh! On Feb 11, 2009, at 8:36 PM, Joshua Root wrote: Timothy Lee wrote: I thought choosing which version was an either/or scenario. Are you saying that its possible to choose more than one per build? They are actually just variants under the hood. The only difference compared to normal variants is that platform variants are automatically selected based on the platform you're building on. Selecting platform variants manually is normally a really bad idea, but if you need to target a different platform, it just might work in some cases. - 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: ENV to macports
Unfortunately, no. I guess that I could start working through the issues one by one (and posting tickets) but I was hoping for a 'quick' turn and move on to the actual app I'm using macports for. It seems like 'sudo port -d install qt4-mac' fails on every third dependency (+universal). Tim On Feb 4, 2009, at 10:56 PM, Ryan Schmidt wrote: So the underlying issue is: On Feb 3, 2009, at 21:54, Timothy Lee wrote: I can't compile universal. The project that I'm building for includes too many macports ports and I can't get all of the macports to successfully install. Have these issues already been reported via MacPorts tickets? ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
ENV to macports
Hello! Quick question... How do I tell macports to use my CFLAGS, CXXFLAGS, LDFLAGS, and my MACOSX_DEPLOYMENT_TARGET from my environment when building an app?? Thanks! Tim ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: ENV to macports
Is it possible to 'pass in' environment variables to the 'port
install' command?
Or is the only way to pass something like CFLAGS to macports is
through a portfile?
For example... I would like to
$sudo port install pan2 CFLAGS=-isysroot /Developers/SDKs/
MacOSX10.4u.sdk
thoughts?
On Feb 3, 2009, at 9:46 PM, Rainer Müller wrote:
Bradley Giesbrecht wrote:
If your building a Portfile here is a piece of the postfix Portfile:
variant ldap description add ldap support via openldap {
depends_lib-append port:openldap
set CCARGS [concat ${CCARGS} -DHAS_LDAP]
set AUXLIBS [concat ${AUXLIBS} -lldap -llber]
}
`set' does not affect the environment at all, these are just local Tcl
variables.
If you need special variables in the environment for building, specify
configure.env (and build.env) in the Portfile. But also note there are
predefined options to set CFLAGS, LDFLAGS and others, namely
configure.cflags, configure.ldflags, etc. They should be preferred
over
manipulating configure.env.
They are explained in the guide:
http://guide.macports.org/#reference.phases.configure
HTH,
Rainer
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: ENV to macports
So here is the issue... I can't compile universal. The project that I'm building for includes too many macports ports and I can't get all of the macports to successfully install. I DO have a 10.4 PPC machine that has successfully built everything that I need (obviously with no args added, its targeting 10.4). I want to build a 10.4 i386 build on my leopard i386 machine. When this is complete, I'll 'lipo' together all pieces of each individual tree (using mozilla's 'unify' script). I have tried adding +universal to my variants.conf and changing my macports.conf to universal_target to 10.4, universal_sysroot to the 10.4 sdk, and universal_archs to ONLY i386 (as per your suggestion). Unfortunately this didn't work (too many assumptions in macports regarding the +universal variant and having at least two archs present). So now my only option is to explicitly drive into macports my CFLAGS, LDFLAGS, and most importantly my MACOSX_DEPLOYMENT_TARGET vars. Is it possible to 'pass in' this information to macports? Thanks Tim On Feb 3, 2009, at 10:34 PM, Joshua Root wrote: Timothy Lee wrote: Is it possible to 'pass in' environment variables to the 'port install' command? Or is the only way to pass something like CFLAGS to macports is through a portfile? For example... I would like to $sudo port install pan2 CFLAGS=-isysroot /Developers/SDKs/ MacOSX10.4u.sdk thoughts? Why do you need to set the sysroot? The universal_sysroot setting from macports.conf will be used when building with the universal variant, and when building non-universal an SDK shouldn't be needed. If pan2 does need it for some reason, then it should be added in the portfile. It is *possible* to tell MP to use arbitrary parts of your environment, but it's almost certainly a bad idea. - Josh ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: dbus failed to activate
Hm... the portion regarding startupitem_type in macports.conf makes it
sound like setting this variable to none is the 'big hammer' and
that all portfiles specifying startup items are explicitly overridden.
Is this not true?
On Jan 27, 2009, at 1:16 AM, Ryan Schmidt wrote:
On Jan 26, 2009, at 22:07, Timothy Lee wrote:
It looks like dbus is failing to activate on my setup. I have two
active macport installs (one in /opt/local and one in /tigeropt/
local). I'm very careful to be using the correct paths based on
which version I'm working with. I installed my /opt/local dbus
first and the /tigeropt/local second. In my /tigeropt/local/etc/
macports/macports.conf I have startupitem_type set to 'none'.
This is the output I'm receiving when I try to install the /tiger/
opt dbus:
--- Activating dbus @1.2.12_4+universal
Error: Target org.macports.activate returned: Image error: /Library/
LaunchAgents/org.freedesktop.dbus-session.plist already exists and
does not belong to a registered port. Unable to activate port dbus.
Warning: the following items did not execute (for dbus):
org.macports.activate
Error: The following dependencies failed to build: dbus jpeg libmng
autoconf help2man gettext libiconv gperf ncurses ncursesw p5-locale-
gettext perl5 perl5.8 m4 automake lcms tiff zlib libtool libpng
mysql5 openssl postgresql83 bison libxml2 libxslt ossp-uuid
readline sqlite3 unixODBC
Error: Status 1 encountered during processing.
Both copies of the port want to install the same file, /Library/
LaunchAgents/org.freedesktop.dbus-session.plist. This is a startup
item of sorts that Mac OS X looks for at system startup to start a
service. This file cannot be placed in a different directory,
otherwise it will not have any effect. That is why this file's
location is not confined to ${prefix} and why its location is not
configurable. So with the way the dbus port is currently written,
I'm afraid you cannot have it installed and activated simultaneously
in more than one MacPorts install on a single machine.
The same would be true of any port that uses the startupitem
portfile keywords or manually installs launchd plists.
Some such ports offer +no_startupitem variants to turn off the
installation of such files; see e.g. the apache2 port. If that is
appropriate for dbus, such a variant could be added there.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
dbus failed to activate
Hello- It looks like dbus is failing to activate on my setup. I have two active macport installs (one in /opt/local and one in /tigeropt/ local). I'm very careful to be using the correct paths based on which version I'm working with. I installed my /opt/local dbus first and the /tigeropt/local second. In my /tigeropt/local/etc/macports/ macports.conf I have startupitem_type set to 'none'. This is the output I'm receiving when I try to install the /tiger/opt dbus: --- Activating dbus @1.2.12_4+universal Error: Target org.macports.activate returned: Image error: /Library/ LaunchAgents/org.freedesktop.dbus-session.plist already exists and does not belong to a registered port. Unable to activate port dbus. Warning: the following items did not execute (for dbus): org.macports.activate Error: The following dependencies failed to build: dbus jpeg libmng autoconf help2man gettext libiconv gperf ncurses ncursesw p5-locale- gettext perl5 perl5.8 m4 automake lcms tiff zlib libtool libpng mysql5 openssl postgresql83 bison libxml2 libxslt ossp-uuid readline sqlite3 unixODBC Error: Status 1 encountered during processing. thanks for any input! ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Universal Binaries
Ryan- Thanks for the tip on not adding the '/' to the --prefix - that fixed the problem. In regards to the +universal variants - my universal_target only contains i386 as suggested by Josh. My other settings look like this: # Options for Universal Binaries (+universal variant) # MACOSX_DEPLOYMENT_TARGET universal_target10.4 # the SDK sysroot to use universal_sysroot /Xcode3_0/SDKs/MacOSX10.4u.sdk # machine architectures universal_archs i386 Again- my variants.conf only contains +universal and my macports.conf as the variants_conf path set correctly - yet I still see the deployment is being set to 10.5. Any suggestions? thanks On Jan 24, 2009, at 8:21 PM, Ryan Schmidt wrote: 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: Universal Binaries
Harry- Thanks for the response! On Jan 25, 2009, at 3:37 PM, Harry van der Wolf wrote: 2009/1/25 Timothy Lee tim...@rochester.rr.com Ryan- Thanks for the tip on not adding the '/' to the --prefix - that fixed the problem. In regards to the +universal variants - my universal_target only contains i386 as suggested by Josh. My other settings look like this: # Options for Universal Binaries (+universal variant) # MACOSX_DEPLOYMENT_TARGET universal_target10.4 # the SDK sysroot to use universal_sysroot /Xcode3_0/SDKs/MacOSX10.4u.sdk # machine architectures universal_archs i386 Again- my variants.conf only contains +universal and my macports.conf as the variants_conf path set correctly - yet I still see the deployment is being set to 10.5. Any suggestions? thanks The line # machine architectures universal_archs i386 is not correct. Sorry for maybe explaining the obvious but do you know what universal means? It means that it will run on both the ppc as well as the intel platform. In it's basic form this means that you will need to make a 32bit binary/library that is both ppc and i386. If you really want to build for all options you should even make 4way architecture builds for 32bit and 64bit, meaning: ppc, i386 (intel single core), ppc64 (G5) and x86_64 (intel core duo and better). ppc can be ppc (runs on =G3), ppc740 (runs on =G4) and ppc750 (runs on =G5 in 32bit mode). So to be able to build universal for all systems =G3 you need ppc and i386. This means that you need to specify # machine architectures universal_archs ppc i386 With your line you only build for i386. This is not universal. Macports does not yet support the 64bit builds. (When I build 4way architecture builds (occasionally for Hugin) I build them outside macports.) Yep - all too familiar with the different architectures. My reasoning for adding i386 on a line by itself is that I only care about i386 builds (suggested by Joshua). I have a ppc 10.4 machine that I am performing my 10.4 builds on and when the i386-10.4-compatible builds are complete on my 10.5 machine, I will 'lipo' the ppc and i386 builds together. Unfortunately my target build (Musicbrainz Picard v0.11) currently needs to be 'lipo'-ed together due to endian-issues. With regard to your Again- my variants.conf only contains +universal and my macports.conf as the variants_conf path set correctly - yet I still see the deployment is being set to 10.5. Please check whether /Xcode3_0/SDKs/MacOSX10.4u.sdk is really the correct path. If it can't find the 10.4u.sdk it might default to the 10.5.sdk using the 0.5 deplyment target (which is default for 10.5). My macports is using the 10.4u.sdk for deployment target 10.4.This functions for me but I do have my sdk's in the default /Developer/ SDKs/MacOSX10.4u.sdk. Yes, I have BOTH xcode 2.5 and 3.0 installed. Why? Aaron Hillegas's Cocoa book uses Xcode 2.5 and there are many changes in Xcode 3.0 that make using the book difficult to use to learn cocoa. So - I have 2.5 installed for educational purposes and Xcode 3.x installed to 'stay current. My directories are /Xcode3_0/SDKs/ and /Xcode2_5/SDKs/. When build with the -v flag in macports I do see it properly linking against /Xcode3_0/SDKs/MacOSX10.4u.sdk. For some reason the I'm still seeing 10.5 show up in my deployment target though. You might even check if /Developer/SDKs/MacOSX10.5.sdk exists. Macports runs on top off gcc. I'm not sure how solid macports can overrule gcc standard settings if gcc finds a 10.5.sdk in / Developer. (I have no experience with that. It's only guessing on this part). Finally: you mention /mopt/local/bin. Do you also have an old default /opt/local/bin that still can be found via the path? So - again, to be confusing :) I keep a 10.5 macports in /opt and my 10.4 'compatible' macports install in /mopt/ (actually i just changed it to /tigeropt/). All paths are properly set in each shell that I use based on which macports install I am using (I have my normal .bash_profile use my /opt/ install and if I want to use my tiger install I explicitly source a file that changes all paths with / opt in it to /tigeropt/ in my env. All configuration files reference the correct (version-dependent) macports install. I've even tried changing my /opt/local/etc/macports/macports.conf's universal_target (when using my /tigeropt/ paths) to see if somehow I was incorrectly reading my /opt/ config files - and that didn't work either - still receiving '10.5' as my deployment target. Harry ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: ncurses failure (5.7)
Seems like this problem might be 'real' - has anyone else observed it? On Jan 24, 2009, at 5:27 PM, Timothy Lee wrote: 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 ___ 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
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
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
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
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: Universal Binaries
I just compile 1.7.0 from source and my macports.conf universal_target has a 10.4 next to it. However, when I compile on my Leopard machine, I see DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.5'. I thought universal_targe would set the MACOSX_DEPLOYMENT_TARGET. Am I wrong? On Jan 22, 2009, at 4:19 AM, Ryan Schmidt wrote: On Jan 21, 2009, at 21:22, Timothy Lee wrote: 1. What is the current state of the +universal variant? Do most ports work? It's unknown if most ports work. If it doesn't work for ports you want, file tickets. Note that 64-bit universal support is likely more broken than plain 32-bit universal support. It's possible we could fix this situation a great deal by switching ports to the new universal build strategy available in the merge- universal portgroup. 2. How is dependencies and the +universal variants used? Meaning if I type sudo port install pan2 +universal will that pass the variant to all dependencies that get built before pan2? Yes, as with all variants, the variants you ask for will get passed down to any other port that needs to get *installed* (but not to any other port that's needed that you already have installed). If you want to install X universal, and X depends on Y and Z, and Y and/or Z are already installed, you must ensure that Y and Z are already universal, otherwise you will get (possibly cryptic) errors installing X universal. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Universal Binaries
Hi Macports people! Two questions: 1. What is the current state of the +universal variant? Do most ports work? 2. How is dependencies and the +universal variants used? Meaning if I type sudo port install pan2 +universal will that pass the variant to all dependencies that get built before pan2? Thanks! Tim ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Liger: It's pretty much my favorite animal
Thanks for the reply Ryan! I've noticed this App Note published by Apple: http://developer.apple.com/technotes/tn2002/tn2064.html It looks like the universal_target (really the MACOSX_DEPLOYMENT_TARGET=10.4) might be the only thing required to build tiger-compatible apps on leopard. Does anyone have any other insight into this? Thanks Tim On Jan 19, 2009, at 9:49 PM, Ryan Schmidt wrote: On Jan 19, 2009, at 20:05, Timothy Lee wrote: New to this list. I've been working on porting Musicbrainz Picard to the mac (dependencies fulfilled by MacPorts) over the past few weeks. While working through some of the issues, a few questions popped up: 1. I'm building on Leopard (i386) but was hoping to target Tiger. What (universal-ity aside) are the proper steps to compile everything on my Leopard install for Tiger? Is it simply setting universal_target to 10.4 in my macports.conf ? Or are there other variables that need to be set? What packages do I need to have installed (the 10.4 SDK) ? 2. For building a Tiger Macports on my Leopard, should I simply download the 10.4 package installer and life will be fine? Welcome to MacPorts! You could try setting universal_sdkroot to the 10.4u SDK, universal_target to 10.4 and x11prefix to /usr/X11R6. However, building on Leopard for Tiger, or any other such cross-compilation, is ill-tested in MacPorts and not supported. To truly test this, use a real Tiger machine. If you don't have one, perhaps someone else who does can test it for you. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Liger: It's pretty much my favorite animal
Hello all! New to this list. I've been working on porting Musicbrainz Picard to the mac (dependencies fulfilled by MacPorts) over the past few weeks. While working through some of the issues, a few questions popped up: 1. I'm building on Leopard (i386) but was hoping to target Tiger. What (universal-ity aside) are the proper steps to compile everything on my Leopard install for Tiger? Is it simply setting universal_target to 10.4 in my macports.conf ? Or are there other variables that need to be set? What packages do I need to have installed (the 10.4 SDK) ? 2. For building a Tiger Macports on my Leopard, should I simply download the 10.4 package installer and life will be fine? Thanks a bunch for any help! Tim Lee ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
