Re: There is no release manager! There is no release manager!
On Wed, Oct 8, 2008 at 5:10 AM, Jordan K. Hubbard [EMAIL PROTECTED] wrote: On Oct 7, 2008, at 9:35 PM, Ryan Schmidt wrote: For the next release, I think we need version 1.7.0, not 1.6.1, because there are countless new features and a year's worth of bug fixes. That much work deserves more than just a bugfix version number increase. That means we release from trunk, not the 1.6 branch. A concern of mine is that the 1.6 branch contains some work that was done only there and not on trunk. I believe some of it was done on trunk in a different way, but I don't know if all changes from the 1.6 branch got put in trunk. Someone needs to figure out whether it was, and if not, identify what needs to be ported from 1.6 to trunk. Ideally that would happen before a 1.7.0 release. I agree entirely. I know that some kind folks have also been tentatively tossing their hat in the ring for this job, and for that I think we should all be thankful and also willing to both encourage and help them do so in any way necessary, but I also agree that we haven't had a release in some time and the accumulated backlog of work is likely to be a little daunting to anyone who isn't already intimately familiar with MacPorts. Ryan. I hate to do this to you, I really do, but given the degree to which you've been active in this project and the fact that you clearly know your way around, I don't suppose YOU would be willing to do this for at least one release, just to get the ball rolling again, as it were? The quoted paragraph clearly demonstrates an agenda of sorts, without which any RE cannot truly be effective, and I think the other volunteers would find you a more than credible candidate for the job and be willing to follow/help you as necessary. Again, I am not suggesting that you volunteer (or be volunteered :-) for anything more than this 1.7.0 release, we just need to break the log jam and there are very few people I can think of who have demonstrated your level of commitment to this project (the svn logs speak for themselves!). Sounds like an excellent solution. Breaking the log jam is an excellent summation of what's needed here and I think once people can see the accumulated body of work that comes with the 1.7 release, the energy level and enthusiasm will go up a bit. Seconded, in other words. -- Paul Beard / www.paulbeard.org/ paulbeard.org ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: There is no release manager! There is no release manager!
On Wed, Oct 8, 2008 at 7:01 AM, [EMAIL PROTECTED] wrote: I don't know which reality you have been living in, but I think the weight of evidence points to exactly the opposite conclusion: There has not been a release manager or portmgr team for quite some time, which is why this and other bugs have been stuck in release limbo. Just the daily reality of an end-user. I didn't realize those positions were completely vacant. Maybe in future those responsibilities, if they are important to the ongoing success of the project, can be taken up by someone else, even on an interim or one shot basis. -- Paul Beard / www.paulbeard.org/ paulbeard.org ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: There is no release manager! There is no release manager!
On Tue, Oct 7, 2008 at 7:00 AM, [EMAIL PROTECTED] wrote: On Oct 6, 2008, at 11:13 AM, Daniel J. Luke wrote: On Oct 6, 2008, at 1:41 PM, William Davis wrote: Pardon me for speaking frankly but! to solve this problem permanently will take an updated version of port with the bug fix in place. This situation has gone on for many months now and I can NOT understand why version 1.61 of port has not been released fixing this path problem. You volunteering to be the new release manager? ;-) Maybe some folks have not [there is no release manager!] gotten the ideal firmly in their heads [there is no release manager!] yet that there is, in fact, NO RELEASE MANAGER for MacPorts right now? Perhaps we should send out some sort of announcement calling formally for volunteers for the position? I dunno, perhaps that seems superfluous, but I'll still bet that there are a couple of people out there laboring under the misapprehension that there is, in fact, a release manager for MacPorts (there isn't!). FAIL. There has been a release manager and portmgr@ team for quite some time and this bug lingers, festers even. If this is part of a strategy of annoying users to the point where they sign up to be release manager just so it gets done, I'm not sure it will work. Civilians like me have no idea what the actual steps are to get a release cut, even one so trivial as the bug fix for 1.6. If the guys who were doing it had a hard time with it, what would make someone who isn't an active port maintainer think they could do it? Absent a release manager or team, what would it take to get a release schedule (quarterly? monthly?) and/or a roadmap? Not sure it makes a lot of sense to fret about a release manager if we don't really know what a release is or why we need one. A roadmap/set of benchmarks/goals would help and from there a release calendar could be derived. If you do really want volunteers, why not provide some insight into what's involved and how it works? Are there tools? Is there a process? Bueller? -- Paul Beard / www.paulbeard.org/ paulbeard.org ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: There is no release manager! There is no release manager!
On Tue, Oct 7, 2008 at 9:35 PM, Ryan Schmidt [EMAIL PROTECTED]wrote: We don't need a roadmap at this time; we just need to release the work that has been done on trunk over the past year. After that, I don't think we need a roadmap either; we just need to make regular releases when there is new work on trunk to release. absent a road map, how to decide what gets worked on, what, if any, features get added/fixed/removed? Example: a packaging system so people on slow hardware can stay up to date: important and useful but not to people with newer/faster hardware. If developers/volunteers set their own priorities, is it really a project? A community garden makeover has more organization than that it doesn't mean everyone gets a rake or watering can: tasks are assigned based on what needs doing. But as we have seen with this niggly little .profile issue, if no one owns it, no one fixes it. In a real software development environment, developers don't always get to pick what they want to work on: some icky stuff just has to be done. I couldn't get arrested as a programmer, but even I know that. To be clear, I'm not saying MacPorts as a project is a waste of time or that the volunteers are a buncha slackers. But it is a little frustrating to see so many people come into the community and face the same issues. How long in actual time would it take for someone with a commit bit to add the fix to .profile and cut a new release? An hour? Two? 24? Weighing that against the potential users who have been turned off or frustrated by the experience of a known issue, simple to fix, left unfixed, and I wonder if MacPorts is just for the developers who can grope around in its guts. Do we have any idea how many people have downloaded it? How many sync their trees and download new portfiles? I would be a bit concerned about a newcomer preparing the releases. I would hope that the release manager would have an intimate familiarity with MacPorts, for which I think you need experience maintaining ports and maybe even contributing some patches to base as well. At least, releases would have to be tested by people familiar with MacPorts before the final release is made. Well, after a year's worth of changes we're going to need some release candidates before the final release anyway. I wasn't considering volunteering ;-) For the next release, I think we need version 1.7.0, not 1.6.1, because there are countless new features and a year's worth of bug fixes. That much work deserves more than just a bugfix version number increase. That means we release from trunk, not the 1.6 branch. A concern of mine is that the 1.6 branch contains some work that was done only there and not on trunk. I believe some of it was done on trunk in a different way, but I don't know if all changes from the 1.6 branch got put in trunk. Someone needs to figure out whether it was, and if not, identify what needs to be ported from 1.6 to trunk. Ideally that would happen before a 1.7.0 release. No argument there. It does seem like not cutting more regular releases has created some work there. -- Paul Beard / www.paulbeard.org/ paulbeard.org ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Getting started
On Mon, Sep 8, 2008 at 1:04 AM, Ryan Schmidt [EMAIL PROTECTED] wrote: On Sep 6, 2008, at 3:42 PM, paul beard wrote: Why don't send along to the list the output of port installed so we can see where you are. If you get a complaint that port does not exist, you will need to try /opt/local/bin/port installed as there as a known bug in the last release that has never been fixed. The bug has been fixed; a new version of MacPorts has just not been released that contains the fix. The workaround is described in the problem hotlist: http://trac.macports.org/wiki/ProblemHotlist#a.profilenotsetup If it hasn't been released, it hasn't really been fixed. Will there be another release? -- Paul Beard / www.paulbeard.org/ paulbeard.org ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: macports-users Digest, Vol 25, Issue 6
On Sat, Sep 6, 2008 at 7:00 AM, [EMAIL PROTECTED] wrote: Greetings. Pardon my ignorance, but I can't find out how to begin using MacPorts. I have a MacBook just under a year old, with a 2GHz Intel Core 2 Duo processor and OS X 10.5.4. I installed appropriate versions of X11, Xcode MacPorts - all successfully, as I understood it. I cannot find MacPort's icon. Perhaps it is not its own app. In which case it is a bit beyond my ken. ...my barbie too. I've checked the online guide FAQ and it all seems to assume this most basic how-to-start-using-it point is self-evident and I can't find any mention of what I need to do to begin doing anything else with it. I've given up on that route, after a couple hours of installing and searching. Began this whole process in an attempt to install GIMP. I'll try the other easy(?) route listed on their site, but would still be interested in checking out what-all MacPorts has to offer. It seems an exciting source to explore. MacPorts is not an application so there is no icon or anything like that. It's a framework to install and manage other open source apps (like the Gimp). It manages dependencies and versions/variants so you can just get what you need. Why don't send along to the list the output of port installed so we can see where you are. If you get a complaint that port does not exist, you will need to try /opt/local/bin/port installed as there as a known bug in the last release that has never been fixed. -- Paul Beard / www.paulbeard.org/ paulbeard.org ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: dependencies for gnome
On Sat, Jul 5, 2008 at 7:30 AM, Randall Wood [EMAIL PROTECTED] wrote: When I maintained this port, it was designed to deliver the official GNOME distribution set as completely as possible. So yes, everything is really required unless it has been removed from GNOME upstream and not from the port. Cheers to the GNOME team for completeness, but still . . . On Fri, Jul 4, 2008 at 4:51 PM, paul beard [EMAIL PROTECTED] wrote: Are all these *really* necessary? Error: The following dependencies failed to build: gnome-desktop-suite evince gdk-pixbuf glib1 gtk1 poppler poppler-data file-roller gcalctool gconf-editor gdm howl gedit gtksourceview2 py25-pygtksourceview gnome-applets gnome-control-center gnome-python-desktop gnome-media gtksourceview gnuregex totem-pl-parser gucharmap system-tools-backends p5-net-dbus p5-xml-twig gnome-audio gnome-backgrounds gnome-games ggz-client-libs libggz guile gmp libsdl_mixer libsdl smpeg py25-gtkglext gtkglext py25-opengl py25-pil py25-setuptools py25-tkinter tcl tk gnome-keyring-manager gnome-mag gnome-session gnome-system-monitor gtkmm cairomm glibmm libsigcxx2 gnome-terminal vte gnome-user-docs gnome-utils gnopernicus libgail-gnome libgtkhtml3 seahorse avahi dbus-python25 gdbm libdaemon py25-gdbm gpgme pth vino yelp firefox-x11 zip zenity seahorse *and* firefox? howl *and* avahi? Don't these do more or less the same thing? Seahorse is a GPG frontend. Firefox is a web browser. No similarity. I'm not sure why howl is in there, everything GNOME should depend on avahi (unless some clever GNOME developer is using howl only on Mac OS X in his project) Gah, I was thinking of seamonkey. My mistake . . I can see needing a lot of libraries, but shouldn't full applications be optional? why gedit? gedit is part of the GNOME desktop as defined by GNOME. If you want the GNOME platform (which has most of the current GNOME libraries), install the gnome-platform-suite port. Maybe there's something in these variants -- Variants:graphics, office, universal, www -- but it's not obvious to me. It would be a worthwhile exercise for maintainers to install a complex meta-port from scratch, just to see if anything needs fixing. I can only imagine how long this will take to build. -- Paul Beard / www.paulbeard.org/ paulbeard.org ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users -- Randall Wood [EMAIL PROTECTED] The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy. -- Paul Beard / www.paulbeard.org/ paulbeard.org ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
ccache errors, when I have it configured OFF?
Anyone know what this is about? --- Building glib1 with target all Error: Target org.macports.build returned: shell command cd /opt/local/var/macports/build/_opt_mports_trunk_dports_devel_glib1/work/glib-1.2.10 make all returned error 2 Command output: make all-recursive Making all in . /bin/sh ./libtool --mode=link ccache /usr/bin/gcc-4.0 -O2 -I/opt/local/include -Wall -D_REENTRANT -L/opt/local/lib -o libglib.la -rpath /opt/local/lib -version-info 0:10:0 -release 1.2 -export-dynamic garray.lo gcache.lo gcompletion.lo gdataset.lo gdate.lo gerror.lo ghash.lo ghook.lo giochannel.lo giounix.lo glist.lo gmain.lo gmem.lo gmessages.lo gmutex.lo gnode.lo gprimes.lo grel.lo gscanner.lo gslist.lo gstrfuncs.lo gstring.lo gtimer.lo gtree.lo gutils.lo rm -fr .libs/libglib.la .libs/libglib.* .libs/libglib-1.2.* ccache -dynamiclib -flat_namespace -undefined suppress -o .libs/libglib-1.2.0.0.10.dylib garray.lo gcache.lo gcompletion.lo gdataset.lo gdate.lo gerror.lo ghash.lo ghook.lo giochannel.lo giounix.lo glist.lo gmain.lo gmem.lo gmessages.lo gmutex.lo gnode.lo gprimes.lo grel.lo gscanner.lo gslist.lo gstrfuncs.lo gstring.lo gtimer.lo gtree.lo gutils.lo -L/opt/local/lib -lc -install_name /opt/local/lib/libglib-1.2.0.dylib -compatibility_version 1 -current_version 1.10 ccache: illegal option -- d I tried just commenting out the line, but wondered if it defaulted to YES if there was nothing configured. macports.conf:# Use ccache (C/C++ compiler cache) - see http://ccache.samba.org/ macports.conf:configureccache no -- Paul Beard / www.paulbeard.org/ paulbeard.org ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
dependencies for gnome
Are all these *really* necessary? Error: The following dependencies failed to build: gnome-desktop-suite evince gdk-pixbuf glib1 gtk1 poppler poppler-data file-roller gcalctool gconf-editor gdm howl gedit gtksourceview2 py25-pygtksourceview gnome-applets gnome-control-center gnome-python-desktop gnome-media gtksourceview gnuregex totem-pl-parser gucharmap system-tools-backends p5-net-dbus p5-xml-twig gnome-audio gnome-backgrounds gnome-games ggz-client-libs libggz guile gmp libsdl_mixer libsdl smpeg py25-gtkglext gtkglext py25-opengl py25-pil py25-setuptools py25-tkinter tcl tk gnome-keyring-manager gnome-mag gnome-session gnome-system-monitor gtkmm cairomm glibmm libsigcxx2 gnome-terminal vte gnome-user-docs gnome-utils gnopernicus libgail-gnome libgtkhtml3 seahorse avahi dbus-python25 gdbm libdaemon py25-gdbm gpgme pth vino yelp firefox-x11 zip zenity seahorse *and* firefox? howl *and* avahi? Don't these do more or less the same thing? I can see needing a lot of libraries, but shouldn't full applications be optional? why gedit? Maybe there's something in these variants -- Variants:graphics, office, universal, www -- but it's not obvious to me. It would be a worthwhile exercise for maintainers to install a complex meta-port from scratch, just to see if anything needs fixing. I can only imagine how long this will take to build. -- Paul Beard / www.paulbeard.org/ paulbeard.org ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
dealing with ports that can't upgrade
So I have this problem where I can't upgrade metacity until I get Leopard. Is there a way to have MacPorts simply ignore you don't want upgraded or that can't be upgraded? Something as simple as a .ignore file in the port directory or an entry in a list in ports.conf . . . In the case of metacity and other ports similarly situated, why not an OS version test, if it's confirmed that Tiger is not suitable build platform? -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: dealing with ports that can't upgrade
On Sat, Jun 21, 2008 at 2:08 PM, Ryan Schmidt [EMAIL PROTECTED] wrote: On Jun 21, 2008, at 3:19 PM, paul beard wrote: So I have this problem where I can't upgrade metacity until I get Leopard. Is there a way to have MacPorts simply ignore you don't want upgraded or that can't be upgraded? Something as simple as a .ignore file in the port directory or an entry in a list in ports.conf . . . There is no such feature at this time. I suspected not: I'll make an RFE. In the case of metacity and other ports similarly situated, why not an OS version test, if it's confirmed that Tiger is not suitable build platform? If the current version of metacity will not be fixed to work on pre-Leopard, then the port should error out on pre-Leopard OS versions, and the last Tiger-compatible version of metacity should be resurrected from the repository and reinstated as a separate port. I am actually working my way through that: looks like 2.21.2 works, where 2.22 fails. But if the current metacity can be fixed to work on pre-Leopard, then that should be done instead. That sounds like a lot of work: something to do with X.org stuff that is leopard-specific. Seems to me that erroring out based on OS version is the cleanest way to go forward. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: dealing with ports that can't upgrade
On Sat, Jun 21, 2008 at 2:28 PM, Ryan Schmidt [EMAIL PROTECTED]
wrote:
On Jun 21, 2008, at 4:12 PM, paul beard wrote:
On Sat, Jun 21, 2008 at 2:08 PM, Ryan Schmidt wrote:
On Jun 21, 2008, at 3:19 PM, paul beard wrote:
So I have this problem where I can't upgrade metacity until I get
Leopard. Is there a way to have MacPorts simply ignore you don't want
upgraded or that can't be upgraded? Something as simple as a .ignore file
in
the port directory or an entry in a list in ports.conf . . .
There is no such feature at this time.
I suspected not: I'll make an RFE.
Do we really want people ignoring available upgrades? I don't think that's
a good feature to add.
If the upgrade doesn't install, why waste the cycles on it? And if a port's
current version is the only one that works for a given use case, do we want
to force an unwanted upgrade or force a user to downgrade it themselves?
Assume that someone who is using MacPorts knows what they're doing: setting
the ignore flag is not something that can be done by accident and it would
be trivial to display a message listing the ignored ports, so the user could
be reminded that they had thrown that switch.
Let's not get in the habit of thinking for others.
In the case of metacity and other ports similarly situated, why not an OS
version test, if it's confirmed that Tiger is not suitable build platform?
If the current version of metacity will not be fixed to work on
pre-Leopard, then the port should error out on pre-Leopard OS versions, and
the last Tiger-compatible version of metacity should be resurrected from the
repository and reinstated as a separate port.
I am actually working my way through that: looks like 2.21.2 works, where
2.22 fails.
But if the current metacity can be fixed to work on pre-Leopard, then
that should be done instead.
That sounds like a lot of work: something to do with X.org stuff that is
leopard-specific. Seems to me that erroring out based on OS version is the
cleanest way to go forward.
OK. Then something like this can be added to the metacity port:
platform darwin 7 {
pre-fetch {
return -code error ${name} requires Mac OS X 10.5 or
newer.
}
}
platform darwin 8 {
pre-fetch {
return -code error ${name} requires Mac OS X 10.5 or
newer.
}
}
However, this will not prevent the port from showing up in the list of
outdated ports, and it will not enable Tiger users to install the older
version. For that, the older version of metacity would need to be broken out
into a new port.
I leave this decision to the port's maintainers: ideally it would no longer
show up in the list of outdated ports, because it really isn't outdated for
that release of the OS.
--
Paul Beard / www.paulbeard.org/
[EMAIL PROTECTED]/[EMAIL PROTECTED]
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New wiki
Hmm, is it about time for the Bike Shed link to be cited?
As a non-committer who has used MacPorts since it was DarwinPorts and used
Fink before that, here's my two shiny bits of something or other.
I wasn't aware there was large body of documentation to be migrated, so the
argument that a new syntax has to be mastered isn't all that strong.
As to whether or not this is the most important issue, that is up to each
person who uses this project. No one is suggesting that port hacking stop so
that documentation can be re-written. What I suspect will happen, if an
accessible format is chosen, is that more contributors will appear to do
that work. I considered doing some docs for DarwinPorts and FreeBSD but the
work was to be done in docbook, if memory serves, and that just didn't work
for me. I didn't want to learn a text formatting system just to document how
to use a port management system. If you want to examine prioritization,
there's an example: how much of a volunteer's scarce attention do you want
applied to productive work vs learning a toolset?
Perhaps in the review of page views/status, we could find out how many
people use the docs in place and how many use TRAC as a resource. I wasn't
aware of it as documentation repository so much as a ticket manager, and I
have not seen a lot of wiki syntax/formatting beyond using the {{{ }}}
markup to denote code or fixed-width output.
I agree that the best way to see if this is a good idea is to try it. As
often as useage tips appear on this list, it would make a lot of sense to
put them all in one place.
Maybe some docs on how to build from the MacPorts trunk, so we can access
all the bug fixes to 1.6, would be a good place to start?
--
Paul Beard / www.paulbeard.org/
[EMAIL PROTECTED]/[EMAIL PROTECTED]
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New Howto
On Tue, Jun 10, 2008 at 12:00 PM, [EMAIL PROTECTED] wrote: Message: 11 Date: Tue, 10 Jun 2008 11:27:30 -0500 From: Lorin Rivers [EMAIL PROTECTED] Subject: Re: New Howto To: Jordan K. Hubbard [EMAIL PROTECTED] Cc: MacPorts Users macports-users@lists.macosforge.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=utf-8 Leaving aside the issue of what the best platform for sharing the info might be. If nobody knows it's there, the kick-assingest wiki server the world has or will ever see is not going to address my suggestion in the slightest. My point was that it's quite a challenge finding the current how-to's even if you already know they exist. If you are not in that smallish (I'm guessing--but I've been using *Ports for a fairly long time, and it was a recent message on this list that made me aware) category, then the chances this very useful series of articles will reach the audience that needs it is quite small. Just to refresh, there needs to be a link from the main MacPorts documentation site to the how-to's. As a first step, it's awesome. Taking up the earlier comment on a need for discussion, what are the pros and cons of the different wiki platforms? I would say, if I had a vote (who does?), that whatever people are willing to use wins. It may not be elegant or state of the art, but the best is the enemy of the good, and good is usually good enough. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: macports-users Digest, Vol 22, Issue 6
On Fri, Jun 6, 2008 at 12:00 PM, [EMAIL PROTECTED] wrote: Message: 14 Date: Thu, 5 Jun 2008 23:26:53 -0500 From: Ryan Schmidt [EMAIL PROTECTED] Subject: Re: New Howto To: Jordan K.Hubbard [EMAIL PROTECTED] Cc: MacPorts Users macports-users@lists.macosforge.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed We should not now add another wiki system with a conflicting syntax. If we wanted to switch from Trac wiki to MediaWiki we could discuss that, but converting all existing content could be difficult (though maybe someone's already written an importer; I haven't looked). Do we have to discuss it? I think discussion is one of the reasons there is no 1.6.x release (or an even more full-featured one). What format are most of the articles in and what flavor is getting the most attention right now? And who decided a format as simple as wiki needed to be forked or otherwise complicated? -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Suggested port command enhancement?
On Thu, Jun 5, 2008 at 1:35 PM, Daniel J. Luke [EMAIL PROTECTED] wrote: On Jun 5, 2008, at 3:43 PM, paul beard wrote: I don't see the difference? There's extra whitespace after the \ in portmirror but not in port. OK. So that's solved. But perhaps these is an additional postflight step needed? [/Users/paul]# portmirror The database doesn't exist at /opt/local/var/macports/distfiles_mirror.db while executing open_database (file /opt/local/bin/portmirror line 91) ([EMAIL PROTECTED])-(01:51 PM / Thu Jun 05) [/Users/paul]# touch /opt/local/var/macports/distfiles_mirror.db ([EMAIL PROTECTED])-(01:51 PM / Thu Jun 05) [/Users/paul]# portmirror deleting /opt/local/var/macports/distfiles/aalib/aalib-1.4rc5.tar.gz deleting /opt/local/var/macports/distfiles/apache2/httpd-2.2.8.tar.bz2 deleting /opt/local/var/macports/distfiles/apr/apr-1.2.12.tar.bz2 -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Suggested port command enhancement?
On Thu, Jun 5, 2008 at 4:34 PM, Rainer Müller [EMAIL PROTECTED] wrote: Sorry, I was unclear, it is not a missing backslash. There is a trailing whitespace after the backslash in portmirror. The backslash has to be the last character on the line, otherwise Tcl doesn't see the next line as continuation of the comment. Tcl interprets the backslash as an escape for the space, not for the newline character, so missing was really misleading here. It's hard to see the difference when looking at the output of head or cat. Fixed in r37393 for the release_1_6 branch. Hope this is clear now? Yup, perfectly. Now if only these changes could be pushed out to a waiting world hint hint -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Any word on a new release?
These features that are not in 1.6 but seem pretty well-tested -- could they be released to those of who haven't switched to the trunk? Maybe a 1.6.1 release to fix the .profile bug and add some of the other odds and ends? -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
admin question: can digests be tweaked to come no more often than daily?
Can the threshold for digests be bumped up so we don't get so many per day? I have gotten as many as four digest mailing in a single day, kinda defeats the purpose. Thanks -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Manual install
On Wed, May 14, 2008 at 2:42 PM, [EMAIL PROTECTED] wrote: Message: 2 Date: Wed, 14 May 2008 12:39:48 +0200 From: Anders F Bj?rklund [EMAIL PROTECTED] Subject: Re: Manual install To: Simon Wheatley [EMAIL PROTECTED] Cc: liste gtk macports-users@lists.macosforge.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Simon Wheatley wrote: Is it possible to point MacPorts at a downloaded package of some kind and say install that? Something similar to Debian's 'dpkg -i'? Not at the moment... You can build a package (pkg/rpm/deb), but then it doesn't integrate with the already installed ports and registry and so goes outside or parallel to what port knows about. Or you can build an archive (tgz/tbz/tlz), but then you have to download and move it to the right directory yourself and make sure port base is already installed etc. Preferably you would use something like 'apt-get install', and that would download and install the binary package ? 'port -b' is supposed to do that, but only works with local packages yet. There is a ticket to implement remote archives, but it's rather stale... http:// trac.macports.org/ticket/8571 and also http://trac.macports.org/ ticket/10919 Just out of curiousity, what is involved in making this work? Assuming I have the package installed and working on machine A, I could use port contents foo and pass that to zip or tar. That gives me all the files in a port neatly stowed in an archive. If I add the receipt file, is there a registry that reads and manages that or is it just the text files on disk? The reason I ask is that a. it would be very useful to have this feature, especially on systems without a lot of horsepower (given the high degree of standardization on this hardware, why compile anything yourself, if a compile farm exists to do that?) and b. I have done the steps above to get around packages that don't build, and I wonder how much cruft that introduces. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: MySQL Server Installer - found 2 repeatable bugs,
Why not create a (succinct) bug report/patch diff in TRAC? I have found the mysql/php/apache cluster to be troublesome to install and run, but never cared enough to generate this much diagnostics (it doesn't seem to be a pressing issue but a patch shows that a solution is possible). On Tue, May 13, 2008 at 2:48 PM, [EMAIL PROTECTED] wrote: Message: 6 Date: Tue, 13 May 2008 16:52:43 -0500 From: Bill Hernandez [EMAIL PROTECTED] Subject: MySQL Server Installer - found 2 repeatable bugs, and a couple of suggestions To: MacPorts Users macports-users@lists.macosforge.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
distcc? is there a howto on using this?
Is anyone successfully using this? I see it mentioned in macports.conf and the possibilities are very tantalizing. If anyone is using it to leverage idle cycles, it would be useful to know how well it works and how to work it. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: gnome-libs fails to install/python bindings for GNOME
On Sun, May 4, 2008 at 9:45 AM, [EMAIL PROTECTED] wrote: Send macports-users mailing list submissions to Message: 4 Date: Sun, 04 May 2008 14:17:10 +0100 From: David Rowe [EMAIL PROTECTED] Subject: Re: gnome-libs fails to install/python bindings for GNOME print To: Randall Wood [EMAIL PROTECTED], macports-users@lists.macosforge.org MacPorts Users macports-users@lists.macosforge.org, [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-1; format=flowed David Rowe wrote: . . . . Does anyone have any suggestions on what port I should install to get the 'python bindings for GNOME print' with py25. Sorry folks, that was a touch of RTFM. http://www.gramps-project.org/wiki/index.php?title=Installation says: Additional software GRAMPS can benefit from GRAMPS does not rely on the following programs, however, having them will increase your productivity: * *Gnome-print*: It adds the ability to directly print, to preview, and to generate fully internationalized PS and PDF output. At this time, one needs to install gnome-python-desktop to obtain this package. . I have now installed gnome-python-desktop and that did the business David Rowe useful to know. I would suggest that be added as a dependency, but a Portfile for 3.0 is in testing right now so perhaps it's best to focus on that. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: [help] Writing to /opt/local/var/log/install_setup.log
I would have thought logger(1) would do this but it seems not to work as advertised. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: .profile not installed
On Thu, Apr 24, 2008 at 8:50 AM, [EMAIL PROTECTED] wrote: Message: 7 Date: Thu, 24 Apr 2008 11:51:59 -0400 From: Marco Battistella [EMAIL PROTECTED] Subject: .profile not installed To: MacPorts Users macports-users@lists.macosforge.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=windows-1252 hi, i have just installed macport in a fresh OS X 10.3.9 server installation using the 1.6 package installer. After the installation i have noticed that no .profile has been installed. on the manual it reads: MacPorts requires changes to the shell environment. If MacPorts was installed using the Mac OS X package installer, a postflight script was run after installation that places a .profile file in the home directory, which contains the environmental variables required for MacPorts. If a current .profile file exists at installation time it is renamed to mpsaved_$timestamp. So that i would be able to use the port command witout specifying the full path i run: # echo export PATH=/opt/local/bin:/opt/local/sbin:$PATH ~/.bash_profile So it works for me right now, but i would like to find out why it didn't install by default and is there something else that would have been part of the .profile file that i should add to my .bash_profile file? Anyone know how many times the MacPorts installer/dmg has been downloaded since 1.6 was released? That's a lot of people who have been bitten by this bug. Is there any plan to release a 1.6.1 or 1.7 release to fix it? -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: ??? MACOSX_DEPLOYMENT_TARGET environment variable set to: 10.1
On Tue, Apr 22, 2008 at 3:19 PM, Ryan Schmidt [EMAIL PROTECTED]
wrote:
This should not be a problem with MacPorts trunk which passes the correct
value for MACOSX_DEPLOYMENT_TARGET to every port.
For MacPort 1.6.0 as released, try adding this to the port:
platform darwin 7 {
configure.env-append MACOSX_DEPLOYMENT_TARGET=10.3
build.env-append MACOSX_DEPLOYMENT_TARGET=10.3
}
platform darwin 8 {
configure.env-append MACOSX_DEPLOYMENT_TARGET=10.4
build.env-append MACOSX_DEPLOYMENT_TARGET=10.4
}
platform darwin 9 {
configure.env-append MACOSX_DEPLOYMENT_TARGET=10.5
build.env-append MACOSX_DEPLOYMENT_TARGET=10.5
}
all the more reason to wonder when a new release will be cut off the trunk.
--
Paul Beard / www.paulbeard.org/
[EMAIL PROTECTED]/[EMAIL PROTECTED]
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
Re: ruby malloc errors
On Mon, Apr 14, 2008 at 11:38 AM, [EMAIL PROTECTED] wrote: Message: 2 Date: Mon, 14 Apr 2008 10:35:00 -0700 From: Carina C. Zona [EMAIL PROTECTED] Subject: Re: ruby malloc errors To: macports-users@lists.macosforge.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=iso-8859-1 How much RAM do you have installed? 3GB total, 1.4GB free Hmm, that seems adequate ;-) I had this problem on another system and it was due to the ruby-docs taking a lot of RAM to build. Once I commented or configured that out, all was well. Maybe comment out install-doc and see if that makes a difference? 50 destroot.target install install-doc -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: ruby malloc errors
in malloc_error_break to debug tclsh(81864,0x80254fa0) malloc: *** mmap(size=65536) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug tclsh(81865,0x80254fa0) malloc: *** mmap(size=65536) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug tclsh(81866,0x80254fa0) malloc: *** mmap(size=65536) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug tclsh(81867,0x80254fa0) malloc: *** mmap(size=65536) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug tclsh(81868,0x80254fa0) malloc: *** mmap(size=65536) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug tclsh(81869,0x80254fa0) malloc: *** mmap(size=65536) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug tclsh(81870,0x80254fa0) malloc: *** mmap(size=65536) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug tclsh(81871,0x80254fa0) malloc: *** mmap(size=65536) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug tclsh(81872,0x80254fa0) malloc: *** mmap(size=65536) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug tclsh(81873,0x80254fa0) malloc: *** mmap(size=65536) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug tclsh(81874,0x80254fa0) malloc: *** mmap(size=65536) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug tclsh(81875,0x80254fa0) malloc: *** mmap(size=65536) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug tclsh(81876,0x80254fa0) malloc: *** mmap(size=65536) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug tclsh(81877,0x80254fa0) malloc: *** mmap(size=65536) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug tclsh(81878,0x80254fa0) malloc: *** mmap(size=65536) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug tclsh(81879,0x80254fa0) malloc: *** mmap(size=65536) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug tclsh(81881,0x80254fa0) malloc: *** mmap(size=65536) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug tclsh(55731,0xa09c3074) malloc: *** mmap(size=16384) failed (error code=12) *** error: can't allocate region *** set a breakpoint in malloc_error_break to debug unable to alloc 4096 bytes Abort trap How much RAM do you have installed? -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
seahorse build issues (I would have used trac, spelled c-r-a-p, but can't get a working password.)
/usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../.. -DXTHREADS -I/opt/local/include/nautilus -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include -I/opt/local/include/gtk-2.0 -I/opt/local/lib/gtk-2.0/include -I/opt/local/include/atk-1.0 -I/opt/local/include/cairo -I/opt/local/include/pango-1.0 -I/opt/local/include/freetype2 -I/opt/local/include/libpng12 -I/usr/X11R6/include -DGNOMELOCALEDIR=\/opt/local/share/locale\ -I/opt/local/include -O2 -MT seahorse-nautilus.lo -MD -MP -MF .deps/seahorse-nautilus.Tpo -c seahorse-nautilus.c -fno-common -DPIC -o .libs/seahorse-nautilus.o seahorse-nautilus.c:27:41: error: libgnomevfs/gnome-vfs-utils.h: No such file or directory seahorse-nautilus.c:28:45: error: libgnomevfs/gnome-vfs-file-info.h: No such file or directory seahorse-nautilus.c:29:39: error: libgnomevfs/gnome-vfs-ops.h: No such file or directory make[3]: *** [seahorse-nautilus.lo] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 kitchen:~ root# locate gnome-vfs-file-info.h /opt/local/include/gnome-vfs-2.0/libgnomevfs/gnome-vfs-file-info.h /opt/local/share/gtk-doc/html/gnome-vfs-2.0/gnome-vfs-20-gnome-vfs-file-info.html /opt/local/var/macports/software/gnome-vfs/2.20.1_1/opt/local/include/gnome-vfs-2.0/libgnomevfs/gnome-vfs-file-info.h /opt/local/var/macports/software/gnome-vfs/2.20.1_1/opt/local/share/gtk-doc/html/gnome-vfs-2.0/gnome-vfs-20-gnome-vfs-file-info.html kitchen:~ root# port provides /opt/local/include/gnome-vfs-2.0/libgnomevfs/gnome-vfs-file-info.h /opt/local/include/gnome-vfs-2.0/libgnomevfs/gnome-vfs-file-info.h is provided by: gnome-vfs and I reinstalled gnome-vfs already today to ensure it was all up to date. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: .profile not installed; 'ports' command not found
On Thu, Mar 27, 2008 at 12:31 PM, Ryan Schmidt [EMAIL PROTECTED] wrote: There is a bug in MacPorts 1.6.0 which prevents the .profile from being created. You'll have to create it yourself. The bug has been fixed in trunk but we haven't released a new version of MacPorts since then. Is there a reason why a new release hasn't been cut, considering how many new users are getting bitten by this bug? -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: is the avahi user creation supposed to be part of
On Mon, Mar 24, 2008 at 5:21 PM, Adam Dershowitz [EMAIL PROTECTED] wrote: On Mar 24, 2008, at 3:17 PM, Nehemiah Dacres wrote: why are you installing avahi?it already says on their Track that avahi is an implimentation of mDNS. having 2 of those on the same machine would clearly be a problem, simply use Bonjour. The Avahi mac people will simply have to make their avahi damon work around Bonjour becasue removing bonjour will most likely break mac os functionality. It is installed as part of a dependency chain. I have gimp installed, which depends on librsvg, which depends on gnome-vfs which in turn depends on avahi I don't really know why avahi is necessary (or if it actually is necessary), but both avahi and Bonjour seem to be working fine, and coexisting, on my machine. Not sure if any of this means it has to be running, just so long as it's installed. It doesn't look like avahi has been running here and I haven't noticed anything missing. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: is the avahi user creation supposed to be part of installing avahi?
On Mon, Mar 24, 2008 at 6:53 PM, nodje [EMAIL PROTECTED] wrote: thanks for the tip Adam. but the dbus is already started in my case: It's avahi-daemon that cannot start. For some obscure reason, it cannot connect to dbus... do you need it to? -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: [pymetar-dev] man py-metar
On Sun, Mar 23, 2008 at 6:28 AM, Charlse Darwin [EMAIL PROTECTED] wrote: Begin forwarded message: From: Tobias Klausmann [EMAIL PROTECTED] Date: March 23, 2008 9:16:25 AM EDT (CA) To: [EMAIL PROTECTED] Subject: Re: [pymetar-dev] man py-metar Hi! On Sun, 23 Mar 2008, Charlse Darwin wrote: Is there any man page for py-metar? How do I use this thing In a way, yes. Python has its own manpage-like docs system, called, cunningly, pydoc. So pydoc pymetar should give you a manpage-like description of pymetars API (it's a library, so that's its primary documentation). In case you don't have pydoc, the package comes with a file called librarydoc.txt which is identical in content. As for a more general description, there's also a README. Where those files typically end up in the macports package system, I don't know. $ uname -a Darwin Mac.local 8.11.0 Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC Power Macintosh powerpc $ metar -bash: metar: command not found $ py-metar -bash: py-metar: command not found Pymetar comes with two example scripts, called pymet and weather.py. Both are examples only but might be enough for what you need. Unfortunately, I don't know where macports packages usually put the auxillary files for installed packages. The packager might also have removed the examples, though I doubt it. Maybe someone else on the -dev list can shed a light on this? Regards, Tobias 'locate pydoc' should tell you what versions of pydoc you have. There will be a system-supplied one in /usr/bin and MacPorts-provided ones in /opt/local/bin, with version numbers attached. I found pydoc2.5. I couldn't get it to run in the terminal in any useful way but running it like this: pydoc2.5 -p81 pydoc server ready at http://localhost:81/ was useful. But for all that, I found that there was no documentation for metar (I just installed it to see how this worked). I don't know why it wouldn't be installed by default. Poking around in the build directory might be informative. I would file a bug report, as I think all modules/libs should install docs if they have them. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: [pymetar-dev] man py-metar
On Sun, Mar 23, 2008 at 6:28 AM, Charlse Darwin [EMAIL PROTECTED] wrote: Begin forwarded message: From: Tobias Klausmann [EMAIL PROTECTED] Date: March 23, 2008 9:16:25 AM EDT (CA) To: [EMAIL PROTECTED] Subject: Re: [pymetar-dev] man py-metar Hi! On Sun, 23 Mar 2008, Charlse Darwin wrote: Is there any man page for py-metar? How do I use this thing And as noted, there are sample scripts: # weather.py kbfi Weather report for Seattle, Seattle Boeing Field, WA, United States (kbfi) as of 2008-03-23 13:53:00Z Values of None indicate that the value is missing from the report. Temperature: 6.7 C / 44.1 F Rel. Humidity: 88% Wind speed: 4.02 m/s (3 Bft) Wind direction: 120 deg (ESE) Pressure: 1016 hPa Dew Point: 5.0 C / 41.0 F Weather: rain; mist Sky Conditions: overcast They will likely provide a lot of useful details. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: is the avahi user creation supposed to be part of installing avahi?
On Sun, Mar 23, 2008 at 8:19 PM, nodje [EMAIL PROTECTED] wrote: I had an avahi probleme due to thuis missing user. I recently updated avahi to 0.6.22_0 (from 0.6.17_0). It fixed the missing avahi user problem. But I'm still having an issue, apparently similar with Paul's one. Console log: 24/03/2008 12:05:13 PM org.freedesktop.avahi-dnsconfd[522] Failed to connect to the daemon. This probably means that you 24/03/2008 12:05:13 PM org.freedesktop.avahi-dnsconfd[522] didn't start avahi-daemon before avahi-dnsconfd. 24/03/2008 12:05:13 PM com.apple.launchd[1] (org.freedesktop.avahi-dnsconfd[522]) Exited with exit code: 1 24/03/2008 12:05:13 PM com.apple.launchd[1] ( org.freedesktop.avahi-dnsconfd) Throttling respawn: Will start in 10 seconds 24/03/2008 12:05:14 PM org.freedesktop.avahi-daemon[523] Found user 'avahi' (UID 502) and group 'avahi' (GID 502). 24/03/2008 12:05:14 PM org.freedesktop.avahi-daemon[523] Successfully dropped root privileges. 24/03/2008 12:05:14 PM org.freedesktop.avahi-daemon[523] avahi-daemon 0.6.22 starting up. 24/03/2008 12:05:14 PM org.freedesktop.avahi-daemon[523] WARNING: No NSS support for mDNS detected, consider installing nss-mdns! 24/03/2008 12:05:14 PM org.freedesktop.avahi-daemon[523] dbus_bus_get_private(): Failed to connect to socket /opt/local/var/run/dbus/system_bus_socket: Connection refused 24/03/2008 12:05:14 PM org.freedesktop.avahi-daemon[523] WARNING: Failed to contact D-Bus daemon. 24/03/2008 12:05:14 PM com.apple.launchd[1] (org.freedesktop.avahi-daemon[523]) Exited with exit code: 255 24/03/2008 12:05:14 PM com.apple.launchd[1] (org.freedesktop.avahi-daemon) Throttling respawn: Will start in 10 seconds 24/03/2008 12:05:23 PM org.freedesktop.avahi-dnsconfd[524] connect(): No such file or directory 24/03/2008 12:05:23 PM org.freedesktop.avahi-dnsconfd[524] Failed to connect to the daemon. This probably means that you 24/03/2008 12:05:23 PM org.freedesktop.avahi-dnsconfd[524] didn't start avahi-daemon before avahi-dnsconfd. 24/03/2008 12:05:23 PM com.apple.launchd[1] (org.freedesktop.avahi-dnsconfd[524]) Exited with exit code: 1 Would reinstall avahi solve the problem? I have seen very few thread about the topic. Paul, did you manage to get a working asahi? Thanks, --nodje To be honest, I'm not sure. This seems to be one of those areas where MacPorts and Apple duplicate each other's efforts. I don't know if avahi is supposed to do anything other than just be installed so other applications don't grumble. An mDNS responder exists on OS X, anyway. At the moment, my avahi isn't even running, for some reason. I don't know if it matters or not. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: changing perl path to /opt/local/bin/perl5.8.8
On Sat, Mar 22, 2008 at 4:04 AM, Marc Manthey [EMAIL PROTECTED] wrote: come on , i just changed #!/usr/bin/perl to #!/opt/local/bin/perl5.8.8 You asked: I need to change the systemwide variable for using perl5.8.8 to * /opt/local/bin/perl5.8.8 * instead of using * /usr/bin/perl5.8.8 * could someone provide me a comand line for dummys to change it ;) ? And that's what changing your PATH will do. The instructions that Ryan sent you to aren't optional. MacPorts is not guaranteed to work without that (indeed, without the right PATH, nothing will work properly). If you're going to ask for help, take it when it's offered. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: changing perl path to /opt/local/bin/perl5.8.8
On Fri, Mar 21, 2008 at 5:03 PM, Marc Manthey [EMAIL PROTECTED] wrote: hello list, i would like to run a little analysis tool whitch is writen in perl on my leopard ppc mac. After upgrading my perl librarys *) on OSX PPC with macports I need to change the systemwide variable for using perl5.8.8 to */opt/local/bin/perl5.8.8 * instead of using */usr/bin/perl5.8.8* could someone provide me a comand line for dummys to change it ;) ? use the PATH, Luke. What does echo $PATH tell you? -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: how to delete deactivated ports
On Thu, Mar 20, 2008 at 3:17 PM, Ryan Schmidt [EMAIL PROTECTED] wrote: I wish you wouldn't indiscriminately use the -f (force) flag all the time. If it were intended to be used all the time it would have been made the default. In particular it should only be needed for port -f uninstall inactive. It should not be needed for clean, and the only times it would be needed for upgrade are in unusual situations, which you would probably want to handle by hand individually rather than automate. I non-concur on this: I think -f should be the default on upgrades (if you don't mean it, don't ask for it). It's confusing, in case the regular flow of questions on this hasn't made clear. Ideally, you wouldn't need any flags: port upgrade foo would Just Work. I would put clean in a central config file as well: I suspect this isn't done on a port by port basis. Are there cases where you don't need -f on upgrades? I generally find I have to use it all the time if I am upgrading anything. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: GCC compilation time
On Thu, Mar 20, 2008 at 5:47 PM, James Sumners [EMAIL PROTECTED] wrote: GCC can take a _long_ time to compile. Um, yeah. The first I ever tried to build a new gcc, it took me several *days*. But that was a long time ago and a hardware platform far far away (you kids ever use a SPARCstation 20?). Yes, it will take a long time. An hour is nothing to a gcc compile job. It will finish in hours, not days, but it's a big job. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: gtk2 compilation failed
On Thu, Mar 20, 2008 at 6:50 PM, Alejandro Aragon [EMAIL PROTECTED] wrote: Hello everyone, I was trying to build pidgin, and when compiling gtk2 I had the following error: i686-apple-darwin9-gcc-4.0.1: /usr/X11/lib/libXrandr.2.0.0.dylib: No such file or directory make[4]: *** [libgdk-x11-2.0.la] Error 1 I'm new to Mac OS so I was wondering why this library is not there. Is there an easy way to fix this? You installed the X11 SDK when you installed XCode? And have the latest X11 installed? [/Users/paul]:: locate libXrandr /Developer/SDKs/MacOSX10.3.9.sdk/usr/X11R6/lib/libXrandr.2.0.dylib /Developer/SDKs/MacOSX10.3.9.sdk/usr/X11R6/lib/libXrandr.2.dylib /Developer/SDKs/MacOSX10.3.9.sdk/usr/X11R6/lib/libXrandr.a /Developer/SDKs/MacOSX10.3.9.sdk/usr/X11R6/lib/libXrandr.dylib /Developer/SDKs/MacOSX10.4u.sdk/usr/X11R6/lib/libXrandr.2.0.dylib /Developer/SDKs/MacOSX10.4u.sdk/usr/X11R6/lib/libXrandr.2.dylib /Developer/SDKs/MacOSX10.4u.sdk/usr/X11R6/lib/libXrandr.a /Developer/SDKs/MacOSX10.4u.sdk/usr/X11R6/lib/libXrandr.dylib /usr/X11R6/lib/libXrandr.2.0.dylib /usr/X11R6/lib/libXrandr.2.dylib /usr/X11R6/lib/libXrandr.a /usr/X11R6/lib/libXrandr.dylib -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
ticket 14547 (libgnomecups printing problem)
Anyone in a position to verify and commit that patch that's with this ticket? http://trac.macosforge.org/projects/macports/ticket/14547 -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: how to delete deactivated ports
On Wed, Mar 19, 2008 at 10:04 PM, J P Lewis [EMAIL PROTECTED] wrote: Hello, (a novice question) I installed a package (py25-matplotlib), had some trouble with using it, then did a port selfupdate, then upgraded the package. In the process, a number of packages were deactivated. For example, it looks like I now have two copies of python25, numpy, 3 copies of libpng, etc. How can I uninstall these now (to clean up and save disk space)? For example port uninstall python25 @2.5.1_2+darwin_8 says that I cannot uninstall this (deactivated) python because other things depend on it. Most of those things are things that I'm actively using (py-readline for example). should I uninstall and reinstall all of these? If so, it seems like upgrading is a bad strategy, one can save work by uninstalling and reinstalling? port -f uninstall inactive should do it. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Kismet on OSX 10.5.1 Leopard
On Sun, Mar 16, 2008 at 1:26 PM, walts [EMAIL PROTECTED] wrote: I followed the instructions and did not notice any errors in setting up libpcap. Here's what I get: does the Kismac binary work with 10.5.x? -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Kismet on OSX 10.5.1 Leopard
On Sun, Mar 16, 2008 at 2:22 PM, Walt Scrivens [EMAIL PROTECTED] wrote: I'm pretty comfortable with command-line and green-screen interfaces so I haven't tried it so far. Me too, but sometimes it's worth trying a known-good solution to isolate problems. I just downloaded and installed R65 (there are several versions shown in my google search and that seemed to be the highest number). Hmm, I have r239 . . . it seems to work just fine. latest version seems to be 242 http://tehbin.com/Bin/KisMAC/trunk/. In any event, here is the error I got: KisMAC is not able to load the Apple Airport driver, if you killed it by loading the Viha driver. Try restarting KisMAC. The error dialog box kept on popping up over and over, so I force-quit Kismac and restarted it, with the same result. I have never had a problem with it (late 2003 iBook, Airport Extreme card, 10.4.11). -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Kismet on OSX 10.5.1 Leopard
On Sun, Mar 16, 2008 at 4:49 PM, Walt Scrivens [EMAIL PROTECTED] wrote: That worked! I have only my own home network to look at here - will have to wait until I get to work tomorrow where I have a more robust test environment to really give this a workout, but it looks promising. Thanks for the help! No problem. A walk around the block can be informative as well (I think I counted 30-something networks last time I tried it). -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Upgrade to Leopard mostly smooth, but has small glitch
On Fri, Mar 7, 2008 at 7:11 PM, Ryan Schmidt [EMAIL PROTECTED] wrote: On Mar 7, 2008, at 14:31, Bill Hernandez wrote: I just installed Leopard on iMacG5 and everything went off very well. However when I restarted and looked at all the usual preferences, I launched the terminal and tried : Did I understand correctly that you had Tiger, installed MacPorts and several ports, and now upgraded to Leopard and are trying to continue using the ports that were already installed? If so, I can't recommend that. I suggest reinstalling MacPorts and your ports from scratch. Ports may need to build differently on each version of Mac OS X. That seems really cumbersome. If it is necessary, any way that the MacPorts team could whip up a script to migrate ports to a new OS release? or will a simple for loop (for i in `port installed`; do . . . ) do it? But on to the OP's question, httpd is running? What do those lines do if you run them in the Terminal? % export ULIMIT_MAX_FILES=ulimit -S -n `ulimit -H -n` % echo $ULIMIT_MAX_FILES and as a hint, if you install BBedit's command line tools, you can simply type edit filename instead of all that other stuff. Or use TextWrangler, for those who are short of coin. It has the same facility. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: MacPorts caching of distfiles [was Re: ntfs-3g 1.1120 source missing]
On Feb 24, 2008, at 9:29 PM, Rainer Müller wrote: Why are you against adding more logic to the fetch code? given the oft-stated lack of hackers on the MacPorts base, insisting on this without stepping up to do the work to make it happen doesn't do much. If you have an itch to hack on base/ there are more pressing needs, I think 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: anyone seeing issues with ruby not building?
On Thu, Feb 21, 2008 at 11:26 PM, Paul Guyot [EMAIL PROTECTED] wrote: It sounds like an old problem with the ruby port. You need to deactivate the old version first. I don't think that's it. I have gone so far as to uninstall ruby and I get the same result. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
anyone seeing issues with ruby not building?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is after several iterations of sync/clean/build/repeat. - --- Staging ruby into destroot Error: Target org.macports.destroot returned: shell command cd / opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ru by/work/ruby-1.8.6-p111 make install install-doc DESTDIR=/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ru by/work/destroot returned error 2 Command output: ./miniruby ./instruby.rb --dest-dir=/opt/local/var/ macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ru by/work/destroot --extout=.ext --make=make --mflags= --make- flags=DESTDIR=/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ru by/work/destroot --installed-list .installed.list --mantype=doc installing binary commands installing command scripts installing library scripts installing headers installing manpages installing extension objects installing extension scripts Generating RDoc documentation ./miniruby ./runruby.rb --extout=.ext -- ./bin/rdoc --all --ri -- op .ext/rdoc . dyld: lazy symbol binding failed: Symbol not found: _snprintf$LDBLStub Referenced from: /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ru by/work/ruby-1.8.6-p111/libruby.dylib Expected in: flat namespace dyld: Symbol not found: _snprintf$LDBLStub Referenced from: /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_ru by/work/ruby-1.8.6-p111/libruby.dylib Expected in: flat namespace make: *** [rdoc] Trace/BPT trap Error: Unable to upgrade port: 1 [/Users/paul]# uname -a Darwin tichy.paulbeard.org 8.11.0 Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC Power Macintosh powerpc ([EMAIL PROTECTED])-(10:06 PM / Thu Feb 21) [/Users/paul]# gcc -v Using built-in specs. Target: powerpc-apple-darwin8 Configured with: /private/var/tmp/gcc/gcc-5367.obj~1/src/configure -- disable-checking -enable-werror --prefix=/usr --mandir=/share/man -- enable-languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg] [^.-]*$/s/$/-4.0/ --with-gxx-include-dir=/include/c++/4.0.0 --with- slibdir=/usr/lib --build=powerpc-apple-darwin8 --host=powerpc-apple- darwin8 --target=powerpc-apple-darwin8 Thread model: posix gcc version 4.0.1 (Apple Computer, Inc. build 5367) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAke+ZvcACgkQjE2ksZfa4ZVYNQCcCxMt8e/CUQHghrmH1BQVwqCR vPIAn18aDiG493zvtkNzlwxAiBYnTZM7 =2Ufd -END PGP SIGNATURE- ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
unpleasant surprises: no ports are installed
Something has come undone in my efforts to get the MAMP stack re-installed. [/opt/local/var/macports/receipts]# port installed | more Error: port installed failed: Registry error: php5 @ 5.2.5_1+apache2+darwin_8+macosx+mysql5 not registered as installed. No ports are installed. This looks worse than it is. It looked like a couple of malformed receipts in php5 (5.2.5_1+apache2+darwin_8+macosx+mysql5, 5.2.5_1+apache2+macosx) had blocked things up. Once I removed them, the list of installed ports is available. Seems to me that either bad receipts (which I think is actually a case of a malformed installation/wrong variants) should not be written (the port request would exit before doing anything wrong) or the parsing process would ignore them rather than bombing out. The bits are all installed: it's now just a matter of getting them recognized by the infrastructure. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: {Disarmed} unpleasant surprises: no ports are installed
On Feb 19, 2008 9:32 AM, Jay Chandler [EMAIL PROTECTED] wrote: The FreeBSD ports tree has a tool to address such things-- pkgdb -F tends to sort 'em out quickly. Is there a MacPorts equivalent to this? yes, i have used that many times. it might be a worthwhile RFE for the next release of MacPorts. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Specifying an install directory
On Feb 10, 2008 8:39 PM, Eric Soli [EMAIL PROTECTED] wrote: I am attempting to install pear-base into /usr/bin instead of /opt/local/bin. My best understanding from the man page is that I should use: bash$ sudo port -D /usr/bin install pear-base but it still ends up in /opt/local. Is there a way plant this pear tree next to /usr/bin/php? You don't say why you want to do this or why the source tarball/distribution doesn't work for you. It looks, from reading the INSTALL file, that it is best installed by and within the php process. Unix make sure you have enabled default extensions, and if you want faster downloads, enable the zlib extension. You must also enable the CLI SAPI with the --enable-cli extension directive. After this, simply run: make install-pear and PEAR will be automatically configured for you. go-pear === For users who cannot perform the above steps, or who wish to obtain the latest PEAR with a slightly higher risk of failure, use go-pear. go-pear is obtained by downloading http://go-pear.org and saving it as go-pear.php. After downloading, simply run php go-pear.php or open it in a web browser (windows only) to download and install PEAR. Seems like you could use the system php to perform the second operation. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Specifying an install directory
a On Feb 10, 2008 8:39 PM, Eric Soli [EMAIL PROTECTED] wrote: I am attempting to install pear-base into /usr/bin instead of /opt/local/bin. My best understanding from the man page is that I should use: bash$ sudo port -D /usr/bin install pear-base but it still ends up in /opt/local. Is there a way plant this pear tree next to /usr/bin/php? what does /usr/bin/pear not provide? Comparing /usr/bin/pear with the one I just built in destroot doesn't show much difference. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Specifying an install directory
On Feb 11, 2008 4:04 PM, Eric Soli [EMAIL PROTECTED] wrote: Hi Paul I tried the instructions in the distrbution, but the 'make' command failed. I'll be poring over this: http://www.cs.utah.edu/dept/old/texinfo/make/make_toc.html the man pages for a while. well, the docs are quite stale. the go-pear.org domain is expired and for sale, so that's busted. Does pear run well from /opt/local? I am trying to build a *AMP stack. (DAMP for Darwin?) It just looks like less re-configuring if it runs from the same directory as php. I don't see why it wouldn't. Is there some reason to run the stock Apple php (PHP 4.4.7 ) vs a more recent and perhaps more extensible one? -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Is HFS really scary?
On Feb 6, 2008 5:17 AM, David Corking [EMAIL PROTECTED] wrote: He is known for exaggeration. He once called all C++ programmers unspeakable names on a mailing list. However if you like his designs, there is an ext2 fs driver for Mac OS X! I personally am I bit frustrated with HFS+, as I experienced first-hand the limits of its fsck utility (*). But I am no filesystem expert, and my one anecdote would not be enough to justify a 'crappy' label. if people seriously ask you to consider linux, ask them which one and why that one and not the others. They could ask you why you prefer macports over fink or even FreeBSD. Be ready to answer! [OT] I use FreeBSD and like it just fine: in fact that's one of the reason I use [Mac|Darwin]Ports. fink was fine but once it became a leaderless mob, I left. So I have tried the two ports systems that have traction, and have a choice. Now let's talk about hundreds of Linux distros . . . . ;-) [/OT] -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: libIDL woes
On Feb 5, 2008 6:14 PM, Ryan Schmidt [EMAIL PROTECTED] wrote: The problem has not been worked around. The bug is still open: http://trac.macosforge.org/projects/macports/ticket/14144 The problems that were worked around were the unable to infer tagged configuration bug affecting apache2, mjpegtools and possibly others. These were fixed by bumping the revision of apr and libtool to force their rebuild. The libidl bug is a different and unrelated bug. libidl is unmaintained so someone will have to volunteer to figure out what's breaking, and how to fix it. Actually, Tod Morrison just posted in the bug that he found a reason why it's failing, and a workaround, but not yet a fix that we can apply to the portfile. howsomever, it upgraded just fine two days ago: I assumed it was fixed. The following ports are currently installed: libidl @0.8.10_0 (active) -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Is HFS really scary?
On Feb 5, 2008 8:32 PM, Jordan K. Hubbard [EMAIL PROTECTED] wrote: *sigh* If Linus Torvalds had said that HFS ate babies and eroded the moral fiber of the nation's youth, would you still be asking this question? Probably not, since that would be clearly recognizable hyperbole. Him saying it's complete and utter crap without any supporting evidence or even any specifics, however, evidently merits some sort of serious response, does it? :-) Perhaps you should ask your boss whether he follows all the successful deployments (both enterprise and otherwise) of XServes or if he follows the random pronouncements of someone who had nothing to do with the development of MacOSX, does not use it, and in fact is seriously biased against anything but the OS he *did* create. Hardly the most objective opinion. Linus is a bomb-thrower, and I'm sure my opinion that Linux is complete and utter crap carries just as weight with him as his comments should with you. if people seriously ask you to consider linux, ask them which one and why that one and not the others. That should keep them out of your hair for quite some time. Seriously, HFS has been around an awfully long time in a lot of places to be so crappy. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: libtool woes
On Feb 4, 2008 10:33 AM, Ryan Schmidt [EMAIL PROTECTED] wrote: libtool's revision has been bumped so that everyone will be forced to rebuild it so that this problem should disappear. This is confusing to me, since the libtool that is crapping out is ./libtool (relative to the port's build directory). Where does the ports-installed libtool enter into it? Interestingly, I just found that libidl built without issue on another system here (also PPC, also 10.4.11). kitchen:~ root# port installed | grep libidl libidl @0.8.10_0 (active) This makes me wonder why two systems are having issues and one isn't. G4 good, G5 bad: also the G4s have been using MacPorts for quite awhile (since it was DarwinPorts). Could there be some conflicting cruft in there somewhere? -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: libtool woes
On Feb 3, 2008 8:29 AM, Anders F Björklund [EMAIL PROTECTED] wrote: Rebuilding libtool might also work, haven't tried that either. I have. It doesn't help. How do you use the configure args you posted? Just on the commandline? -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: libtool woes
On Feb 3, 2008 1:24 PM, David Epstein [EMAIL PROTECTED] wrote: Ryan Schmidt-24 wrote: unable to infer tagged configuration when trying to build apache2 is already filed: http://trac.macosforge.org/projects/macports/ticket/13653 ...[snip]... Both tickets include lots of discussion. The apache2 ticket includes patches which someone said worked. Neither maintainer has responded to the tickets. Looks like it's time for someone else to commit the fixes. Probably not me, since I'm not experiencing the issue. As an inexperienced MacPorter, I would like advice on what to do, in view of my need for apache2. Possible strategies: 1) Wait for someone to put the advertised patches into the official macport distribution. 2) Install the advertised patches. (Are there instructions somewhere for how to do this?) 3) Try rebuilding libtool. (But won't port object to deleting libtool because other packages depend on it?) I am trying this regime: sudo port -f uninstall libtool sudo port -f uninstall apr sudo port install libtool sudo port install apr sudo port clean apache2 sudo port upgrade apache2 port -f overrides any complaints (on your #3 above). if peter o'gorman's diagnosis above is correct, how can this be fixed in a more systematic manner? -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
SOLVED: libtool woes
On Feb 3, 2008 1:33 PM, paul beard [EMAIL PROTECTED] wrote: I am trying this regime: sudo port -f uninstall libtool sudo port -f uninstall apr sudo port install libtool sudo port install apr sudo port clean apache2 sudo port upgrade apache2 This seems to work. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
libtool woes
Looks like I have some problem with libtool. libIDL and Apache2 both fail to upgrade. --- Building apache2 with target all Error: Target org.macports.build returned: shell command cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd- 2.2.8 make all returned error 2 Command output: Making all in srclib Making all in os Making all in unix /opt/local/share/apr-1/build/libtool --silent --mode=compile /usr/bin/gcc- 4.0 -I/opt/local/include -O2 -DDARWIN -DSIGPROCMASK_SETS_THREAD_MASK -no-cpp-precomp -I/opt/local/include -I. -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd- 2.2.8/os/unix -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd- 2.2.8/server/mpm/prefork -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd- 2.2.8/modules/http -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd- 2.2.8/modules/filters -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd- 2.2.8/modules/proxy -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd- 2.2.8/include -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd- 2.2.8/modules/generators -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd- 2.2.8/modules/mappers -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd- 2.2.8/modules/database -I/opt/local/include/apr-1 -I/opt/local/include -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd- 2.2.8/server -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd- 2.2.8/modules/proxy/../generators -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd- 2.2.8/modules/ssl -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_apache2/work/httpd- 2.2.8/modules/dav/main -prefer-non-pic -static -c unixd.c touch unixd.lo libtool: compile: unable to infer tagged configuration libtool: compile: specify a tag with `--tag' make[3]: *** [unixd.lo] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all-recursive] Error 1 -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts High-speed Connection
On Jan 27, 2008 6:41 AM, Charlse Darwin [EMAIL PROTECTED] wrote: Is there any configuration to let MacPorts know that it's on a high- speed bandwidth and it can start downloading everything it needs all at once and then get on with installing later? ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users man port(1) and look at the fetch option. Don't know if it does exactly what you want. fetch Fetches the distribution files required to build portname. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Re: [MacPorts] #14062: Website does not render properly in IE7
On Jan 24, 2008 12:47 PM, Mark Hattam [EMAIL PROTECTED] wrote: Subject: Re: [MacPorts] #14062: Website does not render properly in IE7 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Thu, 24 Jan 2008 12:45:51 -0800 X-BeenThere: [EMAIL PROTECTED] List-Id: MacPorts Project Trac ticket activity macports-tickets.lists.macosforge.org Sender: [EMAIL PROTECTED] You are not allowed to post to this mailing list, and your message has been automatically rejected. If you think that your messages are being rejected in error, contact the mailing list owner at [EMAIL PROTECTED] Message-Id: [EMAIL PROTECTED] In-Reply-To: [EMAIL PROTECTED] References: [EMAIL PROTECTED] [EMAIL PROTECTED] Date: Thu, 24 Jan 2008 20:45:55 + To: [EMAIL PROTECTED], [EMAIL PROTECTED] From: Mark Hattam [EMAIL PROTECTED] Subject: Re: [MacPorts] #14062: Website does not render properly in IE7 Cc: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii ; format=flowed X-Brightmail-Tracker: AgirT1UIq5+s If I save the offered downloaded file to disk ... change the .php into .htm (or .html) ... the file then opens up in IE7 and renders everything. Changing the relative links for the .css etc to absolute links, makes it look good too. In doing so, I haven't changed the xml at the top of the file. That's still there and IE7 doesn't appear to mind. So the difference is that IE7 doesn't understand or mis-interprets the type of file being sent from the server, and thinks that it can't render it. Other php pages (on other sites) work fine (usually :-) ), but the server is sending something different here. Mark -- At 19:47 + 24/1/08, MacPorts wrote: #14062: Website does not render properly in IE7 --+- Reporter: [EMAIL PROTECTED] | Owner: [EMAIL PROTECTED] Type: defect | Status: new Priority: Normal | Milestone: Website Documentation Component: website | Version: Resolution: |Keywords: ie7 windows content-type --+- Changes (by [EMAIL PROTECTED]): * cc: [EMAIL PROTECTED] (added) * owner: [EMAIL PROTECTED] = [EMAIL PROTECTED] * component: server/hosting = website Comment: I'm sure that's because of the `echo ?xml version=\1.0\ encoding=\$encoding\?\n;` declaration at the top of each of our pages, which I crafted to strictly adhere to the XHTML standard, not caring too much about how bad IE handles that particular line, I admit. I don't think it's a server level PHP issue or anything of the sort. Personally I have no feeling about catering to such a broken browser as IE (there's always Firefox for Windows ;-), but I guess we could remove that line even if only for the purpose of giving MacPorts a wider net-surfing audience... -jmpp There's an interesting discussion of IE7/8/whatever and its rendering strategy here http://rc3.org/2008/01/23/the-implications-of-ie8/. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Ticket #13984: ffmpeg fails to compile [ld: Undefined symbols: _av_crc_get_table]
I just opened this ticket against ffmpeg, as I didn't find any other tickets that matched my issue. ld: Undefined symbols: _av_crc_get_table /usr/bin/libtool: internal link edit command failed make[1]: *** [libavcodec.51.dylib] Error 1 make: *** [lib] Error 2 http://trac.macosforge.org/projects/macports/ticket/13984 -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: How to Get Mac Apps on the Mac OS X Dock?
well, the fact remains that installing the Aqua bits for the Gimp uses all of 196k of disk space: is there any compelling reason *not* to install it by default? [/Applications/MacPorts]# du -sk Gimp.app/ 196 Gimp.app/ Especially when you consider that, deep in the bowels of all that stuff, you find a script[*] that simply runs the command-line app. /Applications/MacPorts/Gimp.app/Contents/Resources/script -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: How to Get Mac Apps on the Mac OS X Dock?
On Jan 16, 2008 6:26 AM, Jeffrey Thompson [EMAIL PROTECTED] wrote: I have successfully compiled gimp (!!) and I would like to put it's icon on the Mac OS X Dock. Dragging the /opt/local/bin/gimp shortcut doesn't work. How would I create a Gimp Icon button on my dock? Thanks! is there a Gimp in your /Applications/MacPorts folder? -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: How to Get Mac Apps on the Mac OS X Dock?
On Jan 16, 2008 12:13 PM, Jeffrey Thompson [EMAIL PROTECTED] wrote: No the gimp executable is in /opt/local/bin/gimp. [/Users/paul]:: port provides /Applications/MacPorts/Gimp.app/Contents/Info.plist /Applications/MacPorts/Gimp.app/Contents/Info.plist is provided by: gimp-app Yes, but the gimp-app port saves you from having to create an Applescript wrapper by making a wrapper of its own and installing it where you would expect it. Someone has already done all this for, if you installed the meta-port. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: How to Get Mac Apps on the Mac OS X Dock?
On Jan 16, 2008 10:16 PM, William Davis [EMAIL PROTECTED] wrote: Did you bother to look in /Applications/MacPorts? The MacPorts gimp port *also* installs Gimp.App in that location whose icon you would have seen if you had bothered to look. I'm not sure the gimp port does by default: I think it's the meta-port. But the description of gimp vs gimp-app doesn't make it clear to me. [/Users/paul]:: port info gimp gimp 2.4, Revision 3, graphics/gimp (Variants: universal, macosx, animation) http://www.gimp.org/ This is a META port for the gimp2 which includes help and documentation, support for icns, jp2000 and RAW formats, content-aware rescaling Gutenprint and scanner frontends and even a nice theme (Nodoka). Mac OS X users also get a Gimp.app bundle, a Show in Finder menu and clipboard integration. Library Dependencies: icns-gimp, gimp-jp2, gimp-lqr-plugin, gimp-user-manual, gtk-nodoka-engine, gutenprint, ufraw, xsane, gimp-app, macclipboard-gimp, macfile-gimp Platforms: darwin Maintainers: [EMAIL PROTECTED] -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Using Leopard's ruby with Macports' ruby libraries
On Jan 13, 2008 5:49 AM, Douglas Tan [EMAIL PROTECTED] wrote: As the subject states, I'm looking to find a way to use Leopard's ruby with Macport's ruby libraries like rb-rubygems, rb-mysql, et al. The main reason for doing this is so that I can use DTrace probes for ruby applications. Would a DTraced ruby be in the horizon for Macports? I don't have Leopard and won't see it for quite some time. What does it take to make an app DTrace-able? Is this something that can be done in the port? -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: ocaml fails on Tiger (was: Re: sudo port install mldonkey)
On Jan 4, 2008, at 10:16 AM, Charlse Darwin wrote: I get the message here that say `Software was successfully installed' for ocml. Why can't they put the same thing on MacPorts server? Also README file of the ocaml.package says this: Files will be installed in the following directories: /usr/local/bin - command-line executables /usr/local/lib/ocaml - library and support files /usr/local/man - manual pages Is there any way to move the stuff manually? Does ocaml come with an ocaml-config binary that might explain how those porters got it to work? Or, perhaps easiest, ask them what their special sauce it? ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Standardizing a MacPorts system
On Jan 3, 2008 12:17 PM, Tabitha McNerney [EMAIL PROTECTED] wrote: Hello all -- I would like to build, from source, on an Xserve running Leopard Server, a standard MacPorts system that could be deployed, in an organization, on numerous other Apple servers running the same version of the OS ( e.g. Leopard Server). In doing so I would use Apple's command-line tools (such as hdiutil and asr) create a restorable disk image (.dmg) file of a disc volume that hangs off an external disk on my original Xserve which houses the MacPorts prefix ( e.g., /opt/local). I would then restore from this disc image to the additional machines slated to be the recipients of the original standard. I wonder if some combination of nfs (to mount your master repository), rsync (to update your local store) and some voodoo with a regex to update any files that are tied to hostnames (all your master builds might be tagged with master or changeme). I don't see any immediate problems in doing so, however I have noticed when installing some ports (when I have occasionally enabled verbose mode -v during the install), depending on the port, some ports seem to take into consideration the Hostname of the Xserve I'm running it on. On my Xserve running Leopard Server, the Hostname is very importantly tied to the DNS name because I am running Apple's DNS server that is buncled with Leopard Server since I need it for other services on the machine which are not directly related to MacPorts such as running an OpenDirectory Master. The problem is, with hundreds of MacPorts tied together and with complex dependency chains, how can anyone determine when a specific MacPort reads the hostname and uses the hostname of the machine during the configuration process (unless a sys admin such as myself builds each and every port with verbose mode and analysis the output grepping for the hostname)? It might be problematic if the hostname of any given MacPort somehow becomes hard wired into the port itself during the configuration / install processing. Then again, I might be making a mountain out of a mole hill. Has anyone else built a Standardized MacPorts system that is cloned to multiple Macs? Thanks, T.M. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Standardizing a MacPorts system
On Jan 3, 2008 6:22 PM, Ryan Schmidt [EMAIL PROTECTED] wrote: I wasn't aware that any ports tied themselves to the build system's hostname. That would be problematic as well if we started to distribute binaries of ports. Then again, I'm only familiar with a small minority of our ports collection. With which ports have you observed this problem? Aren't you the maintainer of the mysql port? [/opt/local/var/db/mysql5]# ls .turd_mysql5ibdata1 test ib_logfile0 localhost.err white.paulbeard.org.err ib_logfile1 mysql There may well be others but this one came to mind immediately. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Standardizing a MacPorts system
On Jan 3, 2008 8:21 PM, Ryan Schmidt [EMAIL PROTECTED] wrote: On Jan 3, 2008, at 22:13, paul beard wrote: On Jan 3, 2008 6:22 PM, Ryan Schmidt wrote: I wasn't aware that any ports tied themselves to the build system's hostname. That would be problematic as well if we started to distribute binaries of ports. Then again, I'm only familiar with a small minority of our ports collection. With which ports have you observed this problem? Aren't you the maintainer of the mysql port? Yes I am. [/opt/local/var/db/mysql5]# ls .turd_mysql5ibdata1 test ib_logfile0 localhost.err white.paulbeard.org.err ib_logfile1 mysql There may well be others but this one came to mind immediately. MySQL writes logfiles whose names contain the hostname, yes. The hostname is not, however, to the best of my knowledge, encoded into any files installed by the MySQL ports. There should be no problem installing MySQL on one system and running it on another. The two systems will merely use separate logfiles by default -- which is in fact probably a good thing, isn't it? If it isn't, there's probably a way to have MySQL write to a logfile of a name of your choosing. Consult the MySQL documentation. I'm not that interested in a solution to a problem I don't have. But the inferred question was, do any ports make use of the hostname. it looks like mysql derives it when it creates the file (I tested it). I'm not sure this one admittedly thin example answers the OP's question. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: So who owns the macports Wordpress/TRAC system?
On Dec 29, 2007 12:08 PM, Ryan Schmidt [EMAIL PROTECTED] wrote: On Dec 29, 2007, at 06:31, Boey Maun Suang wrote: any problems with the system as a whole can be filed as a ticket on Trac, with component set to the newly-created Server/Hosting category. You mean the server/hosting Component. No Milestone seems to be appropriate to this Component. Do we just leave the Milestone blank? Or does this fall under the Website Documentation Milestone? Hmm, it all sounds pretty inconclusive ;-) Anyone in PortMgr want to take a stab at this? -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
tone generator?
Is there, in the ever-increasing galaxy of MacPorts, a tone generator than can be used to tune a wireless network? Briefly, the idea is to play a tone based on the signal strength, with higher pitches for better signal, etc. Not sure how to do this in OS X. http://forum.openwrt.org/viewtopic.php?pid=10283 -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problems compiling Python25 MPlayer on 10.5 with Case-sensitive filesystem
On Dec 23, 2007 8:56 AM, Scott C. Kennedy [EMAIL PROTECTED] wrote: Well, I re-installed XCode 3.0 and then re did the sudo find / -ls new_find.txt to see what files were added. Macintosh:~ sck$ grep -i quicktime/quicktime.h find.txt new_find.txt find.txt:5776618 -rw-rw-r--1 _devdocs wheel 218 May 2 2007 /Developer/Documentation/DocSets/com.apple.ADC_Reference_Library.CoreReference.docset/Contents/Resources/Documents/documentation/QuickTime/QuickTime.html find.txt:5139498 lrwxr-xr-x1 root wheel 77 Oct 29 23:50 /Developer/SDKs/MacOSX10.4u.sdk/Developer/Headers/CFMCarbon/QuickTime/QuickTime.h - ../../../../System/Library/Frameworks/QuickTime.framework/Headers/QuickTime.h new_find.txt:41021178 -rw-rw-r--1 _devdocs wheel 218 May 2 2007 /Developer/Documentation/DocSets/com.apple.ADC_Reference_Library.CoreReference.docset/Contents/Resources/Documents/documentation/QuickTime/QuickTime.html new_find.txt:41196218 lrwxr-xr-x1 root wheel 77 Dec 23 07:34 /Developer/SDKs/MacOSX10.3.9.sdk/Developer/Headers/CFMCarbon/QuickTime/QuickTime.h - ../../../../System/Library/Frameworks/QuickTime.framework/Headers/QuickTime.h new_find.txt:40386508 lrwxr-xr-x1 root wheel 77 Dec 23 07:31 /Developer/SDKs/MacOSX10.4u.sdk/Developer/Headers/CFMCarbon/QuickTime/QuickTime.h - ../../../../System/Library/Frameworks/QuickTime.framework/Headers/QuickTime.h Macintosh:~ sck$ So, according to find, there's only the new 10.3 sdk file added... Originally when I did the XCode install I did not install WebObjects or 10.3 SDK, but this time I installed everything and it worked... So, officially, I don't understand, but I comply and am happy... :) It's software: it doesn't have to make sense. This is looking like a FAQ or FEP (frequently encountered problem). -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: sudo port install bing
On Dec 18, 2007 12:08 PM, Charlse Darwin [EMAIL PROTECTED] wrote: $ sudo port install bing --- Fetching bing --- Attempting to fetch bing-1.0.5.tar.gz from http:// www.freenix.org/reseau/ --- Attempting to fetch bing-1.0.5.tar.gz from http:// svn.macports.org/repository/macports/distfiles/bing --- Attempting to fetch bing-1.0.5.tar.gz from http:// svn.macports.org/repository/macports/distfiles/general/ --- Attempting to fetch bing-1.0.5.tar.gz from http:// svn.macports.org/repository/macports/downloads/bing Error: Target org.macports.fetch returned: fetch failed Error: Status 1 encountered during processing. $ This isn't the most helpful error message you could have composed, Charlse. It looks like freenix.org redirects to here ( http://www.usenix.org/events/bytopic/freenix.html) kitchen:~ paul$ ping freenix.org PING freenix.org (208.67.219.130): 56 data bytes 64 bytes from 208.67.219.130: icmp_seq=0 ttl=241 time=64.320 ms 64 bytes from 208.67.219.130: icmp_seq=1 ttl=241 time=63.792 ms ^C --- freenix.org ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max/stddev = 63.792/64.056/64.320/0.264 ms and that www.freenix.org is unreachable. Connection closed by foreign host. kitchen:~ paul$ ping www.freenix.org PING www.freenix.org (194.57.169.110): 56 data bytes 36 bytes from or-angers-nantes.cssi.renater.fr (193.51.182.149): Destination Net Unreachable Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 0054 452d 0 30 01 0e4a 192.168.10.226 194.57.169.110 36 bytes from or-angers-nantes.cssi.renater.fr (193.51.182.149): Destination Net Unreachable Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 0054 4533 0 30 01 0e44 192.168.10.226 194.57.169.110 36 bytes from or-angers-nantes.cssi.renater.fr (193.51.182.149): Destination Net Unreachable Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 0054 4553 0 30 01 0e24 192.168.10.226 194.57.169.110 ^C --- www.freenix.org ping statistics --- 3 packets transmitted, 0 packets received, 100% packet loss and looking at the port's information, I can find out where the project is based and find out that that server is the same as the unreachable one above. kitchen:~ paul$ port info bing bing 1.0.5, net/bing (Variants: universal) http://www.freenix.fr/freenix/logiciels/bing.html Bing is a point-to-point bandwidth measurement tool (hence the 'b'), based on ping. Bing determines the real (raw, as opposed to available or average) throughput on a link by measuring ICMP echo requests roundtrip times for different packet sizes for each end of the link. and it looks like the project may be dormant. Subcategory: Bandwidth / Throughput Measurement bing *URL:*http://fgouget.free.fr/bing/index-en.shtml*Contact:*Author: Pierre Beyssac ( pb @ fasterix.freenix.fr )*Overview:*Bing is a point-to-point bandwidth measurement tool (hence the 'b'), based on ping. Bing determines the real (raw, as opposed to available or average) throughput on a link by measuring ICMP echo requests roundtrip times for different packet sizes for each end of the link.*Access:*Original page is no longer maintained. A mirror exists for Bing 1.3.5http://fgouget.free.fr/bing/bing_src-1.3.5.tar.gz . But there is a mirror listed there. You may want incorporate that into the Portfile and see if it works. A diff from that would be helpful. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: sudo port -Rdu upgrade installed (Automated)
On 12/15/07, Charlse Darwin [EMAIL PROTECTED] wrote: Need a launchd daemon to automate the upgrade process. I've the following but for some reason it's stopped working. Also I would like it to right the results into a log file. I don't know about anyone else, but unattended port upgrades may not always work as intended. A halfway measure I use is to put a port sync port outdated sequence in cron and mail the results: that way I can see if anything needs doing and plan when to do it. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Ion3 license and possible removal
On 12/13/07, Rainer Müller [EMAIL PROTECTED] wrote: For me this sounds like a removal request... What is the problem with a version more than 28 days old? In my personal opinion ion3 with this license addition does not qualify as free software any more. Definitely remove it. Wow, from that thread, I would have to agree. for those not inclined to read through the flamethread, FreeBSD is in a ports freeze, where updates and changes are verboten, unless they are to fix an issue like a segfault or the like: these often last a month, and that would span the 28 days. Never heard of ion3 before today, and I guess I won't miss it. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Kismet on OSX 10.5.1 Leopard
On 11/28/07, caliel [EMAIL PROTECTED] wrote: I have returned home from my holiday travels with eager anticipation to try kismet with my ralink USB Wi-Fi card. Just as I plugged it in, I realized .. .. darwin and viha are the only valid capture sources for OSX! Any reason not to use KisMac? -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: keeping a (maximally) clean active tree
On 12/5/07, Ryan Schmidt [EMAIL PROTECTED] wrote: I agree here again. You should not have to force anything in normal use. But you currently do, to uninstall old versions of software on which other software depends. Discussion of how this situation could be improved would probably be welcomed on the macports-dev list. is there a reason not to make what we now use as -f the default behavior? If I use port upgrade foo I expect foo to be upgraded to the latest version. the use of upgrade implies that I have an existing version that may be out of date and if it is, I want it upgraded. I realize, in circumstances like the gettext issue mentioned above, that can hose things up, but that could be something is flagged in a Portfile that might display a message like: Installed port foo 0.6-7,1 is superceded by foo 0.7. foo 0.7 is incompatible with installed ports bar 1.1 baz 0.9-1 quux 0.2-3,1_3 To upgrade foo correctly, please uninstall the ports that depend on it, upgrade foo and reinstall the dependents. here's a particularly hairy example from FreeBSD's UPDATING file: 20050201: AFFECTS: users of lang/perl5 and lang/perl5.8 AUTHOR: [EMAIL PROTECTED] lang/perl5 has been updated to 5.6.2, and lang/perl5.8 has been updated to 5.8.6. you should update everything depending on perl, that is: * first, upgrade your perl installation (use either lang/perl5 or lang/perl5.8, the latter being recommended); * for FreeBSD 4.X, run use.perl port, so that the system knows you have 5.8.6 or 5.6.2; this step is not needed on FreeBSD 5.X and FreeBSD -CURRENT; * run some magic incantations to upgrade all ports depending on perl, that is run something like : portupgrade -f `(pkg_info -R perl-5\* |tail +4; \ find /usr/local/lib/perl5/site_perl/5.[68].[1245] -type f -print0 \ | xargs -0 pkg_which -fv | sed -e '/: ?/d' -e 's/.*: //')|sort -u` This is likely to fail for a few ports, you'll have to upgrade them afterwards by hand. Personally, I would have this be dumped out to the console when an upgrade matches the date and version that this applies to. But that's cuz I am too lazy/absent-minded to read UPDATING as often as I should. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: keeping a (maximally) clean active tree
On 12/7/07, William Davis [EMAIL PROTECTED] wrote: pardon, but doesnt using -R (-dfunR) take care of this? Yes, it does The Right Thing if there a newly-introduced mismatch in a port that has dependents. -R also upgrade dependents (only for upgrading) But I think that the OP was looking for a simpler way to upgrade existing ports without using force or ideally with no flags at all (well, maybe an optional -c). using -fundR is 5 flags, and I usually add -c, so we're up to 6 arguments to do what many would expect to be the default operaion. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Upgrade of libgtop fails
On 11/30/07, David Rowe [EMAIL PROTECTED] wrote: I have just tried upgrading all my installed macports (which include Gimp). Gimp itself upgraded OK, but the upgrade of libgtop fails with the following message: There seems to a fix available here: http://trac.macosforge.org/projects/macports/ticket/13390 -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: problem with libraries path
On 11/27/07, Rémi Thébault [EMAIL PROTECTED] wrote: Hi I have some problems with pathes and env. variables. It seems my system get confused and doesn't want in some situations to find libraries or headers elsewhere than /opt/local. here is my profile file: $ cat ~/.profile # # Your previous .profile (if any) is saved as .profile.mpsaved # Setting the path for MacPorts. export PATH=/usr/local/bin:/usr/local/sbin:/opt/local/bin:/opt/local/ sbin:/sw/bin:/sw/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/X11/bin export C_INCLUDE_PATH=/usr/local/include:/opt/local/include:/sw/ include:/usr/include export LIBRARY_PATH=/usr/local/lib:/opt/local/lib:/sw/lib:/usr/lib I have for instance installed liblrdf in /usr/local and when I want to build Ardour from source (it uses scons instead of ./configure make) : ardour-2.1 $ scons AUDIOUNITS=1 COREAUDIO=1 GTKOSX=1 FFT_ANALYSIS=1 SURFACES=1 scons: Reading SConscript files ... Checking for pkg-config version = 0.8.0... yes Checking for gthread-2.0... yes Checking for lrdf... no lrdf = 0.4.0 not found. You do not have the necessary dependencies required to build ardour Please consult http://ardour.org/building for more information a workaround is to install all dependencies in /opt/local, but I don't like it, and some of them (like JackOSX) cannot be installed elsewhere than /usr/local. I would like to find a system wide way to make any building or configure script look first in /usr/local then in /opt/local to find whatever is needed (libraries or headers). I assue this behaviour should be automatic but it's not, and I've never had this kind of problem on linux. May be this a problem specific to scons ? I've tried to specify CFLAGS : $ CFLAGS=-I/usr/local/include -I/opt/ local/include -I/usr/include scons but the same error occurs. Rémi Intel Macbook, Leopard 10.5.1 do you still have fink installed? Be aware that you may have problems with both MacPorts and fink co-resident . . . And others can speak more learnedly on your other questions, but the reasons to keep things in /opt/local are pretty hard to argue against. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Can't install Gimp on 10.5.1
On 11/27/07, Michael E. Shamgochian [EMAIL PROTECTED] wrote: On Nov 26, 2007, at 11:44 PM, paul beard wrote: On 11/26/07, Michael E. Shamgochian [EMAIL PROTECTED] wrote: Strange! This is pretty much a clean install of MacPorts - I've tried reinstalling MacPorts to see if that would solve the problem. Right now, I'm just getting this from port installed: The following ports are currently installed: par2 @0.4_1+darwin_9 (active) unrar @3.7.8_0 (active) (I installed those two with no trouble.) odd. Not sure how you picked out two ports that don't depend on gettext, expat, or libiconv ;-) to go back to the top of this thread, gimp2 has library dependencies on: aalib curl libart_lgpl libexif libgnomeui libgtkhtml libmng librsvg libwmf p5-xml-parser poppler py25-gtk and those all have dependencies on other things. So it should take some time to install. Why you were seeing all those messages eludes me. Want to try installing gimp2 again? try: port -d install gimp2 | tee /tmp/logfile.txt so you get the entrails to peruse later. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] It seems to be working now (compiling stuff), after issuing that command. I'm not sure what was going wrong before, except that I was trying to install gimp before, not gimp2 (but they seem to be mostly the same)... One is a superset of the other . . . . glad it's working now. [/Users/paul]:: port info gimp gimp2 gimp 2.4, Revision 3, graphics/gimp (Variants: universal, macosx, animation) http://www.gimp.org/ This is a META port for the gimp2 which includes help and documentation, support for icns, jp2000 and RAW formats, content-aware rescaling Gutenprint and scanner frontends and even a nice theme (Nodoka). Mac OS X users also get a Gimp.app bundle, a Show in Finder menu and clipboard integration. Library Dependencies: icns-gimp, gimp-jp2, gimp-lqr-plugin, gimp-user-manual, gtk-nodoka-engine, gutenprint, ufraw, xsane, gimp-app, macclipboard-gimp, macfile-gimp Platforms: darwin Maintainers: [EMAIL PROTECTED] gimp2 2.4.2, graphics/gimp2 (Variants: universal, without_gnome, no_python, dbus) http://www.gimp.org/ The GNU Image Manipulation Program (GIMP) is a powerful tool for the preparation and manipulation of digital images. The GIMP provides the user with a wide variety of image manipulation, painting, processing, and rendering tools. Library Dependencies: aalib, curl, libart_lgpl, libexif, libgnomeui, libgtkhtml, libmng, librsvg, libwmf, p5-xml-parser, poppler, py25-gtk Platforms: darwin Maintainers: [EMAIL PROTECTED] -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Can't install Gimp on 10.5.1
On 11/26/07, chagrins [EMAIL PROTECTED] wrote: Thanks. I did sudo port -d install gimp, and I get this output, seemingly ad infinitum: DEBUG: Didn't find receipt, going to depspec regex for: expat DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/XFree86 DEBUG: Searching for dependency: XFree86 DEBUG: Didn't find receipt, going to depspec regex for: XFree86 DEBUG: Found Dependency: path: /usr/X11R6/lib filename: libX11.6.dylib regex: ^libX11\.6\.dylib$ DEBUG: Found Dependency: path: /usr/X11R6/lib filename: libX11.6.dylib regex: ^libX11\.6\.dylib$ DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/render DEBUG: Searching for dependency: render DEBUG: Didn't find receipt, going to depspec regex for: render DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libiconv DEBUG: Searching for dependency: libiconv DEBUG: Didn't find receipt, going to depspec regex for: libiconv DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/expat DEBUG: Searching for dependency: expat DEBUG: Didn't find receipt, going to depspec regex for: expat DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/print/freetype DEBUG: Searching for dependency: freetype DEBUG: Didn't find receipt, going to depspec regex for: freetype To use a technical expression, that looks pretty well hosed up. What does port installed look like? It looks like perhaps your receipts got messed with somehow, and that's how MacPorts keeps track of what's installed and what files make up each port's contents. I have had this happen when I ran out of space and the receipt for a port (or ports) could not be written to disk. It's unpleasant. Show up port installed and we'll see if that jibes with what you should have. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Can't install Gimp on 10.5.1
On 11/26/07, Michael E. Shamgochian [EMAIL PROTECTED] wrote: Strange! This is pretty much a clean install of MacPorts - I've tried reinstalling MacPorts to see if that would solve the problem. Right now, I'm just getting this from port installed: The following ports are currently installed: par2 @0.4_1+darwin_9 (active) unrar @3.7.8_0 (active) (I installed those two with no trouble.) odd. Not sure how you picked out two ports that don't depend on gettext, expat, or libiconv ;-) to go back to the top of this thread, gimp2 has library dependencies on: aalib curl libart_lgpl libexif libgnomeui libgtkhtml libmng librsvg libwmf p5-xml-parser poppler py25-gtk and those all have dependencies on other things. So it should take some time to install. Why you were seeing all those messages eludes me. Want to try installing gimp2 again? try: port -d install gimp2 | tee /tmp/logfile.txt so you get the entrails to peruse later. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: problem initializing macports
On 11/25/07, tania habib [EMAIL PROTECTED] wrote: Dear List, It has been long since I installed macports on my mac osx 10.4. I used the ports to install many packages but then I went on to do some other things and did not use ports for a while. Last week, when I tried to intialize the port, it did not work! When I go to and X11 terminal and type port , it gives me the following error message Error: /opt/local/bin/port: Failed to initialize ports system, no suitable image found. Did find: /opt/local/share/darwinports/Tcl/pextlib1.0/Pextlib.dylib: mach-o, but wrong architecture sounds like you have an Intel system with a PPC code base installed. the problem isn't in your PATH, as it find port correctly, but can't run it. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: problem initializing macports
On 11/25/07, Ryan Schmidt [EMAIL PROTECTED] wrote: What Mac do you have? Did you previously have a different Mac, back when you originally installed MacPorts? Maybe you used Migration Assistant to transfer everything (including MacPorts) from the old Mac to the new Mac? IF the old Mac was PowerPC-based and the new one is Intel-based, that could explain the error you're seeing, and you should really uninstall everything and start over. You can use port installed to see what ports are installed. How will that work if the port command doesn't run? Once you reinstall MacPorts, you can manually reinstall all those ports. To uninstall MacPorts, follow these instructions: http://trac.macosforge.org/projects/macports/wiki/ FAQ#HowdoIremoveoruninstallMacPorts If you're sure MacPorts previously worked on this Mac, then it shouldn't be necessary to uninstall, though I can't yet explain what else might be going on. It also sounds like your PATH is not correct since it can't find the port command. Actually, it does seem to find it OK: if the user types 'port something' and the result is Error: /opt/local/bin/port: Failed to initialize ports system, no suitable image found. Did find: /opt/local/share/darwinports/Tcl/pextlib1.0/Pextlib.dylib: mach-o, but wrong architecture it sounds like the command is there but if the error message is right, that the architecture is wrong. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: problem initializing macports
On 11/25/07, Ryan Schmidt [EMAIL PROTECTED] wrote: On Nov 25, 2007, at 13:29, paul beard wrote: On 11/25/07, Ryan Schmidt wrote: What Mac do you have? Did you previously have a different Mac, back when you originally installed MacPorts? Maybe you used Migration Assistant to transfer everything (including MacPorts) from the old Mac to the new Mac? IF the old Mac was PowerPC-based and the new one is Intel-based, that could explain the error you're seeing, and you should really uninstall everything and start over. You can use port installed to see what ports are installed. How will that work if the port command doesn't run? Good question. It might not work then. We might have to dig deeper to see what's installed. Like this: cd /opt/local/var/macports/receipts/ find . -name receipt.bz2 | sed -E 's%^\./(.*)/(.*)/receipt\.bz2$%\1 @ \2%' Watch the line-wrap: that \2% should stay on the same line. Same below . . . . Or, for the user's version of DarwinPorts before the new layout, I hope this is it: cd /opt/local/var/db/dports/receipts/ find . -name receipt.bz2 | sed -E 's%^\./(.*)/(.*)/receipt\.bz2$%\1 @ \2%' It also sounds like your PATH is not correct since it can't find the port command. Actually, it does seem to find it OK: if the user types 'port something' and the result is Error: /opt/local/bin/port: Failed to initialize ports system, no suitable image found. Did find: /opt/local/share/darwinports/Tcl/pextlib1.0/Pextlib.dylib: mach-o, but wrong architecture it sounds like the command is there but if the error message is right, that the architecture is wrong. It sounds to me like the user is having to run /opt/local/bin/port because when just port is run this error was shown: On Nov 25, 2007, at 11:14, tania habib wrote: On Nov 25, 2007 2:11 PM, William Davis wrote: Did you try : sudo port -d selfupdate ? Yes I did, but it comes with the error that port:command not found. I feel there is some path problem. Can please guide me through the procedure of setting the path variable in X11! -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: compiling as root?
On 11/24/07, Michael Thon [EMAIL PROTECTED] wrote: Linux people generally recommend that you do not compile source code with a user that has superuser privileges, which I assume is a guard against possibly malicious commands that may be in the compile scripts. When I install packages with macports (sudo port install xyz) they're compiled by the root user. I assume that the developers have thought about this and decided that it is not a security problem. But I am curious, is it ok or not ok to compile source code as root? cheers you can compile as any user, so long as you have permissions to write to where you're doing it. It's the installation step that might require root. This, I suspect, is part of the reason why MacPorts uses the /opt/local sandbox and doesn't write to the other parts of the system. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: the easy fix to get python 2.5 working again
On 11/23/07, Randall Wood [EMAIL PROTECTED] wrote:
On 23 Nov 2007, at 00:29, paul beard wrote:
On 11/22/07, Ryan Schmidt [EMAIL PROTECTED] wrote: On Nov
22, 2007, at 16:02, paul beard wrote:
I should have attached this to my earlier email. Since it is
explicitly for darwin 8, it shouldn't break anything else. Right?
platform darwin 8 {
- configure.compiler gcc-4.0
- configure.args-append --with-cxx=/usr/bin/g++-4.0
+ configure.compiler gcc-3.3
+ configure.args-append --with-cxx=/usr/bin/g++- 3.3
}
I would expect that not to work on Intel Macs, since Apple's gcc 3.3
only compiles PowerPC binaries.
Well, that's all I have to work with. I have no idea if it's
working at all on Intel hardware. Anyone else seeing a problem with
it?
See ticket #13377[1]. I think the problem is the configure flags
being passed to python, not the compiler.
[1] http://trac.macosforge.org/projects/macports/ticket/13377
That's as may be: I saw a lot of Google results that suggested that, but I
could never get it to work.
That ticket is marked as a duplicate, and I have been down the same road as
the older one, even unto the same cited webpages. Tried the same Portfile
modifications as well.
What I did worked, though it may not be ideal for whatever reason.
--
Paul Beard / www.paulbeard.org/
[EMAIL PROTECTED]/[EMAIL PROTECTED]
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
not specifically MacPorts but tools-related
Does anyone have any experience with the gcc 3.3-fast compiler? it's listed as an option on my system but gcc_select says it doesn't really exist. And how do I use the compilers that MacPorts builds, if I ever had a need? gcc33 @3.3.6 lang/gcc33 gcc34 @3.4.6 lang/gcc34 gcc40 @4.0.4 lang/gcc40 gcc41 @4.1.2 lang/gcc41 gcc42 @4.2.2 lang/gcc42 gcc43 @4.3-20071116 lang/gcc43 And does gcc_select override what's in the Portfile? For instance, python 2.5 is balking with gcc 4 (the default) but builds with gcc 3.3. I made the change explicit in the Portfile. Could I have saved that step? -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: not specifically MacPorts but tools-related
On 11/22/07, paul beard [EMAIL PROTECTED] wrote: Does anyone have any experience with the gcc 3.3-fast compiler? it's listed as an option on my system but gcc_select says it doesn't really exist. And how do I use the compilers that MacPorts builds, if I ever had a need? gcc33 @3.3.6 lang/gcc33 gcc34 @3.4.6 lang/gcc34 gcc40 @ 4.0.4 lang/gcc40 gcc41 @4.1.2 lang/gcc41 gcc42 @4.2.2 lang/gcc42 gcc43 @4.3-20071116 lang/gcc43 And does gcc_select override what's in the Portfile? For instance, python 2.5 is balking with gcc 4 (the default) but builds with gcc 3.3. I made the change explicit in the Portfile. Could I have saved that step? Well, I answered one of my own questions: gcc_select has no effect on the value in a portfile, or to put it another way, you can override it with the portfile's values. So that's python 2.5 sorted. What changed upstream, I wonder? -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
the easy fix to get python 2.5 working again
I should have attached this to my earlier email. Since it is explicitly for
darwin 8, it shouldn't break anything else. Right?
--- Portfile2007-11-19 12:21:26.0 -0800
+++ /tmp/Portfile 2007-11-22 13:58:08.0 -0800
@@ -67,8 +67,8 @@
}
platform darwin 8 {
- configure.compiler gcc-4.0
- configure.args-append --with-cxx=/usr/bin/g++-4.0
+ configure.compiler gcc-3.3
+ configure.args-append --with-cxx=/usr/bin/g++-3.3
}
platform darwin 9 {
--
Paul Beard / www.paulbeard.org/
[EMAIL PROTECTED]/[EMAIL PROTECTED]
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
Re: not specifically MacPorts but tools-related
On 11/22/07, Ryan Schmidt [EMAIL PROTECTED] wrote: gcc_select should probably never be used. The system ships with a default compiler (gcc 3.3 on Panther, gcc 4.0 on Tiger and Leopard) and that should probably never be changed. Software that needs a different compiler should specify that explicitly. Users who had used gcc_select to select a different compiler used to experience all sorts of weird breakage with some MacPorts software. Recently (1.5.2?), MacPorts was changed so that it doesn't matter what the user has selected with gcc_select; MacPorts will use gcc 3.3 on Panther and 4.0 on Tiger and Leopard unless the portfile specifies something different using configure.compiler. This is a good thing. Apple's gcc 3.3 only builds PowerPC binaries, so it's not suitable for use on Intel Macs. Is the gcc_select in MacPorts any better? gcc_select @0.1sysutils/gcc_select gcc_select 0.1, sysutils/gcc_select (Variants: universal, darwin_7, darwin_8_ppc, darwin_8_i386) http://svn.macports.org/repository/macports/users/mww/select/ gcc_select lets you switch the default compiler. It symlinks the standard compiler executables in the MacPorts prefix to the selected version. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: the easy fix to get python 2.5 working again
On 11/22/07, Ryan Schmidt [EMAIL PROTECTED] wrote:
On Nov 22, 2007, at 16:02, paul beard wrote:
I should have attached this to my earlier email. Since it is
explicitly for darwin 8, it shouldn't break anything else. Right?
platform darwin 8 {
- configure.compiler gcc-4.0
- configure.args-append --with-cxx=/usr/bin/g++-4.0
+ configure.compiler gcc-3.3
+ configure.args-append --with-cxx=/usr/bin/g++-3.3
}
I would expect that not to work on Intel Macs, since Apple's gcc 3.3
only compiles PowerPC binaries.
Well, that's all I have to work with. I have no idea if it's working at all
on Intel hardware. Anyone else seeing a problem with it?
--
Paul Beard / www.paulbeard.org/
[EMAIL PROTECTED]/[EMAIL PROTECTED]
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
Re: verifying your macports
On 11/21/07, Alexy Khrabrov [EMAIL PROTECTED] wrote: After the scare of spurious libgcc getting in the way, I'm wondering how can we verify our setups. This is when rpm-style verification and binary distros shine. Sure you can compile stuff, but what if some crap got into your PATH -- beginning with a wrong gcc? What if some other crap got into LDFLAGS or DYLD_LIBRARY_PATH or whatever? What tools are there to verify -- completeness of each port -- proper chain of dependencies of each port -- checking that no port depends on any package not built by the ports -- e.g., nothing outside /opt/local -- that each executable in /opt/local/bin will load -- what else? sounds like you have a fine project scoped out there ;-) -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Something to tail -f during a long build?
On 11/3/07, Lloyd Zusman [EMAIL PROTECTED] wrote: Once I've started a long build (for example, of something like gcc42), is there a file somewhere that I can look at with tail -f in order to watch the progress of the build? I know that I can start a build with the -v or maybe -d flag to see more info, but I'm specfically wondering if there's a log file somewhere for the non--v case (for example, for a simple port install gcc42) that I can look at while the build is running. Thanks in advance. -- Lloyd Zusman [EMAIL PROTECTED] God bless you. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
