Hi,
We now have the XCode command line tools since March 2012. An initiative
you probably have heard of and started by Kenneth Reitz (0,1) and now fully
supported by Apple. They can be downloaded from within XCode 4.3.x or
directly as a command line tool set. This last is of course the preferred
Sorry, single reply instead of reply all.
-- Forwarded message --
From: Harry van der Wolf hvdw...@gmail.com
Date: 2011/3/23
Subject: Re: xcode4 - How can we restore ppc/ppc64 as well as full 10.4/10.5
SDK support to Xcode 4? - Stack Overflow
To: Jeremy Huddleston jerem
Note that Apple is gradually stopping support for ppc64.
Take for example the QTKit.framework, which is part of the quickTime player
and resides inside /System/Library. It is nowadays only x86_64 i386
ppc7400.
Lots of graphic applications, and not only video like are linked against
the
Hi,
2010/10/4 Ryan Schmidt ryandes...@macports.org
On Oct 3, 2010, at 22:52, Nikos Chantziaras wrote:
I tried this and added macosx_deployment_target 10.5. However, the
wrong compilers are used then. Instead of:
/usr/libexec/gcc/i686-apple-darwin10/4.2.1
2010/10/4 Brandon S Allbery KF8NH allb...@kf8nh.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/3/10 21:21 , Nikos Chantziaras wrote:
Thanks, Ryan. I suppose I will need to find someone who has a 10.5
installation to do a sanity check for me before I release any binaries
tagged
2010/10/4 Nikos Chantziaras rea...@arcor.de
On 10/04/2010 09:07 PM, Brandon S Allbery KF8NH wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/3/10 21:21 , Nikos Chantziaras wrote:
Thanks, Ryan. I suppose I will need to find someone who has a 10.5
installation to do a sanity
Sorry, direct reply instead of reply to macports.
2010/10/4 Harry van der Wolf hvdw...@gmail.com
2010/10/4 Jeremy Huddleston jerem...@macports.org
On Oct 4, 2010, at 04:38, Harry van der Wolf wrote:
I simply build with gcc 4.0.1 for i386/ppc and with 4.2.x for 64bit (I
also
build
2010/9/8 Joshua Root j...@macports.org
This is implemented more sanely, but is still completely unsupported, in
1.9.0+. Just set macosx_deployment_target to whatever version you want
(e.g. 10.5) in macports.conf. Base will then set
MACOSX_DEPLOYMENT_TARGET in the environment (which is
2010/9/9 Harry van der Wolf hvdw...@gmail.com
2010/9/8 Joshua Root j...@macports.org
This is implemented more sanely, but is still completely unsupported, in
1.9.0+. Just set macosx_deployment_target to whatever version you want
(e.g. 10.5) in macports.conf. Base will then set
2010/9/9 Joshua Root j...@macports.org
On 2010-9-9 17:17 , Ryan Schmidt wrote:
My understanding from what Joshua wrote above is that your macports.conf
should be expanded by only the following line:
macosx_deployment_target 10.5
And it sounds like you do not set the SDK manually;
2010/9/8 Ryan Schmidt ryandes...@macports.org
On Sep 8, 2010, at 02:17, Harry van der Wolf wrote:
In previous versions of macports it was possible to specify an SDK and a
macosx-version-min (-mmacosx-version-min from CFLAGS).
When switching from Leopard to Snow Leopard about 6 weeks ago I
2010/7/29 chrissam bedpot...@gmail.com
Ryan Schmidt-24 wrote:
Yes, wine can only compile for i386. It cannot compile for x86_64, ppc,
or
ppc64, and the wine ports ensure this.
I agree, Harry, I see -arch i386 -arch ppc in the log too. Chrissam,
are
you requesting libsdl_image be
2010/7/28 chrissam bedpot...@gmail.com
Ryan Schmidt-24 wrote:
Yes, MacPorts should be taking care of dependencies for you. But it looks
like it is not, for reasons I don't understand.
To work around this for now, you can manually install all of wine-devel's
dependencies, like this:
, at 08:06, Harry van der Wolf wrote:
2010/7/22 Ryan Schmidt ryandes...@macports.org
On Jul 22, 2010, at 06:51, Harry van der Wolf wrote:
This simplifies the Portfile. Building is succesful but.. the
install_name is still not in the libraries.
The setting from the cmake portgroup
2010/7/22 Ryan Schmidt ryandes...@macports.org
On Jul 21, 2010, at 08:35, Harry van der Wolf wrote:
Thanks for your reply. I was already typing a mail to mention that I had
found it. I grepped for other Portfiles having sourceforge:.
I came to:
master_sitessourceforge:hugin
2010/7/22 Ryan Schmidt ryandes...@macports.org
On Jul 22, 2010, at 04:20, Harry van der Wolf wrote:
The resulted build, both hugin itself as the hugin dylibs, don't have the
correct path when questioned with the otool -L bin or lib. They do for
the external libraries they are linked to like
Hi,
currently hugin is at svn version 2903 which is way too old. I'm trying to
update the port to the current stable version 2010.0 which can be found at
http://sourceforge.net/projects/hugin/files/hugin and than at
hugin-2010.0/hugin-2010.0.0.tar.gz
Note that the folder name is hugin-2010.0 and
time (if succesful).
Harry
2010/7/21 Joshua Root j...@macports.org
On 2010-7-21 20:05 , Harry van der Wolf wrote:
Hi,
currently hugin is at svn version 2903 which is way too old. I'm trying
to update the port to the current stable version 2010.0 which can be
found at http
Hi Zachary,
It's great that you try to build hugin via Macports. However, the hugin
version is version 7.0 svn 2903 and autopano-sift-c macports is also svn
2903. Both are old versions from October 2008. We had already 4 new versions
with great new added functionality and we are working on the
2010/7/18 Ryan Schmidt ryandes...@macports.org
On Jul 18, 2010, at 04:00, Harry van der Wolf wrote:
It's great that you try to build hugin via Macports. However, the hugin
version is version 7.0 svn 2903 and autopano-sift-c macports is also svn
2903. Both are old versions from October 2008
Hi,
When I want to create a universal build that needs to be built in separate
steps due to differences in ppc and i386 (big_endian or little_endian or SSE
dependencies), how do I specify that in the Portfile?
It used to be necessary to script it with either
if { [variant_isset universal] }
2010/7/18 Ryan Schmidt ryandes...@macports.org
On Jul 18, 2010, at 09:02, Ryan Schmidt wrote:
On Jul 18, 2010, at 08:32, Harry van der Wolf wrote:
When I want to create a universal build that needs to be built in
separate steps due to differences in ppc and i386 (big_endian
Hi,
I upgraded to 1.9.1 yesterday and tried to do an upgrade outdated. I
received this shell command failed for dbus-glib (0.86_1) and I filed a
ticket for it at the macports trac (see
herehttp://trac.macports.org/ticket/25581)
as it also failed on 1.8.1.
However, I now get the same shell command
2010/7/9 Ryan Schmidt ryandes...@macports.org
On Jul 9, 2010, at 09:48, Harry van der Wolf wrote:
I received this shell command failed for dbus-glib (0.86_1) and I filed
a ticket for it at the macports trac (see here) as it also failed on 1.8.1.
However, I now get the same shell command
Hi,
2010/5/21 Michael_google gmail_Gersten keybou...@gmail.com
port search svn turns up 22 ports, but does not turn up subversion.
It is exactly as you say :-)
Use: port search subversion
Harry
___
macports-users mailing list
When I try to install whichever python package, I get the following error:
distutils.errors.DistutilsPlatformError: $MACOSX_DEPLOYMENT_TARGET mismatch:
now 10.5 but 10.4 during configure
When I do: which python, I:q
get:
/opt/local/bin/python
And python --version gives Python 2.6.4
in
2010/3/4 Daniel J. Luke dl...@geeklair.net
On Mar 4, 2010, at 7:43 AM, Harry van der Wolf wrote:
In my macports.conf I have since a very long time (over multiple macports
versions) the following setting.
# MACOSX_DEPLOYMENT_TARGET
universal_target10.4
I would remove
Hi,
There is a bugfix for this and it is also filed as a bug.
http://trac.macports.org/ticket/21007
The patch works just fine (last post tells it correctly). I had to apply it
on a Tiger G5 of a frined of mine last weekend.
Harry
2009/11/30 Ivan Kawaler ink_b...@att.net
I haven't been
What if you install: xorg-libXrandr and/or xorg-randrproto and/or xrandr?
like sudo port install xorg-libXrandr xorg-randrproto xrandr
It's just a guess from my side
Harry
2009/5/31 Merton Campbell Crockett m.c.crock...@roadrunner.com
I've attempted to upgrade Wireshark to the latest
PM, Harry van der Wolf wrote:
Hi,
I have the following settings in my macports.conf:
# MACOSX_DEPLOYMENT_TARGET
universal_target10.4
# the SDK sysroot to use
universal_sysroot /Developer/SDKs/MacOSX10.4u.sdk
# machine architectures
universal_archs ppc i386
I'm now
]/.fonts-cache-1 file and a bunch of
*.cache-2 files in /Users/[user name]/.fontconfig. Do I need to do anything
with those files?
Thanks,
On Wed, May 20, 2009 at 11:46 AM, Harry van der Wolf hvdw...@gmail.comwrote:
Based on your logs it looks as if your font cache is updated (on every
With regard to X11 (no gnucash experience). After upgrading to 10.5.7 you
should also install the new X11 from
http://xquartz.macosforge.org/trac/wiki/X112.3.3.
Harry
2009/5/20 Jeremy Huddleston jerem...@macports.org
On May 19, 2009, at 20:46, cory steers wrote:
A little background: I
Based on your logs it looks as if your font cache is updated (on every
startup?). This should happen only once until some major changes take place
regarding fonts, updates on fontconfig or freetype, or programs heavily
using fontconfig and/or freetype. Sometimes it can happen that your font
cache
ntop needs to write to a couple of locations within /opt/local.
Did you start ntop with sudo, like sudo ntop
Harry
2009/5/4 Zav - Public zavpub...@mac.com
Can anyone launch the current version of ntop from the terminal without it
immediately quitting? If so, what did you do to launch it?
I also tried to compile libGLEW universally, both via MacPorts and outside
macports. The make files and configures scripts are so old that they do not
allow to build a universal dylib on OSX. It doesn't even allow you to just
cross-compile libglew dynamically without lot's of patching in the make
From what I understand is that you want to do this from within XCode. In
that case it is very simple.
In XCode double-click your target. You will get the target app name info
screen, go to the Build tab and scroll down.
In the header Search Paths you specify /opt/local/include. (If the
2009/1/25 Joshua Root j...@macports.org
Timothy Lee wrote:
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:
2009/1/26 Vincent Lefevre vincent-opd...@vinc17.org
On 2009-01-24 19:25:51 +0100, 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
(Sorry, my previous mail was a direct mail and not to the macports users
group).
Why don't you use the ready available universal dmg available for OSX (
http://musicbrainz.org/ftpmirror/pub/musicbrainz/users/robert/picard-0.9.0beta1-build2.dmg
)
Harry
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
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?
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
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
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_target
Please check which curl version is used. curl is part of MacOsx and resides
in /usr/bin/curl. Macports curl is in /opt/local/bin. If I compare them I
see that they are not equally compiled with equal dependencies on my system
(10.5.6). Normally when macports is installed it places /opt/local/bin
macosx curl gives you a different
message/error.
Ok, I'll give that a try.
___
Craig Hoffman
iChat / AIM: mountain.dog
___
On Jan 23, 2009, at 10:51 AM, Harry van der Wolf wrote:
Please check which curl version is used. curl is part of MacOsx
on ppc too.
From this point also libsamplerate builds correctly universally.
x264 does not build correctly universally and the Portfile needed to be
patched (see attached).
xvid builds correctly as such but ignores deployment target (need to sort
that out).
Harry
2008/8/22 Harry van der Wolf
Hi,
I'm currently on Tiger but I'm planning to move to Leopard. I build bundles
for 2 open source projects currently by hand compiling almost every
library as universal. I'm trying to move to MacPorts as that's much simpler
and MacPorts has much improved in the Universal section.
If I build an
nice for mail clients that do automatic threading.
Is that an option here?
Harry
2008/8/22 Harry van der Wolf [EMAIL PROTECTED]
Thanks for the hints and the fast response. The options
universal_target10.4
universal_sysroot /Developer/SDKs/MacOSX10.4u.sdk
universal_archs
[EMAIL PROTECTED]
On Aug 3, 2008, at 10:52, Harry van der Wolf wrote:
I'm working on the pango Portfile to make it a real two-step Universal
compilation.
What is the matter with pango +universal the way it works now?
Pango is ENDIAN dependent and was built incorrectly within MacPorts
Well, I think I solved it in a clean way. See attached Portfile-rrdtool.diff
file for the Portfile.
It works fine on my system.
Harry
2008/8/3 Ryan Schmidt [EMAIL PROTECTED]
On Aug 3, 2008, at 02:25, Harry van der Wolf wrote:
About the --enable-atsui option. I hadn't checked that since
I'm working on the pango Portfile to make it a real two-step Universal
compilation. I modified the portfile and did a sudo port clean pango and
even checked whether the
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_pango/work/
had been removed
Sorry, I can't get used to not directly hit reply instead of first selecting
the macports-users.. mail address.
-- Forwarded message --
From: Harry van der Wolf [EMAIL PROTECTED]
Date: 2008/8/2
Subject: Re: more woes with php 5.2.6
To: Tabitha McNerney [EMAIL PROTECTED
To get cairo compiled in macports using the correct SDK I used an extremely
dirty hack (See attached Portfile).
The reason for this is that enabling '-isysroot $SDK_path' treats all other
includes as SDK relative path. I don't know how to get around that, so I
used a dirty hack (copied from
: This enables you to build Gtk-Quartz applications: Very nice!
Harry
-- Forwarded message --
From: Harry van der Wolf [EMAIL PROTECTED]
Date: 2008/8/1
Subject: Dirty hack to get cairo compiled universally
To: MacPorts Users macports-users@lists.macosforge.org
To get cairo compiled
One last thing to check is whether Macports /opt/local/bin comes before
/usr/bin (where Aplle bison resides) in your PATH.
From the terminal do a set | grep PATH
It should have /opt/local/bin as first entry, otherwise it will still pick
the old binaries from Apple and Xcode.
If it already has
Sorry,
should be tpo macports users group
2008/7/28 Harry van der Wolf [EMAIL PROTECTED]
You do not tell us whether you are using a cmake or a .configure config
tool, but in case it is an automake .configure tool, you should use
something like:
export CFLAGS=-I/opt/local/include
export
This is most probably a bison bug (solved Febr 2008 for OSX). The bison
version that comes with XCode is too old. Try using the bison from macports:
sudo port install bison and try again.
Harry
2008/7/28 Michael Thon [EMAIL PROTECTED]
On Jul 28, 2008, at 7:17 PM, Harry van der Wolf wrote
Hi,
As Macports does not build all ports as universal and as some of the
universal ports are not correct anyway due to the endian problem of
MacPorts(*), I wanted to set up two parallel macports trees in user space
using the ./configure option --with-install-user=USER with my own userid,
thereby
59 matches
Mail list logo
