Re: realpath failed -- error uninstalling ports
On 2009-10-9 12:11, Dexter Douglas wrote: Hello, I still have this problem on my PowerBook G4, but I do not have this problem on my Intel-based MacBook Pro (Snow Leopard). Does anyone know what realpath is? I am not sure how to track this problem down. http://developer.apple.com/mac/library/documentation/Darwin/Reference/ManPages/man3/realpath.3.html http://trac.macports.org/browser/tags/release_1_8_1/base/src/registry1.0/portuninstall.tcl#L196 Basically we need to know which file doesn't exist. Adding something like: ui_debug getting realpath for $theFile to portuninstall.tcl just above line 199 would produce this information. - Josh ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Install Error
On 2009-10-9 10:24, Peter Hindrichs wrote: I am looking to further my understanding and knowledge of the command line and Ports so when I tried to install the port CosmicDebris I got this message. I have tried to figure it out, but am having no luck, could someone please help me to understand what is actually being said here. Could this have something to do with the fact that the program is not Snow Leopard compatible or is there another reason ? The port is in much better shape now that it has been updated to version 2.1 and is using the xcode portgroup. It still uses NSMailDelivery which is not available when building 64-bit, so I've restricted the port to building 32-bit until upstream fixes this. - Josh ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Install Error
On 2009-10-08, at 23:02 , Ryan Schmidt wrote: On Oct 8, 2009, at 22:01, Peter Hindrichs wrote: I did find this note in the Xcode Release notes: Note: GCC 4.2 cannot be used with the Mac OS X 10.4u SDK. If you want to build targets using the 10.4u SDK on Xcode 3.2, you must set the Compiler Version to GCC 4.0 Not sure how to set the compiler version By adding the line configure.compiler gcc-4.0 to the portfile. I have read through section 4 of the MacPorts Guide, and am at a loss as to how I access the portfile for CosmicDebris assuming that this is what is meant by the portfile. Thanks Peter ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Install Error
On 2009-10-08, at 23:02 , Ryan Schmidt wrote: On Oct 8, 2009, at 22:01, Peter Hindrichs wrote: I did find this note in the Xcode Release notes: Note: GCC 4.2 cannot be used with the Mac OS X 10.4u SDK. If you want to build targets using the 10.4u SDK on Xcode 3.2, you must set the Compiler Version to GCC 4.0 Not sure how to set the compiler version By adding the line configure.compiler gcc-4.0 to the portfile. Upon further reading and some experimenting I have found via Spotlight the portfile for CosmicDebris, and opened it with TextEdit. I tried to add the line suggested, however it won't let me save it. I haven't got write privileges. I must be able to do this on the command line with sudo but I am at a loss. Any help would be appreciated. Peter ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Install Error
On 2009-10-08, at 23:02 , Ryan Schmidt wrote: On Oct 8, 2009, at 22:01, Peter Hindrichs wrote: I did find this note in the Xcode Release notes: Note: GCC 4.2 cannot be used with the Mac OS X 10.4u SDK. If you want to build targets using the 10.4u SDK on Xcode 3.2, you must set the Compiler Version to GCC 4.0 Not sure how to set the compiler version By adding the line configure.compiler gcc-4.0 to the portfile. First I must apologize for the excessive e-mails prior to doing further research on my part. I have been able to get the CosmicDebris portfile open with TextWrangler and insert the configure.compiler gcc-4.0 and save the file. The result is the same when I try to install CosmicDebris. If I read correctly what Joshua Root wrote, then I am out of luck till a 64-bit update is built. I still have the question how would I get to the portfile via the command line, this is still puzzling. Thank you though, for your patience regarding what must be very basic and obvious to all of you. I am learning more each day and that is my goal here, to be more conversant with using the command line. Peter ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
apr-util not building because it can't find db
Everytime I issue port upgrade outdated, it tries to build apr-util, and fails with configure: error: Berkeley DB not found. db46 is installed, but the apr-util build just doesn't seem to believe it is there. Any advice? Regards David ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Error building python26 on ppc, Tiger
Here's my setup Xserve 2Ghz DP G5 OSXS 10.4.11 Macports 1.8.1 gcc 4.0 (also tried 3.3 got same error) Here's the error /usr/bin/gcc-4.0 -o hacklocaledir.so -fPIC -bundle hacklocaledir.c hacklocaledir.c: In function '__open': hacklocaledir.c:44: error: 'RTLD_NEXT' undeclared (first use in this function) hacklocaledir.c:44: error: (Each undeclared identifier is reported only once hacklocaledir.c:44: error: for each function it appears in.) hacklocaledir.c: At top level: hacklocaledir.c:113: warning: alias definitions not supported in Mach-O; ignored make: *** [hacklocaledir.so] Error 1 Error: The following dependencies failed to build: tk xorg-libXScrnSaver xorg-libXext xorg-libX11 autoconf help2man m4 automake libtool xorg-bigreqsproto xorg-inputproto xorg-kbproto xorg-libXau xorg-libXdmcp xorg-util-macros xorg-xcmiscproto xorg-xextproto xorg-xf86bigfontproto xorg-xtrans xorg-scrnsaverproto Error: Status 1 encountered during processing. Looks like it might night be python that's the issue, but one or more of the dependencies? -- Randall Perry ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Install error of postgres84 + leopard
I'm getting this: configure: error: library 'ossp-uuid' or 'uuid' is required for OSSP-UUID I found something to try within the comments of this post: http://www.robbyonrails.com/articles/2008/01/22/installing-ruby-on-rails-and-postgresql-on-os-x-third-edition (look for njakobsen) But after doing so I was still getting the same thing. Any ideas? Thanks. -Abe ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Install error of postgres84 + leopard
OK, so doing an uninstall and reinstall fixed the issue, though I suspect the steps I did from the previously-mentioned post may have helped. -Abe On Fri, Oct 9, 2009 at 2:19 PM, Abram Gillespie abe.gillespie.li...@gmail.com wrote: I'm getting this: configure: error: library 'ossp-uuid' or 'uuid' is required for OSSP-UUID I found something to try within the comments of this post: http://www.robbyonrails.com/articles/2008/01/22/installing-ruby-on-rails-and-postgresql-on-os-x-third-edition (look for njakobsen) But after doing so I was still getting the same thing. Any ideas? Thanks. -Abe ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
PostGIS / libproj Issues
I'm getting an error when installing PostGIS. Note that ls /opt/local/lib/*proj* gives me this: /opt/local/lib/libproj.0.5.5.dylib /opt/local/lib/libproj.dylib /opt/local/lib/libproj.0.dylib /opt/local/lib/libproj.la /opt/local/lib/libproj.a The error is: configure: error: could not find libproj - you may need to specify the directory of a PROJ.4 installation using --with-projdir Thanks. -Abe OS X Leopard / 10.6.1 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Install Error
On Oct 9, 2009, at 09:44 , Peter Hindrichs wrote: I still have the question how would I get to the portfile via the command line, this is still puzzling. mress:23478 Z$ port file CosmicDebris /opt/local/var/macports/sources/rsync.macports.org/release/ports/aqua/ CosmicDebris/Portfile (which was mentioned earlier in this thread) Also, TextWrangler should be able to tell you the full path; for a GUI editor it's fairly CLI friendly. -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allb...@kf8nh.com system administrator [openafs,heimdal,too many hats] allb...@ece.cmu.edu electrical and computer engineering, carnegie mellon universityKF8NH PGP.sig Description: This is a digitally signed message part ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: apr-util not building because it can't find db
On Oct 9, 2009, at 11:49 AM, David Cake wrote: Everytime I issue port upgrade outdated, it tries to build apr- util, and fails with configure: error: Berkeley DB not found. db46 is installed, but the apr-util build just doesn't seem to believe it is there. Any advice? are you sure your db46 port is happy/healthy? You could try uninstalling/cleaning/reinstalling it, then cleaning apr- util and see if it works then? Otherwise posting the port -dv upgrade apr-util output (or opening a bug with it attached) would be the next step in helping to troubleshoot it. -- Daniel J. Luke ++ | * dl...@geeklair.net * | | *-- http://www.geeklair.net -* | ++ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | ++ ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Error building python26 on ppc, Tiger
On Oct 9, 2009, at 12:32, Randall Perry wrote: hacklocaledir.c:44: error: 'RTLD_NEXT' undeclared (first use in this function) Google searching this error I see: http://www.macgeek.co.za/2009/05/11/compliation-of-package-x-failed-rtld_next-undeclared/ Do you have /usr/local/include/dlfcn.h? Stuff in /usr/local interferes with MacPorts and I recommend you remove anything you have there. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: PostGIS / libproj Issues
On Oct 9, 2009, at 14:10, Abram Gillespie wrote: I'm getting an error when installing PostGIS. Note that ls /opt/local/lib/*proj* gives me this: /opt/local/lib/libproj.0.5.5.dylib /opt/local/lib/libproj.dylib /opt/local/lib/libproj.0.dylib /opt/local/lib/libproj.la /opt/local/lib/libproj.a The error is: configure: error: could not find libproj - you may need to specify the directory of a PROJ.4 installation using --with-projdir Thanks. -Abe OS X Leopard / 10.6.1 Please file a ticket in the issue tracker and provide more information including the full debug output of your attempted installation. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: manually building Dosbox CVS in 32-bit
On Oct 9, 2009, at 17:16, Dominik Reichardt wrote:
I'm wondering how to build Dosbox CVS in 32-bit. If I edit the port
file of dosbox by adding
if {$build_arch == x86_64} {
configure.build_arch i386
} elseif {$build_arch == ppc64} {
configure.build_arch ppc
}
if {[variant_isset universal] [string match *64*
$universal_archs]} {
pre-fetch {
return -code error $name $version cannot be built for 64-bit
architectures
}
}
and commenting out
#platform darwin {
#configure.args-append --build=${build_arch}-apple-darwin$
{os.major}
#}
stopping the port install process in configuring and then
overwriting the 0.73 release source with the CVS and then starting
port install dosbox again, I am able to build a 32-bit Dosbox CVS
that is stable and doesn't crash when switching to dynamic core
(like the 64-bit version properly built by MacPorts does).
So that is working by tricking MacPort but I'm wondering how to do
that manually.
I've tried with configuring dosbox with
./configure -build=i386-apple-darwin10.0.0 --target=i386-apple-
darwin10 --prefix=/opt/local --disable-sdltest --disable-alsatest
but that didn't work and has the same compile errors that the
MacPorts port had before the last patch. So I'm obviously missing
something that MacPorts does right when I use the above trick to
build Dosbox in 32-bit.
What is it? Can anyone help me?
You're probably missing the -arch i386 flags MacPorts adds to
various environment variables. Use sudo port -d configure dosbox and
examine the line beginning with DEBUG: Environment: to see all the
environment variables MacPorts sets for you.
P.S.: Dosbox CVS still needs the midi_coreaudio.h patch that
MacPorts does and in src/hardware/serialport/libserial.cpp you need
to exchange #include malloc.h with #include stdlib.h (line 260)
- just as an help to anyone trying their hand on the cvs as well.
I've reported both issues to the Dosbox developers.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: MacPorts 1.8.1 has been released
I have now done a sudo port selfupdate on two more Macs running Snow Leopard: One a Macbook Pro that is about 30 months old and an iMac that was purchased a month ago. Both times it worked and the sudo port update outdated did as well. The only problem machine was a Macbook Pro purchased four months ago. I guess the only solution is to remove Macports and reinstall. Ralph Pass Bryan Blackburn wrote: On Tue, Sep 29, 2009 at 04:47:54PM -0400, Ralph Pass said: More information: doing a lipo -info /Libary/Tcl/macports1.0/Macports.dylib shows that on the system that works, the architecture is x86_64 and on the one that does not work, the architecture is i386. Both cases the gcc is gcc-4.2. Further the dates on the Macports.dylib file is the time of the sudo port selfupdate. So why did the selfupdate use architecture i386 (and I know that Snow Leopard now defaults to x87_64 rather than i386)? That's definitely the question, as it shouldn't be doing that. It shouldn't be what you have for build_arch in macports.conf as I tried that, and MacPorts.dylib was still x86_64 after a selfupdate. What is the result from the following commands? $ ls -l /usr/bin/gcc* $ port installed gcc* Also, did you run selfupdate from the shell, or where you in port's interactive mode? Bryan Ralph Pass Ralph Pass wrote: Like several other people I have had trouble with updating to 1.8.1 on Snow Leopard. On my Mac Pro (about 19 months old), I updated to Snow Leopard and then 1.8.0 and things worked. I then did a sudo port selfupdate and it worked. A sudo port upgrade outdated also worked. On a new (3 month old) Macbook Pro, I updated to Snow Leopard and then 1.8.0 and things worked. However, it failed when I did a sudo port selfupdate: sudo port selfupdate dlopen(/Library/Tcl/macports1.0/MacPorts.dylib, 10): no suitable image found. Did find: /Library/Tcl/macports1.0/MacPorts.dylib: mach-o, but wrong architecture while executing load /Library/Tcl/macports1.0/MacPorts.dylib (package ifneeded macports 1.0 script) invoked from within package require macports (file /opt/local/bin/port line 39) Note that for uname -a gives: Darwin mars.local 10.0.0 Darwin Kernel Version 10.0.0: Fri Jul 31 22:47:34 PDT 2009; root:xnu-1456.1.25~1/RELEASE_I386 i386 sw_vers gives: ProductName:Mac OS X ProductVersion:10.6.1 BuildVersion:10B504 So I am bit perplexed and looking for guidance. Thanks, Ralph Pass [...] ___ 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: MacPorts 1.8.1 has been released
On 2009-10-10 11:47, Ralph Pass wrote: I have now done a sudo port selfupdate on two more Macs running Snow Leopard: One a Macbook Pro that is about 30 months old and an iMac that was purchased a month ago. Both times it worked and the sudo port update outdated did as well. The only problem machine was a Macbook Pro purchased four months ago. I guess the only solution is to remove Macports and reinstall. Or install 1.8.1 from the dmg. - Josh ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Install Error
On 2009-10-10 00:44, Peter Hindrichs wrote: If I read correctly what Joshua Root wrote, then I am out of luck till a 64-bit update is built. Sorry, I guess I didn't make myself very clear. The port builds and works fine now AFAICT, it just builds for i386 where everything would normally be built for x86_64. - Josh ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Install Error
On 2009-10-09, at 17:00 , Brandon Allbery wrote: On Oct 9, 2009, at 09:44 , Peter Hindrichs wrote: I still have the question how would I get to the portfile via the command line, this is still puzzling. mress:23478 Z$ port file CosmicDebris /opt/local/var/macports/sources/rsync.macports.org/release/ports/ aqua/CosmicDebris/Portfile (which was mentioned earlier in this thread) Also, TextWrangler should be able to tell you the full path; for a GUI editor it's fairly CLI friendly. -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allb...@kf8nh.com system administrator [openafs,heimdal,too many hats] allb...@ece.cmu.edu electrical and computer engineering, carnegie mellon university KF8NH OK Thanks for that, I must have missed the earlier mention. Peter ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Installing old version of a port
I'm trying to figure out how to install an outdated version of a port and having not much luck. Is there a simple way of installing, for instance, rdiff-backup-devel @1.1.5? I've found the portfile for it but I'm not sure what to do with it. Thanks ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
