November 2007 - macports-users - lists.macosforge.org

Need help getting Firewalk to compile.
by Endahl, John 17 Nov '07

17 Nov '07

Can anyone help me install Mark Shiffman's Firewalk? There doesn't seem to be any ports available through Fink or MacPorts and nothing seems to come googling it. I've copied over the config.guess and config.sub files and tried to compile it. Installed libnet11 using MacPorts. One of my co-workers added it to the path and he got the configure to work but the Make step throws all kinds of errors. TIA. --john.endahl(a)sbcglobal.net

2 1

KedPM not working on Leopard
by Toby Curl 17 Nov '07

17 Nov '07

I had KedPM working fine in Tiger. Now on Leopard it is not working. I know there are some issues with the new Implementation of X11, so I have got Tiger X11 installed now (using these instructions: http://lists.apple.com/archives/x11-users/2007/Nov/msg00005.html) but still getting the same errors. Running KedPM in X11 gives this output: Traceback (most recent call last): File "/opt/local/bin/kedpm", line 67, in <module> main(sys.argv[1:]) File "/opt/local/bin/kedpm", line 57, in main app = frontendFactory(frontend) File "/opt/local/lib/python2.5/site-packages/kedpm/frontends/__init__.py", line 35, in frontendFactory from kedpm.frontends.gtk.app import Application File "/opt/local/lib/python2.5/site-packages/kedpm/frontends/gtk/__init__.py", line 4, in <module> import gtk.glade File "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_python_py25-gtk/work/destroot/opt/local/lib/python2.5/site-packages/gtk-2.0/gtk/__init__.py", line 38, in <module> File "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_python_py25-gobject/work/destroot/opt/local/lib/python2.5/site-packages/gtk-2.0/gobject/__init__.py", line 30, in <module> File "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_python_py25-gobject/work/destroot/opt/local/lib/python2.5/site-packages/gtk-2.0/gobject/constants.py", line 22, in <module> ImportError: dlopen(/opt/local/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so, 2): Symbol not found: _PyGBoxed_Type Referenced from: /opt/local/lib/python2.5/site-packages/gtk-2.0/gobject/_gobject.so Expected in: flat namespace Is there anyway to get it running? Thanks

2 1

rsync daemon down?
by Evan Weaver 17 Nov '07

17 Nov '07

Hi, Is the Rsync daemon down? I haven't been able to selfupdate for a couple of days now: chloe:~ eweaver$ sudo port -v selfupdate Synchronizing from rsync://rsync.macports.org/release/ports/ rsync: failed to connect to rsync.macports.org: Connection refused (61) rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync-24.1/rsync/clientserver.c(94) Error: /opt/local/bin/port: selfupdate failed: Couldn't sync the ports tree: sync failed doing rsync I can see rsync.macports.org in my browser (it says "it works"), and disabling my firewall doesn't help. Thanks very much Evan -- Evan Weaver Cloudburst, LLC

2 4

Re: Tripwire fails to install
by markd＠macports.org 17 Nov '07

17 Nov '07

>I just took a couple of minutes to checkout the current stable Open >Soure Tripwire(R) 2.4.1.2 on Mac OS X 10.4.11 PPC. > >I unpacked the source code, ran "./configure && make && make install". >Tripwire configures and compiles without any problems using the tool >chain that comes with 10.4 out of the box, I didn't even update to the >latest XCode etc. > >This is the output of "tripwire --version" > >Open Soure Tripwire(R) 2.4.1.2 built for powerpc-apple-darwin8.11.0 > >The developer of the original code and/or files is Tripwire, Inc. >Portions >created by Tripwire, Inc. are copyright 2000 Tripwire, Inc. Tripwire is a >registered trademark of Tripwire, Inc. All rights reserved. > >This program is free software. The contents of this file are subject to >the >terms of the GNU General Public License as published by the Free Software >Foundation; either version 2 of the License, or (at your option) any later >version. You may redistribute it and/or modify it only in compliance with >the GNU General Public License. > >This program is distributed in the hope that it will be useful. However, >this program is distributed "AS-IS" WITHOUT ANY WARRANTY; INCLUDING THE >IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. >Please see the GNU General Public License for more details. > >You should have received a copy of the GNU General Public License along >with >this program; if not, write to the Free Software Foundation, Inc., >59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. > >Nothing in the GNU General Public License or any other license to use the >code or files shall permit you to use Tripwire's trademarks, service >marks, >or other intellectual property without Tripwire's prior written consent. > >If you have any questions, please contact Tripwire, Inc. at either >info(a)tripwire.org or www.tripwire.org. > >--- > >cheers, > >Tobias W. Tobias, To install tripwire via MacPorts, you would use "sudo port intall tripwire". What happens when you type that? It instals fine for me, but I don't use tripwire so I can't test its operation. Mark

1 0

Re: Tripwire fails to install -> Tripwire 2.4.1.2 builds out of the box on 10.4.11 PPC
by Tobias Weisserth 17 Nov '07

17 Nov '07

Hi everybody, I just took a couple of minutes to checkout the current stable Open Soure Tripwire(R) 2.4.1.2 on Mac OS X 10.4.11 PPC. I unpacked the source code, ran "./configure && make && make install". Tripwire configures and compiles without any problems using the tool chain that comes with 10.4 out of the box, I didn't even update to the latest XCode etc. This is the output of "tripwire --version" Open Soure Tripwire(R) 2.4.1.2 built for powerpc-apple-darwin8.11.0 The developer of the original code and/or files is Tripwire, Inc. Portions created by Tripwire, Inc. are copyright 2000 Tripwire, Inc. Tripwire is a registered trademark of Tripwire, Inc. All rights reserved. This program is free software. The contents of this file are subject to the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. You may redistribute it and/or modify it only in compliance with the GNU General Public License. This program is distributed in the hope that it will be useful. However, this program is distributed "AS-IS" WITHOUT ANY WARRANTY; INCLUDING THE IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Please see the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. Nothing in the GNU General Public License or any other license to use the code or files shall permit you to use Tripwire's trademarks, service marks, or other intellectual property without Tripwire's prior written consent. If you have any questions, please contact Tripwire, Inc. at either info(a)tripwire.org or www.tripwire.org. --- cheers, Tobias W.

2 1

Re: xmgrace and leopard?
by Ryan Schmidt 17 Nov '07

17 Nov '07

Please keep this discussion on the mailing list by using the Reply To All feature when you reply. On Nov 16, 2007, at 16:44, Brian Barnes wrote: > On Nov 16, 2007, at 4:33 PM, Ryan Schmidt wrote: > >> On Nov 16, 2007, at 11:25, Brian Barnes wrote: >> >>> I was wondering if anyone had grace functioning under OS X 10.5. >>> I am currently using Tiger, but haven't found any positive >>> reports of someone getting grace working under Leopard, and that >>> is a showstopper for my upgrading. There are some X11/Xquartz >>> updates available, but none mention helping of building grace. >>> Nothing in fink or at hpc.sourceforge.net yet either. Is anyone >>> working on building this package, or is a specific problem triaged? >>> >>> Thanks, >>> >>> Brian >>> >>> http://grace.darwinports.com/dports/x11/grace/Portfile >>> http://www.x.org/wiki/XDarwin >> >> Please note that darwinports.com is not affiliated with the >> MacPorts project and I recommend you do not refer to that site for >> any information. The MacPorts web site is http://www.macports.org/ > > Thanks for the pointer -- I am new to macports. My understanding > is that the project name changed from darwinports to macports > sometime last year or so. Are the darwinports.com people that just > branched off macports and are doing their own thing? I am totally > oblivious to any story between the two sites. I tried finding a > package listing on the macports webpage and failed. Is there a > webpage for the grace package in macports somewhere? I am curious > as to whether it requires g95 as a dependency, or if it can be > built with gfotran (which I would prefer). I think the fftw > dependency of grace typically spurs the dependency of a fortran > compiler. MacPorts used to be called DarwinPorts. However, darwinports.com has never been affiliated with the MacPorts (formerly DarwinPorts) project. It's just some other individual who wanted to start a web site, and failed to coordinate that effort with the project. The MacPorts project cannot vouch for the accuracy of the information on that or any other site, other than the official MacPorts web site. The current MacPorts web site does not have a port list. The old official DarwinPorts site did, but when our old host OpenDarwin died, we moved to the new Mac OS Forge host and used their default site template, which is a bit lacking. The site is being redesigned and will hopefully be relaunched soon. You can peek at the new version here: http://apollo.homeunix.net/macports/ There is no web page for the grace port, or for most other ports. However, you can use port commands to learn about the port. "port cat foo" prints the port to the screen. "port edit foo" opens it in your favorite editor. "port info foo" and "port deps foo" tell you about the dependencies. "port variants foo" tells you about available variants. "man port" tells you more. In this case, the grace portfile makes no reference to either g95 or gfortran. I'd say ask the maintainer, but unfortunately the grace port has no maintainer. You mentioned fftw, but as far as I can tell, grace does not depend on fftw. fftw has a fortran variant which uses gcc34, which is rather old. But fftw is rather old too. If you want fftw, you may want the port fftw-3 instead. It has two variants, fortran and g95, so you can choose which fortran you want. Unfortunately, the "fortran" variant uses gfortran from gcc40. This port should be updated to use gfortran from gcc42. > My first macports experience just now was a build failure compiling > xscorch on 10.4/intel. :( Moria built fine, and now I'm trying > dopewars and xboard. Starting with a few little things as tests :) Sorry about the problem. Unfortunately xscorch is also unmaintained. I do not see a ticket filed in Trac about any xscorch problem. You should file a ticket. Instructions are here: http://trac.macosforge.org/projects/macports/wiki/TracTicketing > Maybe you can also answer, as macports uses "mac" in its name, is > it somehow affiliated with Apple or does it have some Apple > employees that contribute? I am not sure what would be better in > the long term, to use MacPorts, or Fink. Fink has a couple really > good maintainers of packages that I care about (e.g. Jack Howarth > and gfortran related things), but MacPorts may be more "official"? MacPorts changed its name from DarwinPorts to emphasize the fact that it's meant for Mac users. MacPorts is hosted by Mac OS Forge, an open- source hosting venture of Apple. Some MacPorts contributors are Apple employees. But none of this makes MacPorts an Apple project; it's not. Neither Fink nor MacPorts are more official. I imagine some Fink contributors work at Apple too. Apple's a big company. I personally decided a few years ago to switch to MacPorts (then DarwinPorts) since Fink was giving me grief, and as you see I've stuck with it now and I'm happy with that decision. About half the ports in MacPorts are unmaintained. But the other half do have maintainers. It is still a growing project and needs all the help it can get. Willing maintainers who stay on top of their ports and keep them updated and working are certainly sought. If you see a port in MacPorts that's unmaintained, but you care about the software, it would be appreciated if you would offer to maintain it. If you would spend the time and energy to compile it for yourself manually, why not invest that time and energy into fixing the MacPorts portfile so all can enjoy it, right? Leopard is being especially problematic. I personally am not upgrading to Leopard yet because of all the problems I've seen reported. (Just search the issue tracker for "Leopard".) On the other hand, this makes it difficult for me to help fix the Leopard problems that people report with the ports I maintain. As an early adopter of Leopard, you might be uniquely able to help us during this troublesome transition.

1 0

Trac tickets db updated
by Juan Manuel Palacios 17 Nov '07

17 Nov '07

When moving away from the Trac ticket configuration we started with when moving to Mac OS Forge (priorities like "Expected" & severities like "Data loss", for instance) and moved to our more sane current values ("High", "Normal", "Low", etc), some tickets were lost in the "Reports" area as the queries no longer matched the old values (manual searching for tickets had to be performed if you didn't know their numbers). I'm glad to say this has been fixed by updating the Trac db directly to enforce the new values on all tickets, including old ones that had the original set, http://trac.macports.org/projects/macports/ticket/12603 So, in a nutshell, Trac reports at http://trac.macports.org/projects/macports/report should now return full lists of matching tickets, spanning the entire DB. Let me know if you feel there are some still missing and please give me the details of your query so I can look into it. Lastly, feel free to disregard this message if its content didn't make any sense to you ;-) Regards,... -jmpp

1 0

Re: New Macports using trying to install octave
by Ryan Schmidt 17 Nov '07

17 Nov '07

On Nov 9, 2007, at 11:36, Jackson Myers wrote: > On Nov 9, 2007, at 4:42 AM, Ryan Schmidt wrote: > >> On Nov 8, 2007, at 16:52, Jackson Myers wrote: >> >>> I am new to Macports (but I have some Unix/Darwin experience and >>> I have used Fink before). I am trying to install Octave on >>> Leopard and not having much luck. The following is an error I got >>> on my first attempt. Can anybody decipher this and tell me how >>> to make it work? thanks, >>> -Jax >> >> I think it means that you have a PowerPC Mac, and the octave port >> requests gcc40 on PowerPC machines, and gcc40 apparently won't >> build on Leopard anymore. We've had at least one other report of >> this that I recall. There's an open bug requesting that this be >> changed to use gcc42. There's a patch attached to the ticket. You >> could try the patch and see if it helps: >> >> http://trac.macports.org/projects/macports/ticket/12144 >> >> There's also an open request to update the port to the current >> version: >> >> http://trac.macports.org/projects/macports/ticket/12937 >> >> The port's maintainer is busy with other things right now so he >> hasn't had a chance to look at these tickets. But if you try the >> patches and they fix the problem for you, someone else could >> commit them. > > Thanks for the info. I'll give it a try. Just a quick question > though: How do I apply that patch? Whoops, it looks like my patch in ticket 12144 has rotted. I'm attaching an updated patch to the ticket. So now you can: sudo port clean --work octave cd `port dir octave` sudo patch -p0 < ~/Desktop/octave-gcc42-2.diff sudo port install octave The patch will disappear the next time you do a "sudo port selfupdate" or "sudo port sync". I don't use octave and I haven't tried the patch myself so if you run into more problems please let us know.

3 3

Re: Problem installing package
by Randall Wood 16 Nov '07

16 Nov '07

Please remember to reply to all so that the discussion remains on the mailing list. On 16 Nov 2007, at 16:47, R T wrote: > 10.5 ship with python 2.5.1. Unfortunately, when building our > system one of the modules blows up with python 2.5.1. It was > originally built to use python 2.3. > > > CC: macports-users(a)lists.macosforge.org > > From: rhwood(a)mac.com > > Subject: Re: Problem installing package > > Date: Fri, 16 Nov 2007 16:22:31 -0500 > > To: wraith_1(a)hotmail.com > > > > Note that Mac OS X 10.4 ships with python 2.3. Don't know what > > version 10.5 ships with. > > > > On 16 Nov 2007, at 13:41, R T wrote: > > > > > My company started to move to the Mac for our system > development so > > > I am new to Macports. Our current system requires the use of > python > > > 2.3 during its build process. I was attempting to use macports to > > > install python23 and ran into a problem. Below is a listing with > > > the error. Any insite would be helpful. > > > > > > $ sudo port -v -d install python23 > > > > > > DEBUG: Found port in file:///opt/local/var/macports/sources/ > > > rsync.macports.org/release/ports/lang/python23 > > > DEBUG: Changing to port directory: /opt/local/var/macports/ > sources/ > > > rsync.macports.org/release/ports/lang/python23 > > > DEBUG: Requested variant i386 is not provided by port python23. > > > DEBUG: Requested variant macosx is not provided by port python23. > > > DEBUG: Executing variant darwin provides darwin > > > DEBUG: Found port in file:///opt/local/var/macports/sources/ > > > rsync.macports.org/release/ports/archivers/gnutar > > > DEBUG: Changing to port directory: /opt/local/var/macports/ > sources/ > > > rsync.macports.org/release/ports/archivers/gnutar > > > DEBUG: Requested variant darwin is not provided by port gnutar. > > > DEBUG: Requested variant i386 is not provided by port gnutar. > > > DEBUG: Requested variant macosx is not provided by port gnutar. > > > DEBUG: Searching for dependency: gnutar > > > DEBUG: Didn't find receipt, going to depspec regex for: gnutar > > > DEBUG: Found Dependency: path: /usr/bin filename: gnutar regex: > > > ^gnutar$ > > > DEBUG: Skipping completed org.macports.main (python23) > > > DEBUG: Skipping completed org.macports.fetch (python23) > > > DEBUG: Skipping completed org.macports.checksum (python23) > > > DEBUG: setting option extract.cmd to /usr/bin/bzip2 > > > DEBUG: Skipping completed org.macports.extract (python23) > > > DEBUG: Skipping completed org.macports.patch (python23) > > > DEBUG: Skipping completed org.macports.configure (python23) > > > ---> Building python23 with target all > > > DEBUG: Executing org.macports.build (python23) > > > DEBUG: Environment: > > > DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ > > > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ > > > python23/work/Python-2.3.6" && make all' > > > gcc -L/opt/local/lib -u __dummy -u _PyMac_Error -framework > System - > > > framework CoreServices -framework Foundation -o python.exe \ > > > Modules/python.o \ > > > -L. -lpython2.3 -ldl -framework CoreServices -framework > > > Foundation > > > Undefined symbols: > > > "__dummy", referenced from: > > > ld: symbol(s) not found > > > collect2: ld returned 1 exit status > > > make: *** [python.exe] Error 1 > > > Error: Target org.macports.build returned: shell command " cd "/ > opt/ > > > local/var/macports/build/ > > > > _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ > > > python23/work/Python-2.3.6" && make all " returned error 2 > > > Command output: gcc -L/opt/local/lib -u __dummy -u _PyMac_Error - > > > framework System -framework CoreServices -framework Foundation -o > > > python.exe \ > > > Modules/python.o \ > > > -L. -lpython2.3 -ldl -framework CoreServices -framework > > > Foundation > > > Undefined symbols: > > > "__dummy", referenced from: > > > ld: symbol(s) not found > > > collect2: ld returned 1 exit status > > > make: *** [python.exe] Error 1 > > > > > > Warning: the following items did not execute (for python23): > > > org.macports.activate org.macports.build org.macports.destroot > > > org.macports.install > > > Error: Status 1 encountered during processing. > > > > > > > > > Help yourself to FREE treats served up daily at the Messenger > Café. > > > Stop by today! > > > _______________________________________________ > > > macports-users mailing list > > > macports-users(a)lists.macosforge.org > > > http://lists.macosforge.org/mailman/listinfo/macports-users > > > > > > > > Randall Wood > > rhwood(a)mac.com > > http://shyramblings.blogspot.com > > > > "The rules are simple: The ball is round. The game lasts 90 minutes. > > All the > > rest is just philosophy." > > > > > > Climb to the top of the charts! Play Star Shuffle: the word > scramble challenge with star power. Play Now! Randall Wood rhwood(a)mac.com http://shyramblings.blogspot.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy."

1 0

Re: selfupdate failing under Leopard
by markd＠macports.org 16 Nov '07

16 Nov '07

>> On the other hand, if a user installs stuff in /usr/local/ after >> installing MacPorts it wouldn't help unless selfupdate (and/or port) >> also >> checked those paths so maybe it isn't feasible. The Cisco VPN >> client uses >> /usr/local, though it causes no problems. Comments? > > >So the 'problem' is only when the user installs some library in /usr/ >local that macports uses and either that install is broken somehow or >the user removes it. > >It's good to make macports robust against mistakes, but at some point >we probably have to realize that end-users are going to be able to >configure their systems in ways that are broken, and we may or may not >be able to do something about that specific broken-ness. I agree. Especially since the woes of manually installed OSS is one if the problems MacPorts is trying to overcome. :) Is readline the main offender? I want to document this problem and though I think any non-MP software could potentially be a problem, I might mention the worst offenders as examples. What are others? Mark

4 4