From talklists at newgeo.com Sun Mar 1 01:00:43 2009 From: talklists at newgeo.com (Scott Haneda) Date: Sun, 1 Mar 2009 01:00:43 -0800 Subject: Perl error, once and for all In-Reply-To: <20090301025356.GB4629@prunille.vinc17.org> References: <23BD24AB-1FC6-4B87-AC4D-44DF68BAB2A1@newgeo.com> <3D7F2DE3-A9D5-4657-9FDA-A69F7440CFC8@geeklair.net> <1DD62C2A-5E85-4481-9246-96FE34E4CF50@newgeo.com> <20090226055133.GE27410@darkart.com> <29A68AD6-F99A-48A2-B050-69A08EA349A8@newgeo.com> <68BBA4C9-23A4-414D-AFED-BC996C061CD9@macports.org> <707C94E4-9868-4B39-BF42-E0D003BA6DBA@macports.org> <20090301025356.GB4629@prunille.vinc17.org> Message-ID: On Feb 28, 2009, at 6:53 PM, Vincent Lefevre wrote: > On 2009-02-26 04:28:46 -0800, Scott Haneda wrote: >> I think you have to modify the module to "use lib" and supply a path. > > No need to do that. Just modify PERL5LIB in your environment once and > for all (you or MacPorts had to do the same for $PATH, $LIBRARY_PATH, > $C_INCLUDE_PATH or whatever, anyway). RTFM. So, let me get this straight, if MacPorts was to install a .profile with a certain PERL5LIB env var in it, this issue is solved? -- Scott * If you contact me off list replace talklists@ with scott@ * From jmr at macports.org Sun Mar 1 01:18:53 2009 From: jmr at macports.org (Joshua Root) Date: Sun, 01 Mar 2009 20:18:53 +1100 Subject: apache2 location In-Reply-To: References: <1154B802-5D94-4754-8848-2EF8375E1069@newgeo.com> <594B9628-56C8-4537-865E-5ACFE52B63A9@geeklair.net> <95884C34-693A-4570-8AEA-15C48E4693E8@newgeo.com> <1FE454BE-FE0D-428C-AE09-3F7EE7EB2B3F@macports.org> Message-ID: <49AA52FD.40106@macports.org> Ryan Schmidt wrote: > MacPorts itself even installs outside of > ${prefix} by default, into /Library/Tcl. There doesn't seem to be a good reason for that, though. I'd like to change it. - Josh From talklists at newgeo.com Sun Mar 1 01:20:46 2009 From: talklists at newgeo.com (Scott Haneda) Date: Sun, 1 Mar 2009 01:20:46 -0800 Subject: Perl error, once and for all In-Reply-To: <3A4C4D61-E80C-4B2E-9B56-828620B53966@pixilla.com> References: <23BD24AB-1FC6-4B87-AC4D-44DF68BAB2A1@newgeo.com> <3D7F2DE3-A9D5-4657-9FDA-A69F7440CFC8@geeklair.net> <1DD62C2A-5E85-4481-9246-96FE34E4CF50@newgeo.com> <20090226055133.GE27410@darkart.com> <29A68AD6-F99A-48A2-B050-69A08EA349A8@newgeo.com> <68BBA4C9-23A4-414D-AFED-BC996C061CD9@macports.org> <707C94E4-9868-4B39-BF42-E0D003BA6DBA@macports.org> <20090301025356.GB4629@prunille.vinc17.org> <3A4C4D61-E80C-4B2E-9B56-828620B53966@pixilla.com> Message-ID: <0FE43229-E98C-42B3-AACA-5AF1F18BCBDF@newgeo.com> On Feb 28, 2009, at 9:35 PM, Bradley Giesbrecht wrote: > On Feb 28, 2009, at 6:53 PM, Vincent Lefevre wrote: >> On 2009-02-26 04:28:46 -0800, Scott Haneda wrote: >>> I think you have to modify the module to "use lib" and supply a >>> path. >> >> No need to do that. Just modify PERL5LIB in your environment once and >> for all (you or MacPorts had to do the same for $PATH, $LIBRARY_PATH, >> $C_INCLUDE_PATH or whatever, anyway). RTFM. > > This is the MacPorts Users list. Right? Hey, that's a good point, while off topic, are the questions I am asking about port creation in general better suited to some other list? > So just who are MacPorts Users? I know next to nothing about perl. > But I use it everyday because it's everywhere. > > I just want to install something that needs a perl and a p5 module. > Do I really need to RTFM for that? You my friend, are hitting the nail right on the head from my perspective. I do not at all mind this discussion from portfile devs, and port devs in general. You have to think about the kid who want to install wireshark, to learn about his network, or troubleshoot something. Maybe a bad example, we all know what they want wireshark for :) The goal should be, for 99% of MacPorts users, to not know what -d -v - f clean, distclean etc are for. At least, that is largely my opinion. Custom built apps like this, are by nature, mysterious and scary to most average users, a less than comforting install process is a turn off. It would be nice to have Mac OS X native binary installers for everything, since that is not going to happen anytime soon, MacPorts is wonderful, but there are a few issues that need solving IMHO. > If I want to install a something written in C of C++ should I just > RTFM? > > Now if your talking to port authors you may have a point but even > then I don't understand why the perl5 port wouldn't set necessary > env's up for me. I would like to know that too. That can not be the solution to solving a 1+ year old trac issue, it has to be more complicated than that. > Why do I have to -f an install to install a p5? I am still trying to parse all this data to answer that myself. If this is 90% man pages conflicting with other man pages, and 10% non man pages conflicting with other installed perl things... Can I solve this on my own by updating the port file with patch, that instructs to to instal the offending file elsewhere? I am sure I would have to replace out some paths and such, but is that a workable solution? Maybe that is the solution, patch the source files to put the files elsewhere. I have no idea the repercussions of this. >>> Does anyone know how CPAN solves this? >> >> CPAN lets the user choose where he wants to install things. > > And that is what I decided to do, just not use macports for modules > and use cpan much like I use php pear. > > And then I got totally confused by the cpan docs as to how to set up > the prefix. > > I hope there is a perl guru that can help us through this mess. Yes, > I think it's a mess. This bear importance to me in the long run to have solved. I am relying on MacPorts to help build out a entire package of things for users. The slogan I want to slap on the website, more or less, will amount to "all this in one command", where "all this" is a combination of 20 or more things that a server admin may need. I can meet the "all this" requirement, I can not meet the "one command" requirement, without putting a -f in there. The end user will be ok with that, I am not, as I know there are dangers. If this is really just a matter of getting a perl guru to guide us through the process, and a tcl person to patch it up, I am more than willing to start a fund, and donate to it, to entice those people to come around. It matters to me, my ramp up speed to learn how to be that guru would be too long. I can at least help in the ways I know how, which would be to get an enticing fund together to get the right people on the task. > I'm no expert on anything but when someone like me doesn't > understand how to make this work without -f and friends I feel sorry > for the other 90%. Agreed. And we need to help that 90%. I have seen many posts, where a port is not installing. The reply from other users has been "you need to -f it, some ports are just that way", and that is not the right info, it will spiral out of control, to the point where as illustrated above, they blindly -f things. -f is for when you know what you are doing, it should not be propagating as a solution. -- Scott * If you contact me off list replace talklists@ with scott@ * From talklists at newgeo.com Sun Mar 1 01:37:27 2009 From: talklists at newgeo.com (Scott Haneda) Date: Sun, 1 Mar 2009 01:37:27 -0800 Subject: logging postfix and others In-Reply-To: References: Message-ID: <6F710CB7-4579-47EB-85E4-35B4254C402D@newgeo.com> I just started looking into this.... On Feb 28, 2009, at 5:47 PM, Bradley Giesbrecht wrote: > What are others doing for logging? > > Postfix wants to use syslog facilities and I would like to move the > logs from /var/log to /opt/local/var/xxx. I knew we needed to do this, but I had no idea it was going to be an issue, I see it as being one now. One way, would be to leave them as they are, write a small launchd item that pipes them from /var/log/ mail to wherever we want, seems messy, less than ideal. > But changing /etc/syslog.conf doesn't seem like a macports way of > doing it. > > I'm not totally opposed to making changes to /etc/syslog.conf but I > wouldn't be surprised if Apple supdates over wrote them some day. I would say, it is pretty stable, in that it is how it is now, but right it is going to change, for sure. > I'll figure this out but in case there is something more or less > standard for macports packages I thought I'd ask. I do not know of anything, but this gets worse. Somewhere in /etc/ periodic, it a roller, that will roll the mail logs, but it saves a certain amount of them, and then rolls them off, deleting them. If we keep using syslog for postfix, we have to also tell people to alter that, as it is too frequent a lot roll. Some will not want them deleted as well, like myself. So add that to your list of things to solve about thsi logging issues :) That is what is nice about apache being away from apple, the http logs do not get rolled away. First thing I do in setting up a new server is comment out the log rollers, second is set up a ntpudpate command in launchd to keep the clock from drifting. -- Scott * If you contact me off list replace talklists@ with scott@ * From jmr at macports.org Sun Mar 1 01:43:54 2009 From: jmr at macports.org (Joshua Root) Date: Sun, 01 Mar 2009 20:43:54 +1100 Subject: Perl error, once and for all In-Reply-To: <0FE43229-E98C-42B3-AACA-5AF1F18BCBDF@newgeo.com> References: <23BD24AB-1FC6-4B87-AC4D-44DF68BAB2A1@newgeo.com> <3D7F2DE3-A9D5-4657-9FDA-A69F7440CFC8@geeklair.net> <1DD62C2A-5E85-4481-9246-96FE34E4CF50@newgeo.com> <20090226055133.GE27410@darkart.com> <29A68AD6-F99A-48A2-B050-69A08EA349A8@newgeo.com> <68BBA4C9-23A4-414D-AFED-BC996C061CD9@macports.org> <707C94E4-9868-4B39-BF42-E0D003BA6DBA@macports.org> <20090301025356.GB4629@prunille.vinc17.org> <3A4C4D61-E80C-4B2E-9B56-828620B53966@pixilla.com> <0FE43229-E98C-42B3-AACA-5AF1F18BCBDF@newgeo.com> Message-ID: <49AA58DA.9000107@macports.org> Scott Haneda wrote: > I have seen many posts, where a > port is not installing. The reply from other users has been "you need > to -f it, some ports are just that way", and that is not the right info, > it will spiral out of control, to the point where as illustrated above, > they blindly -f things. -f is for when you know what you are doing, it > should not be propagating as a solution. You should've seen the situation pre-1.7. You had to use -f half the time to uninstall old inactive versions of ports. And yes, some users ended up blindly using -f for everything, sometimes with undesired consequences. We are getting better, slowly but surely. :-) What the perl situation needs is someone who understands the issue to just get in and get the job done. The ticket has well and truly hit maintainer timeout by now. - Josh From ryandesign at macports.org Sun Mar 1 01:56:55 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 1 Mar 2009 03:56:55 -0600 Subject: apache2 location In-Reply-To: <49AA52FD.40106@macports.org> References: <1154B802-5D94-4754-8848-2EF8375E1069@newgeo.com> <594B9628-56C8-4537-865E-5ACFE52B63A9@geeklair.net> <95884C34-693A-4570-8AEA-15C48E4693E8@newgeo.com> <1FE454BE-FE0D-428C-AE09-3F7EE7EB2B3F@macports.org> <49AA52FD.40106@macports.org> Message-ID: <608975FC-C573-4BC4-B79E-FA0CEA494CDB@macports.org> On Mar 1, 2009, at 03:18, Joshua Root wrote: > Ryan Schmidt wrote: > >> MacPorts itself even installs outside of >> ${prefix} by default, into /Library/Tcl. > > There doesn't seem to be a good reason for that, though. I'd like to > change it. IIRC, the good reason that was cited in the past was that if someone wrote another MacPorts client in Tcl that wanted to load the MacPorts Tcl library, it could only do so if it were in a known location. Or maybe Tcl will only look in /Library/Tcl for libraries. Or something like that. I'm not familiar enough with Tcl to be able to speak to that, but it seems like if MacPorts itself can be told to look for its Tcl library elsewhere, e.g. in ${prefix}/Library/Tcl, then any other MacPorts client can be told that too. Such a client could default to /opt/ local for ${prefix} which should handle most users, and offer a way to configure it if the user has installed MacPorts to a different prefix. In fact I can't imagine there being another Tcl-based MacPorts client. The "port" command handles most of what a user would need in a command line client, and if someone were making a GUI for MacPorts, I doubt they would do so in Tcl. From talklists at newgeo.com Sun Mar 1 01:58:40 2009 From: talklists at newgeo.com (Scott Haneda) Date: Sun, 1 Mar 2009 01:58:40 -0800 Subject: apache2 location In-Reply-To: References: <1154B802-5D94-4754-8848-2EF8375E1069@newgeo.com> <594B9628-56C8-4537-865E-5ACFE52B63A9@geeklair.net> <95884C34-693A-4570-8AEA-15C48E4693E8@newgeo.com> <1FE454BE-FE0D-428C-AE09-3F7EE7EB2B3F@macports.org> Message-ID: <074BFD17-3354-4154-B207-0EC3699D4265@newgeo.com> On Feb 28, 2009, at 3:55 PM, Ryan Schmidt wrote: > On Feb 26, 2009, at 07:25, Scott Haneda wrote: >>> One possible reason we might want separate directories for the >>> different apaches (${prefix}/apache2, ${prefix}/apache20, $ >>> {prefix}/apache) is to allow simultaneous installation of multiple >>> versions. However this is not even possible today; the manpages >>> still conflict. We could go to considerable effort to make all >>> three ports install into ${prefix} but with version-specific names >>> for each file, or we could admit that probably nobody needs to >>> have both apache (1) and apache2 at the same time and just let >>> them conflict with one another. >> >> You lost me on this one. What conflicts? Apache and Apache2 share >> man pages? > > $ port installed apache* > The following ports are currently installed: > apache @1.3.41_0 > apache2 @2.2.11_0 (active) > $ port activate apache @1.3.41_0 > ---> Activating apache @1.3.41_0 > Error: port activate failed: Image error: /mp/share/man/man1/ > dbmmanage.1.gz is being used by the active apache2 port. Please > deactivate this port first, or use the -f flag to force the > activation. > $ Why does ports care if a man page is shared? I do not really even consider it in use. Forgive my lack of understanding, and hopefully no one jumps my butt on this idea... Why are man pages part of the process of being registered as activated? It is a man page, not a binary. Maybe man pages should just not be part of this entire chain of checks. Sounds to me, like the best thing to do is just patch the source to put the man page elsewhere, so it does not conflict. Could I, as a port writer, use a system call to simply rm the man page? These portfiles would have to be approved sparingly, and cautiously, but in the end, heck it is just a man page. >> Actually, are there any valid reasons ever, at all, to violate- >> mtree, or is this just legacy support? > > Yes, there are valid reasons. Some examples: > > php5 has a variant +apache (will be renamed +apache_apple) which > installs a PHP module for Apple's Apache web server. Apache requires > modules to go in a particular directory, and in the case of Apple's > Apache, that directory is outside of the prefix. Normally ports > would not install things that interact with Apple software, but > there was strong demand to provide a PHP module that worked with > Apple's web server, so it was provided. Very cool, I had no idea that was being done, that creates a super awesome case where people can get a strong dev box up and running, and still use the system prefs to manage their apache, very cool. This also solves OS X Server where it was weak in php support, as in most cases, OS X Server only really fails on that front. > tuntaposx installs a kernel extension into ${prefix}/Library/ > Extensions which is not a directory we've included in the mtree thus > far. In the case of a kext, I would be inclined to have a different message, as these are much more prone to system issues. > macfuse installs a new filesystem for Mac OS X which has to go into / > System/Library/Filesystems. Yeah, I have no idea why I did not think of this, much like I am sure, if there is a port for ZFS, it will have to violate mtree all over the place. Thanks for the explanation. >> This solves it for me for the time that these warnings are going to >> be around. Of course, I believe the goal should be no warnings, >> etc, but where there must be, a wiki page, short and then long >> description, both for user and maintainer, is perfect. > > We could start creating some of these wiki pages by breaking things > out of the FAQ. The first one that comes to mind is the checksum > mismatch entry. As for where in the wiki these pages should go, I > don't even think we need a prefix; they can just go at e.g. > > http://trac.macports.org/wiki/ChecksumMismatch Sounds valid to me. Do I need special access to the wiki to contribute? I can help here, and I can certainly make the time. Having the wiki pages ready for a update to MacPorts would be nice. Then it all just falls into place. If someone can seed the wiki with a list of names for which need the detailed warnings, I am more than happy to start entering in stuff, and then having others edit it to final form. -- Scott * If you contact me off list replace talklists@ with scott@ * From afb at macports.org Sun Mar 1 02:09:44 2009 From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=) Date: Sun, 1 Mar 2009 11:09:44 +0100 Subject: apache2 location In-Reply-To: <608975FC-C573-4BC4-B79E-FA0CEA494CDB@macports.org> References: <1154B802-5D94-4754-8848-2EF8375E1069@newgeo.com> <594B9628-56C8-4537-865E-5ACFE52B63A9@geeklair.net> <95884C34-693A-4570-8AEA-15C48E4693E8@newgeo.com> <1FE454BE-FE0D-428C-AE09-3F7EE7EB2B3F@macports.org> <49AA52FD.40106@macports.org> <608975FC-C573-4BC4-B79E-FA0CEA494CDB@macports.org> Message-ID: Ryan Schmidt: > In fact I can't imagine there being another Tcl-based MacPorts > client. The "port" command handles most of what a user would need > in a command line client, and if someone were making a GUI for > MacPorts, I doubt they would do so in Tcl. PortAuthority (formerly known as dpgui) is written in Tcl... See http://www.codebykevin.com/blosxom.cgi for some details. But you are right, Pallet and friends are in Objective-C... I guess there are more Cocoa fans than Tcl/Tk or something. --anders From talklists at newgeo.com Sun Mar 1 02:20:18 2009 From: talklists at newgeo.com (Scott Haneda) Date: Sun, 1 Mar 2009 02:20:18 -0800 Subject: logging postfix and others In-Reply-To: <6F710CB7-4579-47EB-85E4-35B4254C402D@newgeo.com> References: <6F710CB7-4579-47EB-85E4-35B4254C402D@newgeo.com> Message-ID: <36E854DB-FF4A-4F5D-AF3F-8617BEB0BF93@newgeo.com> Sorry, I meant this to be off list, which is why some of this is a little non relevant, carry on. On Mar 1, 2009, at 1:37 AM, Scott Haneda wrote: > I just started looking into this.... > > On Feb 28, 2009, at 5:47 PM, Bradley Giesbrecht wrote: > >> What are others doing for logging? >> >> Postfix wants to use syslog facilities and I would like to move the >> logs from /var/log to /opt/local/var/xxx. > > I knew we needed to do this, but I had no idea it was going to be an > issue, I see it as being one now. One way, would be to leave them > as they are, write a small launchd item that pipes them from /var/ > log/mail to wherever we want, seems messy, less than ideal. > >> But changing /etc/syslog.conf doesn't seem like a macports way of >> doing it. >> >> I'm not totally opposed to making changes to /etc/syslog.conf but I >> wouldn't be surprised if Apple supdates over wrote them some day. > > I would say, it is pretty stable, in that it is how it is now, but > right it is going to change, for sure. > >> I'll figure this out but in case there is something more or less >> standard for macports packages I thought I'd ask. > > > I do not know of anything, but this gets worse. Somewhere in /etc/ > periodic, it a roller, that will roll the mail logs, but it saves a > certain amount of them, and then rolls them off, deleting them. If > we keep using syslog for postfix, we have to also tell people to > alter that, as it is too frequent a lot roll. Some will not want > them deleted as well, like myself. So add that to your list of > things to solve about thsi logging issues :) > > That is what is nice about apache being away from apple, the http > logs do not get rolled away. First thing I do in setting up a new > server is comment out the log rollers, second is set up a ntpudpate > command in launchd to keep the clock from drifting. > -- > Scott -- Scott * If you contact me off list replace talklists@ with scott@ * From talklists at newgeo.com Sun Mar 1 02:23:15 2009 From: talklists at newgeo.com (Scott Haneda) Date: Sun, 1 Mar 2009 02:23:15 -0800 Subject: Perl error, once and for all In-Reply-To: <49AA58DA.9000107@macports.org> References: <23BD24AB-1FC6-4B87-AC4D-44DF68BAB2A1@newgeo.com> <3D7F2DE3-A9D5-4657-9FDA-A69F7440CFC8@geeklair.net> <1DD62C2A-5E85-4481-9246-96FE34E4CF50@newgeo.com> <20090226055133.GE27410@darkart.com> <29A68AD6-F99A-48A2-B050-69A08EA349A8@newgeo.com> <68BBA4C9-23A4-414D-AFED-BC996C061CD9@macports.org> <707C94E4-9868-4B39-BF42-E0D003BA6DBA@macports.org> <20090301025356.GB4629@prunille.vinc17.org> <3A4C4D61-E80C-4B2E-9B56-828620B53966@pixilla.com> <0FE43229-E98C-42B3-AACA-5AF1F18BCBDF@newgeo.com> <49AA58DA.9000107@macports.org> Message-ID: <1763FD47-6F0A-49EA-9113-EFEFF89F2B33@newgeo.com> On Mar 1, 2009, at 1:43 AM, Joshua Root wrote: > Scott Haneda wrote: >> I have seen many posts, where a >> port is not installing. The reply from other users has been "you >> need >> to -f it, some ports are just that way", and that is not the right >> info, >> it will spiral out of control, to the point where as illustrated >> above, >> they blindly -f things. -f is for when you know what you are >> doing, it >> should not be propagating as a solution. > > You should've seen the situation pre-1.7. You had to use -f half the > time to uninstall old inactive versions of ports. And yes, some users > ended up blindly using -f for everything, sometimes with undesired > consequences. > > We are getting better, slowly but surely. :-) Indeed, and this dialogue is always good. > What the perl situation needs is someone who understands the issue to > just get in and get the job done. The ticket has well and truly hit > maintainer timeout by now. Thanks Josh, this is the first I have sort of gotten the impression the issue is even know how to be solved. I assume the ticket was so old was that no one could come to a consensus as to the best way to solve it, making it more political. As I offered before, if someone knows someone who is capable, but just needs a little motivation, let me know, I am sure that motivation can be drummed up, at least, I will do my part to help. -- Scott * If you contact me off list replace talklists@ with scott@ * From ryandesign at macports.org Sun Mar 1 03:34:24 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 1 Mar 2009 05:34:24 -0600 Subject: apache2 location In-Reply-To: <074BFD17-3354-4154-B207-0EC3699D4265@newgeo.com> References: <1154B802-5D94-4754-8848-2EF8375E1069@newgeo.com> <594B9628-56C8-4537-865E-5ACFE52B63A9@geeklair.net> <95884C34-693A-4570-8AEA-15C48E4693E8@newgeo.com> <1FE454BE-FE0D-428C-AE09-3F7EE7EB2B3F@macports.org> <074BFD17-3354-4154-B207-0EC3699D4265@newgeo.com> Message-ID: <6A6666FF-3F71-49D7-8697-6A5179C31135@macports.org> On Mar 1, 2009, at 03:58, Scott Haneda wrote: > On Feb 28, 2009, at 3:55 PM, Ryan Schmidt wrote: >> $ port installed apache* >> The following ports are currently installed: >> apache @1.3.41_0 >> apache2 @2.2.11_0 (active) >> $ port activate apache @1.3.41_0 >> ---> Activating apache @1.3.41_0 >> Error: port activate failed: Image error: /mp/share/man/man1/ >> dbmmanage.1.gz is being used by the active apache2 port. Please >> deactivate this port first, or use the -f flag to force the >> activation. >> $ > > Why does ports care if a man page is shared? I do not really even > consider it in use. Forgive my lack of understanding, and > hopefully no one jumps my butt on this idea... > > Why are man pages part of the process of being registered as > activated? It is a man page, not a binary. Maybe man pages should > just not be part of this entire chain of checks. MacPorts has no special knowledge at destroot time that this is a manpage. It treats all files the same. All files need to be part of the destroot and registered to the port so that "port contents" can show them and "port uninstall" can uninstall them. You wouldn't want an older manpage provided with the apache (1) port to silently overwrite the newer manpage you already had from the apache2 port. These are the kinds of problems having a destroot solves. > Sounds to me, like the best thing to do is just patch the source to > put the man page elsewhere, so it does not conflict. "man" only finds manpages in the manpath, which is always ${prefix}/ share/man (not just in MacPorts; that's how "man" works on all platforms). So in order for "man dbmmanage" to be able to show you the dbmmanage manpage, the file dbmmanage.1.gz needs to be in the directory ${prefix}/share/man/man1. So for these ports to not conflict we would need to for example have the apache (1) port install files like dbmmanage1.1.gz instead. Then the user would have to type "man dbmmanage1" to read the manpage. > Could I, as a port writer, use a system call to simply rm the man > page? Yes, that capability exists. You can do anything you want in the post- destroot phase. > These portfiles would have to be approved sparingly, and > cautiously, but in the end, heck it is just a man page. manpages are a common way for people to learn about software, so I would be hesitant to remove them in any port. There may also be other conflicting files besides manpages. I haven't checked. MacPorts only prints the name of the first conflicting file and then aborts. >>> Actually, are there any valid reasons ever, at all, to violate- >>> mtree, or is this just legacy support? >> >> Yes, there are valid reasons. Some examples: >> >> php5 has a variant +apache (will be renamed +apache_apple) which >> installs a PHP module for Apple's Apache web server. Apache >> requires modules to go in a particular directory, and in the case >> of Apple's Apache, that directory is outside of the prefix. >> Normally ports would not install things that interact with Apple >> software, but there was strong demand to provide a PHP module that >> worked with Apple's web server, so it was provided. > > Very cool, I had no idea that was being done, that creates a super > awesome case where people can get a strong dev box up and running, > and still use the system prefs to manage their apache, very cool. The variant was never updated for Leopard. It only works with Apple's Apache 1, thus it only works on Mac OS X 10.4 and earlier. There really haven't been that many complaints about this, certainly not recently. So perhaps we could reconsider whether we need to offer support for Apple's Apache at all anymore, since by necessity all Leopard users who are using php5 with Apache are already using the MacPorts apache2 port to do so. > This also solves OS X Server where it was weak in php support, as > in most cases, OS X Server only really fails on that front. Mac OS X Server's apache is probably different from Mac OS X's apache in several ways and the variant of php5 was designed for Mac OS X's apache, not Mac OS X Server's. >> tuntaposx installs a kernel extension into ${prefix}/Library/ >> Extensions which is not a directory we've included in the mtree >> thus far. > > In the case of a kext, I would be inclined to have a different > message, as these are much more prone to system issues. The port is free to output an additional message in this case. I don't think we have that many kernel extension ports in MacPorts that it merits adding a special message to MacPorts base for this circumstance. >> We could start creating some of these wiki pages by breaking >> things out of the FAQ. The first one that comes to mind is the >> checksum mismatch entry. As for where in the wiki these pages >> should go, I don't even think we need a prefix; they can just go >> at e.g. >> >> http://trac.macports.org/wiki/ChecksumMismatch > > Sounds valid to me. Do I need special access to the wiki to > contribute? I can help here, and I can certainly make the time. > Having the wiki pages ready for a update to MacPorts would be > nice. Then it all just falls into place. > > If someone can seed the wiki with a list of names for which need > the detailed warnings, I am more than happy to start entering in > stuff, and then having others edit it to final form. Anyone should be able to edit the wiki. From face at CentosPrime.COM Sun Mar 1 05:07:17 2009 From: face at CentosPrime.COM (Chris Janton) Date: Sun, 01 Mar 2009 06:07:17 -0700 Subject: apache2 location In-Reply-To: <6A6666FF-3F71-49D7-8697-6A5179C31135@macports.org> References: <1154B802-5D94-4754-8848-2EF8375E1069@newgeo.com> <594B9628-56C8-4537-865E-5ACFE52B63A9@geeklair.net> <95884C34-693A-4570-8AEA-15C48E4693E8@newgeo.com> <1FE454BE-FE0D-428C-AE09-3F7EE7EB2B3F@macports.org> <074BFD17-3354-4154-B207-0EC3699D4265@newgeo.com> <6A6666FF-3F71-49D7-8697-6A5179C31135@macports.org> Message-ID: On 2009-03-01 , at 04:34 , Ryan Schmidt wrote: >>> php5 has a variant +apache (will be renamed +apache_apple) which >>> installs a PHP module for Apple's Apache web server. Apache ... >> Very cool, I had no idea that was being done, that creates a super >> awesome case where people can get a strong dev box up and running, >> and still use the system prefs to manage their apache, very cool. > > The variant was never updated for Leopard. It only works with > Apple's Apache 1, thus it only works on Mac OS X 10.4 and earlier. > There really haven't been that many complaints about this, certainly > not recently. So perhaps we could reconsider whether we need to > offer support for Apple's Apache at all anymore, since by necessity > all Leopard users who are using php5 with Apache are already using > the MacPorts apache2 port to do so. Having long experience with MacPorts on a pre Leopard server, uh, pre Tiger really... Apache 1 support (apple_apache) needs to remain for all of us legacy folks, please. It really is the only "reasonable" way to keep a reasonably updated PHP (and MySQL) on the older systems. Just "freeze" apache for posterity, or somehow only allow it on darwin_7 or darwin_8 ? >> This also solves OS X Server where it was weak in php support, as >> in most cases, OS X Server only really fails on that front. > > Mac OS X Server's apache is probably different from Mac OS X's > apache in several ways and the variant of php5 was designed for Mac > OS X's apache, not Mac OS X Server's. the php5 variant for apache on Mac OS X Server works just fine. There is small bit of configuration file fiddling around, but it's not hard. I haven't tried bringing up apache2 on the Panther server. 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From ryandesign at macports.org Sun Mar 1 05:09:47 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 1 Mar 2009 07:09:47 -0600 Subject: apache2 location In-Reply-To: References: <1154B802-5D94-4754-8848-2EF8375E1069@newgeo.com> <594B9628-56C8-4537-865E-5ACFE52B63A9@geeklair.net> <95884C34-693A-4570-8AEA-15C48E4693E8@newgeo.com> <1FE454BE-FE0D-428C-AE09-3F7EE7EB2B3F@macports.org> <074BFD17-3354-4154-B207-0EC3699D4265@newgeo.com> <6A6666FF-3F71-49D7-8697-6A5179C31135@macports.org> Message-ID: On Mar 1, 2009, at 07:07, Chris Janton wrote: > On 2009-03-01 , at 04:34 , Ryan Schmidt wrote: > >>>> php5 has a variant +apache (will be renamed +apache_apple) which >>>> installs a PHP module for Apple's Apache web server. Apache > ... >>> Very cool, I had no idea that was being done, that creates a >>> super awesome case where people can get a strong dev box up and >>> running, and still use the system prefs to manage their apache, >>> very cool. >> >> The variant was never updated for Leopard. It only works with >> Apple's Apache 1, thus it only works on Mac OS X 10.4 and earlier. >> There really haven't been that many complaints about this, >> certainly not recently. So perhaps we could reconsider whether we >> need to offer support for Apple's Apache at all anymore, since by >> necessity all Leopard users who are using php5 with Apache are >> already using the MacPorts apache2 port to do so. > > Having long experience with MacPorts on a pre Leopard server, uh, > pre Tiger really... > > Apache 1 support (apple_apache) needs to remain for all of us > legacy folks, please. It really is the only "reasonable" way to > keep a reasonably updated PHP (and MySQL) on the older systems. > > Just "freeze" apache for posterity, or somehow only allow it on > darwin_7 or darwin_8 ? It's not a problem to keep it around and make it fail more gracefully on Leopard and above. However, I must ask why you feel it's "the only 'reasonable' way" to have PHP on the older systems. Why is using apache2 on those systems unreasonable? It's how I've configured my systems and it works great. >>> This also solves OS X Server where it was weak in php support, as >>> in most cases, OS X Server only really fails on that front. >> >> Mac OS X Server's apache is probably different from Mac OS X's >> apache in several ways and the variant of php5 was designed for >> Mac OS X's apache, not Mac OS X Server's. > > the php5 variant for apache on Mac OS X Server works just fine. > There is small bit of configuration file fiddling around, but it's > not hard. I haven't tried bringing up apache2 on the Panther server. Ok, that's good to know. I have apache2 running on my Panther Mac. No problems that I've seen, though it's not used very much. From face at CentosPrime.COM Sun Mar 1 05:52:44 2009 From: face at CentosPrime.COM (Chris Janton) Date: Sun, 01 Mar 2009 06:52:44 -0700 Subject: apache2 location In-Reply-To: References: <1154B802-5D94-4754-8848-2EF8375E1069@newgeo.com> <594B9628-56C8-4537-865E-5ACFE52B63A9@geeklair.net> <95884C34-693A-4570-8AEA-15C48E4693E8@newgeo.com> <1FE454BE-FE0D-428C-AE09-3F7EE7EB2B3F@macports.org> <074BFD17-3354-4154-B207-0EC3699D4265@newgeo.com> <6A6666FF-3F71-49D7-8697-6A5179C31135@macports.org> Message-ID: On 2009-03-01 , at 06:09 , Ryan Schmidt wrote: > It's not a problem to keep it around and make it fail more > gracefully on Leopard and above. However, I must ask why you feel > it's "the only 'reasonable' way" to have PHP on the older systems. > Why is using apache2 on those systems unreasonable? It's how I've > configured my systems and it works great. I should have been more clear. It's a reasonable way to have a properly functioning, up to date, PHP5 with Apache 1 on a Mac OS X Server, vintage Panther. There were other options in the past - Marc Liyanage's bundled up version worked particularly well. When that package was discontinued the only option was to "build your own". Build your own with MacPorts is far more useful than doing things "by hand". Switching the Panther server to use apache2 is a possibility, but just adds a "new" port to the mix of things that may (or may not) work going forward. At some point we will have the web sites served by the Panther system migrated away to a VMware cluster. Then I can upgrade the Panther box to Leopard and stop worrying about the ancient software. 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From face at CentosPrime.COM Sun Mar 1 06:19:33 2009 From: face at CentosPrime.COM (Chris Janton) Date: Sun, 01 Mar 2009 07:19:33 -0700 Subject: xorg-libs / Panther Message-ID: I can't seem to upgrade xorg-libs on my Panther system. 1.7 MacPorts ---> Building mesa Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_x11_mesa/work/Mesa-7.2" && make default INSTALL_DIR=/opt/local " returned error 2 Command output: Making sources for darwin make[2]: Nothing to be done for `default'. (cd drivers && make) /bin/sh ../../../../bin/mklib -o OSMesa -linker 'gcc' -ldflags '' \ -major 7 -minor 2 -patch 0 \ -install ../../../../lib \ -id /opt/local/lib/libOSMesa.7.dylib \ -L../../../../lib -lGL osmesa.o ../../../../src/mesa/ libmesa.a ../../../../src/mesa/libglapi.a mklib: Making Darwin shared library: libOSMesa.7.2.dylib mklib: Installing libOSMesa.7.2.dylib libOSMesa.7.dylib libOSMesa.dylib in ../../../../lib make[4]: `../../../lib/libGLU.dylib' is up to date. gcc -c -I../../../include -ggdb3 -Os -Wall -Wmissing-prototypes - std=c99 -ffast-math -fno-strict-aliasing -fno-common -I/opt/local/ include -I/opt/local/include -fPIC -D_DARWIN_C_SOURCE - D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE -D_SVID_SOURCE - D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - DGLX_INDIRECT_RENDERING glut_event.c glut_event.c: In function `glutTimerFunc': glut_event.c:145: warning: implicit declaration of function `gettimeofday' glut_event.c: In function `interruptibleXNextEvent': glut_event.c:309: error: `fd_set' undeclared (first use in this function) glut_event.c:309: error: (Each undeclared identifier is reported only once glut_event.c:309: error: for each function it appears in.) glut_event.c:309: error: parse error before "fds" glut_event.c:328: warning: implicit declaration of function `FD_ZERO' glut_event.c:328: error: `fds' undeclared (first use in this function) glut_event.c:329: warning: implicit declaration of function `FD_SET' glut_event.c:330: warning: implicit declaration of function `select' glut_event.c: In function `waitForSomething': glut_event.c:868: error: `fd_set' undeclared (first use in this function) glut_event.c:868: error: parse error before "fds" glut_event.c:922: error: `fds' undeclared (first use in this function) make[2]: *** [glut_event.o] Error 1 make[1]: *** [subdirs] Error 1 make: *** [default] Error 1 Error: The following dependencies failed to build: mesa DEBUG: invalid command name "::ui_init" while executing "::ui_init $priority $prefix $channels $message" ("uplevel" body line 2) invoked from within "uplevel 1 $body" Error: Unable to upgrade port: 1 admin at x:admin:132 $ port outdated The following installed ports are outdated: xorg-libs 20090105_0 < 20090224_0 8) ---------------------------------- Chris Janton - face at CentosPrime dot COM Netminder for Opus1.COM From brad at pixilla.com Sun Mar 1 08:15:20 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Sun, 1 Mar 2009 08:15:20 -0800 Subject: logging postfix and others In-Reply-To: <6F710CB7-4579-47EB-85E4-35B4254C402D@newgeo.com> References: <6F710CB7-4579-47EB-85E4-35B4254C402D@newgeo.com> Message-ID: <24BEF9A7-E75B-48DE-88A8-CB7168540A5A@pixilla.com> On Mar 1, 2009, at 1:37 AM, Scott Haneda wrote: > I just started looking into this.... > > On Feb 28, 2009, at 5:47 PM, Bradley Giesbrecht wrote: > >> What are others doing for logging? >> >> Postfix wants to use syslog facilities and I would like to move the >> logs from /var/log to /opt/local/var/xxx. > > I knew we needed to do this, but I had no idea it was going to be an > issue, I see it as being one now. One way, would be to leave them > as they are, write a small launchd item that pipes them from /var/ > log/mail to wherever we want, seems messy, less than ideal. > >> But changing /etc/syslog.conf doesn't seem like a macports way of >> doing it. >> >> I'm not totally opposed to making changes to /etc/syslog.conf but I >> wouldn't be surprised if Apple supdates over wrote them some day. > > I would say, it is pretty stable, in that it is how it is now, but > right it is going to change, for sure. > >> I'll figure this out but in case there is something more or less >> standard for macports packages I thought I'd ask. > > > I do not know of anything, but this gets worse. Somewhere in /etc/ > periodic, it a roller, that will roll the mail logs, but it saves a > certain amount of them, and then rolls them off, deleting them. If > we keep using syslog for postfix, we have to also tell people to > alter that, as it is too frequent a lot roll. Some will not want > them deleted as well, like myself. So add that to your list of > things to solve about thsi logging issues :) I'm going to look into the syslog-ng port and switching postfix to use syslog-ng. Crossing my fingers. I really think I should be able to find a five minute simple low risk solution to moving postfix logs. //Brad From brad at pixilla.com Sun Mar 1 09:39:10 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Sun, 1 Mar 2009 09:39:10 -0800 Subject: apache2 location In-Reply-To: <6A6666FF-3F71-49D7-8697-6A5179C31135@macports.org> References: <1154B802-5D94-4754-8848-2EF8375E1069@newgeo.com> <594B9628-56C8-4537-865E-5ACFE52B63A9@geeklair.net> <95884C34-693A-4570-8AEA-15C48E4693E8@newgeo.com> <1FE454BE-FE0D-428C-AE09-3F7EE7EB2B3F@macports.org> <074BFD17-3354-4154-B207-0EC3699D4265@newgeo.com> <6A6666FF-3F71-49D7-8697-6A5179C31135@macports.org> Message-ID: <6A169AA1-51FF-4D89-B0BD-9986234EB23F@pixilla.com> On Mar 1, 2009, at 3:34 AM, Ryan Schmidt wrote: > > On Mar 1, 2009, at 03:58, Scott Haneda wrote: >> On Feb 28, 2009, at 3:55 PM, Ryan Schmidt wrote: >>> $ port installed apache* >>> The following ports are currently installed: >>> apache @1.3.41_0 >>> apache2 @2.2.11_0 (active) >>> $ port activate apache @1.3.41_0 >>> ---> Activating apache @1.3.41_0 >>> Error: port activate failed: Image error: /mp/share/man/man1/ >>> dbmmanage.1.gz is being used by the active apache2 port. Please >>> deactivate this port first, or use the -f flag to force the >>> activation. >>> $ >> >> Why does ports care if a man page is shared? I do not really even >> consider it in use. Forgive my lack of understanding, and >> hopefully no one jumps my butt on this idea... >> >> Why are man pages part of the process of being registered as >> activated? It is a man page, not a binary. Maybe man pages should >> just not be part of this entire chain of checks. > > MacPorts has no special knowledge at destroot time that this is a > manpage. It treats all files the same. > > All files need to be part of the destroot and registered to the port > so that "port contents" can show them and "port uninstall" can > uninstall them. > > You wouldn't want an older manpage provided with the apache (1) port > to silently overwrite the newer manpage you already had from the > apache2 port. These are the kinds of problems having a destroot > solves. Is it very common to have apache and apache2 installed at the same time? Looks like they conflict to me. They write the same files. Shouldn't they just be conflicted so you have to uninstall apache to get apache2. As for perl5, why do p5 man pages exist for yet to be installed p5 modules? Is that normal on other systems? How about moving collisions instead of over writing? /opt/local/var/macports/collisions/[datetime]/opt/local/share/man/ [existing-file] //Brad From jeremyhu at macports.org Sun Mar 1 09:42:27 2009 From: jeremyhu at macports.org (Jeremy Huddleston) Date: Sun, 1 Mar 2009 09:42:27 -0800 Subject: xorg-libs / Panther In-Reply-To: References: Message-ID: Well that's specifically a problem with mesa for you... I don't have access to Panther, so I have no way of figuring out the problem, but I welcome a patch. According to the man page, gettimeofday should be defined by including sys/time.h. That is included on line 46 of glut_event.c On Mar 1, 2009, at 06:19, Chris Janton wrote: > I can't seem to upgrade xorg-libs on my Panther system. 1.7 MacPorts > > ---> Building mesa > Error: Target org.macports.build returned: shell command " cd "/opt/ > local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_x11_mesa/work/Mesa-7.2" && make default > INSTALL_DIR=/opt/local " returned error 2 > Command output: Making sources for darwin > make[2]: Nothing to be done for `default'. > (cd drivers && make) > /bin/sh ../../../../bin/mklib -o OSMesa -linker 'gcc' -ldflags '' \ > -major 7 -minor 2 -patch 0 \ > -install ../../../../lib \ > -id /opt/local/lib/libOSMesa.7.dylib \ > -L../../../../lib -lGL osmesa.o ../../../../src/mesa/ > libmesa.a ../../../../src/mesa/libglapi.a > mklib: Making Darwin shared library: libOSMesa.7.2.dylib > mklib: Installing libOSMesa.7.2.dylib libOSMesa.7.dylib > libOSMesa.dylib in ../../../../lib > make[4]: `../../../lib/libGLU.dylib' is up to date. > gcc -c -I../../../include -ggdb3 -Os -Wall -Wmissing-prototypes - > std=c99 -ffast-math -fno-strict-aliasing -fno-common -I/opt/local/ > include -I/opt/local/include -fPIC -D_DARWIN_C_SOURCE - > D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE - > D_SVID_SOURCE -D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - > DGLX_INDIRECT_RENDERING glut_event.c > glut_event.c: In function `glutTimerFunc': > glut_event.c:145: warning: implicit declaration of function > `gettimeofday' > glut_event.c: In function `interruptibleXNextEvent': > glut_event.c:309: error: `fd_set' undeclared (first use in this > function) > glut_event.c:309: error: (Each undeclared identifier is reported > only once > glut_event.c:309: error: for each function it appears in.) > glut_event.c:309: error: parse error before "fds" > glut_event.c:328: warning: implicit declaration of function `FD_ZERO' > glut_event.c:328: error: `fds' undeclared (first use in this function) > glut_event.c:329: warning: implicit declaration of function `FD_SET' > glut_event.c:330: warning: implicit declaration of function `select' > glut_event.c: In function `waitForSomething': > glut_event.c:868: error: `fd_set' undeclared (first use in this > function) > glut_event.c:868: error: parse error before "fds" > glut_event.c:922: error: `fds' undeclared (first use in this function) > make[2]: *** [glut_event.o] Error 1 > make[1]: *** [subdirs] Error 1 > make: *** [default] Error 1 > > Error: The following dependencies failed to build: mesa > DEBUG: invalid command name "::ui_init" > while executing > "::ui_init $priority $prefix $channels $message" > ("uplevel" body line 2) > invoked from within > "uplevel 1 $body" > Error: Unable to upgrade port: 1 > > admin at x:admin:132 $ port outdated > The following installed ports are outdated: > xorg-libs 20090105_0 < 20090224_0 > > 8) > ---------------------------------- > Chris Janton - face at CentosPrime dot COM > Netminder for Opus1.COM > > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From dp.chaoswerks at gmail.com Sun Mar 1 09:55:30 2009 From: dp.chaoswerks at gmail.com (David P. Henderson) Date: Sun, 1 Mar 2009 09:55:30 -0800 Subject: Spim Install Failure Message-ID: I am hoping that someone can point me in the right direction to get the spim port installing. It is currently marked as nomaintainer and appears to fail during the install into DESTROOT. Using the latest version of macports (ran selfupdate before attempting to install spim) and the spim version is 7.4. Specifically it looks as if the install is failing while trying to install documentation. I am attaching a file containing the output of the following commands: port -d install spim sw_vers uname -a Thanks in advance for any help Dave Henderson -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: spim_install_fail.txt URL: -------------- next part -------------- -- "God was left out of the [US] Constitution but was furnished a front seat on the coins of the country. " -- Mark Twain From jjdanimoth at gmail.com Sun Mar 1 12:47:17 2009 From: jjdanimoth at gmail.com (DaNiMoTh) Date: Sun, 1 Mar 2009 21:47:17 +0100 Subject: Distribuiting packages Message-ID: <7b71803f0903011247m44db2347jcf685068d5436369@mail.gmail.com> Hello to all. I have written an application with python and some others things, but to have these installed on a mac is using macports. There is a way to include these dependencies in only one .dmg file ? I need to learn how make it from basics. Could you give me some links, and how I can use the macports packages as dependencies? ( and distribuite it, clearly ) Many thanks From talklists at newgeo.com Sun Mar 1 15:33:33 2009 From: talklists at newgeo.com (Scott Haneda) Date: Sun, 1 Mar 2009 15:33:33 -0800 Subject: apache2 location In-Reply-To: <6A169AA1-51FF-4D89-B0BD-9986234EB23F@pixilla.com> References: <1154B802-5D94-4754-8848-2EF8375E1069@newgeo.com> <594B9628-56C8-4537-865E-5ACFE52B63A9@geeklair.net> <95884C34-693A-4570-8AEA-15C48E4693E8@newgeo.com> <1FE454BE-FE0D-428C-AE09-3F7EE7EB2B3F@macports.org> <074BFD17-3354-4154-B207-0EC3699D4265@newgeo.com> <6A6666FF-3F71-49D7-8697-6A5179C31135@macports.org> <6A169AA1-51FF-4D89-B0BD-9986234EB23F@pixilla.com> Message-ID: <56058CA9-5DED-421E-B423-A6CF019C9749@newgeo.com> On Mar 1, 2009, at 9:39 AM, Bradley Giesbrecht wrote: > Is it very common to have apache and apache2 installed at the same > time? > Looks like they conflict to me. They write the same files. > Shouldn't they just be conflicted so you have to uninstall apache to > get apache2. > > As for perl5, why do p5 man pages exist for yet to be installed p5 > modules? > Is that normal on other systems? > > How about moving collisions instead of over writing? > > /opt/local/var/macports/collisions/[datetime]/opt/local/share/man/ > [existing-file] Good idea... Also, where does MacPorts get the man pages from? Maybe they should just all be removed, then only the new ones get installed as you need them when you add in a p5? Can I simply rm all the perl man pages, new ones will come in when I instal something? -- Scott * If you contact me off list replace talklists@ with scott@ * From talklists at newgeo.com Sun Mar 1 15:37:11 2009 From: talklists at newgeo.com (Scott Haneda) Date: Sun, 1 Mar 2009 15:37:11 -0800 Subject: Spim Install Failure In-Reply-To: References: Message-ID: I could be way wrong on this one, but this seems to be an issue that is being discussed in a few others threads. If you look at the error, it is not finding a html doc page, and failing on installing that, thereby failing the activation. I believe, you could use the -f flag to force it on install, `port -df install spim`, or, since you already have it close to installed, you can try `port -df activate spim` though you will still be missing that one doc page. Please report back to let us know. On Mar 1, 2009, at 9:55 AM, David P. Henderson wrote: > I am hoping that someone can point me in the right direction to get > the spim port installing. It is currently marked as nomaintainer and > appears to fail during the install into DESTROOT. Using the latest > version of macports (ran selfupdate before attempting to install > spim) and the spim version is 7.4. Specifically it looks as if the > install is failing while trying to install documentation. > > I am attaching a file containing the output of the following commands: > > port -d install spim > sw_vers > uname -a > > Thanks in advance for any help -- Scott * If you contact me off list replace talklists@ with scott@ * From vincent-opdarw at vinc17.org Sun Mar 1 16:18:41 2009 From: vincent-opdarw at vinc17.org (Vincent Lefevre) Date: Mon, 2 Mar 2009 01:18:41 +0100 Subject: Perl error, once and for all In-Reply-To: References: <3D7F2DE3-A9D5-4657-9FDA-A69F7440CFC8@geeklair.net> <1DD62C2A-5E85-4481-9246-96FE34E4CF50@newgeo.com> <20090226055133.GE27410@darkart.com> <29A68AD6-F99A-48A2-B050-69A08EA349A8@newgeo.com> <68BBA4C9-23A4-414D-AFED-BC996C061CD9@macports.org> <707C94E4-9868-4B39-BF42-E0D003BA6DBA@macports.org> <20090301025356.GB4629@prunille.vinc17.org> Message-ID: <20090302001841.GD4629@prunille.vinc17.org> On 2009-03-01 01:00:43 -0800, Scott Haneda wrote: > So, let me get this straight, if MacPorts was to install a .profile with > a certain PERL5LIB env var in it, this issue is solved? Yes, but MacPorts should not override the user's settings (i.e. it should test whether PERL5LIB is already set...). One should end up with something like: if [ -n "$PERL5LIB" ]; then PERL5LIB="${PERL5LIB}:/opt/local/lib/perl5/vendor_perl" else export PERL5LIB PERL5LIB="/opt/local/lib/perl5/vendor_perl" fi Also, the modules that overwrite the core modules should be fixed. But there's still the potential problem with binaries and man pages, though. But a directory /opt/local/perl5 can be used for that. Adding /opt/local/perl5/bin to $PATH just before /opt/local/bin would be sufficient. -- Vincent Lef?vre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon) From ryandesign at macports.org Sun Mar 1 16:39:14 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 1 Mar 2009 18:39:14 -0600 Subject: apache2 location In-Reply-To: <6A169AA1-51FF-4D89-B0BD-9986234EB23F@pixilla.com> References: <1154B802-5D94-4754-8848-2EF8375E1069@newgeo.com> <594B9628-56C8-4537-865E-5ACFE52B63A9@geeklair.net> <95884C34-693A-4570-8AEA-15C48E4693E8@newgeo.com> <1FE454BE-FE0D-428C-AE09-3F7EE7EB2B3F@macports.org> <074BFD17-3354-4154-B207-0EC3699D4265@newgeo.com> <6A6666FF-3F71-49D7-8697-6A5179C31135@macports.org> <6A169AA1-51FF-4D89-B0BD-9986234EB23F@pixilla.com> Message-ID: <5329D54F-61BF-4048-8B32-5092EE57B263@macports.org> On Mar 1, 2009, at 11:39, Bradley Giesbrecht wrote: > On Mar 1, 2009, at 3:34 AM, Ryan Schmidt wrote: > >> On Mar 1, 2009, at 03:58, Scott Haneda wrote: >>> On Feb 28, 2009, at 3:55 PM, Ryan Schmidt wrote: >>>> $ port installed apache* >>>> The following ports are currently installed: >>>> apache @1.3.41_0 >>>> apache2 @2.2.11_0 (active) >>>> $ port activate apache @1.3.41_0 >>>> ---> Activating apache @1.3.41_0 >>>> Error: port activate failed: Image error: /mp/share/man/man1/ >>>> dbmmanage.1.gz is being used by the active apache2 port. Please >>>> deactivate this port first, or use the -f flag to force the >>>> activation. >>>> $ >>> >>> Why does ports care if a man page is shared? I do not really >>> even consider it in use. Forgive my lack of understanding, and >>> hopefully no one jumps my butt on this idea... >>> >>> Why are man pages part of the process of being registered as >>> activated? It is a man page, not a binary. Maybe man pages >>> should just not be part of this entire chain of checks. >> >> MacPorts has no special knowledge at destroot time that this is a >> manpage. It treats all files the same. >> >> All files need to be part of the destroot and registered to the >> port so that "port contents" can show them and "port uninstall" >> can uninstall them. >> >> You wouldn't want an older manpage provided with the apache (1) >> port to silently overwrite the newer manpage you already had from >> the apache2 port. These are the kinds of problems having a >> destroot solves. > > Is it very common to have apache and apache2 installed at the same > time? > Looks like they conflict to me. They write the same files. It is not possible with MacPorts today because of the conflicting files. Well, it would be possible if someone forced the activation of one apache after installing the other, but we strongly discourage users from using the force option. > Shouldn't they just be conflicted so you have to uninstall apache > to get apache2. They do conflict because they want to write the same files. To get apache2 if you already have apache, you need to deactivate apache and then activate apache2. Or activate apache2 forcibly, which is not recommended. > As for perl5, why do p5 man pages exist for yet to be installed p5 > modules? > Is that normal on other systems? I'm not sure what you mean. Can you give an example? > How about moving collisions instead of over writing? > > /opt/local/var/macports/collisions/[datetime]/opt/local/share/man/ > [existing-file] In fact, they do get moved. The old files get an extension ".mp_$ {timestamp}" From vincent-opdarw at vinc17.org Sun Mar 1 16:57:56 2009 From: vincent-opdarw at vinc17.org (Vincent Lefevre) Date: Mon, 2 Mar 2009 01:57:56 +0100 Subject: Perl error, once and for all In-Reply-To: <3A4C4D61-E80C-4B2E-9B56-828620B53966@pixilla.com> References: <3D7F2DE3-A9D5-4657-9FDA-A69F7440CFC8@geeklair.net> <1DD62C2A-5E85-4481-9246-96FE34E4CF50@newgeo.com> <20090226055133.GE27410@darkart.com> <29A68AD6-F99A-48A2-B050-69A08EA349A8@newgeo.com> <68BBA4C9-23A4-414D-AFED-BC996C061CD9@macports.org> <707C94E4-9868-4B39-BF42-E0D003BA6DBA@macports.org> <20090301025356.GB4629@prunille.vinc17.org> <3A4C4D61-E80C-4B2E-9B56-828620B53966@pixilla.com> Message-ID: <20090302005756.GE4629@prunille.vinc17.org> On 2009-02-28 21:35:59 -0800, Bradley Giesbrecht wrote: > I just want to install something that needs a perl and a p5 module. Do I > really need to RTFM for that? MacPorts can do things for you or tell you what to do. Otherwise, yes, you should RTFM. But this is not specific to perl... > If I want to install a something written in C of C++ should I just RTFM? This is a good example. MacPorts installs headers in /opt/local/include and libraries in /opt/local/lib, and these are not standard locations searched by compilers not installed by MacPorts (such as Apple's gcc from Xcode). And it seems that MacPorts does not change the .profile to declare these locations. So, if you want to install a C or C++ program that needs such headers/libraries, you must tell it where to find them. > I have a question. Why are there man pages for perl modules that are not > installed? I'm not sure. I've also noticed that man pages from modules do not have the same suffix (e.g. "3" instead of "3pm"). > Why do I have to -f an install to install a p5? You shouldn't. >>> Does anyone know how CPAN solves this? >> >> CPAN lets the user choose where he wants to install things. > > And that is what I decided to do, just not use macports for modules and > use cpan much like I use php pear. But a CPAN user is not just a perl user or MacPorts user. > And then I got totally confused by the cpan docs as to how to set up the > prefix. > > I hope there is a perl guru that can help us through this mess. Yes, I > think it's a mess. Yes, it's a mess, but I finally managed to do what I wanted thanks to the information found here: http://sial.org/howto/perl/life-with-cpan/non-root/ -- Vincent Lef?vre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon) From vincent-opdarw at vinc17.org Sun Mar 1 17:11:13 2009 From: vincent-opdarw at vinc17.org (Vincent Lefevre) Date: Mon, 2 Mar 2009 02:11:13 +0100 Subject: Perl error, once and for all In-Reply-To: <20090302001841.GD4629@prunille.vinc17.org> References: <1DD62C2A-5E85-4481-9246-96FE34E4CF50@newgeo.com> <20090226055133.GE27410@darkart.com> <29A68AD6-F99A-48A2-B050-69A08EA349A8@newgeo.com> <68BBA4C9-23A4-414D-AFED-BC996C061CD9@macports.org> <707C94E4-9868-4B39-BF42-E0D003BA6DBA@macports.org> <20090301025356.GB4629@prunille.vinc17.org> <20090302001841.GD4629@prunille.vinc17.org> Message-ID: <20090302011113.GA23645@prunille.vinc17.org> On 2009-03-02 01:18:41 +0100, Vincent Lefevre wrote: > Yes, but MacPorts should not override the user's settings (i.e. it > should test whether PERL5LIB is already set...). One should end up > with something like: > > if [ -n "$PERL5LIB" ]; then > PERL5LIB="${PERL5LIB}:/opt/local/lib/perl5/vendor_perl" > else > export PERL5LIB > PERL5LIB="/opt/local/lib/perl5/vendor_perl" > fi BTW, the order can also be changed at build time. I don't know how to do this, but I haven't searched closely... Also, a 7-year-old thread on @INC search order was resurrected a couple of weeks ago: http://www.nntp.perl.org/group/perl.perl5.porters/2009/02/msg144185.html > Also, the modules that overwrite the core modules should be fixed. > > But there's still the potential problem with binaries and man pages, > though. But a directory /opt/local/perl5 can be used for that. Adding > /opt/local/perl5/bin to $PATH just before /opt/local/bin would be > sufficient. Concerning the man pages, I'm not so sure. As I've said in another mail, the suffix (a.k.a. man section) is different, meaning that there would be no conflicts, but this may depend on the modules. -- Vincent Lef?vre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon) From brad at pixilla.com Sun Mar 1 17:49:01 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Sun, 1 Mar 2009 17:49:01 -0800 Subject: apache2 location In-Reply-To: <56058CA9-5DED-421E-B423-A6CF019C9749@newgeo.com> References: <1154B802-5D94-4754-8848-2EF8375E1069@newgeo.com> <594B9628-56C8-4537-865E-5ACFE52B63A9@geeklair.net> <95884C34-693A-4570-8AEA-15C48E4693E8@newgeo.com> <1FE454BE-FE0D-428C-AE09-3F7EE7EB2B3F@macports.org> <074BFD17-3354-4154-B207-0EC3699D4265@newgeo.com> <6A6666FF-3F71-49D7-8697-6A5179C31135@macports.org> <6A169AA1-51FF-4D89-B0BD-9986234EB23F@pixilla.com> <56058CA9-5DED-421E-B423-A6CF019C9749@newgeo.com> Message-ID: On Mar 1, 2009, at 3:33 PM, Scott Haneda wrote: > On Mar 1, 2009, at 9:39 AM, Bradley Giesbrecht wrote: > >> Is it very common to have apache and apache2 installed at the same >> time? >> Looks like they conflict to me. They write the same files. >> Shouldn't they just be conflicted so you have to uninstall apache >> to get apache2. >> >> As for perl5, why do p5 man pages exist for yet to be installed p5 >> modules? >> Is that normal on other systems? >> >> How about moving collisions instead of over writing? >> >> /opt/local/var/macports/collisions/[datetime]/opt/local/share/man/ >> [existing-file] > > > Good idea... > Also, where does MacPorts get the man pages from? Maybe they should > just all be removed, then only the new ones get installed as you > need them when you add in a p5? > > Can I simply rm all the perl man pages, new ones will come in when I > instal something? Unless someone perl wise explains why they need to be there in the first place it's a flaw in the port that put them there. Where do they come from? I'm going to wipe /opt and do a clean install to find out. Something is clearly wrong. Is it true that if I want to install assp as an example, and assp relies on p5-z thru p5-z, and I call port like so "port -f install assp" that the -f flag does not apply to the deps? If so, then I have to install all the failed p5 deps by hand with -f. If not, holy cow. I just ran -f on a whole chain of installs. //Brad From ryandesign at macports.org Sun Mar 1 18:02:35 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 1 Mar 2009 20:02:35 -0600 Subject: apache2 location In-Reply-To: References: <1154B802-5D94-4754-8848-2EF8375E1069@newgeo.com> <594B9628-56C8-4537-865E-5ACFE52B63A9@geeklair.net> <95884C34-693A-4570-8AEA-15C48E4693E8@newgeo.com> <1FE454BE-FE0D-428C-AE09-3F7EE7EB2B3F@macports.org> <074BFD17-3354-4154-B207-0EC3699D4265@newgeo.com> <6A6666FF-3F71-49D7-8697-6A5179C31135@macports.org> <6A169AA1-51FF-4D89-B0BD-9986234EB23F@pixilla.com> <56058CA9-5DED-421E-B423-A6CF019C9749@newgeo.com> Message-ID: On Mar 1, 2009, at 19:49, Bradley Giesbrecht wrote: > On Mar 1, 2009, at 3:33 PM, Scott Haneda wrote: > >> Also, where does MacPorts get the man pages from? Maybe they >> should just all be removed, then only the new ones get installed >> as you need them when you add in a p5? >> >> Can I simply rm all the perl man pages, new ones will come in when >> I instal something? > > Unless someone perl wise explains why they need to be there in the > first place it's a flaw in the port that put them there. > > Where do they come from? I still don't know what files you're talking about. Could you name a specific file? > I'm going to wipe /opt and do a clean install to find out. You can do that if you like. Correct uninstall instructions are a bit more than wiping out /opt/local; see the FAQ: http://trac.macports.org/wiki/FAQ#HowdoIremoveoruninstallMacPorts But note that "port provides /path/to/file" will tell you what port provided a file. > Something is clearly wrong. > > Is it true that if I want to install assp as an example, and assp > relies on p5-z thru p5-z, and I call port like so "port -f install > assp" that the -f flag does not apply to the deps? -f applies to the whole chain of dependencies. > If so, then I have to install all the failed p5 deps by hand with -f. > > If not, holy cow. I just ran -f on a whole chain of installs. Yes, you did. -f applies to everything. You most likely never want to use -f without also using -n (non-recursive). From brad at pixilla.com Sun Mar 1 18:20:32 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Sun, 1 Mar 2009 18:20:32 -0800 Subject: apache2 location In-Reply-To: <5329D54F-61BF-4048-8B32-5092EE57B263@macports.org> References: <1154B802-5D94-4754-8848-2EF8375E1069@newgeo.com> <594B9628-56C8-4537-865E-5ACFE52B63A9@geeklair.net> <95884C34-693A-4570-8AEA-15C48E4693E8@newgeo.com> <1FE454BE-FE0D-428C-AE09-3F7EE7EB2B3F@macports.org> <074BFD17-3354-4154-B207-0EC3699D4265@newgeo.com> <6A6666FF-3F71-49D7-8697-6A5179C31135@macports.org> <6A169AA1-51FF-4D89-B0BD-9986234EB23F@pixilla.com> <5329D54F-61BF-4048-8B32-5092EE57B263@macports.org> Message-ID: On Mar 1, 2009, at 4:39 PM, Ryan Schmidt wrote: > On Mar 1, 2009, at 11:39, Bradley Giesbrecht wrote: > >> On Mar 1, 2009, at 3:34 AM, Ryan Schmidt wrote: >> >>> On Mar 1, 2009, at 03:58, Scott Haneda wrote: >>>> On Feb 28, 2009, at 3:55 PM, Ryan Schmidt wrote: >>>>> $ port installed apache* >>>>> The following ports are currently installed: >>>>> apache @1.3.41_0 >>>>> apache2 @2.2.11_0 (active) >>>>> $ port activate apache @1.3.41_0 >>>>> ---> Activating apache @1.3.41_0 >>>>> Error: port activate failed: Image error: /mp/share/man/man1/ >>>>> dbmmanage.1.gz is being used by the active apache2 port. Please >>>>> deactivate this port first, or use the -f flag to force the >>>>> activation. >>>>> $ >>>> >>>> Why does ports care if a man page is shared? I do not really >>>> even consider it in use. Forgive my lack of understanding, and >>>> hopefully no one jumps my butt on this idea... >>>> >>>> Why are man pages part of the process of being registered as >>>> activated? It is a man page, not a binary. Maybe man pages >>>> should just not be part of this entire chain of checks. >>> >>> MacPorts has no special knowledge at destroot time that this is a >>> manpage. It treats all files the same. >>> >>> All files need to be part of the destroot and registered to the >>> port so that "port contents" can show them and "port uninstall" >>> can uninstall them. >>> >>> You wouldn't want an older manpage provided with the apache (1) >>> port to silently overwrite the newer manpage you already had from >>> the apache2 port. These are the kinds of problems having a >>> destroot solves. >> >> Is it very common to have apache and apache2 installed at the same >> time? >> Looks like they conflict to me. They write the same files. > > It is not possible with MacPorts today because of the conflicting > files. > Well, it would be possible if someone forced the activation of one > apache after installing the other, but we strongly discourage users > from using the force option. > >> Shouldn't they just be conflicted so you have to uninstall apache >> to get apache2. > > They do conflict because they want to write the same files. To get > apache2 if you already have apache, you need to deactivate apache > and then activate apache2. Or activate apache2 forcibly, which is > not recommended. >> As for perl5, why do p5 man pages exist for yet to be installed p5 >> modules? >> Is that normal on other systems? > > I'm not sure what you mean. Can you give an example? I'll reinstall mports and give you some examples. I can't recall now but I have seen it. >> How about moving collisions instead of over writing? >> >> /opt/local/var/macports/collisions/[datetime]/opt/local/share/man/ >> [existing-file] > > In fact, they do get moved. The old files get an extension ".mp_$ > {timestamp}" I've noticed that. Moving them under a common dir would allow periodic cleanup to come into play without traversing the tree. Maybe /opt/local/var/macports/collisions/opt_local_share_man_[existing- file]_[datetime] would be even better. //Brad From ryandesign at macports.org Sun Mar 1 18:34:46 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 1 Mar 2009 20:34:46 -0600 Subject: apache2 location In-Reply-To: References: <1154B802-5D94-4754-8848-2EF8375E1069@newgeo.com> <594B9628-56C8-4537-865E-5ACFE52B63A9@geeklair.net> <95884C34-693A-4570-8AEA-15C48E4693E8@newgeo.com> <1FE454BE-FE0D-428C-AE09-3F7EE7EB2B3F@macports.org> <074BFD17-3354-4154-B207-0EC3699D4265@newgeo.com> <6A6666FF-3F71-49D7-8697-6A5179C31135@macports.org> <6A169AA1-51FF-4D89-B0BD-9986234EB23F@pixilla.com> <5329D54F-61BF-4048-8B32-5092EE57B263@macports.org> Message-ID: On Mar 1, 2009, at 20:20, Bradley Giesbrecht wrote: >>> How about moving collisions instead of over writing? >>> >>> /opt/local/var/macports/collisions/[datetime]/opt/local/share/man/ >>> [existing-file] >> >> In fact, they do get moved. The old files get an extension ".mp_$ >> {timestamp}" > > I've noticed that. Moving them under a common dir would allow > periodic cleanup to come into play without traversing the tree. > Maybe /opt/local/var/macports/collisions/opt_local_share_man_ > [existing-file]_[datetime] would be even better. I don't think we need to change the current behavior. Traversing the tree is not difficult: find /opt/local -type f -name '*.mp_*' Append "-delete" to that command if you want to delete the found files. You'll probably also need to prepend "sudo" to have permission to do so. From dp.chaoswerks at gmail.com Sun Mar 1 19:44:36 2009 From: dp.chaoswerks at gmail.com (David P. Henderson) Date: Sun, 1 Mar 2009 19:44:36 -0800 Subject: Spim Install Failure In-Reply-To: References: Message-ID: <86F3C8DB-4058-4F41-B5AE-41AE0AE3E539@gmail.com> On 01 Mar 2009, at 15:37, Scott Haneda wrote: > I could be way wrong on this one, but this seems to be an issue > that is being discussed in a few others threads. Thanks. I didn't do more than a cursory search of the archives since I couldn't find any way to search them other than reading thru every article posted over the last few months and google was of no help. > If you look at the error, it is not finding a html doc page, and > failing on installing that, thereby failing the activation. > > I believe, you could use the -f flag to force it on install, `port - > df install spim`, or, since you already have it close to installed, > you can try `port -df activate spim` though you will still be > missing that one doc page. > > Please report back to let us know. > Scott, thanks for the feedback but I did try to force install it to no avail. I have however done some more investigating and it seems that the source I'm pulling is newer than the portfile. Perhaps that is the cause of the problem. [503:3] $ sudo port distcheck spim Warning: port spim: http://pages.cs.wisc.edu/~larus/SPIM/spim.tar.gz is newer than portfile Warning: couldn't fetch http://trd.no.distfiles.macports.org/spim/7.4/ spim.tar.gz for spim (HTTP response code said error) Warning: couldn't fetch http://arn.se.distfiles.macports.org/spim/7.4/ spim.tar.gz for spim (couldn't connect to server) Warning: couldn't fetch http://svn.macports.org/repository/macports/ distfiles/spim/spim.tar.gz for spim (HTTP response code said error) Warning: couldn't fetch http://svn.macports.org/repository/macports/ distfiles/general/spim.tar.gz for spim (HTTP response code said error) Warning: couldn't fetch http://svn.macports.org/repository/macports/ downloads/spim/spim.tar.gz for spim (HTTP response code said error) Also in examining the build directory under macports, the missing file does appear to be in the Documentation directory. [508:8] $ sudo ls -l /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_emulato rs_spim/work/spim-7.4/ total 160 drwx------ 33 root admin 1122 Jan 1 11:51 CPU -rw-r--r-- 1 root admin 67900 Jan 1 11:51 ChangeLog drwx------ 9 root admin 306 Feb 28 22:01 Documentation -rw-r--r-- 1 root admin 4286 Jan 1 11:51 README drwx------ 11 root admin 374 Feb 28 22:00 Tests -rw-r--r-- 1 root admin 31 Jan 1 11:51 VERSION drwx------ 23 root admin 782 Mar 1 19:23 spim drwx------ 32 root admin 1088 Feb 28 22:01 xspim [509:9] $ sudo ls -l /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_emulato rs_spim/work/spim-7.4/Documentation/ total 128 -rw-r--r-- 1 root admin 2637 Jan 1 11:51 BLURB -rw-r--r-- 1 root admin 29479 Jan 1 11:51 SPIM.html drwx------ 13 root admin 442 Jan 1 11:51 TeX -rw-r--r-- 1 root admin 4770 Jan 1 11:51 spim.man -rw-r--r-- 1 root admin 6917 Feb 28 22:01 xspim.1.html lrwxr-xr-x 1 root admin 9 Feb 28 22:01 xspim._man -> xspim.man -rw-r--r-- 1 root admin 5077 Jan 1 11:51 xspim.man The "missing" file definitely looks to be there. I'm not familiar enough with how macports does its job to do much more troubleshooting without some guidance. Thanks again for any help Dave -- "There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." -- C. A. R. "Tony" Hoare From clytie at riverland.net.au Sun Mar 1 22:20:52 2009 From: clytie at riverland.net.au (Clytie Siddall) Date: Mon, 2 Mar 2009 16:50:52 +1030 Subject: problem building py25-boto Message-ID: <5F5B5995-9326-48C3-B4F0-1EA3E6C4B922@riverland.net.au> Hi everyone :) Adam Mercer macports.org> writes: > > On Sun, Jan 25, 2009 at 01:42, John Joseph Bachir > gmail.com> wrote: > > I encountered this problem when trying to build py25-boto: > > > > $ sudo port install py25-boto > > ---> Building py25-boto > > Error: Target org.macports.build returned: shell command " cd > > "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_py thon_py25-boto/work/boto-1.6b" > > && /opt/local/bin/python2.5 setup.py --no-user-cfg build " returned error 1 > > Command output: usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 > > [cmd2_opts] ...] > > or: setup.py --help [cmd1 cmd2 ...] > > or: setup.py --help-commands > > or: setup.py cmd --help > > > > error: option --no-user-cfg not recognized > > > > Error: Status 1 encountered during processing. > > > > > > I am on 10.5.6, intel. let me know if you would like any more info. > > Thats very odd, I'm on the same platform and it builds without issue > for me (setup.py recognises the --no-user-cfg flag). Can you send me > the full debug output, i.e. the output of > > $ sudo port -d install py25-boto &> log I have exactly the same problem installing py25-lxml. I'm also on Intel 10.5.6; MacPorts was selfupdated before this installation attempt. Any help would be very much welcome. :) Install log (using your command syntax above): ___ DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/python/py25-xml DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/python/py25-xml DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre- existing procedure. Target override will not be provided DEBUG: Using group file /opt/local/var/macports/sources/ rsync.macports.org/release/ports/_resources/port1.0/group/ python25-1.0.tcl DEBUG: not using configure, so not adding the default universal variant DEBUG: Requested variant darwin is not provided by port py25-xml. DEBUG: Requested variant i386 is not provided by port py25-xml. DEBUG: Requested variant macosx is not provided by port py25-xml. DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/python25 DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/lang/python25 DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre- existing procedure. Target override will not be provided DEBUG: universal variant already exists, so not adding the default one DEBUG: Requested variant darwin is not provided by port python25. DEBUG: Requested variant i386 is not provided by port python25. DEBUG: Executing variant macosx provides macosx DEBUG: Executing variant darwin_9 provides darwin_9 DEBUG: Searching for dependency: python25 DEBUG: Found Dependency: receipt exists for python25 DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/expat DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/textproc/expat DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre- existing procedure. Target override will not be provided DEBUG: adding the default universal variant DEBUG: Requested variant darwin is not provided by port expat. DEBUG: Requested variant i386 is not provided by port expat. DEBUG: Requested variant macosx is not provided by port expat. DEBUG: Searching for dependency: expat DEBUG: Found Dependency: receipt exists for expat DEBUG: Executing org.macports.main (py25-xml) ---> Fetching py25-xml DEBUG: Executing org.macports.fetch (py25-xml) ---> PyXML-0.8.4.tar.gz doesn't seem to exist in /opt/local/var/ macports/distfiles/python DEBUG: Pinging downloads.sourceforge.net... DEBUG: Pinging easynews.dl.sourceforge.net... DEBUG: Pinging internap.dl.sourceforge.net... DEBUG: Pinging superb-east.dl.sourceforge.net... DEBUG: Pinging superb-west.dl.sourceforge.net... DEBUG: Pinging voxel.dl.sourceforge.net... DEBUG: Pinging ufpr.dl.sourceforge.net... DEBUG: Pinging dfn.dl.sourceforge.net... DEBUG: Pinging garr.dl.sourceforge.net... DEBUG: Pinging heanet.dl.sourceforge.net... DEBUG: Pinging kent.dl.sourceforge.net... DEBUG: Pinging mesh.dl.sourceforge.net... DEBUG: Pinging puzzle.dl.sourceforge.net... DEBUG: Pinging surfnet.dl.sourceforge.net... DEBUG: Pinging switch.dl.sourceforge.net... DEBUG: Pinging nchc.dl.sourceforge.net... DEBUG: Pinging internode.dl.sourceforge.net... DEBUG: Pinging transact.dl.sourceforge.net... DEBUG: Pinging optusnet.dl.sourceforge.net... DEBUG: Pinging distfiles.macports.org... DEBUG: Pinging trd.no.distfiles.macports.org... DEBUG: Pinging arn.se.distfiles.macports.org... DEBUG: downloads.sourceforge.net ping time is 336.383 DEBUG: easynews.dl.sourceforge.net ping time is 204.650 DEBUG: internap.dl.sourceforge.net ping time is 267.508 DEBUG: superb-east.dl.sourceforge.net ping time is 272.159 DEBUG: superb-west.dl.sourceforge.net ping time is 233.755 DEBUG: voxel.dl.sourceforge.net ping time is 299.545 DEBUG: ufpr.dl.sourceforge.net ping time is 534.097 DEBUG: dfn.dl.sourceforge.net ping time is 357.660 DEBUG: garr.dl.sourceforge.net ping time is 405.445 DEBUG: heanet.dl.sourceforge.net ping time is 362.231 DEBUG: kent.dl.sourceforge.net ping time is 361.285 DEBUG: mesh.dl.sourceforge.net ping time is 364.264 DEBUG: puzzle.dl.sourceforge.net ping time is 367.412 DEBUG: surfnet.dl.sourceforge.net ping time is 366.091 DEBUG: switch.dl.sourceforge.net ping time is 384.705 DEBUG: nchc.dl.sourceforge.net ping time is 270.851 DEBUG: internode.dl.sourceforge.net ping time is 26.083 DEBUG: transact.dl.sourceforge.net ping time is 67.700 DEBUG: optusnet.dl.sourceforge.net ping time is 66.127 DEBUG: distfiles.macports.org ping time is 237.945 DEBUG: trd.no.distfiles.macports.org ping time is 414.815 DEBUG: arn.se.distfiles.macports.org ping time is 372.576 ---> Attempting to fetch PyXML-0.8.4.tar.gz from http://internode.dl.sourceforge.net/pyxml % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 717k 0 1154 0 0 13715 0 0:00:53 --:--:-- 0:00:53 13715 2 717k 2 20866 0 0 47464 0 0:00:15 --:--:-- 0:00:15 55370 17 717k 17 123k 0 0 83653 0 0:00:08 0:00:01 0:00:07 87753 32 717k 32 232k 0 0 97247 0 0:00:07 0:00:02 0:00:05 97k 50 717k 50 365k 0 0 106k 0 0:00:06 0:00:03 0:00:03 108k 71 717k 71 509k 0 0 115k 0 0:00:06 0:00:04 0:00:02 117k 88 717k 88 636k 0 0 117k 0 0:00:06 0:00:05 0:00:01 123k 100 717k 100 717k 0 0 120k 0 0:00:05 0:00:05 --:--:-- 133k ---> Verifying checksum(s) for py25-xml DEBUG: Executing org.macports.checksum (py25-xml) ---> Checksumming PyXML-0.8.4.tar.gz DEBUG: Correct (md5) checksum for PyXML-0.8.4.tar.gz ---> Extracting py25-xml DEBUG: Executing org.macports.extract (py25-xml) ---> Extracting PyXML-0.8.4.tar.gz DEBUG: setting option extract.args to /opt/local/var/macports/ distfiles/python/PyXML-0.8.4.tar.gz DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.5' DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_python_py25-xml/work" && gzip -dc /opt/ local/var/macports/distfiles/python/PyXML-0.8.4.tar.gz | /usr/bin/ gnutar --no-same-owner -xf -' DEBUG: Executing org.macports.patch (py25-xml) ---> Configuring py25-xml DEBUG: Using compiler 'Mac OS X gcc 4.0' DEBUG: Executing org.macports.configure (py25-xml) ---> Building py25-xml DEBUG: Executing org.macports.build (py25-xml) DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.5' CC='gcc' DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_python_py25-xml/work/PyXML-0.8.4" && /opt/ local/bin/python2.5 setup.py --no-user-cfg build --with-libexpat=/opt/ local' usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: option --no-user-cfg not recognized Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_python_py25-xml/work/PyXML-0.8.4" && /opt/ local/bin/python2.5 setup.py --no-user-cfg build --with-libexpat=/opt/ local " returned error 1 Command output: usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: option --no-user-cfg not recognized Warning: the following items did not execute (for py25-xml): org.macports.activate org.macports.build org.macports.destroot org.macports.install Error: Status 1 encountered during processing. ___ from Clytie Vietnamese Free Software Translation Team http://vnoss.net/dokuwiki/doku.php?id=projects:l10n From blb at macports.org Sun Mar 1 22:42:38 2009 From: blb at macports.org (Bryan Blackburn) Date: Sun, 1 Mar 2009 23:42:38 -0700 Subject: problem building py25-boto In-Reply-To: <5F5B5995-9326-48C3-B4F0-1EA3E6C4B922@riverland.net.au> References: <5F5B5995-9326-48C3-B4F0-1EA3E6C4B922@riverland.net.au> Message-ID: <20090302064238.GJ917@ninagal.withay.com> On Mon, Mar 02, 2009 at 04:50:52PM +1030, Clytie Siddall said: [...] > > I have exactly the same problem installing py25-lxml. I'm also on Intel > 10.5.6; MacPorts was selfupdated > before this installation attempt. Any help would be very much welcome. :) > [...] > DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_python_py25-xml/work/PyXML-0.8.4" && /opt/ > local/bin/python2.5 setup.py --no-user-cfg build --with-libexpat=/opt/ > local' > usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] > or: setup.py --help [cmd1 cmd2 ...] > or: setup.py --help-commands > or: setup.py cmd --help > > error: option --no-user-cfg not recognized You need to upgrade your python25 port, newer versions support --no-user-cfg; see also Bryan [...] > ___ > > from Clytie > > Vietnamese Free Software Translation Team > http://vnoss.net/dokuwiki/doku.php?id=projects:l10n > From clytie at riverland.net.au Sun Mar 1 22:46:59 2009 From: clytie at riverland.net.au (Clytie Siddall) Date: Mon, 2 Mar 2009 17:16:59 +1030 Subject: problem building py25-boto In-Reply-To: <20090302064238.GJ917@ninagal.withay.com> References: <5F5B5995-9326-48C3-B4F0-1EA3E6C4B922@riverland.net.au> <20090302064238.GJ917@ninagal.withay.com> Message-ID: <35AFFFF1-432C-4E98-BE2C-05646B0883E1@riverland.net.au> On 02/03/2009, at 5:12 PM, Bryan Blackburn wrote: > On Mon, Mar 02, 2009 at 04:50:52PM +1030, Clytie Siddall said: > [...] >> >> I have exactly the same problem installing py25-lxml. I'm also on >> Intel >> 10.5.6; MacPorts was selfupdated >> before this installation attempt. Any help would be very much >> welcome. :) >> > [...] >> DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_python_py25-xml/work/PyXML-0.8.4" && / >> opt/ >> local/bin/python2.5 setup.py --no-user-cfg build --with-libexpat=/ >> opt/ >> local' >> usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] >> or: setup.py --help [cmd1 cmd2 ...] >> or: setup.py --help-commands >> or: setup.py cmd --help >> >> error: option --no-user-cfg not recognized > > You need to upgrade your python25 port, newer versions support > --no-user-cfg; see also > > I checked the Hotlist and FAQ before posting, can't believe I missed that... :S Thanks, will upgrade the Python pkgs now. :) from Clytie Vietnamese Free Software Translation Team http://vnoss.net/dokuwiki/doku.php?id=projects:l10n From joshmiks at yahoo.co.in Sun Mar 1 22:54:33 2009 From: joshmiks at yahoo.co.in (vinitha ks) Date: Mon, 2 Mar 2009 12:24:33 +0530 (IST) Subject: GLew for MAC Message-ID: <451028.33256.qm@web95416.mail.in2.yahoo.com> Hi, How do i create or download universal glew libaries for Leopard? Thanks. Did you know? You can CHAT without downloading messenger. Go to http://in.webmessenger.yahoo.com/ From blb at macports.org Sun Mar 1 23:00:39 2009 From: blb at macports.org (Bryan Blackburn) Date: Mon, 2 Mar 2009 00:00:39 -0700 Subject: problem building py25-boto In-Reply-To: <35AFFFF1-432C-4E98-BE2C-05646B0883E1@riverland.net.au> References: <5F5B5995-9326-48C3-B4F0-1EA3E6C4B922@riverland.net.au> <20090302064238.GJ917@ninagal.withay.com> <35AFFFF1-432C-4E98-BE2C-05646B0883E1@riverland.net.au> Message-ID: <20090302070039.GL917@ninagal.withay.com> On Mon, Mar 02, 2009 at 05:16:59PM +1030, Clytie Siddall said: > > On 02/03/2009, at 5:12 PM, Bryan Blackburn wrote: > >> On Mon, Mar 02, 2009 at 04:50:52PM +1030, Clytie Siddall said: >> [...] >>> >>> I have exactly the same problem installing py25-lxml. I'm also on >>> Intel >>> 10.5.6; MacPorts was selfupdated >>> before this installation attempt. Any help would be very much >>> welcome. :) >>> >> [...] >>> DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ >>> _opt_local_var_macports_sources_rsync >>> .macports.org_release_ports_python_py25-xml/work/PyXML-0.8.4" && / >>> opt/ >>> local/bin/python2.5 setup.py --no-user-cfg build --with-libexpat=/ >>> opt/ >>> local' >>> usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] >>> or: setup.py --help [cmd1 cmd2 ...] >>> or: setup.py --help-commands >>> or: setup.py cmd --help >>> >>> error: option --no-user-cfg not recognized >> >> You need to upgrade your python25 port, newer versions support >> --no-user-cfg; see also >> >> > > I checked the Hotlist and FAQ before posting, can't believe I missed > that... :S You didn't actually, I just added it since it's come up enough I figured it should probably be there. Bryan > > Thanks, will upgrade the Python pkgs now. :) > > from Clytie > > Vietnamese Free Software Translation Team > http://vnoss.net/dokuwiki/doku.php?id=projects:l10n > From ryandesign at macports.org Sun Mar 1 23:38:56 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 2 Mar 2009 01:38:56 -0600 Subject: GLew for MAC In-Reply-To: <451028.33256.qm@web95416.mail.in2.yahoo.com> References: <451028.33256.qm@web95416.mail.in2.yahoo.com> Message-ID: <01176D49-5832-479B-B0E3-7C5480BAC43C@macports.org> On Mar 2, 2009, at 00:54, vinitha ks wrote: > How do i create or download universal glew libaries for Leopard? After installing MacPorts, type this in a Terminal: sudo port install glew +universal Note that unless you want to use these compiled binaries on both an Intel Mac and a PowerPC Mac, you don't need +universal. From jeremyhu at macports.org Mon Mar 2 00:48:47 2009 From: jeremyhu at macports.org (Jeremy Huddleston) Date: Mon, 2 Mar 2009 00:48:47 -0800 Subject: GLew for MAC In-Reply-To: <01176D49-5832-479B-B0E3-7C5480BAC43C@macports.org> References: <451028.33256.qm@web95416.mail.in2.yahoo.com> <01176D49-5832-479B-B0E3-7C5480BAC43C@macports.org> Message-ID: <74E5AEBB-3588-4F73-B46E-E85C0CA99187@macports.org> On Mar 1, 2009, at 23:38, Ryan Schmidt wrote: > > On Mar 2, 2009, at 00:54, vinitha ks wrote: > >> How do i create or download universal glew libaries for Leopard? > > After installing MacPorts, type this in a Terminal: > > sudo port install glew +universal > > Note that unless you want to use these compiled binaries on both an > Intel Mac and a PowerPC Mac, you don't need +universal. I highly recommend you add +universal to /opt/local/etc/macports/ variants.conf ... otherwise you may run into trouble if you want to build something universal and its dependent is already built -universal. --Jeremy From ryandesign at macports.org Mon Mar 2 01:18:41 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 2 Mar 2009 03:18:41 -0600 Subject: Spim Install Failure In-Reply-To: References: Message-ID: On Mar 1, 2009, at 17:37, Scott Haneda wrote: > On Mar 1, 2009, at 9:55 AM, David P. Henderson wrote: > >> I am hoping that someone can point me in the right direction to >> get the spim port installing. It is currently marked as >> nomaintainer and appears to fail during the install into DESTROOT. >> Using the latest version of macports (ran selfupdate before >> attempting to install spim) and the spim version is 7.4. >> Specifically it looks as if the install is failing while trying to >> install documentation. > > I could be way wrong on this one, but this seems to be an issue > that is being discussed in a few others threads. I haven't seen any similar errors reported in other threads. > If you look at the error, it is not finding a html doc page, and > failing on installing that, thereby failing the activation. It's failing during destroot, so it hasn't even gotten to the activation phase. > I believe, you could use the -f flag to force it on install, `port - > df install spim`, or, since you already have it close to installed, > you can try `port -df activate spim` though you will still be > missing that one doc page. Forcing can't help. It can't find the file it's trying to install. No amount of coercion will allow MacPorts to install a file it can't find. David, I was able to reproduce the issue if I do not have the imake port installed (that is, if I'm using imake provided by Apple in /usr/ X11R6). The problem goes away if I use imake provided by MacPorts. In r47624 I switched the port's dependencies so that the MacPorts imake port will always be used. Please wait an hour, then "sudo port sync" and try installing again. From ryandesign at macports.org Mon Mar 2 03:15:27 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 2 Mar 2009 05:15:27 -0600 Subject: Distribuiting packages In-Reply-To: <7b71803f0903011247m44db2347jcf685068d5436369@mail.gmail.com> References: <7b71803f0903011247m44db2347jcf685068d5436369@mail.gmail.com> Message-ID: On Mar 1, 2009, at 14:47, DaNiMoTh wrote: > I have written an application with python and some others things, but > to have these installed on a mac is using macports. There is a way to > include these dependencies in only one .dmg file ? > > I need to learn how make it from basics. Could you give me some links, > and how I can use the macports packages as dependencies? ( and > distribuite it, clearly ) You can use sudo port mdmg your_software where "your_software" is a port that installs your software. Notes: 1. You should do this in a custom MacPorts install that uses a different prefix than /opt/local. Otherwise anyone who uses your package AND MacPorts will run into problems as your package would overwrite things in the standard MacPorts prefix, or at least install into it, which should not be done. 2. I believe your port and all the dependencies need to be *not* installed at the time you run "sudo port mdmg". Let "sudo port mdmg" build the ports itself. I believe I have seen messages on the list about this being the case, but I haven't tried it myself. From ryandesign at macports.org Mon Mar 2 03:21:24 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 2 Mar 2009 05:21:24 -0600 Subject: OT: clock drift (was: Re: logging postfix and others) In-Reply-To: <6F710CB7-4579-47EB-85E4-35B4254C402D@newgeo.com> References: <6F710CB7-4579-47EB-85E4-35B4254C402D@newgeo.com> Message-ID: On Mar 1, 2009, at 03:37, Scott Haneda wrote: > First thing I do in setting up a new server is comment out the log > rollers, second is set up a ntpudpate command in launchd to keep > the clock from drifting. I realize this is off-topic now, but you've made me curious. Can the clock drift if you do not do this? I thought Apple's "set date and time automatically" option was supposed to ensure clocks were synchronized. Though I admit I don't know what it does specifically. From daveesq at gmail.com Mon Mar 2 03:35:05 2009 From: daveesq at gmail.com (David J. Haines) Date: Mon, 2 Mar 2009 06:35:05 -0500 Subject: OT: clock drift (was: Re: logging postfix and others) In-Reply-To: References: <6F710CB7-4579-47EB-85E4-35B4254C402D@newgeo.com> Message-ID: Actually, running ntpdate won't help keep your clock from drifting. It only sets the clock once, at the time it is run. After that, your clock is free to drift - and this does happen. To keep your clock set and to correct for drift, you need to use ntpd. The "set time and date automatically" checkbox makes OS X run ntpd. NTP does a really good job of keeping things synchronized, taking into account network lag, and slowly adjusting the clock over time, so as to avoid "jumps" in time. On Mar 2, 2009, at 6:21 AM, Ryan Schmidt wrote: > > On Mar 1, 2009, at 03:37, Scott Haneda wrote: > >> First thing I do in setting up a new server is comment out the log >> rollers, second is set up a ntpudpate command in launchd to keep >> the clock from drifting. > > I realize this is off-topic now, but you've made me curious. Can the > clock drift if you do not do this? I thought Apple's "set date and > time automatically" option was supposed to ensure clocks were > synchronized. Though I admit I don't know what it does specifically. > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2417 bytes Desc: not available URL: From ryandesign at macports.org Mon Mar 2 05:32:18 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 2 Mar 2009 07:32:18 -0600 Subject: Distribuiting packages In-Reply-To: <7b71803f0903020504h4e43c796j3c0fb29d2cd5bb11@mail.gmail.com> References: <7b71803f0903011247m44db2347jcf685068d5436369@mail.gmail.com> <7b71803f0903020504h4e43c796j3c0fb29d2cd5bb11@mail.gmail.com> Message-ID: <7D215821-55AE-4438-95B9-81D3FD093E84@macports.org> On Mar 2, 2009, at 07:04, DaNiMoTh wrote: > 2009/3/2 Ryan Schmidt wrote: > >> On Mar 1, 2009, at 14:47, DaNiMoTh wrote: >> >> You can use >> >> sudo port mdmg your_software >> >> where "your_software" is a port that installs your software. > > It sounds good, I can do this. > > But, if I want to distribute a Application.app, runnable everywhere by > a double click ? If your app requires external libraries, the Apple Way would be to include those external libraries within your application bundle as relocatable frameworks. I'm sure there must be a wealth of documentation available on that topic from Apple and others. But it is not something that MacPorts is designed to help you with. MacPorts installs non-relocatable libraries and programs into a particular prefix, by default /opt/local, changeable at compile time but not otherwise. P.S: Use Reply All so your reply goes to the list too, not just to me. From dp.chaoswerks at gmail.com Mon Mar 2 08:21:15 2009 From: dp.chaoswerks at gmail.com (David P. Henderson) Date: Mon, 2 Mar 2009 08:21:15 -0800 Subject: Spim Install Failure In-Reply-To: References: Message-ID: <6738F041-9DBE-47BA-83CE-95B6F35AE8FB@gmail.com> Ryan, That did the trick. Thanks ever so much for all the help. When I've more time, I want to delve into the workings of macports so that I've a better understanding and can do more troubleshooting on my own, but right now I'm a full-time engineering undergrad with a wife and 3 kids and little to no time. Dave On 02 Mar 2009, at 01:18, Ryan Schmidt wrote: > David, I was able to reproduce the issue if I do not have the imake > port installed (that is, if I'm using imake provided by Apple in / > usr/X11R6). The problem goes away if I use imake provided by > MacPorts. In r47624 I switched the port's dependencies so that the > MacPorts imake port will always be used. Please wait an hour, then > "sudo port sync" and try installing again. -- "A fanatic is one who redoubles his effort when he has forgotten his aim." -- George Santayana From deric.lists at gmail.com Mon Mar 2 08:46:56 2009 From: deric.lists at gmail.com (Daniel Ericsson) Date: Mon, 2 Mar 2009 17:46:56 +0100 Subject: Distribuiting packages In-Reply-To: <7D215821-55AE-4438-95B9-81D3FD093E84@macports.org> References: <7b71803f0903011247m44db2347jcf685068d5436369@mail.gmail.com> <7b71803f0903020504h4e43c796j3c0fb29d2cd5bb11@mail.gmail.com> <7D215821-55AE-4438-95B9-81D3FD093E84@macports.org> Message-ID: <80bd4430903020846s5f9605du6930c52f724684bf@mail.gmail.com> > > But, if I want to distribute a Application.app, runnable everywhere by > > a double click ? http://svn.pythonmac.org/py2app/py2app/trunk/doc/index.html py2app is avaliable in MacPorts. -- Daniel From yannick.carissan at univ-cezanne.fr Mon Mar 2 08:51:44 2009 From: yannick.carissan at univ-cezanne.fr (Yannick CARISSAN) Date: Mon, 2 Mar 2009 17:51:44 +0100 (CET) Subject: Error building python26[SOLVED] In-Reply-To: <20090228225139.GE885@ninagal.withay.com> References: <090B7E9A-8270-4C59-8A63-E364164606FE@univ-cezanne.fr> <20090227222616.GE1054@ninagal.withay.com> <992F9516-67DC-4BFC-82E0-CBCF44C3F7D8@univ-cezanne.fr> <49A9117C.3070600@macports.org> <265ABFA2-C585-40BA-A356-91928347985C@univ-cezanne.fr> <49A95251.20801@macports.org> <8F25A50A-2C36-4FF5-A776-FC224DB8465E@univ-cezanne.fr> <20090228225139.GE885@ninagal.withay.com> Message-ID: <22360966.90783.1236012704416.JavaMail.root@frontal2> Thank you for your help. I cleaned my usr/local and it works now. I am sorry I used your time. Yannick > ---------------------------------------- > From: Bryan Blackburn > Sent: Sat Feb 28 23:51:39 CET 2009 > To: > Subject: Re: Error building python26 > > > On Sat, Feb 28, 2009 at 07:51:09PM +0100, Yannick Carissan said: > > yes, when python26 is cleaned, the problem stays : > > > > [...] > >From the debug output: > > > /usr/bin/install -c -m 644 ./Misc/python.man \ > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_python26/work/destroot/opt/local/Library/Frameworks/Python.framework/Versions/2.6/share/man/man1/python.1 > *** WARNING: renaming "_struct" since importing it failed: > dlopen(build/lib.macosx-10.5-i386-2.6/_struct.so, 2): Symbol not > found: ___sysctl > Referenced from: /usr/local/lib/libgcc_s.1.dylib > Expected in: /usr/lib/libSystem.B.dylib > > > It looks like you may have something in /usr/local (a gcc build perhaps) > that is interferring with building. There are quite a few similar warnings > like this one, which eventually conclude in: > > > Failed to build these modules: > _bisect _bsddb _bytesio > _CF _CG _codecs_cn > _codecs_hk _codecs_iso2022 _codecs_jp > _codecs_kr _codecs_tw _collections > _csv _ctypes _ctypes_test > _curses _curses_panel _elementtree > _fileio _functools _hashlib > _heapq _hotshot _json > _Launch _locale _lsprof > _multibytecodec _multiprocessing _random > _socket _sqlite3 _ssl > _struct _testcapi _tkinter > _weakref array audioop > autoGIL binascii bz2 > cmath cPickle crypt > cStringIO datetime dbm > dl fcntl future_builtins > gdbm grp imageop > itertools math mmap > nis operator parser > pyexpat readline resource > select strop syslog > termios time unicodedata > zlib > > > It looks like most modules are failing to build because of it. > > Bryan > > [...] > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From lanceboyle at qwest.net Mon Mar 2 11:52:42 2009 From: lanceboyle at qwest.net (Jerry) Date: Mon, 2 Mar 2009 12:52:42 -0700 Subject: gnat-gcc won't install Message-ID: <720776A9-6A83-47CD-99A5-B3C51BA91293@qwest.net> I'm having trouble installing gnat-gcc on PPC running OS X 10.5.4. (This Leopard is a sandbox for the purpose of trying to install GNAT. FWIW, I'm still running 10.4.11 day-to-day because of the past GNAT issues with PPC and Leopard.) Here are the last few lines of output from my attempt: Fetching gnat-gcc Attempting to fetch gcc-core-4.3.3.tar.bz2 from http:// mirrors.kernel.org/gnu//gcc/gcc-4.3.3 Attempting to fetch gcc-ada-4.3.3.tar.bz2 from http:// mirrors.kernel.org/gnu//gcc/gcc-4.3.3 Attempting to fetch gcc-fortran-4.3.3.tar.bz2 from http:// mirrors.kernel.org/gnu//gcc/gcc-4.3.3 Attempting to fetch gcc-g++-4.3.3.tar.bz2 from http:// mirrors.kernel.org/gnu//gcc/gcc-4.3.3 Attempting to fetch gcc-java-4.3.3.tar.bz2 from http:// mirrors.kernel.org/gnu//gcc/gcc-4.3.3 Attempting to fetch gcc-objc-4.3.3.tar.bz2 from http:// mirrors.kernel.org/gnu//gcc/gcc-4.3.3 Verifying checksum(s) for gnat-gcc Extracting gnat-gcc Configuring gnat-gcc Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_lang_gn at-gcc/work/build" && ../gcc-4.3.3/configure --prefix=/opt/local -- enable-languages=c,c++,ada,objc,obj-c++,java,fortran --libdir=/opt/ local/lib/gnat-gcc --includedir=/opt/local/include/gnat-gcc -- infodir=/opt/local/share/info --mandir=/opt/local/share/man --with- local-prefix=/opt/local --with-system-zlib --disable-nls -- program-suffix=-gnat-4.3 --with-gxx-include-dir=/opt/local/include/ gnat-gcc/c++/ --with-gmp=/opt/local --with-mpfr=/opt/local --disable- multilib " returned error 77 Command output: checking build system type... powerpc-apple-darwin9.4.0 checking host system type... powerpc-apple-darwin9.4.0 checking target system type... powerpc-apple-darwin9.4.0 checking for a BSD-compatible install... /usr/bin/install -c checking whether ln works... yes checking whether ln -s works... yes checking for gcc... /opt/local/ bin/gcc-gnat-4.3 checking for C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details. Error: Status 1 encountered during processing. Executing: /opt/local/bin/port install gnat-gcc +powerpc +gnuada Any ideas? Jerry From ms at mac-specialist.com Mon Mar 2 12:10:27 2009 From: ms at mac-specialist.com (Bill Hernandez) Date: Mon, 02 Mar 2009 14:10:27 -0600 Subject: man pages plus {with cached sample code} Message-ID: Over time I have written a bunch of shell scripts. Some I use frequently, some I never use. One of the handy ones is called bh_man. It creates a small hierarchy of directories if they don't exist, checks the $PATH in ./ bash_profile, and sets it if necessary. The gist of it, is that it would be nice to be able to add {comments, notes, sample code, urls, etc} to man pages, but I don't know of an easy way to do that, so with that in mind I wrote "bh_man". When bh_man is called with an argument (unix_command_name) it first determines if I already have that command in my personal cache, if it exists then it pulls it up instead of the actual man page, if it does not exist in the cache, it copies the man page, strips out all the bizarre characters, and opens it in BBEdit. The huge advantage is that the cached document pulls up instantly, is easily editable with BBEdit, or any other text editor, and the best thing is that I can add/modify {comments, notes, sample code, urls, etc} for each man page I choose to. Consequently most of the commands I have already cached have a lot of example code included. The example code is right at the top, so once I have added some snippets, I don't even have to scroll through the document. The examples are right there... The hierarchy below shows that a dir is created that provides a starting place at "~/unix_scripts". The "bh_man" script does the following : ( 1 ) checks the "~/unix_scripts" hierarchy, and creates it, if it does not exist. ( 2 ) checks "~/.bash_profile", and creates it, if it does not exist. ( 3 ) checks "~/.bash_profile" to make sure "~/unix_scripts/bin" exists in the path, and adds it to the $PATH, if it does not exist. ( 4 ) creates the "bh_open" shell script in "~/unix_scripts/bin" ( 5 ) when finished with steps ( 1 ) thru ( 4 ) above, it moves (itself) "bh_man" to "~/unix_scripts/bin" as shown below. Note : The hierarchy below shows, for example, when you do "bh_man open" it creates "open.txt" as shown below. I put the hierarchy in my home directory instead of /usr/local or /opt/ local, because it gets backed up more often that way. > unix_scripts > admin > bbedit > bin bh_man bh_open > docs > manual open.txt > help > history > logs > macports > misc > modules > src These are the commands I have already, many of them contain sample usage code, which for me, is what the man pages have always lacked, even some simple examples would be nice. Anyway I figured out a way around the problem for myself. If anyone is interested in trying the script please reply. If there is enough interest, I'll put it on my server. > docs > manual addgroup.txt adduser.txt alias.txt ascii.txt awk.txt bash.txt bz2.txt bzip2.txt case.txt cat.txt chmod.txt colrm.txt curl.txt cut.txt date.txt defaults.txt diff.txt DirectoryService.txt dscl.txt dseditgroup.txt dsexport.txt dsmemberutil.txt echo.txt egrep.txt export.txt file.txt for.txt format.txt FUNCNAME.txt functions.txt getcwd.txt getopts.txt grep.txt group.txt id.txt jot.txt kill.txt launchd.txt lookupd.txt loop.txt ls.txt mkdir.txt mysql.basic_info.txt mysql.GRANT.txt mysql.mysqladmin.txt nicl.txt nidump.txt niload.txt nireport.txt niutil.txt open.txt operator.txt parameters.txt passwd.txt pgsql.txt pidof.txt port.txt printf.txt PS1.txt psql.txt rand.txt read.txt reboot.txt redirection.txt repl.txt rm.txt rmdir.txt rpl.txt rs.txt security.txt sed.txt seq.txt sh.txt sort.txt ssh.txt str_repeat.txt stty.txt su.txt sudo.txt tar.txt tee.txt termcap.txt test.txt touch.txt tr.txt uname.txt wc.txt wget.txt xargs.txt Best Regards, Bill Hernandez Plano, Texas From brad at pixilla.com Mon Mar 2 12:51:01 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Mon, 2 Mar 2009 12:51:01 -0800 Subject: perl -f (was apache2 location) In-Reply-To: References: <1154B802-5D94-4754-8848-2EF8375E1069@newgeo.com> <594B9628-56C8-4537-865E-5ACFE52B63A9@geeklair.net> <95884C34-693A-4570-8AEA-15C48E4693E8@newgeo.com> <1FE454BE-FE0D-428C-AE09-3F7EE7EB2B3F@macports.org> <074BFD17-3354-4154-B207-0EC3699D4265@newgeo.com> <6A6666FF-3F71-49D7-8697-6A5179C31135@macports.org> <6A169AA1-51FF-4D89-B0BD-9986234EB23F@pixilla.com> <56058CA9-5DED-421E-B423-A6CF019C9749@newgeo.com> Message-ID: <73FAE155-D73A-4F80-9301-80CCDACB31F2@pixilla.com> On Mar 1, 2009, at 6:02 PM, Ryan Schmidt wrote: > On Mar 1, 2009, at 19:49, Bradley Giesbrecht wrote: > >> On Mar 1, 2009, at 3:33 PM, Scott Haneda wrote: >> >>> Also, where does MacPorts get the man pages from? Maybe they >>> should just all be removed, then only the new ones get installed >>> as you need them when you add in a p5? >>> >>> Can I simply rm all the perl man pages, new ones will come in when >>> I instal something? >> >> Unless someone perl wise explains why they need to be there in the >> first place it's a flaw in the port that put them there. >> >> Where do they come from? > > I still don't know what files you're talking about. Could you name a > specific file? I uninstalled and reinstalled macports. Installed perl5.8 and and then p5-digest-md5 to give you an example. I think the problem may be that perl5.8 installs a lot of modules but they do not get registered so when a port like imapsync depends on p5- digest-md5 macports may not know that it's installed already. Or maybe p5-digest-md5 is not installed but the man page is. You will see a lot of perl module man pages in /opt/local/man/man3 after installing only perl5.8. bash-3.2# ls /opt/local/man/man1 .turd_MacPorts port.1.gz bash-3.2# ls /opt/local/man/man3 .turd_MacPorts bash-3.2# port install perl5.8 bash-3.2# ls /opt/local/man/man1 .turd_MacPorts perl583delta.1.gz perlcheat.1.gz perlfaq3.1.gz perlirix.1.gz perlopentut.1.gz perlsolaris.1.gz perlvos.1.gz a2p.1.gz perl584delta.1.gz perlclib.1.gz perlfaq4.1.gz perlivp. 1.gz perlos2.1.gz perlstyle.1.gz perlwin32.1.gz c2ph.1.gz perl585delta.1.gz perlcn.1.gz perlfaq5.1.gz perljp.1.gz perlos390.1.gz perlsub.1.gz perlxs.1.gz corelist.1.gz perl586delta.1.gz perlcommunity.1.gz perlfaq6.1.gz perlko.1.gz perlos400.1.gz perlsyn.1.gz perlxstut.1.gz cpan.1.gz perl587delta.1.gz perlcompile.1.gz perlfaq7.1.gz perllexwarn.1.gz perlothrtut.1.gz perlthanks.1.gz piconv.1.gz dprofpp.1.gz perl588delta.1.gz perlcygwin.1.gz perlfaq8.1.gz perllinux.1.gz perlpacktut.1.gz perlthrtut.1.gz pl2pm.1.gz enc2xs.1.gz perl589delta.1.gz perldata.1.gz perlfaq9.1.gz perllocale.1.gz perlplan9.1.gz perltie.1.gz pod2html.1.gz find2perl.1.gz perl58delta.1.gz perldbmfilter.1.gz perlfilter.1.gz perllol.1.gz perlpod.1.gz perltoc.1.gz pod2latex.1.gz h2ph.1.gz perlaix.1.gz perldebguts.1.gz perlfork.1.gz perlmachten. 1.gz perlpodspec.1.gz perltodo.1.gz pod2man.1.gz h2xs.1.gz perlamiga.1.gz perldebtut.1.gz perlform.1.gz perlmacos. 1.gz perlport.1.gz perltooc.1.gz pod2text.1.gz instmodsh.1.gz perlapi.1.gz perldebug.1.gz perlfreebsd.1.gz perlmacosx.1.gz perlqnx.1.gz perltoot.1.gz pod2usage.1.gz libnetcfg.1.gz perlapio.1.gz perldelta.1.gz perlfunc.1.gz perlmint. 1.gz perlre.1.gz perltrap.1.gz podchecker.1.gz perl.1.gz perlapollo.1.gz perldgux.1.gz perlglossary.1.gz perlmod. 1.gz perlrebackslash.1.gz perltru64.1.gz podselect.1.gz perl5004delta.1.gz perlartistic.1.gz perldiag.1.gz perlgpl.1.gz perlmodinstall.1.gz perlrecharclass.1.gz perltw.1.gz port.1.gz perl5005delta.1.gz perlbeos.1.gz perldoc.1.gz perlguts.1.gz perlmodlib.1.gz perlref.1.gz perlunicode.1.gz prove.1.gz perl561delta.1.gz perlbook.1.gz perldos.1.gz perlhack.1.gz perlmodstyle.1.gz perlreftut.1.gz perlunifaq.1.gz psed.1.gz perl56delta.1.gz perlboot.1.gz perldsc.1.gz perlhist.1.gz perlmpeix. 1.gz perlreguts.1.gz perluniintro.1.gz pstruct.1.gz perl570delta.1.gz perlbot.1.gz perlebcdic.1.gz perlhpux.1.gz perlnetware.1.gz perlrequick.1.gz perlunitut.1.gz s2p.1.gz perl571delta.1.gz perlbs2000.1.gz perlembed.1.gz perlhurd.1.gz perlnewmod.1.gz perlreref.1.gz perlutil.1.gz splain.1.gz perl572delta.1.gz perlbug.1.gz perlepoc.1.gz perlintern.1.gz perlnumber.1.gz perlretut.1.gz perluts.1.gz xsubpp.1.gz perl573delta.1.gz perlcall.1.gz perlfaq.1.gz perlintro.1.gz perlobj. 1.gz perlriscos.1.gz perlvar.1.gz perl581delta.1.gz perlcc.1.gz perlfaq1.1.gz perliol.1.gz perlop. 1.gz perlrun.1.gz perlvmesa.1.gz perl582delta.1.gz perlce.1.gz perlfaq2.1.gz perlipc.1.gz perlopenbsd.1.gz perlsec.1.gz perlvms.1.gz bash-3.2# ls /opt/local/man/man3 .turd_MacPorts Encode::Byte.3pm.gz File::DosGlob.3pm.gz NEXT. 3pm.gz Test::Harness::Results.3pm.gz AnyDBM_File.3pm.gz Encode::CJKConstants.3pm.gz File::Find.3pm.gz Net::Cmd.3pm.gz Test::Harness::Straps.3pm.gz Attribute::Handlers.3pm.gz Encode::CN.3pm.gz File::Glob.3pm.gz Net::Config.3pm.gz Test::Harness::TAP.3pm.gz AutoLoader.3pm.gz Encode::CN::HZ.3pm.gz File::Path.3pm.gz Net::Domain.3pm.gz Test::Harness::Util.3pm.gz AutoSplit.3pm.gz Encode::Config.3pm.gz File::Spec.3pm.gz Net::FTP.3pm.gz Test::More.3pm.gz B.3pm.gz Encode::EBCDIC.3pm.gz File::Spec::Cygwin.3pm.gz Net::NNTP.3pm.gz Test::Simple.3pm.gz B::Asmdata.3pm.gz Encode::Encoder.3pm.gz File::Spec::Epoc.3pm.gz Net::Netrc.3pm.gz Test::Tutorial.3pm.gz B::Assembler.3pm.gz Encode::Encoding.3pm.gz File::Spec::Functions. 3pm.gz Net::POP3.3pm.gz Text::Abbrev.3pm.gz B::Bblock.3pm.gz Encode::GSM0338.3pm.gz File::Spec::Mac.3pm.gz Net::Ping.3pm.gz Text::Balanced.3pm.gz B::Bytecode.3pm.gz Encode::Guess.3pm.gz File::Spec::OS2.3pm.gz Net::SMTP.3pm.gz Text::ParseWords.3pm.gz B::C.3pm.gz Encode::JP.3pm.gz File::Spec::Unix.3pm.gz Net::Time. 3pm.gz Text::Soundex.3pm.gz B::CC.3pm.gz Encode::JP::H2Z.3pm.gz File::Spec::VMS.3pm.gz Net::hostent.3pm.gz Text::Tabs.3pm.gz B::Concise.3pm.gz Encode::JP::JIS7.3pm.gz File::Spec::Win32.3pm.gz Net::libnetFAQ.3pm.gz Text::Wrap.3pm.gz B::Debug.3pm.gz Encode::KR.3pm.gz File::Temp.3pm.gz Net::netent. 3pm.gz Thread.3pm.gz B::Deparse.3pm.gz Encode::KR::2022_KR.3pm.gz File::stat.3pm.gz Net::protoent.3pm.gz Thread::Queue.3pm.gz B::Disassembler.3pm.gz Encode::MIME::Header.3pm.gz FileCache. 3pm.gz Net::servent.3pm.gz Thread::Semaphore.3pm.gz B::Lint.3pm.gz Encode::MIME::Name.3pm.gz FileHandle.3pm.gz O. 3pm.gz Tie::Array.3pm.gz B::Lint::Debug.3pm.gz Encode::PerlIO.3pm.gz Filter::Simple. 3pm.gz Opcode.3pm.gz Tie::File.3pm.gz B::Showlex.3pm.gz Encode::Supported.3pm.gz Filter::Util::Call. 3pm.gz POSIX.3pm.gz Tie::Handle.3pm.gz B::Stackobj.3pm.gz Encode::Symbol.3pm.gz FindBin.3pm.gz PerlIO. 3pm.gz Tie::Hash.3pm.gz B::Stash.3pm.gz Encode::TW.3pm.gz GDBM_File.3pm.gz PerlIO::encoding.3pm.gz Tie::Memoize.3pm.gz B::Terse.3pm.gz Encode::Unicode.3pm.gz Getopt::Long.3pm.gz PerlIO::scalar.3pm.gz Tie::RefHash.3pm.gz B::Xref.3pm.gz Encode::Unicode::UTF7.3pm.gz Getopt::Std.3pm.gz PerlIO::via.3pm.gz Tie::Scalar.3pm.gz Benchmark.3pm.gz English.3pm.gz Hash::Util.3pm.gz PerlIO::via::QuotedPrint.3pm.gz Tie::StdHandle.3pm.gz ByteLoader.3pm.gz Env.3pm.gz I18N::Collate.3pm.gz Pod::Checker. 3pm.gz Tie::SubstrHash.3pm.gz CGI.3pm.gz Errno.3pm.gz I18N::LangTags.3pm.gz Pod::Find. 3pm.gz Time::HiRes.3pm.gz CGI::Apache.3pm.gz Exporter.3pm.gz I18N::LangTags::Detect.3pm.gz Pod::Html.3pm.gz Time::Local.3pm.gz CGI::Carp.3pm.gz Exporter::Heavy.3pm.gz I18N::LangTags::List. 3pm.gz Pod::InputObjects.3pm.gz Time::gmtime.3pm.gz CGI::Cookie.3pm.gz ExtUtils::Command.3pm.gz I18N::Langinfo.3pm.gz Pod::LaTeX.3pm.gz Time::localtime.3pm.gz CGI::Fast.3pm.gz ExtUtils::Command::MM.3pm.gz IO.3pm.gz Pod::Man. 3pm.gz Time::tm.3pm.gz CGI::Pretty.3pm.gz ExtUtils::Constant.3pm.gz IO::Dir.3pm.gz Pod::ParseLink.3pm.gz UNIVERSAL.3pm.gz CGI::Push.3pm.gz ExtUtils::Constant::Base.3pm.gz IO::File.3pm.gz Pod::ParseUtils.3pm.gz Unicode::Collate.3pm.gz CGI::Switch.3pm.gz ExtUtils::Constant::Utils.3pm.gz IO::Handle. 3pm.gz Pod::Parser.3pm.gz Unicode::Normalize.3pm.gz CGI::Util.3pm.gz ExtUtils::Constant::XS.3pm.gz IO::Pipe.3pm.gz Pod::Perldoc::ToChecker.3pm.gz Unicode::UCD.3pm.gz CORE.3pm.gz ExtUtils::Embed.3pm.gz IO::Poll.3pm.gz Pod::Perldoc::ToMan.3pm.gz User::grent.3pm.gz CPAN.3pm.gz ExtUtils::Install.3pm.gz IO::Seekable.3pm.gz Pod::Perldoc::ToNroff.3pm.gz User::pwent.3pm.gz CPAN::API::HOWTO.3pm.gz ExtUtils::Installed.3pm.gz IO::Select. 3pm.gz Pod::Perldoc::ToPod.3pm.gz XS::APItest.3pm.gz CPAN::Debug.3pm.gz ExtUtils::Liblist.3pm.gz IO::Socket.3pm.gz Pod::Perldoc::ToRtf.3pm.gz XS::Typemap.3pm.gz CPAN::Distroprefs.3pm.gz ExtUtils::MM.3pm.gz IO::Socket::INET. 3pm.gz Pod::Perldoc::ToText.3pm.gz XSLoader.3pm.gz CPAN::FirstTime.3pm.gz ExtUtils::MM_AIX.3pm.gz IO::Socket::UNIX. 3pm.gz Pod::Perldoc::ToTk.3pm.gz attributes.3pm.gz CPAN::HandleConfig.3pm.gz ExtUtils::MM_Any.3pm.gz IPC::Msg. 3pm.gz Pod::Perldoc::ToXml.3pm.gz attrs.3pm.gz CPAN::Kwalify.3pm.gz ExtUtils::MM_BeOS.3pm.gz IPC::Open2.3pm.gz Pod::PlainText.3pm.gz autouse.3pm.gz CPAN::Nox.3pm.gz ExtUtils::MM_Cygwin.3pm.gz IPC::Open3.3pm.gz Pod::Plainer.3pm.gz base.3pm.gz CPAN::Queue.3pm.gz ExtUtils::MM_DOS.3pm.gz IPC::Semaphore.3pm.gz Pod::Select.3pm.gz bigint.3pm.gz CPAN::Tarzip.3pm.gz ExtUtils::MM_Darwin.3pm.gz IPC::SharedMem. 3pm.gz Pod::Text.3pm.gz bignum.3pm.gz CPAN::Version.3pm.gz ExtUtils::MM_MacOS.3pm.gz IPC::SysV.3pm.gz Pod::Text::Color.3pm.gz bigrat.3pm.gz Carp.3pm.gz ExtUtils::MM_NW5.3pm.gz List::Util.3pm.gz Pod::Text::Overstrike.3pm.gz blib.3pm.gz Carp::Heavy.3pm.gz ExtUtils::MM_OS2.3pm.gz Locale::Constants. 3pm.gz Pod::Text::Termcap.3pm.gz bytes.3pm.gz Class::ISA.3pm.gz ExtUtils::MM_QNX.3pm.gz Locale::Country.3pm.gz Pod::Usage.3pm.gz charnames.3pm.gz Class::Struct.3pm.gz ExtUtils::MM_UWIN.3pm.gz Locale::Currency. 3pm.gz SDBM_File.3pm.gz constant.3pm.gz Config.3pm.gz ExtUtils::MM_Unix.3pm.gz Locale::Language.3pm.gz Safe.3pm.gz diagnostics.3pm.gz Cwd.3pm.gz ExtUtils::MM_VMS.3pm.gz Locale::Maketext.3pm.gz Scalar::Util.3pm.gz encoding.3pm.gz DB.3pm.gz ExtUtils::MM_VOS.3pm.gz Locale::Maketext::TPJ13.3pm.gz Search::Dict.3pm.gz fields.3pm.gz DBM_Filter.3pm.gz ExtUtils::MM_Win32.3pm.gz Locale::Script.3pm.gz SelectSaver.3pm.gz filetest.3pm.gz DBM_Filter::compress.3pm.gz ExtUtils::MM_Win95.3pm.gz MIME::Base64.3pm.gz SelfLoader.3pm.gz gdbm.3.gz DBM_Filter::encode.3pm.gz ExtUtils::MY.3pm.gz MIME::QuotedPrint. 3pm.gz Shell.3pm.gz if.3pm.gz DBM_Filter::int32.3pm.gz ExtUtils::MakeMaker.3pm.gz Math::BigFloat. 3pm.gz Socket.3pm.gz integer.3pm.gz DBM_Filter::null.3pm.gz ExtUtils::MakeMaker::Config.3pm.gz Math::BigInt.3pm.gz Storable.3pm.gz less.3pm.gz DBM_Filter::utf8.3pm.gz ExtUtils::MakeMaker::FAQ.3pm.gz Math::BigInt::Calc.3pm.gz Switch.3pm.gz lib.3pm.gz DB_File.3pm.gz ExtUtils::MakeMaker::Tutorial.3pm.gz Math::BigInt::CalcEmu.3pm.gz Symbol.3pm.gz locale.3pm.gz Data::Dumper.3pm.gz ExtUtils::MakeMaker::bytes.3pm.gz Math::BigRat. 3pm.gz Sys::Hostname.3pm.gz open.3pm.gz Devel::DProf.3pm.gz ExtUtils::MakeMaker::vmsish.3pm.gz Math::Complex. 3pm.gz Sys::Syslog.3pm.gz ops.3pm.gz Devel::InnerPackage.3pm.gz ExtUtils::Manifest.3pm.gz Math::Trig. 3pm.gz Term::ANSIColor.3pm.gz overload.3pm.gz Devel::PPPort.3pm.gz ExtUtils::Miniperl.3pm.gz Memoize.3pm.gz Term::Cap.3pm.gz re.3pm.gz Devel::Peek.3pm.gz ExtUtils::Mkbootstrap.3pm.gz Memoize::AnyDBM_File.3pm.gz Term::Complete.3pm.gz sigtrap.3pm.gz Devel::SelfStubber.3pm.gz ExtUtils::Mksymlists.3pm.gz Memoize::Expire.3pm.gz Term::ReadLine.3pm.gz sort.3pm.gz Digest.3pm.gz ExtUtils::Packlist.3pm.gz Memoize::ExpireFile. 3pm.gz Test.3pm.gz strict.3pm.gz Digest::MD5.3pm.gz ExtUtils::ParseXS.3pm.gz Memoize::ExpireTest. 3pm.gz Test::Builder.3pm.gz subs.3pm.gz Digest::base.3pm.gz ExtUtils::testlib.3pm.gz Memoize::NDBM_File. 3pm.gz Test::Builder::Module.3pm.gz threads.3pm.gz Digest::file.3pm.gz Fatal.3pm.gz Memoize::SDBM_File.3pm.gz Test::Builder::Tester.3pm.gz threads::shared.3pm.gz DirHandle.3pm.gz Fcntl.3pm.gz Memoize::Storable.3pm.gz Test::Builder::Tester::Color.3pm.gz utf8.3pm.gz Dumpvalue.3pm.gz File::Basename.3pm.gz Module::CoreList.3pm.gz Test::Harness.3pm.gz vars.3pm.gz DynaLoader.3pm.gz File::CheckTree.3pm.gz Module::Pluggable.3pm.gz Test::Harness::Assert.3pm.gz vmsish.3pm.gz Encode.3pm.gz File::Compare.3pm.gz Module::Pluggable::Object. 3pm.gz Test::Harness::Iterator.3pm.gz warnings.3pm.gz Encode::Alias.3pm.gz File::Copy.3pm.gz NDBM_File.3pm.gz Test::Harness::Point.3pm.gz warnings::register.3pm.gz bash-3.2# port install p5-digest-md5 ---> Fetching p5-digest-md5 ---> Attempting to fetch Digest-MD5-2.38.tar.gz from http://mirrors.ibiblio.org/pub/mirrors/CPAN/modules/by-module/Digest ---> Verifying checksum(s) for p5-digest-md5 ---> Extracting p5-digest-md5 ---> Configuring p5-digest-md5 ---> Building p5-digest-md5 ---> Staging p5-digest-md5 into destroot ---> Installing p5-digest-md5 @2.38_0 ---> Activating p5-digest-md5 @2.38_0 Error: Target org.macports.activate returned: Image error: /opt/local/ share/man/man3/Digest::MD5.3pm.gz is being used by the active perl5.8 port. Please deactivate this port first, or use the -f flag to force the activation. Error: Status 1 encountered during processing. bash-3.2# bash-3.2# port provides /opt/local/man/man3/Digest\:\:MD5.3pm.gz /opt/local/share/man/man3/Digest::MD5.3pm.gz is provided by: perl5.8 bash-3.2# port installed The following ports are currently installed: db47 @4.7.25_1 (active) gdbm @1.8.3_1 (active) p5-datemanip @5.54_0 (active) p5-digest-md5 @2.38_0 perl5.8 @5.8.9_2+db+gdbm+shared+threads (active) bash-3.2# From talklists at newgeo.com Mon Mar 2 13:56:35 2009 From: talklists at newgeo.com (Scott Haneda) Date: Mon, 2 Mar 2009 13:56:35 -0800 Subject: OT: clock drift (was: Re: logging postfix and others) In-Reply-To: References: <6F710CB7-4579-47EB-85E4-35B4254C402D@newgeo.com> Message-ID: On Mar 2, 2009, at 3:21 AM, Ryan Schmidt wrote: > On Mar 1, 2009, at 03:37, Scott Haneda wrote: > >> First thing I do in setting up a new server is comment out the log >> rollers, second is set up a ntpudpate command in launchd to keep >> the clock from drifting. > > I realize this is off-topic now, but you've made me curious. Can the > clock drift if you do not do this? I thought Apple's "set date and > time automatically" option was supposed to ensure clocks were > synchronized. Though I admit I don't know what it does specifically. I see the clock drift massively on my servers, it seems to be the worst when you are using a server that does not login to an account, then apples "set data and time automatically" does not seem to work well. This drift is a killer when you are trying to figure something out in logs that spam multiple machines. I will add this launchd item: ( Sleep 45 seconds to wait for the network to come up, adjust accordingly, ugly hack, but works ) KeepAlive Label com.hostwizard.ntpdate ProgramArguments /bin/sleep 45; /usr/sbin/ntpdate RunAtLoad StartInterval 300 -- Scott * If you contact me off list replace talklists@ with scott@ * From ryandesign at macports.org Mon Mar 2 20:02:04 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 2 Mar 2009 22:02:04 -0600 Subject: perl -f (was apache2 location) In-Reply-To: <73FAE155-D73A-4F80-9301-80CCDACB31F2@pixilla.com> References: <1154B802-5D94-4754-8848-2EF8375E1069@newgeo.com> <594B9628-56C8-4537-865E-5ACFE52B63A9@geeklair.net> <95884C34-693A-4570-8AEA-15C48E4693E8@newgeo.com> <1FE454BE-FE0D-428C-AE09-3F7EE7EB2B3F@macports.org> <074BFD17-3354-4154-B207-0EC3699D4265@newgeo.com> <6A6666FF-3F71-49D7-8697-6A5179C31135@macports.org> <6A169AA1-51FF-4D89-B0BD-9986234EB23F@pixilla.com> <56058CA9-5DED-421E-B423-A6CF019C9749@newgeo.com> <73FAE155-D73A-4F80-9301-80CCDACB31F2@pixilla.com> Message-ID: <481F8185-4309-450F-A4B7-C35359FAB8B8@macports.org> On Mar 2, 2009, at 14:51, Bradley Giesbrecht wrote: > On Mar 1, 2009, at 6:02 PM, Ryan Schmidt wrote: > >> On Mar 1, 2009, at 19:49, Bradley Giesbrecht wrote: >> >>> On Mar 1, 2009, at 3:33 PM, Scott Haneda wrote: >>> >>>> Also, where does MacPorts get the man pages from? Maybe they >>>> should just all be removed, then only the new ones get installed >>>> as you need them when you add in a p5? >>>> >>>> Can I simply rm all the perl man pages, new ones will come in >>>> when I instal something? >>> >>> Unless someone perl wise explains why they need to be there in >>> the first place it's a flaw in the port that put them there. >>> >>> Where do they come from? >> >> I still don't know what files you're talking about. Could you name >> a specific file? > > I uninstalled and reinstalled macports. > Installed perl5.8 and and then p5-digest-md5 to give you an example. > I think the problem may be that perl5.8 installs a lot of modules > but they do not get registered so when a port like imapsync depends > on p5-digest-md5 macports may not know that it's installed already. > Or maybe p5-digest-md5 is not installed but the man page is. > > You will see a lot of perl module man pages in /opt/local/man/man3 > after installing only perl5.8. Ok, that's what I assumed. So everything is functioning exactly as expected. perl5.8 includes some modules. The modules and their manpages are being registered to the perl5.8 port. And then we also have separate ports for some of those modules. Logically you cannot install both at the same time. So, as has been said before, we need to come up with a solution. Either remove the separate module ports, or remove the modules from the perl5.8 port and let the separate module ports handle it, or have the module ports install into a separate directory from where perl5.8 installs the modules and then find some way to educate the perl-using ports to look in both places for modules. I am not a perl expert so I don't know how to solve this, but if someone wants to tackle the issue, please do. From ryandesign at macports.org Mon Mar 2 20:48:22 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 2 Mar 2009 22:48:22 -0600 Subject: xorg-libs / Panther In-Reply-To: References: Message-ID: On Mar 1, 2009, at 11:42, Jeremy Huddleston wrote: > On Mar 1, 2009, at 06:19, Chris Janton wrote: > >> I can't seem to upgrade xorg-libs on my Panther system. 1.7 MacPorts >> >> ---> Building mesa >> Error: Target org.macports.build returned: shell command " cd "/ >> opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_ >> mesa/work/Mesa-7.2" && make default INSTALL_DIR=/opt/local " >> returned error 2 >> Command output: Making sources for darwin >> make[2]: Nothing to be done for `default'. >> (cd drivers && make) >> /bin/sh ../../../../bin/mklib -o OSMesa -linker 'gcc' -ldflags '' \ >> -major 7 -minor 2 -patch 0 \ >> -install ../../../../lib \ >> -id /opt/local/lib/libOSMesa.7.dylib \ >> -L../../../../lib -lGL osmesa.o ../../../../src/mesa/ >> libmesa.a ../../../../src/mesa/libglapi.a >> mklib: Making Darwin shared library: libOSMesa.7.2.dylib >> mklib: Installing libOSMesa.7.2.dylib libOSMesa.7.dylib >> libOSMesa.dylib in ../../../../lib >> make[4]: `../../../lib/libGLU.dylib' is up to date. >> gcc -c -I../../../include -ggdb3 -Os -Wall -Wmissing-prototypes - >> std=c99 -ffast-math -fno-strict-aliasing -fno-common -I/opt/local/ >> include -I/opt/local/include -fPIC -D_DARWIN_C_SOURCE - >> D_POSIX_SOURCE -D_POSIX_C_SOURCE=199309L -D_BSD_SOURCE - >> D_SVID_SOURCE -D_GNU_SOURCE -DPTHREADS -DGLX_ALIAS_UNSUPPORTED - >> DGLX_INDIRECT_RENDERING glut_event.c >> glut_event.c: In function `glutTimerFunc': >> glut_event.c:145: warning: implicit declaration of function >> `gettimeofday' >> glut_event.c: In function `interruptibleXNextEvent': >> glut_event.c:309: error: `fd_set' undeclared (first use in this >> function) >> glut_event.c:309: error: (Each undeclared identifier is reported >> only once >> glut_event.c:309: error: for each function it appears in.) >> glut_event.c:309: error: parse error before "fds" >> glut_event.c:328: warning: implicit declaration of function `FD_ZERO' >> glut_event.c:328: error: `fds' undeclared (first use in this >> function) >> glut_event.c:329: warning: implicit declaration of function `FD_SET' >> glut_event.c:330: warning: implicit declaration of function `select' >> glut_event.c: In function `waitForSomething': >> glut_event.c:868: error: `fd_set' undeclared (first use in this >> function) >> glut_event.c:868: error: parse error before "fds" >> glut_event.c:922: error: `fds' undeclared (first use in this >> function) >> make[2]: *** [glut_event.o] Error 1 >> make[1]: *** [subdirs] Error 1 >> make: *** [default] Error 1 > > I don't have access to Panther, so I have no way of figuring out > the problem, but I welcome a patch. I can at least confirm the problem on my Panther G4. > According to the man page, gettimeofday should be defined by > including sys/time.h. That is included on line 46 of glut_event.c "man gettimeofday" says the same on Panther. I'll see what I can find out. From jmr at macports.org Mon Mar 2 22:10:41 2009 From: jmr at macports.org (Joshua Root) Date: Tue, 03 Mar 2009 17:10:41 +1100 Subject: xorg-libs / Panther In-Reply-To: References: Message-ID: <49ACC9E1.9040608@macports.org> Ryan Schmidt wrote: > > On Mar 1, 2009, at 11:42, Jeremy Huddleston wrote: > >> According to the man page, gettimeofday should be defined by including >> sys/time.h. That is included on line 46 of glut_event.c > > "man gettimeofday" says the same on Panther. I'll see what I can find out. It's only a warning for gettimeofday. The first error is "`fd_set' undeclared". - Josh From ryandesign at macports.org Mon Mar 2 23:52:29 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 3 Mar 2009 01:52:29 -0600 Subject: Updating MySQL In-Reply-To: <44A33974-92A7-42E7-AAF8-0B2AAFE42111@gmail.com> References: <7FD8D81F-E67A-4020-BFAA-DF2D5CE3F1C2@macports.org> <53E931D2-E801-47B8-9FEB-73423CB73A1A@gmail.com> <195E2500-FBF6-4523-8EA2-030EBAB88E0C@macports.org> <44A33974-92A7-42E7-AAF8-0B2AAFE42111@gmail.com> Message-ID: On Mar 3, 2009, at 01:38, Marion Dumas wrote: > No the server is not running and the socket does not exist because > the server is not running. The problem is that I don't have the > right permissions to do anything with the port mysql4. Indeed, I > also tried to deactivate it and get the following: > ---> Deactivating mysql4 > Error: port deactivate failed: error deleting "/opt/local/var/run/ > mysqld/.turd_mysql4": permission denied > So, how do I set the permissions to act on the mysql4 server? MacPorts installs things as root, so to change anything about your installation, including installing new ports or uninstalling old ones, you need to preface your "port" command with "sudo" (which stands for "SuperUser DO"): sudo port uninstall mysql4 When prompted, type the password for your Mac OS X account (which must be an admin account). P.S: Use Reply All so your reply goes to the list too, not just to me. From ryandesign at macports.org Tue Mar 3 00:41:08 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 3 Mar 2009 02:41:08 -0600 Subject: xorg-libs / Panther In-Reply-To: <49ACC9E1.9040608@macports.org> References: <49ACC9E1.9040608@macports.org> Message-ID: <71AE9FB1-DCC6-4CA5-82C5-B24D5C27301B@macports.org> On Mar 3, 2009, at 00:10, Joshua Root wrote: > Ryan Schmidt wrote: > >> On Mar 1, 2009, at 11:42, Jeremy Huddleston wrote: >> >>> According to the man page, gettimeofday should be defined by >>> including >>> sys/time.h. That is included on line 46 of glut_event.c >> >> "man gettimeofday" says the same on Panther. I'll see what I can >> find out. > > It's only a warning for gettimeofday. The first error is "`fd_set' > undeclared". glut_event.c:309: error: `fd_set' undeclared (first use in this function) However fd_set is defined in sys/types.h which is included on line 39 of glut_event.c. I don't know what to make of it. From brad at pixilla.com Tue Mar 3 07:30:18 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Tue, 3 Mar 2009 07:30:18 -0800 Subject: Perl error, once and for all In-Reply-To: <20090302011113.GA23645@prunille.vinc17.org> References: <1DD62C2A-5E85-4481-9246-96FE34E4CF50@newgeo.com> <20090226055133.GE27410@darkart.com> <29A68AD6-F99A-48A2-B050-69A08EA349A8@newgeo.com> <68BBA4C9-23A4-414D-AFED-BC996C061CD9@macports.org> <707C94E4-9868-4B39-BF42-E0D003BA6DBA@macports.org> <20090301025356.GB4629@prunille.vinc17.org> <20090302001841.GD4629@prunille.vinc17.org> <20090302011113.GA23645@prunille.vinc17.org> Message-ID: On Mar 1, 2009, at 5:11 PM, Vincent Lefevre wrote: > On 2009-03-02 01:18:41 +0100, Vincent Lefevre wrote: >> Yes, but MacPorts should not override the user's settings (i.e. it >> should test whether PERL5LIB is already set...). One should end up >> with something like: >> >> if [ -n "$PERL5LIB" ]; then >> PERL5LIB="${PERL5LIB}:/opt/local/lib/perl5/vendor_perl" >> else >> export PERL5LIB >> PERL5LIB="/opt/local/lib/perl5/vendor_perl" >> fi My path to p5's looks like this: /opt/local/lib/perl5/vendor_perl/5.8.9/ Wouldn't the full path including the version dir need to be added to PERL5LIB? Are you suggesting using this in Portfiles? If so I guess we would need to test for which version of perl is active and then set the path. Could a macports perl5 port group do that? If I have perl5.8 active and install a p5 and then deactivate perl5.8 and activate perl5.10 should I expect my p5 to be active and functional? //Brad From vincent-opdarw at vinc17.org Tue Mar 3 07:55:28 2009 From: vincent-opdarw at vinc17.org (Vincent Lefevre) Date: Tue, 3 Mar 2009 16:55:28 +0100 Subject: Perl error, once and for all In-Reply-To: References: <29A68AD6-F99A-48A2-B050-69A08EA349A8@newgeo.com> <68BBA4C9-23A4-414D-AFED-BC996C061CD9@macports.org> <707C94E4-9868-4B39-BF42-E0D003BA6DBA@macports.org> <20090301025356.GB4629@prunille.vinc17.org> <20090302001841.GD4629@prunille.vinc17.org> <20090302011113.GA23645@prunille.vinc17.org> Message-ID: <20090303155528.GS27518@prunille.vinc17.org> On 2009-03-03 07:30:18 -0800, Bradley Giesbrecht wrote: > On Mar 1, 2009, at 5:11 PM, Vincent Lefevre wrote: >>> if [ -n "$PERL5LIB" ]; then >>> PERL5LIB="${PERL5LIB}:/opt/local/lib/perl5/vendor_perl" >>> else >>> export PERL5LIB >>> PERL5LIB="/opt/local/lib/perl5/vendor_perl" >>> fi > > My path to p5's looks like this: > /opt/local/lib/perl5/vendor_perl/5.8.9/ > > Wouldn't the full path including the version dir need to be added to > PERL5LIB? I don't know whether this has changed in Perl 5.8.9 (I haven't upgraded yet), but with previous versions, the version dir should not be used in $PERL5LIB, as perl automatically adds the paths so that modules installed with previous versions can still be used. For instance: $ perl -V [...] %ENV: PERL5LIB="/Users/vinc17/lib/site_perl:/opt/local/lib/perl5/vendor_perl" @INC: /Users/vinc17/lib/site_perl/darwin-2level /Users/vinc17/lib/site_perl /opt/local/lib/perl5/vendor_perl/5.8.8/darwin-2level /opt/local/lib/perl5/vendor_perl/5.8.8 /opt/local/lib/perl5/vendor_perl/5.8.7/darwin-2level /opt/local/lib/perl5/vendor_perl/5.8.7 /opt/local/lib/perl5/vendor_perl /opt/local/lib/perl5/5.8.8/darwin-2level /opt/local/lib/perl5/5.8.8 /opt/local/lib/perl5/site_perl/5.8.8/darwin-2level /opt/local/lib/perl5/site_perl/5.8.8 /opt/local/lib/perl5/site_perl/5.8.7/darwin-2level /opt/local/lib/perl5/site_perl/5.8.7 /opt/local/lib/perl5/site_perl /opt/local/lib/perl5/vendor_perl/5.8.8/darwin-2level /opt/local/lib/perl5/vendor_perl/5.8.8 /opt/local/lib/perl5/vendor_perl/5.8.7/darwin-2level /opt/local/lib/perl5/vendor_perl/5.8.7 /opt/local/lib/perl5/vendor_perl . > Are you suggesting using this in Portfiles? Either the Portfile could provide the necessary options (I don't know which ones) to change the default @INC in the perl binary (with the advantage that modifying the environment variable won't be necessary) or the PERL5LIB variable needs to be changed in the .profile (either by MacPorts (base?) or by the user). > If I have perl5.8 active and install a p5 and then deactivate perl5.8 > and activate perl5.10 should I expect my p5 to be active and functional? I haven't tried. See the "perl -V" output without the version number in $PERL5LIB. -- Vincent Lef?vre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon) From brad at pixilla.com Tue Mar 3 11:49:12 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Tue, 3 Mar 2009 11:49:12 -0800 Subject: Perl error, once and for all In-Reply-To: <20090303155528.GS27518@prunille.vinc17.org> References: <29A68AD6-F99A-48A2-B050-69A08EA349A8@newgeo.com> <68BBA4C9-23A4-414D-AFED-BC996C061CD9@macports.org> <707C94E4-9868-4B39-BF42-E0D003BA6DBA@macports.org> <20090301025356.GB4629@prunille.vinc17.org> <20090302001841.GD4629@prunille.vinc17.org> <20090302011113.GA23645@prunille.vinc17.org> <20090303155528.GS27518@prunille.vinc17.org> Message-ID: <3A3DD996-D961-4291-AE81-63DF66327429@pixilla.com> On Mar 3, 2009, at 7:55 AM, Vincent Lefevre wrote: > On 2009-03-03 07:30:18 -0800, Bradley Giesbrecht wrote: >> On Mar 1, 2009, at 5:11 PM, Vincent Lefevre wrote: >>>> if [ -n "$PERL5LIB" ]; then >>>> PERL5LIB="${PERL5LIB}:/opt/local/lib/perl5/vendor_perl" >>>> else >>>> export PERL5LIB >>>> PERL5LIB="/opt/local/lib/perl5/vendor_perl" >>>> fi >> >> My path to p5's looks like this: >> /opt/local/lib/perl5/vendor_perl/5.8.9/ >> >> Wouldn't the full path including the version dir need to be added to >> PERL5LIB? > > I don't know whether this has changed in Perl 5.8.9 (I haven't > upgraded yet), but with previous versions, the version dir should > not be used in $PERL5LIB, as perl automatically adds the paths so > that modules installed with previous versions can still be used. > For instance: > > $ perl -V > [...] > %ENV: > PERL5LIB="/Users/vinc17/lib/site_perl:/opt/local/lib/perl5/ > vendor_perl" > @INC: > /Users/vinc17/lib/site_perl/darwin-2level > /Users/vinc17/lib/site_perl > /opt/local/lib/perl5/vendor_perl/5.8.8/darwin-2level > /opt/local/lib/perl5/vendor_perl/5.8.8 > /opt/local/lib/perl5/vendor_perl/5.8.7/darwin-2level > /opt/local/lib/perl5/vendor_perl/5.8.7 > /opt/local/lib/perl5/vendor_perl > /opt/local/lib/perl5/5.8.8/darwin-2level > /opt/local/lib/perl5/5.8.8 > /opt/local/lib/perl5/site_perl/5.8.8/darwin-2level > /opt/local/lib/perl5/site_perl/5.8.8 > /opt/local/lib/perl5/site_perl/5.8.7/darwin-2level > /opt/local/lib/perl5/site_perl/5.8.7 > /opt/local/lib/perl5/site_perl > /opt/local/lib/perl5/vendor_perl/5.8.8/darwin-2level > /opt/local/lib/perl5/vendor_perl/5.8.8 > /opt/local/lib/perl5/vendor_perl/5.8.7/darwin-2level > /opt/local/lib/perl5/vendor_perl/5.8.7 > /opt/local/lib/perl5/vendor_perl # export Adding export PERL5LIB=/opt/local/lib/perl5/vendor_perl @INC: /opt/local/lib/perl5/vendor_perl/5.8.9/darwin-thread-multi-2level /opt/local/lib/perl5/vendor_perl/5.8.9 /opt/local/lib/perl5/vendor_perl /opt/local/lib/perl5/5.8.9/darwin-thread-multi-2level /opt/local/lib/perl5/5.8.9 /opt/local/lib/perl5/site_perl/5.8.9/darwin-thread-multi-2level /opt/local/lib/perl5/site_perl/5.8.9 /opt/local/lib/perl5/site_perl /opt/local/lib/perl5/vendor_perl/5.8.9/darwin-thread-multi-2level /opt/local/lib/perl5/vendor_perl/5.8.9 /opt/local/lib/perl5/vendor_perl . I don't have site_perl on my system so I'll assume that's something you added in one way or another. >> Are you suggesting using this in Portfiles? > > Either the Portfile could provide the necessary options (I don't know > which ones) to change the default @INC in the perl binary (with the > advantage that modifying the environment variable won't be necessary) > or the PERL5LIB variable needs to be changed in the .profile (either > by MacPorts (base?) or by the user). It would be nice to not have to change .profile. If a system has multiple users or a user is added later this would be one more thing that would need to be done. Maybe we could add a port "macports-profile" that would be a script similar to: /opt/local/share/macports/setupenv.bash with the addition of checking for perl5 activation among others. And then instead making a many alterations to a users .profile we would just add one: . /opt/local/sbin/macports_profile The macports_profile script would always append it's vars to the front of existing vars so if PERL5LIB is already set in the users .profile it would be maintained the the macports paths prepended. I suppose the file /opt/local/etc/maports_profile.conf could be looked for and if found could be parsed for overrides and additions. Then if a new user is added they could run /opt/local/sbin/ macports_profile which would check the users .profile file and add the source line if it's missing. This is just an idea, the names and locations of the files might not be great. Heck, the whole idea might be flawed. >> If I have perl5.8 active and install a p5 and then deactivate perl5.8 >> and activate perl5.10 should I expect my p5 to be active and >> functional? > > I haven't tried. See the "perl -V" output without the version number > in $PERL5LIB. Works. I have a macports on my laptop that I'm keeping clean just to help resolve this perl5 issue. I hope we can come up with a work solution soon. Even if it's just the decision to instruct users to add PERL5LIB to their .profile by hand. Oh, and what about other shells? Let that small base work it out themselves as they are probably used to doing? //Brad From brad at pixilla.com Tue Mar 3 11:53:29 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Tue, 3 Mar 2009 11:53:29 -0800 Subject: apache2 location In-Reply-To: References: <1154B802-5D94-4754-8848-2EF8375E1069@newgeo.com> <594B9628-56C8-4537-865E-5ACFE52B63A9@geeklair.net> <95884C34-693A-4570-8AEA-15C48E4693E8@newgeo.com> <1FE454BE-FE0D-428C-AE09-3F7EE7EB2B3F@macports.org> <074BFD17-3354-4154-B207-0EC3699D4265@newgeo.com> <6A6666FF-3F71-49D7-8697-6A5179C31135@macports.org> <6A169AA1-51FF-4D89-B0BD-9986234EB23F@pixilla.com> <56058CA9-5DED-421E-B423-A6CF019C9749@newgeo.com> Message-ID: <2442C182-8767-47EB-83AA-6891950A324B@pixilla.com> On Mar 1, 2009, at 6:02 PM, Ryan Schmidt wrote: > -f applies to the whole chain of dependencies. Thanks. I didn't know that. > Yes, you did. -f applies to everything. You most likely never want > to use -f without also using -n (non-recursive). That's nice to know and the first time I recall it mentioned. Then -f -n it is. Maybe it should be -f -R if you want recursive. //Brad From raimue at macports.org Tue Mar 3 11:58:08 2009 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Tue, 03 Mar 2009 20:58:08 +0100 Subject: apache2 location In-Reply-To: <2442C182-8767-47EB-83AA-6891950A324B@pixilla.com> References: <1154B802-5D94-4754-8848-2EF8375E1069@newgeo.com> <594B9628-56C8-4537-865E-5ACFE52B63A9@geeklair.net> <95884C34-693A-4570-8AEA-15C48E4693E8@newgeo.com> <1FE454BE-FE0D-428C-AE09-3F7EE7EB2B3F@macports.org> <074BFD17-3354-4154-B207-0EC3699D4265@newgeo.com> <6A6666FF-3F71-49D7-8697-6A5179C31135@macports.org> <6A169AA1-51FF-4D89-B0BD-9986234EB23F@pixilla.com> <56058CA9-5DED-421E-B423-A6CF019C9749@newgeo.com> <2442C182-8767-47EB-83AA-6891950A324B@pixilla.com> Message-ID: <49AD8BD0.5070503@macports.org> Bradley Giesbrecht wrote: >> Yes, you did. -f applies to everything. You most likely never want >> to use -f without also using -n (non-recursive). > > That's nice to know and the first time I recall it mentioned. > Then -f -n it is. > > Maybe it should be -f -R if you want recursive. There is already -R, which is recursing dependents. Rainer From brad at pixilla.com Tue Mar 3 12:51:40 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Tue, 3 Mar 2009 12:51:40 -0800 Subject: apache2 location In-Reply-To: <49AD8BD0.5070503@macports.org> References: <1154B802-5D94-4754-8848-2EF8375E1069@newgeo.com> <594B9628-56C8-4537-865E-5ACFE52B63A9@geeklair.net> <95884C34-693A-4570-8AEA-15C48E4693E8@newgeo.com> <1FE454BE-FE0D-428C-AE09-3F7EE7EB2B3F@macports.org> <074BFD17-3354-4154-B207-0EC3699D4265@newgeo.com> <6A6666FF-3F71-49D7-8697-6A5179C31135@macports.org> <6A169AA1-51FF-4D89-B0BD-9986234EB23F@pixilla.com> <56058CA9-5DED-421E-B423-A6CF019C9749@newgeo.com> <2442C182-8767-47EB-83AA-6891950A324B@pixilla.com> <49AD8BD0.5070503@macports.org> Message-ID: On Mar 3, 2009, at 11:58 AM, Rainer M?ller wrote: > Bradley Giesbrecht wrote: >>> Yes, you did. -f applies to everything. You most likely never want >>> to use -f without also using -n (non-recursive). >> >> That's nice to know and the first time I recall it mentioned. >> Then -f -n it is. >> >> Maybe it should be -f -R if you want recursive. > > There is already -R, which is recursing dependents. So with -f and without -n or -R what happens? Recursion just for the target port? //Brad From raimue at macports.org Tue Mar 3 12:59:29 2009 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Tue, 03 Mar 2009 21:59:29 +0100 Subject: apache2 location In-Reply-To: References: <1154B802-5D94-4754-8848-2EF8375E1069@newgeo.com> <594B9628-56C8-4537-865E-5ACFE52B63A9@geeklair.net> <95884C34-693A-4570-8AEA-15C48E4693E8@newgeo.com> <1FE454BE-FE0D-428C-AE09-3F7EE7EB2B3F@macports.org> <074BFD17-3354-4154-B207-0EC3699D4265@newgeo.com> <6A6666FF-3F71-49D7-8697-6A5179C31135@macports.org> <6A169AA1-51FF-4D89-B0BD-9986234EB23F@pixilla.com> <56058CA9-5DED-421E-B423-A6CF019C9749@newgeo.com> <2442C182-8767-47EB-83AA-6891950A324B@pixilla.com> <49AD8BD0.5070503@macports.org> Message-ID: <49AD9A31.9050609@macports.org> Bradley Giesbrecht wrote: >>> Maybe it should be -f -R if you want recursive. >> There is already -R, which is recursing dependents. > > So with -f and without -n or -R what happens? > > Recursion just for the target port? 'port -R upgrade' will rebuild all dependents after the given port has been upgraded. 'port upgrade' should default to recursing dependencies, as this is usually the behavior the user wants. The problem is that 'port -f upgrade' would force a rebuild of all dependencies, even if they are not outdated. So usually you want to use 'port -fn upgrade' to avoid that and upgrade only the given ports. The option -f is global and therefore used for all dependencies and phases. Rainer From deliverable at gmail.com Tue Mar 3 14:45:16 2009 From: deliverable at gmail.com (Alexy Khrabrov) Date: Tue, 3 Mar 2009 17:45:16 -0500 Subject: Why ar doesn't call ranlib on Mac? Message-ID: <6E56105F-260A-4CC7-AF11-05E366589191@gmail.com> In building various Linux things from source on Mac, I've run into the "archive has no table of contents" problem several times. The fix is invariably to go and stick ranlib after each ar. Now I wonder, why don't we replace /usr/bin/ar with a wrapper calling the ar and then ranlib if it's an ar c? No more stupid ranlib peppering then! And what's wrong with Macs anyways? Why do we have to do it where Linux folks are happy without it? Cheers, Alexy From asimmons at rosettastone.com Tue Mar 3 15:32:17 2009 From: asimmons at rosettastone.com (Simmons, Aaron) Date: Tue, 3 Mar 2009 18:32:17 -0500 Subject: pidgin and skype with macports? Message-ID: <1002A5962B6C7B47AE2BC503549E29A80206E625@RSHBGEXVS1.rosettastone.local> Has anyone tried using macports pidgin with the skype plugin ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From raimue at macports.org Tue Mar 3 17:29:18 2009 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Wed, 04 Mar 2009 02:29:18 +0100 Subject: Why ar doesn't call ranlib on Mac? In-Reply-To: <6E56105F-260A-4CC7-AF11-05E366589191@gmail.com> References: <6E56105F-260A-4CC7-AF11-05E366589191@gmail.com> Message-ID: <49ADD96E.9090604@macports.org> Alexy Khrabrov wrote: > In building various Linux things from source on Mac, I've run into the > "archive has no table of contents" problem several times. The fix is > invariably to go and stick ranlib after each ar. > > Now I wonder, why don't we replace /usr/bin/ar with a wrapper calling > the ar and then ranlib if it's an ar c? No more stupid ranlib > peppering then! Make a patch which adds a 's' to the ar arguments and ask upstream to apply it. Running 'ar s' is equivalent to ranlib. Common usage is: ar rcs libfoo.a $LIBS > And what's wrong with Macs anyways? Why do we have to do it where > Linux folks are happy without it? Mac OS X is based on BSD, not GNU/Linux. Welcome to the UNIX world! Rainer From carpediem163163 at gmail.com Tue Mar 3 17:53:22 2009 From: carpediem163163 at gmail.com (Carpe Diem) Date: Tue, 3 Mar 2009 17:53:22 -0800 Subject: Install Zend Optimizer In-Reply-To: References: Message-ID: Hello I installed php and mysql with MacPort. I downloaded Zend Optimizer for Mac OSX and installed them. According phpinfo, I think zend optimizer installed correctly but it didnt work. Should I install linux package not Mac OSX package? http://www.zend.com/en/products/guard/downloads Thank you, Hiromi -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Tue Mar 3 23:54:35 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 4 Mar 2009 01:54:35 -0600 Subject: Install Zend Optimizer In-Reply-To: References: Message-ID: <3D06D00E-40A4-4960-AC3B-D5F3F7DCA7B3@macports.org> On Mar 3, 2009, at 19:53, Carpe Diem wrote: > I installed php and mysql with MacPort. > I downloaded Zend Optimizer for Mac OSX and installed them. > According phpinfo, I think zend optimizer installed correctly but > it didnt work. > Should I install linux package not Mac OSX package? > http://www.zend.com/en/products/guard/downloads Probably not. What output in phpinfo() makes you think it's installed correctly? What did you add to your php.ini to enable it? How do you know that it's not working now? I haven't tried to use Zend Optimizer before so I'm not sure what to look for here. From bentley at crenelle.com Wed Mar 4 00:36:18 2009 From: bentley at crenelle.com (Michael Brian Bentley) Date: Wed, 4 Mar 2009 00:36:18 -0800 Subject: cmake 2.6.2: _FILE_OFFSET_BITS=64/uClibc built w/o large file support Message-ID: Hi! I'm having a moment of trouble building cmake 2.6.2 with the current MacPort. I'm on Mac OS X 10.5.6. It is complaining that _FILE_OFFSET_BITS=64, but uClibc was built without large file support enabled. I looked around but apparently haven't found the obvious toggle switch. bentley-MBP-OSX:~ bentley$ sudo port install cmake ---> Fetching cmake ---> Verifying checksum(s) for cmake ---> Extracting cmake ---> Configuring cmake ---> Building cmake Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_cmake/work/cmake-2.6.2" && make all " returned error 2 Command output: [ 57%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmComputeLinkDepends.o [ 57%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmComputeLinkInformation.o [ 58%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmComputeTargetDepends.o [ 58%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmCustomCommand.o [ 58%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmDepends.o [ 59%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmDependsC.o [ 59%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmDependsFortran.o [ 59%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmDependsFortranLexer.o [ 60%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmDependsFortranParser.o [ 60%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmDependsJava.o [ 60%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmDependsJavaLexer.o [ 61%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmDependsJavaParser.o [ 61%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmDependsJavaParserHelper.o [ 61%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmDocumentation.o [ 62%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmDocumentationFormatter.o [ 62%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmDocumentationFormatterHTML.o [ 62%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmDocumentationFormatterDocbook.o [ 63%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmDocumentationFormatterMan.o [ 63%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmDocumentationFormatterText.o [ 63%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmDocumentationFormatterUsage.o [ 63%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmDocumentationSection.o [ 64%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmDocumentVariables.o [ 64%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmDynamicLoader.o [ 64%] Building CXX object Source/CMakeFiles/CMakeLib.dir/cmELF.o In file included from /usr/include/elf.h:23, from /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_cmake/work/cmake-2.6.2/Source/cmELF.cxx:27: /usr/include/features.h:348:2: error: #error It appears you have defined _FILE_OFFSET_BITS=64. Unfortunately, uClibc was built without large file support enabled. make[2]: *** [Source/CMakeFiles/CMakeLib.dir/cmELF.o] Error 1 make[1]: *** [Source/CMakeFiles/CMakeLib.dir/all] Error 2 make: *** [all] Error 2 From talklists at newgeo.com Wed Mar 4 04:21:45 2009 From: talklists at newgeo.com (Scott Haneda) Date: Wed, 4 Mar 2009 04:21:45 -0800 Subject: adduser, addgroup Message-ID: <89E1C0AC-4C49-4DE3-B682-61ABBADED3DD@newgeo.com> Hello, I am not sure how big a problem this is, but it appears, the adduser and addgroup functions in MacPorts do not clean up after themselves in the even of some port install error. Is this expected behavior? -- Scott * If you contact me off list replace talklists@ with scott@ * From ryandesign at macports.org Wed Mar 4 05:45:03 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 4 Mar 2009 07:45:03 -0600 Subject: Quartz features now optional in cairo and pango Message-ID: <1A847B0B-FD17-4E0C-99B7-AFF20F1EEC79@macports.org> I just committed an update to the cairo and pango ports that make the Quartz features optional. Previously, they were always enabled. If you relied on Quartz features being available in cairo and pango, be sure to install both ports with the +quartz variant from now on. You may want to edit your variants.conf file and add +quartz to it so that this is automatically taken care of when you upgrade your ports. From ryandesign at macports.org Wed Mar 4 05:45:46 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 4 Mar 2009 07:45:46 -0600 Subject: adduser, addgroup In-Reply-To: <89E1C0AC-4C49-4DE3-B682-61ABBADED3DD@newgeo.com> References: <89E1C0AC-4C49-4DE3-B682-61ABBADED3DD@newgeo.com> Message-ID: <22E01BA5-8CD6-4F20-B316-6B5123368370@macports.org> On Mar 4, 2009, at 06:21, Scott Haneda wrote: > Hello, I am not sure how big a problem this is, but it appears, the > adduser and addgroup functions in MacPorts do not clean up after > themselves in the even of some port install error. > > Is this expected behavior? I'm not sure. What do you mean by "do not clean up after themselves"? From peter at pogma.com Wed Mar 4 07:18:31 2009 From: peter at pogma.com (Peter O'Gorman) Date: Wed, 04 Mar 2009 09:18:31 -0600 Subject: Why ar doesn't call ranlib on Mac? In-Reply-To: <6E56105F-260A-4CC7-AF11-05E366589191@gmail.com> References: <6E56105F-260A-4CC7-AF11-05E366589191@gmail.com> Message-ID: <49AE9BC7.3060006@pogma.com> Alexy Khrabrov wrote: > In building various Linux things from source on Mac, I've run into the > "archive has no table of contents" problem several times. The fix is > invariably to go and stick ranlib after each ar. What version of Mac OS X/Xcode are you using? ar, since Mac OS X 10.4 does ranlib the archive. I filed a bug at the time asking for the -S flag to turn off this behavior to speed up creating an archive incrementally. http://www.opensource.apple.com/darwinsource/10.5.6/cctools-667.3/ar/ar.c Peter -- Peter O'Gorman http://pogma.com From jmr at macports.org Wed Mar 4 07:38:32 2009 From: jmr at macports.org (Joshua Root) Date: Thu, 05 Mar 2009 02:38:32 +1100 Subject: Why ar doesn't call ranlib on Mac? In-Reply-To: <49AE9BC7.3060006@pogma.com> References: <6E56105F-260A-4CC7-AF11-05E366589191@gmail.com> <49AE9BC7.3060006@pogma.com> Message-ID: <49AEA078.4000008@macports.org> Peter O'Gorman wrote: > Alexy Khrabrov wrote: >> In building various Linux things from source on Mac, I've run into the >> "archive has no table of contents" problem several times. The fix is >> invariably to go and stick ranlib after each ar. > > What version of Mac OS X/Xcode are you using? ar, since Mac OS X 10.4 > does ranlib the archive. I filed a bug at the time asking for the -S > flag to turn off this behavior to speed up creating an archive > incrementally. > > http://www.opensource.apple.com/darwinsource/10.5.6/cctools-667.3/ar/ar.c Apparently the issue crops up not only on Panther but also when building universal, see for example . - Josh From peter at pogma.com Wed Mar 4 07:54:08 2009 From: peter at pogma.com (Peter O'Gorman) Date: Wed, 04 Mar 2009 09:54:08 -0600 Subject: Why ar doesn't call ranlib on Mac? In-Reply-To: <49AEA078.4000008@macports.org> References: <6E56105F-260A-4CC7-AF11-05E366589191@gmail.com> <49AE9BC7.3060006@pogma.com> <49AEA078.4000008@macports.org> Message-ID: <49AEA420.7070900@pogma.com> Joshua Root wrote: > Peter O'Gorman wrote: >> Alexy Khrabrov wrote: >>> In building various Linux things from source on Mac, I've run into the >>> "archive has no table of contents" problem several times. The fix is >>> invariably to go and stick ranlib after each ar. >> What version of Mac OS X/Xcode are you using? ar, since Mac OS X 10.4 >> does ranlib the archive. I filed a bug at the time asking for the -S >> flag to turn off this behavior to speed up creating an archive >> incrementally. >> >> http://www.opensource.apple.com/darwinsource/10.5.6/cctools-667.3/ar/ar.c > > Apparently the issue crops up not only on Panther but also when building > universal, see for example . Yes, the default is to run `ranlib -q' unless ar got the 's' flag. This seems reasonable to me, as operating on fat ranlibbed archives is painful, as `ar x' for example, no longer works. Peter -- Peter O'Gorman http://pogma.com From deliverable at gmail.com Wed Mar 4 09:41:08 2009 From: deliverable at gmail.com (Alexy Khrabrov) Date: Wed, 4 Mar 2009 12:41:08 -0500 Subject: Why ar doesn't call ranlib on Mac? In-Reply-To: <49AEA078.4000008@macports.org> References: <6E56105F-260A-4CC7-AF11-05E366589191@gmail.com> <49AE9BC7.3060006@pogma.com> <49AEA078.4000008@macports.org> Message-ID: I'm on Intel Leopard 10.5.6 and my xcode is 312_2621, gcc build 5490. The ar I have us from July 9 2008, size 64448 bytes. I've upgraded from gcc build 5488 yesterday to see if the most recent xcode off ADC has a different ar, but it didn't look like it. Peter -- is the new ar supposed to be in xcode.dmg, or you get it via other means? Cheers, Alexy On Mar 4, 2009, at 10:38 AM, Joshua Root wrote: > Peter O'Gorman wrote: ... >> http://www.opensource.apple.com/darwinsource/10.5.6/cctools-667.3/ar/ar.c ... > Apparently the issue crops up not only on Panther but also when > building > universal, see for example . > > - Josh From talklists at newgeo.com Wed Mar 4 13:48:47 2009 From: talklists at newgeo.com (Scott Haneda) Date: Wed, 4 Mar 2009 13:48:47 -0800 Subject: adduser, addgroup In-Reply-To: <22E01BA5-8CD6-4F20-B316-6B5123368370@macports.org> References: <89E1C0AC-4C49-4DE3-B682-61ABBADED3DD@newgeo.com> <22E01BA5-8CD6-4F20-B316-6B5123368370@macports.org> Message-ID: <74E68B2C-2241-49C7-8A3E-3C82CFD3E658@newgeo.com> On Mar 4, 2009, at 5:45 AM, Ryan Schmidt wrote: > On Mar 4, 2009, at 06:21, Scott Haneda wrote: > >> Hello, I am not sure how big a problem this is, but it appears, the >> adduser and addgroup functions in MacPorts do not clean up after >> themselves in the even of some port install error. >> >> Is this expected behavior? > > I'm not sure. What do you mean by "do not clean up after themselves"? As far as I am finding, on error, the user and group are still there, I will also check of on uninstall, the user and group get removed. Though that may not be the right thing to do is files are left around. -- Scott * If you contact me off list replace talklists@ with scott@ * From jmr at macports.org Wed Mar 4 14:01:03 2009 From: jmr at macports.org (Joshua Root) Date: Thu, 05 Mar 2009 09:01:03 +1100 Subject: adduser, addgroup In-Reply-To: <74E68B2C-2241-49C7-8A3E-3C82CFD3E658@newgeo.com> References: <89E1C0AC-4C49-4DE3-B682-61ABBADED3DD@newgeo.com> <22E01BA5-8CD6-4F20-B316-6B5123368370@macports.org> <74E68B2C-2241-49C7-8A3E-3C82CFD3E658@newgeo.com> Message-ID: <49AEFA1F.2040608@macports.org> Scott Haneda wrote: > On Mar 4, 2009, at 5:45 AM, Ryan Schmidt wrote: >> On Mar 4, 2009, at 06:21, Scott Haneda wrote: >> >>> Hello, I am not sure how big a problem this is, but it appears, the >>> adduser and addgroup functions in MacPorts do not clean up after >>> themselves in the even of some port install error. >>> >>> Is this expected behavior? >> >> I'm not sure. What do you mean by "do not clean up after themselves"? > > As far as I am finding, on error, the user and group are still there, I > will also check of on uninstall, the user and group get removed. They don't. - Josh From talklists at newgeo.com Wed Mar 4 14:12:04 2009 From: talklists at newgeo.com (Scott Haneda) Date: Wed, 4 Mar 2009 14:12:04 -0800 Subject: adduser, addgroup In-Reply-To: <49AEFA1F.2040608@macports.org> References: <89E1C0AC-4C49-4DE3-B682-61ABBADED3DD@newgeo.com> <22E01BA5-8CD6-4F20-B316-6B5123368370@macports.org> <74E68B2C-2241-49C7-8A3E-3C82CFD3E658@newgeo.com> <49AEFA1F.2040608@macports.org> Message-ID: <9ED6CED5-A4D0-4772-808A-CFF8162230DC@newgeo.com> On Mar 4, 2009, at 2:01 PM, Joshua Root wrote: > Scott Haneda wrote: >> On Mar 4, 2009, at 5:45 AM, Ryan Schmidt wrote: >>> On Mar 4, 2009, at 06:21, Scott Haneda wrote: >>> >>>> Hello, I am not sure how big a problem this is, but it appears, the >>>> adduser and addgroup functions in MacPorts do not clean up after >>>> themselves in the even of some port install error. >>>> >>>> Is this expected behavior? >>> >>> I'm not sure. What do you mean by "do not clean up after >>> themselves"? >> >> As far as I am finding, on error, the user and group are still >> there, I >> will also check of on uninstall, the user and group get removed. > > They don't. Was this a design decision, or something overlooked? Should it be considered a bug, or intended behavior? -- Scott * If you contact me off list replace talklists@ with scott@ * From brad at pixilla.com Wed Mar 4 14:13:39 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Wed, 4 Mar 2009 14:13:39 -0800 Subject: adduser, addgroup In-Reply-To: <74E68B2C-2241-49C7-8A3E-3C82CFD3E658@newgeo.com> References: <89E1C0AC-4C49-4DE3-B682-61ABBADED3DD@newgeo.com> <22E01BA5-8CD6-4F20-B316-6B5123368370@macports.org> <74E68B2C-2241-49C7-8A3E-3C82CFD3E658@newgeo.com> Message-ID: <986E8FC2-3105-4A19-8771-6F212F8E30BB@pixilla.com> On Mar 4, 2009, at 1:48 PM, Scott Haneda wrote: > On Mar 4, 2009, at 5:45 AM, Ryan Schmidt wrote: >> On Mar 4, 2009, at 06:21, Scott Haneda wrote: >> >>> Hello, I am not sure how big a problem this is, but it appears, >>> the adduser and addgroup functions in MacPorts do not clean up >>> after themselves in the even of some port install error. >>> >>> Is this expected behavior? >> >> I'm not sure. What do you mean by "do not clean up after themselves"? > > As far as I am finding, on error, the user and group are still > there, I will also check of on uninstall, the user and group get > removed. Though that may not be the right thing to do is files are > left around. I don't recall many programs that do remove users when they are uninstalled. It's a good questions though. Please share the answer when you find out. Do you know if you can specify a uid and gid in a Portfile? And is there an accessible var holding uid and gid? Using the port commands to create them that is. //Brad From talklists at newgeo.com Wed Mar 4 14:16:11 2009 From: talklists at newgeo.com (Scott Haneda) Date: Wed, 4 Mar 2009 14:16:11 -0800 Subject: adduser, addgroup In-Reply-To: <986E8FC2-3105-4A19-8771-6F212F8E30BB@pixilla.com> References: <89E1C0AC-4C49-4DE3-B682-61ABBADED3DD@newgeo.com> <22E01BA5-8CD6-4F20-B316-6B5123368370@macports.org> <74E68B2C-2241-49C7-8A3E-3C82CFD3E658@newgeo.com> <986E8FC2-3105-4A19-8771-6F212F8E30BB@pixilla.com> Message-ID: On Mar 4, 2009, at 2:13 PM, Bradley Giesbrecht wrote: > Do you know if you can specify a uid and gid in a Portfile? > And is there an accessible var holding uid and gid? Using the port > commands to create them that is. I believe so: set gid [existsgroup foo] adduser foo gid=${gid} realname=foo home=${prefix}/var/foo -- Scott * If you contact me off list replace talklists@ with scott@ * From brad at pixilla.com Wed Mar 4 14:19:22 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Wed, 4 Mar 2009 14:19:22 -0800 Subject: adduser, addgroup In-Reply-To: References: <89E1C0AC-4C49-4DE3-B682-61ABBADED3DD@newgeo.com> <22E01BA5-8CD6-4F20-B316-6B5123368370@macports.org> <74E68B2C-2241-49C7-8A3E-3C82CFD3E658@newgeo.com> <986E8FC2-3105-4A19-8771-6F212F8E30BB@pixilla.com> Message-ID: On Mar 4, 2009, at 2:16 PM, Scott Haneda wrote: > On Mar 4, 2009, at 2:13 PM, Bradley Giesbrecht wrote: > >> Do you know if you can specify a uid and gid in a Portfile? >> And is there an accessible var holding uid and gid? Using the port >> commands to create them that is. > > > I believe so: > set gid [existsgroup foo] > adduser foo gid=${gid} realname=foo home=${prefix}/var/foo > -- > Scott * If you contact me off list replace talklists@ with scott@ * Thanks. //Brad From jeremyhu at macports.org Wed Mar 4 14:25:36 2009 From: jeremyhu at macports.org (Jeremy Huddleston) Date: Wed, 4 Mar 2009 14:25:36 -0800 Subject: xorg-libs / Panther In-Reply-To: <71AE9FB1-DCC6-4CA5-82C5-B24D5C27301B@macports.org> References: <49ACC9E1.9040608@macports.org> <71AE9FB1-DCC6-4CA5-82C5-B24D5C27301B@macports.org> Message-ID: <9C74996A-E963-4F8B-829D-F78AE9EED2A7@macports.org> Unfortunately, my oldest Apple HW came with Tiger and Panther won't install on it. If someone wants to send me an old powerbook or G4 cube (I'm pretty sure those were in the Panher era) or something like that, I can get this fixed... but short of that /shrug. On Mar 3, 2009, at 00:41, Ryan Schmidt wrote: > > On Mar 3, 2009, at 00:10, Joshua Root wrote: > >> Ryan Schmidt wrote: >> >>> On Mar 1, 2009, at 11:42, Jeremy Huddleston wrote: >>> >>>> According to the man page, gettimeofday should be defined by >>>> including >>>> sys/time.h. That is included on line 46 of glut_event.c >>> >>> "man gettimeofday" says the same on Panther. I'll see what I can >>> find out. >> >> It's only a warning for gettimeofday. The first error is "`fd_set' >> undeclared". > > glut_event.c:309: error: `fd_set' undeclared (first use in this > function) > > However fd_set is defined in sys/types.h which is included on line > 39 of glut_event.c. I don't know what to make of it. > > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From raimue at macports.org Wed Mar 4 14:33:32 2009 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Wed, 04 Mar 2009 23:33:32 +0100 Subject: adduser, addgroup In-Reply-To: <9ED6CED5-A4D0-4772-808A-CFF8162230DC@newgeo.com> References: <89E1C0AC-4C49-4DE3-B682-61ABBADED3DD@newgeo.com> <22E01BA5-8CD6-4F20-B316-6B5123368370@macports.org> <74E68B2C-2241-49C7-8A3E-3C82CFD3E658@newgeo.com> <49AEFA1F.2040608@macports.org> <9ED6CED5-A4D0-4772-808A-CFF8162230DC@newgeo.com> Message-ID: <49AF01BC.3090908@macports.org> Scott Haneda wrote: > On Mar 4, 2009, at 2:01 PM, Joshua Root wrote: >>> As far as I am finding, on error, the user and group are still >>> there, I >>> will also check of on uninstall, the user and group get removed. >> They don't. > > Was this a design decision, or something overlooked? Should it be > considered a bug, or intended behavior? MacPorts does not track created users currently. Multiple installed ports could create the same user, so it would have to create a map of created users and only remove them if all ports are uninstalled. Users are usually already created during destroot, as the user is necessary to assign the correct permissions to files. At this point we do not even know if the user is going to install the port. Rainer From peter at pogma.com Wed Mar 4 15:39:00 2009 From: peter at pogma.com (Peter O'Gorman) Date: Wed, 04 Mar 2009 17:39:00 -0600 Subject: Why ar doesn't call ranlib on Mac? In-Reply-To: References: <6E56105F-260A-4CC7-AF11-05E366589191@gmail.com> <49AE9BC7.3060006@pogma.com> <49AEA078.4000008@macports.org> Message-ID: <49AF1114.3040403@pogma.com> Alexy Khrabrov wrote: > I'm on Intel Leopard 10.5.6 and my xcode is 312_2621, gcc build 5490. > The ar I have us from July 9 2008, size 64448 bytes. I've upgraded from > gcc build 5488 yesterday to see if the most recent xcode off ADC has a > different ar, but it didn't look like it. Peter -- is the new ar > supposed to be in xcode.dmg, or you get it via other means? Then ar is calling ranlib for you unless you are passing it the -S flag. If you are building for multiple arches then you should pass ar the -s flag (as Rainer said) to ar to ensure that the table of contents is created. As you can see from the ar sources it calls ranlib -q normally, and ranlib -f if it saw the -s flag. Ranlib -q will "Do nothing if a universal file would be created." whereas ranlib -f will create the fat archive. Peter -- Peter O'Gorman http://pogma.com From deliverable at gmail.com Wed Mar 4 19:06:57 2009 From: deliverable at gmail.com (Alexy Khrabrov) Date: Wed, 4 Mar 2009 22:06:57 -0500 Subject: Why ar doesn't call ranlib on Mac? In-Reply-To: <49AF1114.3040403@pogma.com> References: <6E56105F-260A-4CC7-AF11-05E366589191@gmail.com> <49AE9BC7.3060006@pogma.com> <49AEA078.4000008@macports.org> <49AF1114.3040403@pogma.com> Message-ID: <09EA2595-5C25-4C2A-BF5D-A2C68462AC0F@gmail.com> On Mar 4, 2009, at 6:39 PM, Peter O'Gorman wrote: > > Then ar is calling ranlib for you unless you are passing it the -S > flag. > > If you are building for multiple arches then you should pass ar the -s > flag (as Rainer said) to ar to ensure that the table of contents is > created. As you can see from the ar sources it calls ranlib -q > normally, > and ranlib -f if it saw the -s flag. Ranlib -q will "Do nothing if a > universal file would be created." whereas ranlib -f will create the > fat > archive. Hmm -- I don't do anything special to build universal binaries. The problem arises in GODI, an OCaml packaging system, from a plain command ar cr libdigest.a -- and adding ranlib libdigest.a solved the problem. Does a regular compilation gcc x.c with Apple's gcc on an Intel Mac try to create a universal binary? Cheers, Alexy From ryandesign at macports.org Wed Mar 4 19:17:16 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed, 4 Mar 2009 21:17:16 -0600 Subject: Why ar doesn't call ranlib on Mac? In-Reply-To: <09EA2595-5C25-4C2A-BF5D-A2C68462AC0F@gmail.com> References: <6E56105F-260A-4CC7-AF11-05E366589191@gmail.com> <49AE9BC7.3060006@pogma.com> <49AEA078.4000008@macports.org> <49AF1114.3040403@pogma.com> <09EA2595-5C25-4C2A-BF5D-A2C68462AC0F@gmail.com> Message-ID: <1D3D22C8-5BCC-45AC-9C72-04E2F8B2AE27@macports.org> On Mar 4, 2009, at 21:06, Alexy Khrabrov wrote: > Does a regular compilation > > gcc x.c > > with Apple's gcc on an Intel Mac try to create a universal binary? No, you have to add various cflags, ldflags, etc. to get a universal. http://developer.apple.com/technotes/tn2005/tn2137.html From artie.ziff at gmail.com Wed Mar 4 22:15:28 2009 From: artie.ziff at gmail.com (Artie Ziff) Date: Wed, 04 Mar 2009 22:15:28 -0800 Subject: py25-pyqt4 build fails In-Reply-To: References: <2E139149-7D5F-4178-9A55-2DCB494F6B1D@macports.org> <4BFC06C7-B237-4CCD-BBC0-F683986B6A99@macports.org> Message-ID: <49AF6E00.1070505@gmail.com> > > I'm on Tiger 10.4.11, Xcode v 2.5. I did update the Portfile descriptions > yesterday, and I've been in the process of upgrading to current packages. I'm > fairly sure all the deps for pyqt4 are up to date. > > So it just works in Leopard? The reasons-to-upgrade list is getting longer. > > Kind regards, > Mike > > FWIW, I see this activation error on Mac OS 10.5.6 $ sudo port install py25-pyqt4 ---> Installing py25-pyqt4 @4.4.4_0 ---> Activating py25-pyqt4 @4.4.4_0 Error: Target org.macports.activate returned: Image error: /opt/local/Library/Frameworks/Python.framework/Versions/2.5/bin/pylupdate4 already exists and does not belong to a registered port. Unable to activate port py25-pyqt4. Error: Status 1 encountered during processing. From peter at pogma.com Thu Mar 5 06:26:05 2009 From: peter at pogma.com (Peter O'Gorman) Date: Thu, 05 Mar 2009 08:26:05 -0600 Subject: cmake 2.6.2: _FILE_OFFSET_BITS=64/uClibc built w/o large file support In-Reply-To: References: Message-ID: <49AFE0FD.8060606@pogma.com> Michael Brian Bentley wrote: > Hi! > > I'm having a moment of trouble building cmake 2.6.2 with the current > MacPort. I'm on Mac OS X 10.5.6. > > It is complaining that _FILE_OFFSET_BITS=64, but uClibc was built > without large file support enabled. > > I looked around but apparently haven't found the obvious toggle switch. > In file included from /usr/include/elf.h:23, Why do you have /usr/include/elf.h ? Peter -- Peter O'Gorman http://pogma.com From raimue at macports.org Thu Mar 5 07:28:26 2009 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Thu, 05 Mar 2009 16:28:26 +0100 Subject: py25-pyqt4 build fails In-Reply-To: <49AF6E00.1070505@gmail.com> References: <2E139149-7D5F-4178-9A55-2DCB494F6B1D@macports.org> <4BFC06C7-B237-4CCD-BBC0-F683986B6A99@macports.org> <49AF6E00.1070505@gmail.com> Message-ID: <49AFEF9A.6080800@macports.org> Artie Ziff wrote: > FWIW, I see this activation error on Mac OS 10.5.6 > > $ sudo port install py25-pyqt4 > ---> Installing py25-pyqt4 @4.4.4_0 > ---> Activating py25-pyqt4 @4.4.4_0 > Error: Target org.macports.activate returned: Image error: > /opt/local/Library/Frameworks/Python.framework/Versions/2.5/bin/pylupdate4 > already exists and does not belong to a registered port. Unable to > activate port py25-pyqt4. > Error: Status 1 encountered during processing. There is a file which was not put there by using MacPorts. Therefore the activation was cancelled. This can happen if you manually installed files into your prefix. You can force the activation to overwrite the existing files: sudo port -f activate py25-pyqt4 Rainer From macsforever2000 at macports.org Thu Mar 5 08:38:22 2009 From: macsforever2000 at macports.org (Frank Schima) Date: Thu, 5 Mar 2009 09:38:22 -0700 Subject: py25-pyqt4 build fails In-Reply-To: <49AFEF9A.6080800@macports.org> References: <2E139149-7D5F-4178-9A55-2DCB494F6B1D@macports.org> <4BFC06C7-B237-4CCD-BBC0-F683986B6A99@macports.org> <49AF6E00.1070505@gmail.com> <49AFEF9A.6080800@macports.org> Message-ID: <8BE56275-E61D-467D-A940-1DE70C629008@macports.org> On Mar 5, 2009, at 8:28 AM, Rainer M?ller wrote: > Artie Ziff wrote: >> FWIW, I see this activation error on Mac OS 10.5.6 >> >> $ sudo port install py25-pyqt4 >> ---> Installing py25-pyqt4 @4.4.4_0 >> ---> Activating py25-pyqt4 @4.4.4_0 >> Error: Target org.macports.activate returned: Image error: >> /opt/local/Library/Frameworks/Python.framework/Versions/2.5/bin/ >> pylupdate4 >> already exists and does not belong to a registered port. Unable to >> activate port py25-pyqt4. >> Error: Status 1 encountered during processing. > > There is a file which was not put there by using MacPorts. Therefore > the > activation was cancelled. This can happen if you manually installed > files into your prefix. > > You can force the activation to overwrite the existing files: > sudo port -f activate py25-pyqt4 Actually it was probably put there by an earlier failed install because of the python25 framework bug. See and The port does work after you force the install, but the registry gets all messed up - macports thinks py25-pyqt4 is active but a "port contents py25-pyqt4" yields nothing. This is why I'm all for fixing the framework bug even if it means users having to reinstall all py25- * ports. Cheers! Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From deliverable at gmail.com Thu Mar 5 14:04:37 2009 From: deliverable at gmail.com (Alexy Khrabrov) Date: Thu, 5 Mar 2009 17:04:37 -0500 Subject: graphviz +ocaml and swig bugs Message-ID: <6C2EFAE5-8C23-4277-A52E-4DB2E0565BA9@gmail.com> Just a heads up about a problem with graphviz +ocaml -- when trying to build, first you'll encounter a bug in swig, and if you manage to fix it, then you'll run into a bug in graphviz. The swig bug is reported in RedHat and a patch is provided: https://bugzilla.redhat.com/show_bug.cgi?id=485540 -- I've extracted, applied it -- fixes -- and submitted ticket https://trac.macports.org/ticket/18745 for it. The graphviz is supposed to be fixed in 2.22 -- didn't check yet -- the bug in ocaml bindings is described in http://www.graphviz.org/bugs/b1586.html -- I manually fixed it in the same way in the work/ source. According to John Ellson of graphviz, the 2.22 is ready to be macportized. The swig bug bothers me a bit as it seems a RedHat patch and I'm not sure it's reported upstream. Cheers, Alexy From artie.ziff at gmail.com Thu Mar 5 17:00:43 2009 From: artie.ziff at gmail.com (Artie Ziff) Date: Thu, 05 Mar 2009 17:00:43 -0800 Subject: py25-pyqt4 build fails In-Reply-To: <8BE56275-E61D-467D-A940-1DE70C629008@macports.org> References: <2E139149-7D5F-4178-9A55-2DCB494F6B1D@macports.org> <4BFC06C7-B237-4CCD-BBC0-F683986B6A99@macports.org> <49AF6E00.1070505@gmail.com> <49AFEF9A.6080800@macports.org> <8BE56275-E61D-467D-A940-1DE70C629008@macports.org> Message-ID: <49B075BB.90201@gmail.com> >> >> There is a file which was not put there by using MacPorts. Therefore the >> activation was cancelled. This can happen if you manually installed >> files into your prefix. I wonder how to work around? >> >> You can force the activation to overwrite the existing files: >> sudo port -f activate py25-pyqt4 > > Actually it was probably put there by an earlier failed install > because of the python25 framework bug. > > See > > and > > > The port does work after you force the install, but the registry gets > all messed up - macports thinks py25-pyqt4 is active but a "port > contents py25-pyqt4" yields nothing. This is why I'm all for fixing > the framework bug even if it means users having to reinstall all > py25-* ports. > Thank you for the info, everyone! I do not mind rebuilding all python 2.5 stuff. It's no problem to build at night. Is there a recommended way to work around the issue? For me, this `sudo port -f activate py25-pyqt4` yields a large pile of the following: Warning: File /opt/local/share/sip/PyQt4/QtXmlPatterns/qxmlquery.sip already exists. Moving to: /opt/local/share/sip/PyQt4/QtXmlPatterns/qxmlquery.sip.mp_1236301109. Warning: File /opt/local/share/sip/PyQt4/QtXmlPatterns/qxmlresultitems.sip already exists. Moving to: /opt/local/share/sip/PyQt4/QtXmlPatterns/qxmlresultitems.sip.mp_1236301109. Warning: File /opt/local/share/sip/PyQt4/QtXmlPatterns/qxmlserializer.sip already exists. Moving to: /opt/local/share/sip/PyQt4/QtXmlPatterns/qxmlserializer.sip.mp_1236301109. Error: port activate failed: Not a directory Thank you! Art From c.watson at pgrad.unimelb.edu.au Thu Mar 5 17:18:18 2009 From: c.watson at pgrad.unimelb.edu.au (Campbell Watson) Date: Fri, 6 Mar 2009 12:18:18 +1100 Subject: solution - xemacs error, non-widget child Message-ID: Reply to my posting at http://www.nabble.com/XEmacs---error,-non-widget-child-td22234642.html...... The solution, with thanks to Ken: "sudo port -f upgrade xemacs" Campbell -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmr at macports.org Thu Mar 5 17:37:13 2009 From: jmr at macports.org (Joshua Root) Date: Fri, 06 Mar 2009 12:37:13 +1100 Subject: solution - xemacs error, non-widget child In-Reply-To: References: Message-ID: <49B07E49.9030000@macports.org> Campbell Watson wrote: > Reply to my posting at > http://www.nabble.com/XEmacs---error,-non-widget-child-td22234642.html...... > > The solution, with thanks to Ken: > > "sudo port -f upgrade xemacs" Which rebuilds all the dependencies. It would be nice to know exactly which one was the problem. Oh well... - Josh From artie.ziff at gmail.com Thu Mar 5 19:08:09 2009 From: artie.ziff at gmail.com (Artie Ziff) Date: Thu, 05 Mar 2009 19:08:09 -0800 Subject: macport user advice Message-ID: <49B09399.1070003@gmail.com> Hello, I did th followiong command: port -vu upgrade outdated I see things ended like this: /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -I.. -I./.. -W -Wall -Wunused -I../../libs/t1lib -I./../../libs/t1lib -I../../libs/t1lib/../type1 -I./../../libs/t1lib/../type1 -DPS_GS -I./gui -I../../libs/t1lib/lib/t1lib -I../kpathsea -I/usr/X11/include -I/opt/local/include -O2 -c x_util.c -o x_util.o /bin/sh ../libtool --mode=link /usr/bin/gcc-4.0 -o xdvi-xaw.bin -L/opt/local/lib browser.o dvi-draw.o dvi-init.o dvisel.o encodings.o events.o filehist.o font-open.o gf.o hypertex.o image-magick.o mime.o my-snprintf.o my-vsnprintf.o pagehist.o pk.o print-internal.o psdps.o psgs.o psheader.o psnews.o read-mapfile.o search-internal.o special.o string-utils.o tfmload.o util.o vf.o xdvi.o xserver-info.o x_util.o ./gui/libgui.a ../../libs/t1lib/libt1.a ../../libs/t1lib/../type1/libtype1.a -L/usr/X11R6 1/lib -L/usr/X11/lib -lXaw -lXmu -lXt -lSM -lICE -lXp -lXext -lX11 -liconv -lXpm ../kpathsea/libkpathsea.la -lm mkdir .libs /usr/bin/gcc-4.0 -o xdvi-xaw.bin browser.o dvi-draw.o dvi-init.o dvisel.o encodings.o events.o filehist.o font-open.o gf.o hypertex.o image-magick.o mime.o my-snprintf.o my-vsnprintf.o pagehist.o pk.o print-internal.o psdps.o psgs.o psheader.o psnews.o read-mapfile.o search-internal.o special.o string-utils.o tfmload.o util.o vf.o xdvi.o xserver-info.o x_util.o 1/lib -L/opt/local/lib ./gui/libgui.a ../../libs/t1lib/libt1.a ../../libs/t1lib/../type1/libtype1.a -L/usr/X11R6 -L/usr/X11/lib -lXaw -lXmu -lXt -lSM -lICE -lXp -lXext -lXpm -lX11 -lXau -lXdmcp -lintl -liconv -lc ../kpathsea/.libs/libkpathsea.a -lm i686-apple-darwin9-gcc-4.0.1: 1/lib: No such file or directory make[2]: *** [xdvi-xaw.bin] Error 1 make[1]: *** [all] Error 1 make: *** [all] Error 1 Warning: the following items did not execute (for teTeX): org.macports.destroot org.macports.build Error: Unable to upgrade port: 1 548.86 real 288.70 user 74.93 sys #### How to manage MacPort after you have been adding packages for a couple of years? Are there any good web pages with advice on managing the MacPort tree? I want to prune mine. Is there a way to start over? i.e. deleting everything and then providing a "manifest" of the packages you want, somewhat like the Gentoo Linux "world" file. How do I determine why I have a particular package on my system? For example, why am I compiling "i686-apple-darwin9-gcc-4.0.1" ? :) And lastly and more specifically, is there an easy work-around to keep my build moving forward? Why did the gcc fail? Clearly, "1/lib" does not exist. :) Apologies if all of these questions have been answered before... If so, then I am happy to read the archives. Cheers! From blb at macports.org Thu Mar 5 19:27:37 2009 From: blb at macports.org (Bryan Blackburn) Date: Thu, 5 Mar 2009 20:27:37 -0700 Subject: macport user advice In-Reply-To: <49B09399.1070003@gmail.com> References: <49B09399.1070003@gmail.com> Message-ID: <20090306032737.GG489@ninagal.withay.com> On Thu, Mar 05, 2009 at 07:08:09PM -0800, Artie Ziff said: > Hello, > > I did th followiong command: > > port -vu upgrade outdated > > I see things ended like this: [...] > -lXpm -lX11 -lXau -lXdmcp -lintl -liconv -lc > ../kpathsea/.libs/libkpathsea.a -lm > i686-apple-darwin9-gcc-4.0.1: 1/lib: No such file or directory That's mentioned on the problem hotlist: [...] > > How to manage MacPort after you have been adding packages for a couple > of years? Are there any good web pages with advice on managing the > MacPort tree? I want to prune mine. That might make a good new wiki page, but to cover a bit of the basics: sudo port uninstall inactive will remove inactive ports (assuming you don't have any you specifically deactivated for a reason). These usually build up through using 'port upgrade'. Other than that, review 'port installed' for things you no longer need, and you can install the port_cutleaves port to remove orphaned ports that were installed as dependencies of stuff you no longer have. > > Is there a way to start over? i.e. deleting everything and then > providing a "manifest" of the packages you want, somewhat like the > Gentoo Linux "world" file. Currently there's only the brute-force method of using 'port installed' to get the list of what you have, then removing everything: then install MacPorts and reinstall what you need from the list prior. > > How do I determine why I have a particular package on my system? For > example, why am I compiling "i686-apple-darwin9-gcc-4.0.1" ? :) That's the gcc for Intel-based Macs, but it's usually called via just gcc. > > And lastly and more specifically, is there an easy work-around to keep > my build moving forward? Why did the gcc fail? Clearly, "1/lib" does not > exist. :) See above. Bryan > > Apologies if all of these questions have been answered before... If so, > then I am happy to read the archives. > > Cheers! > From jmr at macports.org Thu Mar 5 19:38:34 2009 From: jmr at macports.org (Joshua Root) Date: Fri, 06 Mar 2009 14:38:34 +1100 Subject: macport user advice In-Reply-To: <49B09399.1070003@gmail.com> References: <49B09399.1070003@gmail.com> Message-ID: <49B09ABA.10003@macports.org> Artie Ziff wrote: > Hello, > > I did th followiong command: > > port -vu upgrade outdated > > I see things ended like this: > > > /usr/bin/gcc-4.0 -DHAVE_CONFIG_H -I. -I. -I.. -I./.. -W -Wall -Wunused > -I../../libs/t1lib -I./../../libs/t1lib -I../../libs/t1lib/../type1 > -I./../../libs/t1lib/../type1 -DPS_GS -I./gui > -I../../libs/t1lib/lib/t1lib -I../kpathsea -I/usr/X11/include > -I/opt/local/include -O2 -c x_util.c -o x_util.o > /bin/sh ../libtool --mode=link /usr/bin/gcc-4.0 -o xdvi-xaw.bin > -L/opt/local/lib browser.o dvi-draw.o dvi-init.o dvisel.o encodings.o > events.o filehist.o font-open.o gf.o hypertex.o image-magick.o mime.o > my-snprintf.o my-vsnprintf.o pagehist.o pk.o print-internal.o psdps.o > psgs.o psheader.o psnews.o read-mapfile.o search-internal.o special.o > string-utils.o tfmload.o util.o vf.o xdvi.o xserver-info.o x_util.o > ./gui/libgui.a ../../libs/t1lib/libt1.a > ../../libs/t1lib/../type1/libtype1.a -L/usr/X11R6 1/lib -L/usr/X11/lib > -lXaw -lXmu -lXt -lSM -lICE -lXp -lXext -lX11 -liconv -lXpm > ../kpathsea/libkpathsea.la -lm > mkdir .libs > /usr/bin/gcc-4.0 -o xdvi-xaw.bin browser.o dvi-draw.o dvi-init.o > dvisel.o encodings.o events.o filehist.o font-open.o gf.o hypertex.o > image-magick.o mime.o my-snprintf.o my-vsnprintf.o pagehist.o pk.o > print-internal.o psdps.o psgs.o psheader.o psnews.o read-mapfile.o > search-internal.o special.o string-utils.o tfmload.o util.o vf.o xdvi.o > xserver-info.o x_util.o 1/lib -L/opt/local/lib ./gui/libgui.a > ../../libs/t1lib/libt1.a ../../libs/t1lib/../type1/libtype1.a > -L/usr/X11R6 -L/usr/X11/lib -lXaw -lXmu -lXt -lSM -lICE -lXp -lXext > -lXpm -lX11 -lXau -lXdmcp -lintl -liconv -lc > ../kpathsea/.libs/libkpathsea.a -lm > i686-apple-darwin9-gcc-4.0.1: 1/lib: No such file or directory > make[2]: *** [xdvi-xaw.bin] Error 1 > make[1]: *** [all] Error 1 > make: *** [all] Error 1 See this Problem Hotlist entry: > How to manage MacPort after you have been adding packages for a couple > of years? Are there any good web pages with advice on managing the > MacPort tree? I want to prune mine. Try the port_cutleaves port. > Is there a way to start over? i.e. deleting everything and then > providing a "manifest" of the packages you want, somewhat like the > Gentoo Linux "world" file. Not directly. You can use the output of `port echo installed` with a little scripting. > How do I determine why I have a particular package on my system? For > example, why am I compiling "i686-apple-darwin9-gcc-4.0.1" ? :) i686-apple-darwin9-gcc-4.0.1 is part of Apple's gcc 4. It's what you are compiling with, not what you're compiling. If you want to see which port installed a file, use `port provides /path/to/file`. If you want to see why that port is needed, use `port dependents portname`. - Josh From mdwturner at hotmail.com Thu Mar 5 19:53:59 2009 From: mdwturner at hotmail.com (Mark Turner) Date: Thu, 5 Mar 2009 19:53:59 -0800 (PST) Subject: Using Macports libraries in Xcode gcc In-Reply-To: <758644.11599.qm@web65703.mail.ac4.yahoo.com> References: <758644.11599.qm@web65703.mail.ac4.yahoo.com> Message-ID: <22365821.post@talk.nabble.com> vr8ce wrote: > > OS X 10.5.6, Macports 1.7, gcc 4.0.1 from Xcode 3.1.2 > > The FAQ address why Macports installs its own libraries, etc. I have the > opposite question, and I read the FAQ and tried searching a couple of > months of maillist archives and couldn't find it. My apologies if I missed > it. > > I have a program I want to compile that needs popt. I've downloaded the > Macports popt package, and now have the popt.h in /opt/local/include, the > library in /opt/local/lib, etc. > > My question is what I have to do to my gcc setup to get it to "see" the > Macport installed libraries (not just popt, but any other libraries I > might download). I've tried adding the -I and -L's to the gcc command, and > the popt.h is found, but it complains about the library, e.g. > ld: library not found for -l/opt/local/lib/popt > > I see that /opt/local/lib has libpopt.a, libpopt.la, and > libpopt.0.0.0.dylib, which is similar to the other libraries. I didn't > think I needed to specify "-L libpopt", but that gcc automatically added > the lib prefix to the library. But, just in case, I tried adding it > myself, but that didn't work, either. > > An example command line of something I'm trying to compile: > gcc -g -O2 -o src/ascii/ascii src/ascii/ascii.o -l/opt/local/lib/libpopt > > Please don't point out that there's a version of ascii in Macport -- I > know that, I'm just using this as an example of trying to get a Macport > library working in general gcc. :) > > Thanks very much for your help. > > > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > > I've had a similar problem and just figured out that I need to omit the "lib" prefix from the library name, since GCC adds the prefix. Now ... it's been a while since I've dabbled with the C linker let alone GCC, but has this always been the convention? Why in the world would linker insist on changing a file name, by adding a prefix or anything else? Seems weird, and it's taken me several hours to figure out .... d'oh! -- View this message in context: http://www.nabble.com/Using-Macports-libraries-in-Xcode-gcc-tp21392095p22365821.html Sent from the MacPorts - Users mailing list archive at Nabble.com. From ryandesign at macports.org Thu Mar 5 20:08:16 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 5 Mar 2009 22:08:16 -0600 Subject: py25-pyqt4 build fails In-Reply-To: <49B075BB.90201@gmail.com> References: <2E139149-7D5F-4178-9A55-2DCB494F6B1D@macports.org> <4BFC06C7-B237-4CCD-BBC0-F683986B6A99@macports.org> <49AF6E00.1070505@gmail.com> <49AFEF9A.6080800@macports.org> <8BE56275-E61D-467D-A940-1DE70C629008@macports.org> <49B075BB.90201@gmail.com> Message-ID: <90F55783-59CD-4EB0-B8A3-A95B42F8FA2D@macports.org> On Mar 5, 2009, at 19:00, Artie Ziff wrote: >>> You can force the activation to overwrite the existing files: >>> sudo port -f activate py25-pyqt4 >> >> Actually it was probably put there by an earlier failed install >> because of the python25 framework bug. >> >> See >> >> and >> >> >> The port does work after you force the install, but the registry gets >> all messed up - macports thinks py25-pyqt4 is active but a "port >> contents py25-pyqt4" yields nothing. This is why I'm all for fixing >> the framework bug even if it means users having to reinstall all >> py25-* ports. >> > > > Thank you for the info, everyone! > I do not mind rebuilding all python 2.5 stuff. It's no problem to > build > at night. > > Is there a recommended way to work around the issue? > > For me, this `sudo port -f activate py25-pyqt4` yields a large pile of > the following: > > Warning: File /opt/local/share/sip/PyQt4/QtXmlPatterns/qxmlquery.sip > already exists. Moving to: > /opt/local/share/sip/PyQt4/QtXmlPatterns/qxmlquery.sip.mp_1236301109. > Warning: File > /opt/local/share/sip/PyQt4/QtXmlPatterns/qxmlresultitems.sip already > exists. Moving to: > /opt/local/share/sip/PyQt4/QtXmlPatterns/ > qxmlresultitems.sip.mp_1236301109. > Warning: File > /opt/local/share/sip/PyQt4/QtXmlPatterns/qxmlserializer.sip already > exists. Moving to: > /opt/local/share/sip/PyQt4/QtXmlPatterns/ > qxmlserializer.sip.mp_1236301109. Yes, that is what forcing does. It moves the conflicting files out of the way. > Error: port activate failed: Not a directory That sounds like the trying-to-install-into-a-symlink issue. From dp.chaoswerks at gmail.com Thu Mar 5 20:57:18 2009 From: dp.chaoswerks at gmail.com (David P. Henderson) Date: Thu, 5 Mar 2009 20:57:18 -0800 Subject: Using Macports libraries in Xcode gcc In-Reply-To: <22365821.post@talk.nabble.com> References: <758644.11599.qm@web65703.mail.ac4.yahoo.com> <22365821.post@talk.nabble.com> Message-ID: <49861932-E892-4584-B4D3-B7B3C65DDA0D@gmail.com> -L/opt/local/lib/ -lpopt On 05 Mar 2009, at 19:53, Mark Turner wrote: >> I see that /opt/local/lib has libpopt.a, libpopt.la, and >> libpopt.0.0.0.dylib, which is similar to the other libraries. I >> didn't >> think I needed to specify "-L libpopt", but that gcc automatically >> added >> the lib prefix to the library. But, just in case, I tried adding it >> myself, but that didn't work, either. >> >> An example command line of something I'm trying to compile: >> gcc -g -O2 -o src/ascii/ascii src/ascii/ascii.o -l/opt/local/lib/ >> libpopt -- "Suburbia is where the developer bulldozes out the trees, then names the streets after them." -- Bill Vaughn From smurfair at gmail.com Thu Mar 5 21:11:52 2009 From: smurfair at gmail.com (Andy Schmitt) Date: Thu, 5 Mar 2009 23:11:52 -0600 Subject: libpixbufloader Message-ID: <40D232FC-CA49-490D-A924-A1364E7CDB3E@gmail.com> I just compiled something that had expected to find: /lib/gtk-2.0/*/ loaders/libpixbufloader-bmp.so Googling suggests that's a pretty common location for that folder and that perhaps gdk-pixbuf was installed along with gtk2 as recently as 2.8. But I had to manually install the gdk-pixbuf port and adjust that path to /lib/gdk-pixbuf/loaders/libpixbufloader-bmp.so. So, did something change or did I manage to screw something up somewhere along the way. andy From hvdwolf at gmail.com Fri Mar 6 01:59:05 2009 From: hvdwolf at gmail.com (Harry van der Wolf) Date: Fri, 6 Mar 2009 10:59:05 +0100 Subject: Using Macports libraries in Xcode gcc In-Reply-To: <49861932-E892-4584-B4D3-B7B3C65DDA0D@gmail.com> References: <758644.11599.qm@web65703.mail.ac4.yahoo.com> <22365821.post@talk.nabble.com> <49861932-E892-4584-B4D3-B7B3C65DDA0D@gmail.com> Message-ID: <8c242c590903060159v73231f33r5475703060e40613@mail.gmail.com> >From what I understand is that you want to do this from within XCode. In that case it is very simple. In XCode double-click your target. You will get the "target info" screen, go to the Build tab and scroll down. In the "header Search Paths" you specify /opt/local/include. (If the binary/library specifies a subfolder below include, mention that one or use the "recursive" flag) In the "Library Search Paths" you specify /opt/local/lib. Note: XCode already searches the system wide include and lib directories. you only need to specify the extra "non standard" paths. Harry 2009/3/6 David P. Henderson > -L/opt/local/lib/ -lpopt > > On 05 Mar 2009, at 19:53, Mark Turner wrote: > > I see that /opt/local/lib has libpopt.a, libpopt.la, and >>> libpopt.0.0.0.dylib, which is similar to the other libraries. I didn't >>> think I needed to specify "-L libpopt", but that gcc automatically added >>> the lib prefix to the library. But, just in case, I tried adding it >>> myself, but that didn't work, either. >>> >>> An example command line of something I'm trying to compile: >>> gcc -g -O2 -o src/ascii/ascii src/ascii/ascii.o -l/opt/local/lib/libpopt >>> >> > -- > "Suburbia is where the developer bulldozes out the trees, then names the > streets after them." > -- Bill Vaughn > > > > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From devans at macports.org Fri Mar 6 02:45:01 2009 From: devans at macports.org (David Evans) Date: Fri, 06 Mar 2009 02:45:01 -0800 Subject: libpixbufloader In-Reply-To: <40D232FC-CA49-490D-A924-A1364E7CDB3E@gmail.com> References: <40D232FC-CA49-490D-A924-A1364E7CDB3E@gmail.com> Message-ID: <49B0FEAD.4050500@macports.org> Andy Schmitt wrote: > I just compiled something that had expected to find: > /lib/gtk-2.0/*/loaders/libpixbufloader-bmp.so > > Googling suggests that's a pretty common location for that folder and > that perhaps gdk-pixbuf was installed along with gtk2 as recently as > 2.8. But I had to manually install the gdk-pixbuf port and adjust that > path to /lib/gdk-pixbuf/loaders/libpixbufloader-bmp.so. > > So, did something change or did I manage to screw something up > somewhere along the way. > > andy > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > Andy -- I think you are mixing two different versions of gtk. The gdk_pixbuf library is now included as part of gtk2 and bmp file format is one of the default file types that can be loaded or saved without using an external loader module. (also jpeg, png, ico at least) The command gdk-pixbuf-query-loaders will show you what additional external loader modules are installed and where. These are usually installed by other ports to add support for their own file types. The port gdk-pixbuf is an old version that is compatible with gtk1, glib1 where it was a separate library and a loader module was required for bmp. Perhaps the application you are trying to build is a gtk1 application? If you have port gdk-pixbuf installed then you also have its dependencies installed gtk1, glib1. Try port contents to see what files have been installed for a given port. gtk1 and gtk2 can coexist without interfering with each other AFAIK. (As long as you don't link them together) ;-) Dave From devans at macports.org Fri Mar 6 03:39:57 2009 From: devans at macports.org (David Evans) Date: Fri, 06 Mar 2009 03:39:57 -0800 Subject: libpixbufloader In-Reply-To: <49B0FEAD.4050500@macports.org> References: <40D232FC-CA49-490D-A924-A1364E7CDB3E@gmail.com> <49B0FEAD.4050500@macports.org> Message-ID: <49B10B8D.2000401@macports.org> David Evans wrote: > Andy Schmitt wrote: >> I just compiled something that had expected to find: >> /lib/gtk-2.0/*/loaders/libpixbufloader-bmp.so >> >> Googling suggests that's a pretty common location for that folder and >> that perhaps gdk-pixbuf was installed along with gtk2 as recently as >> 2.8. But I had to manually install the gdk-pixbuf port and adjust >> that path to /lib/gdk-pixbuf/loaders/libpixbufloader-bmp.so. >> >> So, did something change or did I manage to screw something up >> somewhere along the way. >> >> andy >> _______________________________________________ >> macports-users mailing list >> macports-users at lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users >> > Andy -- > > I think you are mixing two different versions of gtk. > > The gdk_pixbuf library is now included as part of gtk2 and bmp file > format is one of the default file types that can be loaded or > saved without using an external loader module. (also jpeg, png, ico at > least) > > The command > > gdk-pixbuf-query-loaders > > will show you what additional external loader modules are installed and > where. These are usually installed by other ports > to add support for their own file types. > > The port gdk-pixbuf is an old version that is compatible with gtk1, > glib1 where it was a separate library and a loader module was required > for bmp. > > Perhaps the application you are trying to build is a gtk1 application? > If you have port gdk-pixbuf installed then you also have its > dependencies installed gtk1, glib1. > > Try > > port contents > > to see what files have been installed for a given port. > > gtk1 and gtk2 can coexist without interfering with each other AFAIK. (As > long as you don't link them together) ;-) > > Dave > Just for completeness here is the list of loaders that are currently built in to the gdk_pixbuf library in gtk2 (from the configure output): checking pixbuf loaders to build... ani,icns,pcx,ras,tga,png,pnm,wbmp,xbm,xpm,jasper,bmp,gif,ico,jpeg,tiff From vincent-opdarw at vinc17.org Fri Mar 6 14:15:24 2009 From: vincent-opdarw at vinc17.org (Vincent Lefevre) Date: Fri, 6 Mar 2009 23:15:24 +0100 Subject: Perl error, once and for all In-Reply-To: <3A3DD996-D961-4291-AE81-63DF66327429@pixilla.com> References: <707C94E4-9868-4B39-BF42-E0D003BA6DBA@macports.org> <20090301025356.GB4629@prunille.vinc17.org> <20090302001841.GD4629@prunille.vinc17.org> <20090302011113.GA23645@prunille.vinc17.org> <20090303155528.GS27518@prunille.vinc17.org> <3A3DD996-D961-4291-AE81-63DF66327429@pixilla.com> Message-ID: <20090306221524.GP27518@prunille.vinc17.org> On 2009-03-03 11:49:12 -0800, Bradley Giesbrecht wrote: > Maybe we could add a port "macports-profile" that would be a script > similar to: > /opt/local/share/macports/setupenv.bash Yes, this is a rather standard way of doing such things. > I suppose the file /opt/local/etc/maports_profile.conf could be looked > for and if found could be parsed for overrides and additions. I would call it "/opt/local/etc/profile". > I have a macports on my laptop that I'm keeping clean just to help > resolve this perl5 issue. I hope we can come up with a work solution > soon. Even if it's just the decision to instruct users to add PERL5LIB > to their .profile by hand. > > Oh, and what about other shells? Let that small base work it out > themselves as they are probably used to doing? Isn't the .profile sourced at login time, so that all shells inherit its environment? Otherwise the user should probably source his .profile from the right init file of his shell (e.g. .zprofile in case of zsh), unless he has specific configuration. -- Vincent Lef?vre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon) From smurfair at gmail.com Fri Mar 6 14:27:00 2009 From: smurfair at gmail.com (Andy Schmitt) Date: Fri, 6 Mar 2009 16:27:00 -0600 Subject: libpixbufloader In-Reply-To: <49B0FEAD.4050500@macports.org> References: <40D232FC-CA49-490D-A924-A1364E7CDB3E@gmail.com> <49B0FEAD.4050500@macports.org> Message-ID: <62FAD885-77F7-42BB-880C-CEC961C283E4@gmail.com> On Mar 6, 2009, at 4:45 AM, David Evans wrote: > Andy Schmitt wrote: >> I just compiled something that had expected to find: /lib/gtk-2.0/*/ >> loaders/libpixbufloader-bmp.so >> >> Googling suggests that's a pretty common location for that folder >> and that perhaps gdk-pixbuf was installed along with gtk2 as >> recently as 2.8. But I had to manually install the gdk-pixbuf port >> and adjust that path to /lib/gdk-pixbuf/loaders/libpixbufloader- >> bmp.so. >> >> So, did something change or did I manage to screw something up >> somewhere along the way. >> >> andy >> _______________________________________________ >> macports-users mailing list >> macports-users at lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users >> > Andy -- > > I think you are mixing two different versions of gtk. > > The gdk_pixbuf library is now included as part of gtk2 and bmp file > format is one of the default file types that can be loaded or > saved without using an external loader module. (also jpeg, png, ico at > least) So wait, are you saying that /opt/local/lib/gtk-2.0/2.10.0/loaders *should* be present after gtk2 is installed? > The command > > gdk-pixbuf-query-loaders > > will show you what additional external loader modules are installed > and > where. These are usually installed by other ports > to add support for their own file types. That returned: # Created by gdk-pixbuf-query-loaders from gtk+-2.14.7 # LoaderDir = /opt/local/lib/gtk-2.0/2.10.0/loaders However, the "loaders" folder is noticeably absent. > The port gdk-pixbuf is an old version that is compatible with gtk1, > glib1 where it was a separate library and a loader module was required > for bmp. > > Perhaps the application you are trying to build is a gtk1 application? > If you have port gdk-pixbuf installed then you also have its > dependencies installed gtk1, glib1. I actually only installed gdk-pixbuf when I discovered ../loaders/ libpixbufloader-bmp.so was nowhere to found. So, yeah, I hadn't had gtk1 and glib1 installed until gdk-pixbuf needed them to compile. No it's gtk2. The application in question is NetRadiant- an attempt at maintaining a reliable stabilized distribution of gtkRadiant 1.5, since no others are being maintained. Rudolf Polzer has single- handedly taken this on, but I don't think he has the resources to be testing OS X builds. Historically most OS X Radiant SRC and binaries needed/were built with the Fink tools and libraries. Long story short: the current post-make scripts packs up the executables and dynamic libraries into an .app, but they assumed Fink, and in particular /sw/ lib/gtk-2.0/*/loaders/libpixbufloader-bmp.so. > Try > > port contents > > to see what files have been installed for a given port. Doing: port contents gtk2 shows no sign of any of the libpixbufloader-xxx.so files BTW does "port contents " return what *was installed* with that port or what *was supposed to have been installed*? > > > gtk1 and gtk2 can coexist without interfering with each other AFAIK. > (As > long as you don't link them together) ;-) > > Dave So, I don't know where that leaves me. Thanks for the informative reply Dave. andy From devans at macports.org Fri Mar 6 15:41:50 2009 From: devans at macports.org (David Evans) Date: Fri, 06 Mar 2009 15:41:50 -0800 Subject: libpixbufloader In-Reply-To: <62FAD885-77F7-42BB-880C-CEC961C283E4@gmail.com> References: <40D232FC-CA49-490D-A924-A1364E7CDB3E@gmail.com> <49B0FEAD.4050500@macports.org> <62FAD885-77F7-42BB-880C-CEC961C283E4@gmail.com> Message-ID: <49B1B4BE.5060603@macports.org> Andy Schmitt wrote: > > > So wait, are you saying that /opt/local/lib/gtk-2.0/2.10.0/loaders > *should* be present after gtk2 is installed? No, I'm saying this is where it looks for loaders that are installed by other ports. This path is hard coded into the library (determined at configure). For instance on my system # GdkPixbuf Image Loader Modules file # Automatically generated file, do not edit # Created by gdk-pixbuf-query-loaders from gtk+-2.14.7 # # LoaderDir = /opt/local/lib/gtk-2.0/2.10.0/loaders # "/opt/local/lib/gtk-2.0/2.10.0/loaders/libopenraw_pixbuf.so" "Digital camera RAW" 0 "gtk20" "Digital camera RAW images loader." "LGPL" "image/x-adobe-dng" "image/x-canon-cr2" "image/x-canon-crw" "image/x-nikon-nef" "image/x-olympus-orf" "image/x-pentax-pef" "image/x-sony-arw" "image/x-epson-erf" "image/x-minolta-mrw" "" "dng" "cr2" "crw" "nef" "orf" "pef" "arw" "erf" "mrw" "" "MM *" " z " 80 "II* \020 CR\002 " " z zzz z" 100 "II* " " z" 80 "IIRO" " " 100 " MRM" "z " 100 "II\032 HEAPCCDR" " zzz " 100 "/opt/local/lib/gtk-2.0/2.10.0/loaders/svg_loader.so" "svg" 2 "gtk20" "Scalable Vector Graphics" "LGPL" "image/svg+xml" "image/svg" "image/svg-xml" "image/vnd.adobe.svg+xml" "text/xml-svg" "image/svg+xml-compressed" "" "svg" "svgz" "svg.gz" "" " > No it's gtk2. The application in question is NetRadiant- an attempt at > maintaining a reliable stabilized distribution of gtkRadiant 1.5, > since no others are being maintained. Rudolf Polzer has > single-handedly taken this on, but I don't think he has the resources > to be testing OS X builds. Historically most OS X Radiant SRC and > binaries needed/were built with the Fink tools and libraries. Long > story short: the current post-make scripts packs up the executables > and dynamic libraries into an .app, but they assumed Fink, and in > particular /sw/lib/gtk-2.0/*/loaders/libpixbufloader-bmp.so. > If the app is built against the current gtk2 port, libpixbufloader-bmp.so is unnecessary and will never be called by the program because the built in loader code will be used instead for loading a bmp. So I think you can modify the post-make script to skip this and it should work. > Doing: > port contents gtk2 > shows no sign of any of the libpixbufloader-xxx.so files Right, shouldn't be any unless some other port puts one here to extend the range of files that can be loaded beyond what's built in. > > BTW does "port contents " return what *was installed* with that > port or what *was supposed to have been installed*? > It shows what was actually installed -- there's no way in MacPorts to find out what *would* be installed without actually doing it. > So, I don't know where that leaves me. Thanks for the informative > reply Dave. Well, I hope this helps. To summarize, I don't think you need the external bmp loader module at all. It should work without it (assuming everything built properly). This is a common misunderstanding partly because gkdpixbuf's name doesn't make it clear this is a gtk1 version. It will probably go away one of these days (along with gtk1 and glib1) but for now there are a few gtk1 ports left that depend upon it. Dave From jeremyhu at macports.org Fri Mar 6 19:54:27 2009 From: jeremyhu at macports.org (Jeremy Huddleston) Date: Fri, 6 Mar 2009 22:54:27 -0500 Subject: xorg-libs / Panther In-Reply-To: <71AE9FB1-DCC6-4CA5-82C5-B24D5C27301B@macports.org> References: <49ACC9E1.9040608@macports.org> <71AE9FB1-DCC6-4CA5-82C5-B24D5C27301B@macports.org> Message-ID: My suggestion for now is to do something like: platform darwin 7 { reinplace "s|glut/glx||" ${worksrcpath}/configs/darwin } This will cause glut to not be installed with mesa on Panther, but you'll atleast get everything else... On Mar 3, 2009, at 03:41, Ryan Schmidt wrote: > > On Mar 3, 2009, at 00:10, Joshua Root wrote: > >> Ryan Schmidt wrote: >> >>> On Mar 1, 2009, at 11:42, Jeremy Huddleston wrote: >>> >>>> According to the man page, gettimeofday should be defined by >>>> including >>>> sys/time.h. That is included on line 46 of glut_event.c >>> >>> "man gettimeofday" says the same on Panther. I'll see what I can >>> find out. >> >> It's only a warning for gettimeofday. The first error is "`fd_set' >> undeclared". > > glut_event.c:309: error: `fd_set' undeclared (first use in this > function) > > However fd_set is defined in sys/types.h which is included on line > 39 of glut_event.c. I don't know what to make of it. > > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From deliverable at gmail.com Fri Mar 6 21:05:35 2009 From: deliverable at gmail.com (Alexy Khrabrov) Date: Sat, 7 Mar 2009 00:05:35 -0500 Subject: gtk +no_x11 Message-ID: <7c737f300903062105v43f76b34vaad66d513c596f84@mail.gmail.com> How does this gtk +no_x11 stack against the Imendio GTK+ -- is it the same one? I was building an app one way or another and got two different-looking widget styles, both X-less. One is more angular and another is more mushy. I have the following goodies installed over last year: -- MacPorts: gtk2 +no_x11+quartz -- /Library/Frameworks/GTK+.framework # this contains 2.14.X11 -- /Library/Frameworks/Gtk.framework # looks like Imendio, has ./Resources/dev/lib/pkgconfig/gtk+-quartz-2.0.pc but no -x11 one My way of selecting one was to export PKG_CONFIG_PATH=/opt/local/lib/pkgconfig for MacPorts' one, or the one from a framework which I want to use. Can someone with experience with all of those summarize whether gtk2 +no_x11 obviates the need for any of the frameworks? Alas there's no GtkGlArea and the last time I checked some Gtk folks resisted making their pieces X-less, so not all gtk2 is available without X, quartz-only, but that's a different question -- given I stick with +no_x11, I wonder whether a .framework is in any way superior to the port gtk2. Cheers, Alexy From deliverable at gmail.com Sat Mar 7 22:49:07 2009 From: deliverable at gmail.com (Alexy Khrabrov) Date: Sun, 8 Mar 2009 01:49:07 -0500 Subject: binary rpm repos? Message-ID: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> It turns out RPM works fine on Mac: http://rpm4darwin.sourceforge.net/ -- why not have reference binaries for all ports in RPM format, to avoid endless recompiling if you don't have to? Watching gobs of compiler output fly by doesn't make one a Unix expert, in the immortal words of the funroll-loops.info of the "Gentoo is Rice" fame. Yeah, yeah, it depends on what you have -- but look, Red Hat does it! Cheers, Alexy From blb at macports.org Sat Mar 7 23:23:20 2009 From: blb at macports.org (Bryan Blackburn) Date: Sun, 8 Mar 2009 00:23:20 -0700 Subject: Notification of port deletion: htdig and hfsrsync In-Reply-To: <20090222221821.GC793@ninagal.withay.com> References: <20090222221821.GC793@ninagal.withay.com> Message-ID: <20090308072320.GM921@ninagal.withay.com> On Sun, Feb 22, 2009 at 03:18:21PM -0700, Bryan Blackburn said: > We don't have any policy on deleting ports, so how about an email? I think > both htdig and hfsrsync should be deleted, see tickets 5448 > > > > and 6488 > > > > for reasoning. Neither is a dependency for other ports. > > Any objections? FYI, htdig removed in r47845 [1] and hfsrsync in r47846 [2]. Bryan [1] - [2] - From jmr at macports.org Sat Mar 7 23:45:06 2009 From: jmr at macports.org (Joshua Root) Date: Sun, 08 Mar 2009 18:45:06 +1100 Subject: binary rpm repos? In-Reply-To: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> References: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> Message-ID: <49B37782.8040304@macports.org> Alexy Khrabrov wrote: > It turns out RPM works fine on Mac: > > http://rpm4darwin.sourceforge.net/ > > -- why not have reference binaries for all ports in RPM format, to > avoid endless recompiling if you don't have to? Watching gobs of > compiler output fly by doesn't make one a Unix expert, in the immortal > words of the funroll-loops.info of the "Gentoo is Rice" fame. Yeah, > yeah, it depends on what you have -- but look, Red Hat does it! MacPorts already allows building and installing from binary archives. What's missing is an automated system for building everything on all supported platforms and architectures, with error reporting, and checking for an archive on the server as well as on the local machine. - Josh From brad at pixilla.com Sun Mar 8 00:26:15 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Sun, 8 Mar 2009 00:26:15 -0800 Subject: binary rpm repos? In-Reply-To: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> References: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> Message-ID: On Mar 7, 2009, at 10:49 PM, Alexy Khrabrov wrote: > It turns out RPM works fine on Mac: Nice to know. Please take my comments as they are intended. To shed a little light on why some people may the time it takes to compile worth it. In my experience it's rarely performance optimization. It's usually feature set. RPM is a packaging system so what really matters is how well it's rpm packages work for you. > http://rpm4darwin.sourceforge.net/ > > -- why not have reference binaries for all ports in RPM format, to > avoid endless recompiling if you don't have to? Why don't you compile them for us? Sounds like a good job for the remainder of the year. Compile all those ports for each supported arch and by the time your done you can start working on the ones that had updates while you were working on the first round. > Watching gobs of > compiler output fly by doesn't make one a Unix expert, in the immortal > words of the funroll-loops.info of the "Gentoo is Rice" fame. Yeah, > yeah, it depends on what you have -- but look, Red Hat does it! Just finished putting in 9.5 hr's on rhel that should have been 4 to 6 hr's. The RedHat rpm's for bind9 were to old for me to use. Ended up hunting all over to find a newer source rpm and compiled that. First I tried just downloading bind9 sources and compiling those but RedHat openssl was to out dated to work with the bind9 features I required. My experience with binary distributions is fewer updates, meaning older versions of software. With a source distribution, if all you have to do is change the build instructions and hand out 2k files for download you more inclined to keep your distribution current then if you have to compile those upgrades for all supported archs. Another important consideration for many are the options that are compiled into the software. This might not matter to many users but I often need features that are not normally compiled into binary distributions. Just look at Apples php as an example. Even macports php is missing a few things I like to have, like ming, but at least it's easy enough to edit the Portfile to add ming support with macports still handling of all the other dependancies including ming. Yah man. That's cool. So back to RedHat, the bind9 rpm source I found to compile and replace the outdated RedHat bind9 rpm did have dlz-mysql configured. It also had dlz-postgres, dlz-ldap, dlz-bdb, etc... none of which I wanted. See, there are always trade offs. Compiling takes time but if it didn't have some advantages it wouldn't exist as a way of distributing software. If you want desktop stuff I think your right on the money for most people. But I find it painful to try to work with binary package managers for servers. Fink has been around a long time and when I used it in the past I thought it was pretty good. Have you tried it lately? I haven't but you might want to check it out. What in the world am I doing going on and on about this. I guess it's because I had so much fun on RedHat the other day :) Oh well, I'll be embarrassed tomorrow when I read my own post :) //Brad From brad at pixilla.com Sun Mar 8 00:31:46 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Sun, 8 Mar 2009 00:31:46 -0800 Subject: binary rpm repos? In-Reply-To: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> References: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> Message-ID: On Mar 7, 2009, at 10:49 PM, Alexy Khrabrov wrote: > It turns out RPM works fine on Mac: > > http://rpm4darwin.sourceforge.net/ > > -- why not have reference binaries for all ports in RPM format, to > avoid endless recompiling if you don't have to? Watching gobs of > compiler output fly by doesn't make one a Unix expert, in the immortal > words of the funroll-loops.info of the "Gentoo is Rice" fame. Yeah, > yeah, it depends on what you have -- but look, Red Hat does it! Hey Alexy, forgot to thank you for the funroll link. That brought a smile to my face :) Well actually I was laughing my ass off. Totally reminds me of all the Windows users who hate Macs cause you can't get under the hood and customize them to work the way you want. Always good for a laugh. Thanks for sharing. Brad From afb at macports.org Sun Mar 8 05:19:28 2009 From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=) Date: Sun, 8 Mar 2009 13:19:28 +0100 Subject: binary rpm repos? In-Reply-To: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> References: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> Message-ID: Alexy Khrabrov wrote: > It turns out RPM works fine on Mac: > > http://rpm4darwin.sourceforge.net/ There's also a couple of RPM ports in MacPorts, and a "port rpm" target to package any port up as a binary package or "port srpm" for source rpm. See http://guide.macports.org/#using.binaries The standalone installations of RPM work too, but install to /usr/local. Usually these build from Specfiles or *.src.rpm, rather than Portfiles. Perfectly reasonable, but somewhat off-topic. > -- why not have reference binaries for all ports in RPM format, to > avoid endless recompiling if you don't have to? Watching gobs of > compiler output fly by doesn't make one a Unix expert, in the immortal > words of the funroll-loops.info of the "Gentoo is Rice" fame. Yeah, > yeah, it depends on what you have -- but look, Red Hat does it! Normally MacPorts turns off the spew unless requesting it with port -d, but yeah you still have to install Developer Tools and do the rebuilds. There were binary rpms built for MacPorts 1.3 and 1.4, but not for 1.5 and 1.6 mostly due to the lack of interest. For MacPorts 1.7 it seemed "easier" to use the built-in archives, due to the heavy usage of "variants" and the missing integration of the "dp_light" branch... So at the moment, RPM is an "external" packaging system while the only integrated is the "internal" archiving systems of e.g. TxZ or XPKG*. * http://web.archive.org/web/20061230221957/http://www.xpkg.org/ This means that if you install a port from a RPM package (or from a PKG) then the registry and port(1) command still won't know anything about it. An example: "/opt/local/bin/port is not provided by a MacPorts port." So you would have to build (and rebuild on any updates) every port that you want to install as a package first, as you can't mix ports/packages. One of the problems is that variants (+) are not recorded by the packages, so you set those when building (normally it just uses the default variants) --anders From shreevatsa.public at gmail.com Sun Mar 8 08:37:02 2009 From: shreevatsa.public at gmail.com (Shreevatsa R) Date: Sun, 8 Mar 2009 11:37:02 -0400 Subject: gtk +no_x11 In-Reply-To: <7c737f300903062105v43f76b34vaad66d513c596f84@mail.gmail.com> References: <7c737f300903062105v43f76b34vaad66d513c596f84@mail.gmail.com> Message-ID: <7675454e0903080837p120bd3e3v89e37db61259909c@mail.gmail.com> On Sat, Mar 7, 2009 at 1:05 AM, Alexy Khrabrov wrote: > How does this gtk +no_x11 stack against the Imendio GTK+ -- is it the > same one? I was building an app one way or another and got two > different-looking widget styles, both X-less. One is more angular and Yes, gtk +no_x11 is the same as the GTK+ for Mac OS X from Imendio. The other framework that you have installed is also (very likely) from Imendio. The reason they appear different might be because the entire GTK+ OSX project is experimental and going through rapid changes, and the version in MacPorts is (possibly) slightly older than the newest unstable release from Imendio. (Or simply because they are using different GTK themes.) From ryandesign at macports.org Sun Mar 8 08:46:39 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 8 Mar 2009 10:46:39 -0500 Subject: binary rpm repos? In-Reply-To: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> References: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> Message-ID: <24AD1B84-BFE8-442E-BC64-8A513EC93E41@macports.org> On Mar 8, 2009, at 00:49, Alexy Khrabrov wrote: > It turns out RPM works fine on Mac: > > http://rpm4darwin.sourceforge.net/ tar and zip and Apple's native installer format pkg work on the Mac too. > -- why not have reference binaries for all ports in RPM format, to > avoid endless recompiling if you don't have to? Watching gobs of > compiler output fly by doesn't make one a Unix expert, in the immortal > words of the funroll-loops.info of the "Gentoo is Rice" fame. Yeah, > yeah, it depends on what you have -- but look, Red Hat does it! I agree having binaries available would be useful. We're not missing a format like rpm or tar or zip or pkg to keep it wrapped up in. What we're missing is code in MacPorts base to properly record everything about an install into a binary container so that it can coexist in a MacPorts prefix with ports that are compiled from source. Once that gets written, then we'll need to write scripts to automatically build all ports and package them into whatever binary format we've decided on and post the binaries to a server somewhere. From macports.users at gmail.com Sun Mar 8 08:57:16 2009 From: macports.users at gmail.com (C#4/135 D4/w!~) Date: Sun, 8 Mar 2009 11:57:16 -0400 Subject: slapd Message-ID: <19FE36AB-75BF-435E-8BE7-5B7D2FF31EA2@gmail.com> Hi everyone, I have here Port openldap contains: /Library/LaunchDaemons/org.macports.slapd.plist /Volumes/?/opt/etc/LaunchDaemons/org.macports.slapd/ org.macports.slapd.plist and some more. Picking one and trying: $ launchctl load /Volumes/?/opt/etc/LaunchDaemons/org.macports.slapd/ org.macports.slapd.plist nothing found to load $ chaning OnDemand OnDemand doesn't help either. Any idea? Thanks, From deliverable at gmail.com Sun Mar 8 13:54:31 2009 From: deliverable at gmail.com (Alexy Khrabrov) Date: Sun, 8 Mar 2009 15:54:31 -0500 Subject: binary rpm repos? In-Reply-To: <24AD1B84-BFE8-442E-BC64-8A513EC93E41@macports.org> References: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> <24AD1B84-BFE8-442E-BC64-8A513EC93E41@macports.org> Message-ID: <7c737f300903081354p287d5449yf04d868bdb99a130@mail.gmail.com> Ryan -- thanks for the clear summary, as usual! On Sun, Mar 8, 2009 at 10:46 AM, Ryan Schmidt wrote: > I agree having binaries available would be useful. We're not missing a > format like rpm or tar or zip or pkg to keep it wrapped up in. What we're > missing is code in MacPorts base to properly record everything about an > install into a binary container so that it can coexist in a MacPorts prefix > with ports that are compiled from source. Once that gets written, then we'll > need to write scripts to automatically build all ports and package them into > whatever binary format we've decided on and post the binaries to a server > somewhere. I think RPM has a difference over tarball in the sense it has its own dependency system. I can imagine a direct translation of source ports to binary RPMs to be installed in a separate prefix. Iif you want to mix them with source-built ports, a metadata addition is needed, indeed... Perhaps it can be added as either a Portfile or RPM.spec section? Basically what's funny is that Macs are the most homogeneous hardware platforms in the world. Thus having a prebuilt RPM would most likely benefit the unwashed hordes who don't want to compile. It actually can benefit the brahmins as well when they don't have the time. Surely if you want variants, build to your liking; if you just want the default, why not an RPM? Especially the dreaded GTK -- I can't imagine recompiling it all the time. Just get one bundle and be done with it. I usually compile things when I need language bindings or features. Cheers, Alexy From milosh at macports.org Sun Mar 8 15:00:15 2009 From: milosh at macports.org (Emmanuel Hainry) Date: Sun, 8 Mar 2009 23:00:15 +0100 Subject: binary rpm repos? In-Reply-To: <7c737f300903081354p287d5449yf04d868bdb99a130@mail.gmail.com> References: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> <24AD1B84-BFE8-442E-BC64-8A513EC93E41@macports.org> <7c737f300903081354p287d5449yf04d868bdb99a130@mail.gmail.com> Message-ID: <20090308230015.6311b984@velsheda.lateralis.org> On Sun, 8 Mar 2009 15:54:31 -0500 Alexy Khrabrov wrote: > On Sun, Mar 8, 2009 at 10:46 AM, Ryan Schmidt > wrote: > > I agree having binaries available would be useful. We're not > > missing a format like rpm or tar or zip or pkg to keep it wrapped > > up in. > > I think RPM has a difference over tarball in the sense it has its own > dependency system. I can imagine a direct translation of source ports > to binary RPMs to be installed in a separate prefix. If you want to > mix them with source-built ports, a metadata addition is needed, > indeed... Perhaps it can be added as either a Portfile or RPM.spec > section? The dependency does not need to be in the package, it is already in the Portfiles. macports does not need a new (or borrowed) binary package format, it already builds binary packages and prefers them over building from source when they exist: just have a look in /opt/local/var/macports/packages/$system/$arch. And we even don't need a new option for specifying if we want to install from source or from binary, the switch already exists (-b). The only missing link is that port does not download those packages, but it should not be more difficult than what 'port mirror' does for distfiles! Well obviously, there is another gap: those packages don't get uploaded anywhere at the moment, but you should feel free to share your packages. Emmanuel From deliverable at gmail.com Sun Mar 8 21:33:14 2009 From: deliverable at gmail.com (Alexy Khrabrov) Date: Sun, 8 Mar 2009 23:33:14 -0500 Subject: Why ar doesn't call ranlib on Mac? In-Reply-To: <1D3D22C8-5BCC-45AC-9C72-04E2F8B2AE27@macports.org> References: <6E56105F-260A-4CC7-AF11-05E366589191@gmail.com> <49AE9BC7.3060006@pogma.com> <49AEA078.4000008@macports.org> <49AF1114.3040403@pogma.com> <09EA2595-5C25-4C2A-BF5D-A2C68462AC0F@gmail.com> <1D3D22C8-5BCC-45AC-9C72-04E2F8B2AE27@macports.org> Message-ID: <7c737f300903082133x76f9e0f7jd23198195f3236bb@mail.gmail.com> On Wed, Mar 4, 2009 at 10:17 PM, Ryan Schmidt wrote: >> with Apple's gcc on an Intel Mac try to create a universal binary? > > No, you have to add various cflags, ldflags, etc. to get a universal. > > http://developer.apple.com/technotes/tn2005/tn2137.html OK -- I've got another "archive has no contents" error from ld today, when building a Haskell project form source. Admittedly I don't get it from MacPorts, so this is just an investigation with the most knowledgeable Mac folks I know. :) In several cases already I've found that I get these "archive has no contents" errors where some other folks don't. My XCode is the latest though, 312, gcc build 5490. I don't try to build anything universal. Why would I get the error where others wouldn't? I've checked my ar is the same as theirs. And if Peter asserts that this ar should create table of contents, why doesn't it then? Here's some interesting info on Mac ar: http://osdir.com/ml/lang.haskell.libraries/2005-03/msg00076.html Any ideas on what to check/alter? Cheers, Alexy From deliverable at gmail.com Sun Mar 8 23:01:53 2009 From: deliverable at gmail.com (Alexy Khrabrov) Date: Mon, 9 Mar 2009 01:01:53 -0500 Subject: Why ar doesn't call ranlib on Mac? In-Reply-To: <49AE9BC7.3060006@pogma.com> References: <6E56105F-260A-4CC7-AF11-05E366589191@gmail.com> <49AE9BC7.3060006@pogma.com> Message-ID: <7c737f300903082301q6946adf1h2e49cdc5727a9674@mail.gmail.com> Peter -- On Wed, Mar 4, 2009 at 10:18 AM, Peter O'Gorman wrote: > Alexy Khrabrov wrote: >> In building various Linux things from source on Mac, I've run into the >> "archive has no table of contents" problem several times. ?The fix is >> invariably to go and stick ranlib after each ar. > > What version of Mac OS X/Xcode are you using? ar, since Mac OS X 10.4 > does ranlib the archive. I filed a bug at the time asking for the -S > flag to turn off this behavior to speed up creating an archive > incrementally. > > http://www.opensource.apple.com/darwinsource/10.5.6/cctools-667.3/ar/ar.c In fact, I checked and see that ranlib is not being run! Way to check: get http://www.opensource.apple.com/darwinsource/tarballs/apsl/cctools-667.3.tar.gz -- and patch it like, case 's': (void)fprintf(stderr, "Alexy wants to run ranlib with -s\n"); options |= AR_S; break; ... if(fcall != 0){ retval = (*fcall)(argv); if(retval != EXIT_SUCCESS || ((options & AR_S) != AR_S && // NB (0) /* ((((options & AR_S) != AR_S) && !run_ranlib) && */ // NB (1) (get_unix_standard_mode() == FALSE || archive_opened_for_writing == 0))) (void)fprintf(stderr, "exiting with code %d, run_ranlib==%d\n", retval, run_ranlib); // NB exit(retval); } /* * The default is to run ranlib(1) for UNIX conformance. But if the -S * option is specified by the user we don't run it. */ if(run_ranlib){ (void)fprintf(stderr, "Alexy wants to run ranlib\n"); // NB ... -- where NB mark the additions. Now if you run, in the same directory, make # creates ar.NEW -- not universal and so is only about 31 K in size vs 63 K for /usr/bin/ar /s/src/apple/cctools/cctools-667.3/ar ./ar.NEW crs test.a *.o && echo "exit code $?" Alexy wants to run ranlib with -s Alexy got his with to run ranlib ranlib: file: test.a(vers.o) has no symbols exit code 0 /s/src/apple/cctools/cctools-667.3/ar ./ar.NEW cr test.a *.o && echo "exit code $?" exiting with code 0, run_ranlib==1 exit code 0 -- notice ranlib section governed by run_ranlib is not being run! Replacing the line NB (0) with line NB (1) does the trick -- in order to check exiting, we're checking AR_S only, not ranlib... After doing so both cases become: /s/src/apple/cctools/cctools-667.3/ar ./ar.NEW cr test.a *.o && echo "exit code $?" Alexy got his with to run ranlib ranlib: file: test.a(vers.o) has no symbols exit code 0 Makes sense? The extra parentheses around the chained &&'s can be removed. Cheers, Alexy From afb at macports.org Mon Mar 9 00:59:12 2009 From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=) Date: Mon, 9 Mar 2009 08:59:12 +0100 Subject: binary rpm repos? In-Reply-To: <20090308230015.6311b984@velsheda.lateralis.org> References: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> <24AD1B84-BFE8-442E-BC64-8A513EC93E41@macports.org> <7c737f300903081354p287d5449yf04d868bdb99a130@mail.gmail.com> <20090308230015.6311b984@velsheda.lateralis.org> Message-ID: <8F9044C2-6360-413D-AD53-3A3E9BAE0F7A@macports.org> Emmanuel Hainry wrote: > The dependency does not need to be in the package, it is already in > the > Portfiles. Actually, it does... But currently it just includes the entire Portfile into the archive, which is rather hacky. Or at least it would be nice to not require a Tcl parser in order to read the package metadata, don't you think ? > The only missing link is that port does not download those packages, > but it should not be more difficult than what 'port mirror' does for > distfiles! Well obviously, there is another gap: those packages > don't get uploaded anywhere at the moment, but you should feel free to > share your packages. Sure it does, with a patch. :-) http://trac.macports.org/ticket/8571 (3 years ago) http://trac.macports.org/ticket/10919 (2 years) It just hasn't been added yet... One problem with the current system is that the archives are sorted by OS and Arch, but not including OS version. That is, the binaries for Tiger and Leopard would go to the same file path - unless having a platform variant... It also needs digests (e.g. SHA) and signatures (e.g GPG) as well as better metadata, however those are achieved ? You should take this up on MacPorts Dev, if you want to improve it. It's still stalling on the build logs, I think. --anders From jmr at macports.org Mon Mar 9 01:24:25 2009 From: jmr at macports.org (Joshua Root) Date: Mon, 09 Mar 2009 19:24:25 +1100 Subject: binary rpm repos? In-Reply-To: <8F9044C2-6360-413D-AD53-3A3E9BAE0F7A@macports.org> References: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> <24AD1B84-BFE8-442E-BC64-8A513EC93E41@macports.org> <7c737f300903081354p287d5449yf04d868bdb99a130@mail.gmail.com> <20090308230015.6311b984@velsheda.lateralis.org> <8F9044C2-6360-413D-AD53-3A3E9BAE0F7A@macports.org> Message-ID: <49B4D239.90602@macports.org> Anders F Bj?rklund wrote: > Emmanuel Hainry wrote: >> The only missing link is that port does not download those packages, >> but it should not be more difficult than what 'port mirror' does for >> distfiles! Well obviously, there is another gap: those packages >> don't get uploaded anywhere at the moment, but you should feel free to >> share your packages. > > Sure it does, with a patch. :-) > > http://trac.macports.org/ticket/8571 (3 years ago) > http://trac.macports.org/ticket/10919 (2 years) > > It just hasn't been added yet... > > > One problem with the current system is that the archives > are sorted by OS and Arch, but not including OS version. > That is, the binaries for Tiger and Leopard would go to > the same file path - unless having a platform variant... > > It also needs digests (e.g. SHA) and signatures (e.g GPG) > as well as better metadata, however those are achieved ? > You should take this up on MacPorts Dev, if you want to > improve it. It's still stalling on the build logs, I think. That and registry support for the extra info. - Josh From afb at macports.org Mon Mar 9 02:03:00 2009 From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=) Date: Mon, 9 Mar 2009 10:03:00 +0100 Subject: binary rpm repos? In-Reply-To: <49B4D239.90602@macports.org> References: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> <24AD1B84-BFE8-442E-BC64-8A513EC93E41@macports.org> <7c737f300903081354p287d5449yf04d868bdb99a130@mail.gmail.com> <20090308230015.6311b984@velsheda.lateralis.org> <8F9044C2-6360-413D-AD53-3A3E9BAE0F7A@macports.org> <49B4D239.90602@macports.org> Message-ID: <9A2F4BDF-86B5-4EDD-9FD7-CD2C5FD867B5@macports.org> Joshua Root wrote: >> One problem with the current system is that the archives >> are sorted by OS and Arch, but not including OS version. >> That is, the binaries for Tiger and Leopard would go to >> the same file path - unless having a platform variant... >> >> It also needs digests (e.g. SHA) and signatures (e.g GPG) >> as well as better metadata, however those are achieved ? >> You should take this up on MacPorts Dev, if you want to >> improve it. It's still stalling on the build logs, I think. > > That and registry support for the extra info. The extra info is usually external to the archives, i.e. you add a SHA1SUMS with an .asc or something... Here's one example from the Linux world, for instance: ftp://ftp.slackware.com/pub/slackware/slackware-12.2/CHECKSUMS.md5 ftp://ftp.slackware.com/pub/slackware/slackware-12.2/CHECKSUMS.md5.asc The package format used (.tgz) is similar to MacPorts's. With "better metadata" I mostly meant the storage within the archive, even if there's plenty of missing fields too (but those are listed as separate issues...) Currently the Portfile contents is dumped as +PORTFILE, and then it's included with the rest of the destroot files and compressed with the same compression as well. This can be improved upon without adding registry info. --anders From bforte at adelaide.on.net Mon Mar 9 06:30:23 2009 From: bforte at adelaide.on.net (Brian Forte) Date: Mon, 9 Mar 2009 23:30:23 +1000 Subject: binary rpm repos? In-Reply-To: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> References: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> Message-ID: Gentlefolk, Alexy Khrabrov wrote: >It turns out RPM works fine on Mac: > >http://rpm4darwin.sourceforge.net/ Disclaimer: I work for Red Hat but am writing here entirely on my own time and with my own voice. Nothing that follows can or should be construed as representing Red Hat's opinion or position on anything at all. At risk of igniting an argument I believe it's worth noting there are two active RPM projects. The [RPM 4.x project][1] is maintained by Panu Matilainen, who works for Red Hat. The [RPM 5.x project][2] is maintained by Jeff Johnson, who used to work for Red Hat. Both projects are GPL-licensed and both are in active development. RPM 4.6 came out 2009/02/06 and 4.7 beta 1 was released 2009/02/26. RPM 5.1.7 came out 2009/03/07, the same day as RPM 5.2a3. The entire ['rpm controversy'][3] happened before I joined Red Hat and I'm absolutely not interested in a debate about which project is 'official' or better or improves your charisma most. Just FYI, I have exactly the same lack-of-any-sort-of-relationship with Matliainen as I do with Johnson: I've not met, corresponded or otherwise interacted with either of them. (Also, if the [Supported Linux Distributions][4] discussion on the Wikipedia Talk page for their RPM Package Manager article is anything to go by, Jeff Johnson doesn't want the controversy re-hashed.) Although I know very little about the RPM 5 project, the straight-forward mechanics of forked projects suggest it is unwise to assume an rpm package built to work with the RPM 4.x project code will work seamlessly with an RPM 5-based installation (or vice versa). This would especially be the case for packages built using versions of either RPM project released since Red Hat relaunched the 4.x project in May 2007. Since that relaunch, both projects have proceeded apace with their code-bases inevitably diverging as a consequence. NB: I'm not saying there will be a problem. RPM 5 uses the RPM 4 package format and the [RPM 4 FAQ][4] notes, among other things, that RPM [4] will stay backward compatible to 4.4.2 for a quite long time. (sic) Nonetheless the two projects are separate and, so far as I'm aware, aren't checking their changes against each other to ensure everything works perfectly between the two. Most specifically, there are differences between the projects concerning what is and isn't supported in an rpm package's .spec file. All of which is a long-winded way of suggesting it's possible an rpm package prepared for use against one RPM project might behave in an unexpected way if that package is then installed, managed or otherwise interacted with by the other RPM. The rpm4darwin project noted by Alexy Khrabrov above is based on RPM 5. If you're grabbing binary rpm packages from 'rpm-based distros' such as Red Hat Enterprise Linux, CentOS, Fedora, openSUSE or Mandriva, however, these RPMs were built using RPM 4. Finally, and FWIW, there are portfiles available for RPM [4.x and 5.x][6], although the 5.x portfiles are closer to being in sync with upstream. Regards, Brian Forte. [1]: [2]: [3]: [4]: [5]: [6]: -- Brian Forte mailto:bforte at adelaide.on.net http://betweenborders.com/ insert witty rejoinder here From peter at pogma.com Mon Mar 9 06:59:43 2009 From: peter at pogma.com (Peter O'Gorman) Date: Mon, 09 Mar 2009 08:59:43 -0500 Subject: Why ar doesn't call ranlib on Mac? In-Reply-To: <7c737f300903082301q6946adf1h2e49cdc5727a9674@mail.gmail.com> References: <6E56105F-260A-4CC7-AF11-05E366589191@gmail.com> <49AE9BC7.3060006@pogma.com> <7c737f300903082301q6946adf1h2e49cdc5727a9674@mail.gmail.com> Message-ID: <49B520CF.8000708@pogma.com> Alexy Khrabrov wrote: > Peter -- > > On Wed, Mar 4, 2009 at 10:18 AM, Peter O'Gorman wrote: >> Alexy Khrabrov wrote: >>> In building various Linux things from source on Mac, I've run into the >>> "archive has no table of contents" problem several times. The fix is >>> invariably to go and stick ranlib after each ar. >> What version of Mac OS X/Xcode are you using? ar, since Mac OS X 10.4 >> does ranlib the archive. I filed a bug at the time asking for the -S >> flag to turn off this behavior to speed up creating an archive >> incrementally. >> >> http://www.opensource.apple.com/darwinsource/10.5.6/cctools-667.3/ar/ar.c > > In fact, I checked and see that ranlib is not being run! My 10.5 system is currently unavailable, but to prove that ranlib is being run on 10.4/ppc: $ sudo -s Password: # ls -l /usr/bin/ranlib lrwxr-xr-x 1 root wheel 7 Mar 9 08:38 /usr/bin/ranlib -> libtool # rm /usr/bin/ranlib # vim /usr/bin/ranlib # cat /usr/bin/ranlib #!/bin/sh echo "ranlib $@" # chmod +x /usr/bin/ranlib # exit $ rm -f libf.a; ar cr libf.a f.o ranlib -q libf.a $ rm -f libf.a; ar crs libf.a f.o ranlib -f libf.a $ sudo -s # rm /usr/bin/ranlib # ln -s libtool /usr/bin/ranlib # ls -asl /usr/bin/ranlib 8 lrwxr-xr-x 1 root wheel 7 Mar 9 08:45 /usr/bin/ranlib -> libtool # exit $ xcodebuild -version Component versions: DevToolsCore-757.0; DevToolsSupport-733.0 Note that if your archive has no symbols it is not really useful anyway. Is it supposed to be empty? Are all the global symbols common? If so you need to run ranlib with -c. Also note, if you look at the bottom of the ld manpage on 10.5, you will see a note that ld no longer checks timestamps so that "out of date" errors should be a thing of the past. If you find that ranlib is indeed not being run on 10.5 (as I said, I can not currently check 10.5), then ensure that your COMMAND_MODE environment variable is unset and file a bug at http://bugreporter.apple.com. (btw, a quick way to check if ranlib has been run is to check for a __SYMDEF SORTED file in the archive with ar t). Hope this is some help, Peter -- Peter O'Gorman http://pogma.com From afb at macports.org Mon Mar 9 10:06:14 2009 From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=) Date: Mon, 9 Mar 2009 18:06:14 +0100 Subject: binary rpm repos? In-Reply-To: References: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> Message-ID: Brian Forte wrote: > At risk of igniting an argument I believe it's worth noting there > are two active RPM projects. There are probably better places to pick RPM fights, than on MacPorts... > The [RPM 4.x project][1] is maintained by Panu Matilainen, who > works for Red Hat. The [RPM 5.x project][2] is maintained by Jeff > Johnson, who used to work for Red Hat. > > Both projects are GPL-licensed and both are in active development. > RPM 4.6 came out 2009/02/06 and 4.7 beta 1 was released 2009/02/26. > RPM 5.1.7 came out 2009/03/07, the same day as RPM 5.2a3. Actually rpm5.org uses the LGPL license (i.e. the "Lesser"), not the GPL. RPM 4.4.9 was released 2007/05/21, RPM 4.4.2.3 was released 2008/04/01. > Although I know very little about the RPM 5 project, the straight- > forward mechanics of forked projects suggest it is unwise to assume > an rpm package built to work with the RPM 4.x project code will > work seamlessly with an RPM 5-based installation (or vice versa). > > This would especially be the case for packages built using versions > of either RPM project released since Red Hat relaunched the 4.x > project in May 2007. Since that relaunch, both projects have > proceeded apace with their code-bases inevitably diverging as a > consequence. Both projects have forked away from the original 4.4.2 release in 2005. > Nonetheless the two projects are separate and, so far as I'm aware, > aren't checking their changes against each other to ensure > everything works perfectly between the two. Most specifically, > there are differences between the projects concerning what is and > isn't supported in an rpm package's .spec file. > > All of which is a long-winded way of suggesting it's possible an > rpm package prepared for use against one RPM project might behave > in an unexpected way if that package is then installed, managed or > otherwise interacted with by the other RPM. Spec portability shouldn't matter for RPMS built from MacPorts Portfiles. > The rpm4darwin project noted by Alexy Khrabrov above is based on > RPM 5. That is not true, rpm4darwin was based on RPM 4.0 - 4.3 from 2001 - 2004. > If you're grabbing binary rpm packages from 'rpm-based distros' > such as Red Hat Enterprise Linux, CentOS, Fedora, openSUSE or > Mandriva, however, these RPMs were built using RPM 4. The binary RPM packages for Linux work rather poorly on Darwin, anyway ? > Finally, and FWIW, there are portfiles available for RPM [4.x and > 5.x][6], although the 5.x portfiles are closer to being in sync > with upstream. There are no ports for rpm.org in MacPorts at the moment, only rpm5.org --anders From ryandesign at macports.org Mon Mar 9 10:14:33 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 9 Mar 2009 12:14:33 -0500 Subject: binary rpm repos? In-Reply-To: <20090308230015.6311b984@velsheda.lateralis.org> References: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> <24AD1B84-BFE8-442E-BC64-8A513EC93E41@macports.org> <7c737f300903081354p287d5449yf04d868bdb99a130@mail.gmail.com> <20090308230015.6311b984@velsheda.lateralis.org> Message-ID: <97C6812A-27AD-4503-87C9-FF18AD3DA683@macports.org> On Mar 8, 2009, at 17:00, Emmanuel Hainry wrote: > The dependency does not need to be in the package, it is already in > the > Portfiles. macports does not need a new (or borrowed) binary package > format, Agreed. > it already builds binary packages and prefers them over > building from source when they exist: just have a look > in /opt/local/var/macports/packages/$system/$arch. And we even don't > need a new option for specifying if we want to install from source or > from binary, the switch already exists (-b). I thought an additional problem was that software installed from a binary does not get registered in the registry. > The only missing link is that port does not download those packages, > but it should not be more difficult than what 'port mirror' does for > distfiles! Well obviously, there is another gap: those packages > don't get uploaded anywhere at the moment, but you should feel free to > share your packages. We don't want arbitrary people building packages and uploading them. We want a build server (or probably one build server per supported Mac OS X / processor combination) that automatically and predictably builds packages in a clean environment so we can be sure it will work on everyone's machine. From raimue at macports.org Mon Mar 9 10:20:24 2009 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Mon, 09 Mar 2009 18:20:24 +0100 Subject: binary rpm repos? In-Reply-To: <97C6812A-27AD-4503-87C9-FF18AD3DA683@macports.org> References: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> <24AD1B84-BFE8-442E-BC64-8A513EC93E41@macports.org> <7c737f300903081354p287d5449yf04d868bdb99a130@mail.gmail.com> <20090308230015.6311b984@velsheda.lateralis.org> <97C6812A-27AD-4503-87C9-FF18AD3DA683@macports.org> Message-ID: <49B54FD8.8000506@macports.org> Ryan Schmidt wrote: > On Mar 8, 2009, at 17:00, Emmanuel Hainry wrote: >> it already builds binary packages and prefers them over >> building from source when they exist: just have a look >> in /opt/local/var/macports/packages/$system/$arch. And we even don't >> need a new option for specifying if we want to install from source or >> from binary, the switch already exists (-b). > > I thought an additional problem was that software installed from a > binary does not get registered in the registry. It works fine if you use 'port -b install', but not if you use a dmg/pkg. I would prefer if -b would work without activating archive mode before. Is there a reasoning behind this? Basically the archive skips all build steps and extracts a destroot, so I don't think we need to activate a special mode before. Rainer From brad at pixilla.com Mon Mar 9 11:16:41 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Mon, 9 Mar 2009 11:16:41 -0700 Subject: binary rpm repos? In-Reply-To: <97C6812A-27AD-4503-87C9-FF18AD3DA683@macports.org> References: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> <24AD1B84-BFE8-442E-BC64-8A513EC93E41@macports.org> <7c737f300903081354p287d5449yf04d868bdb99a130@mail.gmail.com> <20090308230015.6311b984@velsheda.lateralis.org> <97C6812A-27AD-4503-87C9-FF18AD3DA683@macports.org> Message-ID: <709EF09A-9BB0-419D-9AB7-2826858D8D5C@pixilla.com> On Mar 9, 2009, at 10:14 AM, Ryan Schmidt wrote: > > On Mar 8, 2009, at 17:00, Emmanuel Hainry wrote: > >> The dependency does not need to be in the package, it is already in >> the >> Portfiles. macports does not need a new (or borrowed) binary package >> format, > > Agreed. > >> it already builds binary packages and prefers them over >> building from source when they exist: just have a look >> in /opt/local/var/macports/packages/$system/$arch. And we even don't >> need a new option for specifying if we want to install from source or >> from binary, the switch already exists (-b). > > I thought an additional problem was that software installed from a > binary does not get registered in the registry. The port dmg approach sounds attractive for binary distribution. Absent a macports build farm what would be the process for submitting binaries? //Brad From raimue at macports.org Mon Mar 9 11:39:30 2009 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Mon, 09 Mar 2009 19:39:30 +0100 Subject: binary rpm repos? In-Reply-To: <709EF09A-9BB0-419D-9AB7-2826858D8D5C@pixilla.com> References: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> <24AD1B84-BFE8-442E-BC64-8A513EC93E41@macports.org> <7c737f300903081354p287d5449yf04d868bdb99a130@mail.gmail.com> <20090308230015.6311b984@velsheda.lateralis.org> <97C6812A-27AD-4503-87C9-FF18AD3DA683@macports.org> <709EF09A-9BB0-419D-9AB7-2826858D8D5C@pixilla.com> Message-ID: <49B56262.8020903@macports.org> Bradley Giesbrecht wrote: > Absent a macports build farm what would be the process for submitting > binaries? There is simply no process. We do not want binaries from random people. And setting up a Public Key Infrastructure (e.g. GnuPG) for trustworthy binaries would be way more complicated and take longer than just fixing the outstanding issues and get a build server. Rainer From dluke at geeklair.net Mon Mar 9 13:42:46 2009 From: dluke at geeklair.net (Daniel J. Luke) Date: Mon, 9 Mar 2009 16:42:46 -0400 Subject: binary rpm repos? In-Reply-To: <49B54FD8.8000506@macports.org> References: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> <24AD1B84-BFE8-442E-BC64-8A513EC93E41@macports.org> <7c737f300903081354p287d5449yf04d868bdb99a130@mail.gmail.com> <20090308230015.6311b984@velsheda.lateralis.org> <97C6812A-27AD-4503-87C9-FF18AD3DA683@macports.org> <49B54FD8.8000506@macports.org> Message-ID: <06E04A74-409C-41AE-9DD1-470F7C7A8625@geeklair.net> On Mar 9, 2009, at 1:20 PM, Rainer M?ller wrote: > I would prefer if -b would work without activating archive mode > before. > Is there a reasoning behind this? I think it's just an artifact of the original archive implementation. IIRC, it's not implemented as a build phase in the same way as the other phases. When I was working on remote-archive, I ended up thinking that a new phase (unarchive) would be the cleanest way to implement it, but never got around to generating a working patch. > Basically the archive skips all build > steps and extracts a destroot, so I don't think we need to activate a > special mode before. I agree. I think there was also some intention to have the portfile in the archive consulted for post-install (and uninstall) procs, but I don't think it was implemented. -- Daniel J. Luke +========================================================+ | *---------------- dluke at geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 194 bytes Desc: This is a digitally signed message part URL: From ryandesign at macports.org Mon Mar 9 13:50:27 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 9 Mar 2009 15:50:27 -0500 Subject: binary rpm repos? In-Reply-To: <06E04A74-409C-41AE-9DD1-470F7C7A8625@geeklair.net> References: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> <24AD1B84-BFE8-442E-BC64-8A513EC93E41@macports.org> <7c737f300903081354p287d5449yf04d868bdb99a130@mail.gmail.com> <20090308230015.6311b984@velsheda.lateralis.org> <97C6812A-27AD-4503-87C9-FF18AD3DA683@macports.org> <49B54FD8.8000506@macports.org> <06E04A74-409C-41AE-9DD1-470F7C7A8625@geeklair.net> Message-ID: <4C01F15F-CA09-47A9-B719-F3A9224A6389@macports.org> On Mar 9, 2009, at 15:42, Daniel J. Luke wrote: > I think there was also some intention to have the portfile in the > archive consulted for post-install (and uninstall) procs, but I > don't think it was implemented. Yes, that's a whole 'nother problem to which someone's comment recently alerted me. We not only need a way for a port to run a phase after deactivation or uninstall, but also that version of the portfile should be stored with the installed port so that the post- deactivate or post-uninstall phase that gets used is the one that was in effect at the time the port was installed, not the one that's in the current version of the portfile. From dluke at geeklair.net Mon Mar 9 15:39:57 2009 From: dluke at geeklair.net (Daniel J. Luke) Date: Mon, 9 Mar 2009 18:39:57 -0400 Subject: binary rpm repos? In-Reply-To: <4C01F15F-CA09-47A9-B719-F3A9224A6389@macports.org> References: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> <24AD1B84-BFE8-442E-BC64-8A513EC93E41@macports.org> <7c737f300903081354p287d5449yf04d868bdb99a130@mail.gmail.com> <20090308230015.6311b984@velsheda.lateralis.org> <97C6812A-27AD-4503-87C9-FF18AD3DA683@macports.org> <49B54FD8.8000506@macports.org> <06E04A74-409C-41AE-9DD1-470F7C7A8625@geeklair.net> <4C01F15F-CA09-47A9-B719-F3A9224A6389@macports.org> Message-ID: <823A9C20-3075-4A9F-B382-F62277755EF0@geeklair.net> On Mar 9, 2009, at 4:50 PM, Ryan Schmidt wrote: > Yes, that's a whole 'nother problem to which someone's comment > recently alerted me. We not only need a way for a port to run a > phase after deactivation or uninstall, but also that version of the > portfile should be stored with the installed port so that the post- > deactivate or post-uninstall phase that gets used is the one that > was in effect at the time the port was installed, not the one that's > in the current version of the portfile. And then once we get that we'll need a way to make sure we maintain enough compatibility to not break these and/or include some way of overriding them with a newer version (say if the Portfile included with the built port has a buggy uninstall method)... The last time I remember seeing list traffic about this, a look over the port tree indicated no useful use of uninstall procs (deactivate didn't exist yet and the ports tree was somewhere around 1000 ports). -- Daniel J. Luke +========================================================+ | *---------------- dluke at geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 194 bytes Desc: This is a digitally signed message part URL: From ryandesign at macports.org Mon Mar 9 15:44:20 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 9 Mar 2009 17:44:20 -0500 Subject: binary rpm repos? In-Reply-To: <823A9C20-3075-4A9F-B382-F62277755EF0@geeklair.net> References: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> <24AD1B84-BFE8-442E-BC64-8A513EC93E41@macports.org> <7c737f300903081354p287d5449yf04d868bdb99a130@mail.gmail.com> <20090308230015.6311b984@velsheda.lateralis.org> <97C6812A-27AD-4503-87C9-FF18AD3DA683@macports.org> <49B54FD8.8000506@macports.org> <06E04A74-409C-41AE-9DD1-470F7C7A8625@geeklair.net> <4C01F15F-CA09-47A9-B719-F3A9224A6389@macports.org> <823A9C20-3075-4A9F-B382-F62277755EF0@geeklair.net> Message-ID: On Mar 9, 2009, at 17:39, Daniel J. Luke wrote: > The last time I remember seeing list traffic about this, a look > over the port tree indicated no useful use of uninstall procs > (deactivate didn't exist yet and the ports tree was somewhere > around 1000 ports). There are the docbook xml ports now which print a message saying I need to run some command I'm never going to remember if I ever uninstall the port. From brad at pixilla.com Mon Mar 9 19:50:28 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Mon, 9 Mar 2009 19:50:28 -0700 Subject: binary rpm repos? In-Reply-To: References: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> <24AD1B84-BFE8-442E-BC64-8A513EC93E41@macports.org> <7c737f300903081354p287d5449yf04d868bdb99a130@mail.gmail.com> <20090308230015.6311b984@velsheda.lateralis.org> <97C6812A-27AD-4503-87C9-FF18AD3DA683@macports.org> <49B54FD8.8000506@macports.org> <06E04A74-409C-41AE-9DD1-470F7C7A8625@geeklair.net> <4C01F15F-CA09-47A9-B719-F3A9224A6389@macports.org> <823A9C20-3075-4A9F-B382-F62277755EF0@geeklair.net> Message-ID: On Mar 9, 2009, at 3:44 PM, Ryan Schmidt wrote: > > On Mar 9, 2009, at 17:39, Daniel J. Luke wrote: > >> The last time I remember seeing list traffic about this, a look >> over the port tree indicated no useful use of uninstall procs >> (deactivate didn't exist yet and the ports tree was somewhere >> around 1000 ports). > > There are the docbook xml ports now which print a message saying I > need to run some command I'm never going to remember if I ever > uninstall the port. I'm not sure what you are meaning here but if there is anything that a user NEEDS to do after uninstalling a port maybe the port uninstall command could pause with the message and wait for confirmation, bailing is the user clicks [n]. This isn't a big deal but some people may do something silly like "port uninstall installed echo p5-*" not knowing that it's going to uninstall everything. Ok, that was me :) Trying to figure out how to chain port commands. //Brad From ryandesign at macports.org Mon Mar 9 22:10:15 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 10 Mar 2009 00:10:15 -0500 Subject: binary rpm repos? In-Reply-To: References: <7c737f300903072249m6321dbabh5b39fc7f3bba38a8@mail.gmail.com> <24AD1B84-BFE8-442E-BC64-8A513EC93E41@macports.org> <7c737f300903081354p287d5449yf04d868bdb99a130@mail.gmail.com> <20090308230015.6311b984@velsheda.lateralis.org> <97C6812A-27AD-4503-87C9-FF18AD3DA683@macports.org> <49B54FD8.8000506@macports.org> <06E04A74-409C-41AE-9DD1-470F7C7A8625@geeklair.net> <4C01F15F-CA09-47A9-B719-F3A9224A6389@macports.org> <823A9C20-3075-4A9F-B382-F62277755EF0@geeklair.net> Message-ID: On Mar 9, 2009, at 21:50, Bradley Giesbrecht wrote: > On Mar 9, 2009, at 3:44 PM, Ryan Schmidt wrote: > >> There are the docbook xml ports now which print a message saying I >> need to run some command I'm never going to remember if I ever >> uninstall the port. > > I'm not sure what you are meaning here I mean that when you install e.g. the port "docbook-xml-4.5" the following message is displayed to the user: ###################################################################### # As MacPorts does not currently have a post-deactivate hook, # you will need to ensure that you manually remove the catalog # entry for this port when you uninstall it. To do so, run # "xmlcatmgr remove nextCatalog /opt/local/share/xml/docbook/4.5/ catalog.xml". ###################################################################### If MacPorts had a post-deactivate hook, the port could do this task itself and not need to bother the user with it. I know I sure as heck am not going to remember what command some port asked me to run when I uninstall it, since it's probably been months or years since I installed it. > but if there is anything that a user NEEDS to do after uninstalling > a port maybe the port uninstall command could pause with the > message and wait for confirmation, bailing is the user clicks [n]. We can't do that today because port is not interactive (except in interactive mode, but that still doesn't allow individual portfiles to interact with the user). Anyway that's also not the solution I would want; I would want proper deactivate and uninstall hooks. > This isn't a big deal but some people may do something silly like > "port uninstall installed echo p5-*" not knowing that it's going to > uninstall everything. > Ok, that was me :) Trying to figure out how to chain port commands. There is no chain of port commands. You only get one action command, but it can then act on any number of ports. In the above case, the action you asked for is "uninstall", and you asked for it to act on the pseudoport "installed" (which expands to the list of all installed ports), and the nonexistent port "echo", and all ports matching "p5-*". Here is the usage for the port command, from its manpage: port [-vdqfonRusbckixpt] [-D portdir] [-F cmdfile] [action] [actionflags] [[portname | pseudo-portname | port-url]] [[@version] [+/-variant ...] ... [option=value ...]] Part of the confusion arises because there are some keywords (for example "installed" and "outdated") which are both actions and pseudoports. As an action, "installed" shows you the versions and variants of all ports you have installed, and "outdated" shows you what ports are outdated along with their current and the newer version that's now available. As pseudoports, "installed" expands to the list of installed ports, and "outdated" to the list of outdated ports. This lets you do things like "port upgrade outdated" (upgrade all outdated ports) or "port info installed" (get info on every installed port). From blb at macports.org Mon Mar 9 22:45:34 2009 From: blb at macports.org (Bryan Blackburn) Date: Mon, 9 Mar 2009 23:45:34 -0600 Subject: binary rpm repos? In-Reply-To: References: <7c737f300903081354p287d5449yf04d868bdb99a130@mail.gmail.com> <20090308230015.6311b984@velsheda.lateralis.org> <97C6812A-27AD-4503-87C9-FF18AD3DA683@macports.org> <49B54FD8.8000506@macports.org> <06E04A74-409C-41AE-9DD1-470F7C7A8625@geeklair.net> <4C01F15F-CA09-47A9-B719-F3A9224A6389@macports.org> <823A9C20-3075-4A9F-B382-F62277755EF0@geeklair.net> Message-ID: <20090310054534.GF1036@ninagal.withay.com> On Tue, Mar 10, 2009 at 12:10:15AM -0500, Ryan Schmidt said: > On Mar 9, 2009, at 21:50, Bradley Giesbrecht wrote: [...] >> This isn't a big deal but some people may do something silly like "port >> uninstall installed echo p5-*" not knowing that it's going to uninstall >> everything. >> Ok, that was me :) Trying to figure out how to chain port commands. > > There is no chain of port commands. You only get one action command, but > it can then act on any number of ports. In the above case, the action you > asked for is "uninstall", and you asked for it to act on the pseudoport > "installed" (which expands to the list of all installed ports), and the > nonexistent port "echo", and all ports matching "p5-*". You can of course 'and' things together, eg, $ port echo installed and "p5-*" to see which p5- ports are installed; echo is a useful command to make sure you're about to affect the list of ports you really want. Of course in this particular instance, 'port installed "p5-*"' is simpler. Bryan From joniplum at gmail.com Tue Mar 10 03:46:01 2009 From: joniplum at gmail.com (chueewowee) Date: Tue, 10 Mar 2009 10:46:01 +0000 Subject: Imagemagick ...system-wide availability Message-ID: Hi, I have the installed port: /opt/local/var/macports/software/ImageMagick/6.4.8-1_0+q16 the command, 'which imagemagick' returns not found, and graphiocsconvertoer.app, similarly cannot find imagemagick ..'in /usr/local/bin' How can I make the mac[ports installation avilable on a system-wide basis? For example, what would I symlink to, if i were to place a symlink in /usr/local/bin? Cheers, John Plum From talklists at newgeo.com Tue Mar 10 04:59:10 2009 From: talklists at newgeo.com (Scott Haneda) Date: Tue, 10 Mar 2009 04:59:10 -0700 Subject: Imagemagick ...system-wide availability In-Reply-To: References: Message-ID: On Mar 10, 2009, at 3:46 AM, chueewowee wrote: > I have the installed port: > /opt/local/var/macports/software/ImageMagick/6.4.8-1_0+q16 > > the command, 'which imagemagick' returns not found, and > graphiocsconvertoer.app, similarly cannot find imagemagick ..'in > /usr/local/bin' > > How can I make the mac[ports installation avilable on a system-wide > basis? For example, what would I symlink to, if i were to place a > symlink in /usr/local/bin? All port files are in /opt/local by default, unless you change that path to somewhere else. You should have the file ~/.profile which will have altered your PATH to include /opt/local. Mine looks like this: # MacPorts Installer addition on 2009-02-24_at_21:16:33: adding an appropriate PATH var iable for use with MacPorts. export PATH=/opt/local/bin:/opt/local/sbin:$PATH # Finished adapting your PATH environment variable for use with MacPorts. # MacPorts Installer addition on 2009-02-24_at_21:16:33: adding an appropriate MANPATH variable for use with MacPorts. export MANPATH=/opt/local/share/man:$MANPATH # Finished adapting your MANPATH environment variable for use with MacPorts. If you do not have this file, you should read the docs on how to repair this issue http://trac.macports.org/wiki/InstallingMacPorts -- Scott * If you contact me off list replace talklists@ with scott@ * From jmr at macports.org Tue Mar 10 05:10:36 2009 From: jmr at macports.org (Joshua Root) Date: Tue, 10 Mar 2009 23:10:36 +1100 Subject: Imagemagick ...system-wide availability In-Reply-To: References: Message-ID: <49B658BC.5010603@macports.org> chueewowee wrote: > Hi, > > I have the installed port: > /opt/local/var/macports/software/ImageMagick/6.4.8-1_0+q16 > > > the command, 'which imagemagick' returns not found, and > graphiocsconvertoer.app, similarly cannot find imagemagick ..'in > /usr/local/bin' > > How can I make the mac[ports installation avilable on a system-wide > basis? For example, what would I symlink to, if i were to place a > symlink in /usr/local/bin? Perhaps ImageMagick is installed but not active. If so, you should just have to run `sudo port activate ImageMagick`. Alternatively, you're looking for the wrong thing. ImageMagick does not contain a command named 'imagemagick', instead it installs several commands such as convert, display and mogrify. You can see a full list of the files it installs with `port contents ImageMagick`. I'm not familiar with GraphicConverter using ImageMagick. Is it a standard feature? Where is it configured? Hopefully it doesn't just always assume /usr/local and there is a way to tell it where ImageMagick really is. - Josh From jmr at macports.org Tue Mar 10 05:28:05 2009 From: jmr at macports.org (Joshua Root) Date: Tue, 10 Mar 2009 23:28:05 +1100 Subject: Imagemagick ...system-wide availability In-Reply-To: <49B658BC.5010603@macports.org> References: <49B658BC.5010603@macports.org> Message-ID: <49B65CD5.3040901@macports.org> Joshua Root wrote: > I'm not familiar with GraphicConverter using ImageMagick. Is it a > standard feature? Where is it configured? Hopefully it doesn't just > always assume /usr/local and there is a way to tell it where ImageMagick > really is. I found it - in the Preferences, under Open -> Formats -> UNIX. Set "Path to UNIX Tool ImageMagick" to /opt/local/bin. - Josh From mukai at sfc.keio.ac.jp Tue Mar 10 09:31:45 2009 From: mukai at sfc.keio.ac.jp (Kuniaki Mukai) Date: Wed, 11 Mar 2009 01:31:45 +0900 Subject: port outdated command works propely after Porticus being installed. Message-ID: <6952B5E9-1E99-4081-BC6E-AC093F261409@sfc.keio.ac.jp> I installed so far more than 400 ports. Thanks for Macports. For these months, may be more than a half of a year, the 'port outdated' command has given nothing to me whenever I checked. Although it was strange, but I persuaded myself to think MacPorts were now so stable that no update was neccessary. However, after I installed recently the Porticus application, I found that every time after doing the selfupdate menu of the application, the same command 'port outdated' shows many outdated ports information to update. It seems as if macports does not work properly without the Porticus. How can MacPorts's 'outdated' command be made to work properly without helps of other applications ? As a fact of matter, I am afraid that some files of Macports of my mac are broken. MacOSX 10.5.6 K. Mukai From jmr at macports.org Tue Mar 10 09:37:33 2009 From: jmr at macports.org (Joshua Root) Date: Wed, 11 Mar 2009 03:37:33 +1100 Subject: port outdated command works propely after Porticus being installed. In-Reply-To: <6952B5E9-1E99-4081-BC6E-AC093F261409@sfc.keio.ac.jp> References: <6952B5E9-1E99-4081-BC6E-AC093F261409@sfc.keio.ac.jp> Message-ID: <49B6974D.2090800@macports.org> Kuniaki Mukai wrote: > I installed so far more than 400 ports. Thanks for Macports. > For these months, may be more than a half of a year, > the 'port outdated' command has given nothing > to me whenever I checked. Although it was > strange, but I persuaded myself to think MacPorts > were now so stable that no update was neccessary. > > However, after I installed recently the Porticus application, > I found that every time after doing the selfupdate menu > of the application, the same command > 'port outdated' shows many outdated ports information > to update. It seems as if macports does not work > properly without the Porticus. > > How can MacPorts's 'outdated' command be made to work > properly without helps of other applications ? > As a fact of matter, I am afraid that some files of Macports > of my mac are broken. > > MacOSX 10.5.6 Did you ever run `sudo port selfupdate` or `sudo port sync` before installing Porticus? - Josh From mukai at sfc.keio.ac.jp Tue Mar 10 09:43:48 2009 From: mukai at sfc.keio.ac.jp (Kuniaki Mukai) Date: Wed, 11 Mar 2009 01:43:48 +0900 Subject: port outdated command works propely after Porticus being installed. In-Reply-To: <49B6974D.2090800@macports.org> References: <6952B5E9-1E99-4081-BC6E-AC093F261409@sfc.keio.ac.jp> <49B6974D.2090800@macports.org> Message-ID: <200DAE34-AE61-42FC-A310-532C11813104@sfc.keio.ac.jp> On Mar 11, 2009, at 1:37 AM, Joshua Root wrote: > Kuniaki Mukai wrote: >> I installed so far more than 400 ports. Thanks for Macports. >> For these months, may be more than a half of a year, >> the 'port outdated' command has given nothing >> to me whenever I checked. Although it was >> strange, but I persuaded myself to think MacPorts >> were now so stable that no update was neccessary. >> >> However, after I installed recently the Porticus application, >> I found that every time after doing the selfupdate menu >> of the application, the same command >> 'port outdated' shows many outdated ports information >> to update. It seems as if macports does not work >> properly without the Porticus. >> >> How can MacPorts's 'outdated' command be made to work >> properly without helps of other applications ? >> As a fact of matter, I am afraid that some files of Macports >> of my mac are broken. >> >> MacOSX 10.5.6 > > Did you ever run `sudo port selfupdate` or `sudo port sync` before > installing Porticus? Yes, I did. I will do it for sure whether it is reproducible even now or not. K. Mukai > > - Josh > From francis at devrx.org Tue Mar 10 10:20:16 2009 From: francis at devrx.org (Francis Devereux) Date: Tue, 10 Mar 2009 17:20:16 +0000 Subject: Error in mod_wsgi Portfile? Message-ID: <49FD50C6-CCC9-4EEE-A52E-9DA1F8D32D99@devrx.org> Hi, I think that the message printed by www/mod_wsgi/Portfile is incorrect. The line that currently reads: ui_msg "# LoadModule python_module modules/mod_wsgi.so" should read: ui_msg "# LoadModule wsgi_module modules/mod_wsgi.so" If the current instructions are followed, attempting to start Apache gives the following error: jupiter LaunchDaemons # /opt/local/apache2/bin/apachectl start httpd: Syntax error on line 116 of /opt/local/apache2/conf/httpd.conf: Can't locate API module structure `python_module' in file /opt/local/ apache2/modules/mod_wsgi.so: dlsym(0x404e10, python_module): symbol not found Regards, Francis From joniplum at gmail.com Tue Mar 10 15:39:11 2009 From: joniplum at gmail.com (chueewowee) Date: Tue, 10 Mar 2009 22:39:11 +0000 Subject: Imagemagick ...system-wide availability References: Message-ID: In article , Scott Haneda wrote: > If you do not have this file, you should read the docs on how to > repair this issue > http://trac.macports.org/wiki/InstallingMacPorts > -- Many thanks Scott. I have those settings in my .bashrc file. Joshua's discovery has paved my way...However, i was unsure about the command 'imagemagick', and so it became questionable at this point, and you have clarified that for me. I suppose then, that any programme requiring imagemagick needs to be told where to find it, unless it conducts a search. ---- John Plum From joniplum at gmail.com Tue Mar 10 15:44:18 2009 From: joniplum at gmail.com (chueewowee) Date: Tue, 10 Mar 2009 22:44:18 +0000 Subject: Imagemagick ...system-wide availability References: <49B658BC.5010603@macports.org> <49B65CD5.3040901@macports.org> Message-ID: In article <49B65CD5.3040901 at macports.org>, Joshua Root wrote: > > I found it - in the Preferences, under Open -> Formats -> UNIX. Set > "Path to UNIX Tool ImageMagick" to /opt/local/bin. Great Sleuth you are! Thanks, Joshua. I only use GraphicConverter occasionally, had it years, and didn't find the preference setting upon my one cursory look. I intend to use it a lot more frequently. I needed it in order to open and quickly modify an .svg file. The programme, you may know about has a venerable history and following. My Fireworks MX failed to load up once again....no font removal could solve the problem (as per official recommendation and prior experience), so I had been stuck. ---- John Plum From artie.ziff at gmail.com Tue Mar 10 17:10:23 2009 From: artie.ziff at gmail.com (Artie Ziff) Date: Tue, 10 Mar 2009 17:10:23 -0700 Subject: Error: Port render not found Message-ID: <49B7016F.1000503@gmail.com> Hello, Thanks to Bryan for the *very* helpful user notes (reminders). I had not resolved that Tiger => Leopard upgrade snafu until now. >From that page I saw this command: sudo port clean --work I used it as so: sudo port clean --work installed It upchucked this: ---> Cleaning antlr ---> Cleaning apache-ant ---> Cleaning apache2 . . . ---> Cleaning rb-rubygems ---> Cleaning rb-sqlite3 ---> Cleaning rb-termios ---> Cleaning readline ---> Cleaning readline Error: Port render not found Just posting for perspective. Is this a bug? Or yet another config problem with my system? Cheers! Art From jeremyhu at macports.org Tue Mar 10 17:43:07 2009 From: jeremyhu at macports.org (Jeremy Huddleston) Date: Tue, 10 Mar 2009 17:43:07 -0700 Subject: Error: Port render not found In-Reply-To: <49B7016F.1000503@gmail.com> References: <49B7016F.1000503@gmail.com> Message-ID: <60210C74-2364-465C-A264-870AF6D463CB@macports.org> The render port was a stub that was nuked. Just uninstall render. On Mar 10, 2009, at 17:10, Artie Ziff wrote: > Hello, > > Thanks to Bryan for the *very* helpful user notes (reminders). > I had not resolved that Tiger => Leopard upgrade snafu until now. > >> From that page I saw this command: > > sudo port clean --work > > I used it as so: > > sudo port clean --work installed > > It upchucked this: > > ---> Cleaning antlr > ---> Cleaning apache-ant > ---> Cleaning apache2 > . > . > . > ---> Cleaning rb-rubygems > ---> Cleaning rb-sqlite3 > ---> Cleaning rb-termios > ---> Cleaning readline > ---> Cleaning readline > Error: Port render not found > > > Just posting for perspective. > Is this a bug? > Or yet another config problem with my system? > > > Cheers! > Art > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From jpg at gmx.com Tue Mar 10 18:04:52 2009 From: jpg at gmx.com (Jamie Griffin) Date: Wed, 11 Mar 2009 01:04:52 +0000 Subject: offlineimap/python problem Message-ID: <20090311010452.GA13031@Macbook.local> Hi I've installed offlineimap just now using macports. The build process went ok, except when i try to run offlineimap i get this error: ------------------------------------------- Traceback (most recent call last): File "/opt/local/bin/offlineimap", line 20, in from offlineimap import init File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/offlineimap/init.py", line 20, in from offlineimap import imapserver, repository, folder, mbnames, threadutil, version, syncmaster, accounts File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/offlineimap/folder/__init__.py", line 1, in import Base, Gmail, IMAP, Maildir, LocalStatus File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/offlineimap/folder/Maildir.py", line 23, in import os.path, os, re, time, socket, md5 File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/md5.py", line 6, in from hashlib import md5 File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/hashlib.py", line 133, in md5 = __get_builtin_constructor('md5') File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/hashlib.py", line 60, in __get_builtin_constructor import _md5 ImportError: No module named _md5 ------------------------------------ I have no idea how to fix this. Has anyne else had this issue and does onyone know what i can do to put it right. I'm using mac os x 10.4.11 with the latest macports installation for tiger. The version of offlineimap installed is 6.0.3_0 TIA, Jamie From blb at macports.org Tue Mar 10 19:25:23 2009 From: blb at macports.org (Bryan Blackburn) Date: Tue, 10 Mar 2009 20:25:23 -0600 Subject: offlineimap/python problem In-Reply-To: <20090311010452.GA13031@Macbook.local> References: <20090311010452.GA13031@Macbook.local> Message-ID: <20090311022523.GH1035@ninagal.withay.com> On Wed, Mar 11, 2009 at 01:04:52AM +0000, Jamie Griffin said: > > Hi > > I've installed offlineimap just now using macports. The build process went ok, except when i try to run offlineimap i get this error: [...] > File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/hashlib.py", line 60, in __get_builtin_constructor > import _md5 > ImportError: No module named _md5 > > ------------------------------------ > > I have no idea how to fix this. Has anyne else had this issue and does onyone know what i can do to put it right. Try installing the py25-hashlib port, if that fixes it then it needs to be a dependency for offlineimap. Bryan > > I'm using mac os x 10.4.11 with the latest macports installation for tiger. > > The version of offlineimap installed is 6.0.3_0 > > TIA, > > Jamie From serra at atmo.arizona.edu Tue Mar 10 21:42:01 2009 From: serra at atmo.arizona.edu (Yolande Serra) Date: Tue, 10 Mar 2009 21:42:01 -0700 Subject: macports netcdf toolbox for mac OS 10.6 and fortran Message-ID: <82FD5FE1-DFDE-4404-8B09-D053AEBA0138@atmo.arizona.edu> I installed macports netcdf +g95 variant on my new intel power mac dual quad core running 10.5.6. The install had no errors but when I try to compile code requiring the netcdf library it gives the following errors: g95 -I/opt/local/include regress_olr_CLLJeast.f handle_err.f get_time.f -o regress_olr_CLLJeast -L/opt/local/lib -lnetcdff -ludunits Undefined symbols: "_nf_inq_compound_fieldname__", referenced from: _U74.678 in ccaNDF8v.o _U82.619 in cca57thG.o "_nf_insert_compound__", referenced from: _U119.769 in ccaNDF8v.o _U128.711 in cca57thG.o "_nf_create_par__", referenced from: _U13.546 in ccaNDF8v.o _U16.487 in cca57thG.o .....all netcdf commands in code are listed ending with ld: symbol(s) not found I should mention that this same code compiles on my other mac which is a powerpc running 10.4.11. In that case I have netcdf 3.6 installed with F90/F77 support. I tried compiling the code with both g95 and gfortran (also a macport install) but with no luck. I also tried the - fno-underscoring option but that did not work either (not that I really thought it would). I also tried with -lnetcdf without the extra f (this is how I did it on the old mac because it only had one library). Why does your install come with two libraries? The netcdf library build on the ncar website for my mac does not come this way. I may have to just install that one elsewhere but wanted to see if I could get this one working since I need it anyway to be able to use my grads2 install with netcdf since you don't share libraries... thanks, Yolande Dr. Yolande Serra, Assoc. Research Faculty Institute of Atmospheric Physics University of Arizona (520) 621-6619 serra at atmo.arizona.edu From mukai at sfc.keio.ac.jp Tue Mar 10 22:32:38 2009 From: mukai at sfc.keio.ac.jp (Kuniaki Mukai) Date: Wed, 11 Mar 2009 14:32:38 +0900 Subject: port outdated command works propely after Porticus being installed. In-Reply-To: <49B6974D.2090800@macports.org> References: <6952B5E9-1E99-4081-BC6E-AC093F261409@sfc.keio.ac.jp> <49B6974D.2090800@macports.org> Message-ID: Here is a command line log of MacPorts. % port outdated The following installed ports are outdated: mpfr 2.4.1-p2_0 < 2.4.1-p4_0 % sudo port selfupdate Password: MacPorts base version 1.700 installed Downloaded MacPorts base version 1.700 The MacPorts installation is not outdated so it was not updated % sudo port sync (Launch Porticus and do the menu item selfupdate, which shows only bash and graphviz are outdated. ) % port outdated The following installed ports are outdated: bash 4.0.0_0 < 4.0.10_0 graphviz 2.22.0_0 < 2.22.1_0 mpfr 2.4.1-p2_0 < 2.4.1-p4_0 % It seems that this log still suggests that 'port outdated' command works correct only after Porticus selfupdate menu being done, as I suspect. K. Mukai On Mar 11, 2009, at 1:37 AM, Joshua Root wrote: > Kuniaki Mukai wrote: >> I installed so far more than 400 ports. Thanks for Macports. >> For these months, may be more than a half of a year, >> the 'port outdated' command has given nothing >> to me whenever I checked. Although it was >> strange, but I persuaded myself to think MacPorts >> were now so stable that no update was neccessary. >> >> However, after I installed recently the Porticus application, >> I found that every time after doing the selfupdate menu >> of the application, the same command >> 'port outdated' shows many outdated ports information >> to update. It seems as if macports does not work >> properly without the Porticus. >> >> How can MacPorts's 'outdated' command be made to work >> properly without helps of other applications ? >> As a fact of matter, I am afraid that some files of Macports >> of my mac are broken. >> >> MacOSX 10.5.6 > > Did you ever run `sudo port selfupdate` or `sudo port sync` before > installing Porticus? Yes, I did. I will do it for sure whether it is reproducible even now or not. K. Mukai > > - Josh > _______________________________________________ macports-users mailing list macports-users at lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From frstan at bellsouth.net Tue Mar 10 22:45:33 2009 From: frstan at bellsouth.net (William Davis) Date: Wed, 11 Mar 2009 01:45:33 -0400 Subject: port outdated command works propely after Porticus being installed. In-Reply-To: References: <6952B5E9-1E99-4081-BC6E-AC093F261409@sfc.keio.ac.jp> <49B6974D.2090800@macports.org> Message-ID: <8AFCCD75-B227-4192-971A-3F2227ED0FD2@bellsouth.net> On Mar 11, 2009, at 1:32 AM, Kuniaki Mukai wrote: > > Here is a command line log of MacPorts. > > % port outdated > The following installed ports are outdated: > mpfr 2.4.1-p2_0 < 2.4.1-p4_0 > % sudo port selfupdate > Password: > > MacPorts base version 1.700 installed > Downloaded MacPorts base version 1.700 > > The MacPorts installation is not outdated so it was not updated > % sudo port sync > > (Launch Porticus and do the menu item selfupdate, which > shows only bash and graphviz are outdated. ) > > % port outdated > The following installed ports are outdated: > bash 4.0.0_0 < 4.0.10_0 > graphviz 2.22.0_0 < 2.22.1_0 > mpfr 2.4.1-p2_0 < 2.4.1-p4_0 > % > > It seems that this log still suggests that 'port outdated' command > works correct only after Porticus selfupdate menu being done, > as I suspect. > > > K. Mukai > You need to do "sudo port -d selfupdate" before port outdated not after. You see "selfupdate" is what causes your own port file index to get updated. Port didnt know about bash and graphviz because your index was not "up-to-date" when up gave the "port outdated" command. All porticus did was give port the same selfupdate command you could have given on the command line before you gave the port outdated command. William Davis frstanATbellsouthDOTnet Mac OS X.5.6 Darwin 9.5.0 XQuartz 2.3.3_rc1 (xorg-server 1.4.2-apple36) Mac Mini Intel Duo @ 1.86 GHz Mundus vult decepi, ego non From mukai at sfc.keio.ac.jp Tue Mar 10 23:09:10 2009 From: mukai at sfc.keio.ac.jp (Kuniaki Mukai) Date: Wed, 11 Mar 2009 15:09:10 +0900 Subject: port outdated command works propely after Porticus being installed. In-Reply-To: <8AFCCD75-B227-4192-971A-3F2227ED0FD2@bellsouth.net> References: <6952B5E9-1E99-4081-BC6E-AC093F261409@sfc.keio.ac.jp> <49B6974D.2090800@macports.org> <8AFCCD75-B227-4192-971A-3F2227ED0FD2@bellsouth.net> Message-ID: On Mar 11, 2009, at 2:45 PM, William Davis wrote: > You need to do "sudo port -d selfupdate" before > port outdated not after. Thank you for help. I will do so henceforth. I thought, without reading manual in details, 'selfupdate' means updating both MacPorts base and port index, and 'sync' updating only port index. Kuniaki Mukai > > On Mar 11, 2009, at 1:32 AM, Kuniaki Mukai wrote: > >> >> Here is a command line log of MacPorts. >> >> % port outdated >> The following installed ports are outdated: >> mpfr 2.4.1-p2_0 < 2.4.1-p4_0 >> % sudo port selfupdate >> Password: >> >> MacPorts base version 1.700 installed >> Downloaded MacPorts base version 1.700 >> >> The MacPorts installation is not outdated so it was not updated >> % sudo port sync >> >> (Launch Porticus and do the menu item selfupdate, which >> shows only bash and graphviz are outdated. ) >> >> % port outdated >> The following installed ports are outdated: >> bash 4.0.0_0 < 4.0.10_0 >> graphviz 2.22.0_0 < 2.22.1_0 >> mpfr 2.4.1-p2_0 < 2.4.1-p4_0 >> % >> >> It seems that this log still suggests that 'port outdated' command >> works correct only after Porticus selfupdate menu being done, >> as I suspect. >> >> >> K. Mukai >> > > > You need to do "sudo port -d selfupdate" before > port outdated not after. > You see "selfupdate" is what causes your own port file index to get updated. Port didnt know about bash and graphviz because your index was not "up-to-date" when up gave the "port outdated" command. All porticus did was give port the same selfupdate command you could have given on the command line before you gave the port outdated command. > > William Davis > frstanATbellsouthDOTnet > Mac OS X.5.6 Darwin 9.5.0 > XQuartz 2.3.3_rc1 (xorg-server 1.4.2-apple36) > Mac Mini Intel Duo @ 1.86 GHz > > Mundus vult decepi, ego non > From jmr at macports.org Wed Mar 11 00:07:53 2009 From: jmr at macports.org (Joshua Root) Date: Wed, 11 Mar 2009 18:07:53 +1100 Subject: Error: Port render not found In-Reply-To: <60210C74-2364-465C-A264-870AF6D463CB@macports.org> References: <49B7016F.1000503@gmail.com> <60210C74-2364-465C-A264-870AF6D463CB@macports.org> Message-ID: <49B76349.3030707@macports.org> You'll probably have to use -f, i.e. `sudo port -f uninstall render`. Jeremy Huddleston wrote: > The render port was a stub that was nuked. Just uninstall render. > > On Mar 10, 2009, at 17:10, Artie Ziff wrote: > >> Hello, >> >> Thanks to Bryan for the *very* helpful user notes (reminders). >> I had not resolved that Tiger => Leopard upgrade snafu until now. >> >>> From that page I saw this command: >> >> sudo port clean --work >> >> I used it as so: >> >> sudo port clean --work installed >> >> It upchucked this: >> >> ---> Cleaning antlr >> ---> Cleaning apache-ant >> ---> Cleaning apache2 >> . >> . >> . >> ---> Cleaning rb-rubygems >> ---> Cleaning rb-sqlite3 >> ---> Cleaning rb-termios >> ---> Cleaning readline >> ---> Cleaning readline >> Error: Port render not found >> >> >> Just posting for perspective. >> Is this a bug? >> Or yet another config problem with my system? >> >> >> Cheers! >> Art >> _______________________________________________ >> macports-users mailing list >> macports-users at lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > From jmr at macports.org Wed Mar 11 00:12:21 2009 From: jmr at macports.org (Joshua Root) Date: Wed, 11 Mar 2009 18:12:21 +1100 Subject: port outdated command works propely after Porticus being installed. In-Reply-To: References: <6952B5E9-1E99-4081-BC6E-AC093F261409@sfc.keio.ac.jp> <49B6974D.2090800@macports.org> <8AFCCD75-B227-4192-971A-3F2227ED0FD2@bellsouth.net> Message-ID: <49B76455.6010405@macports.org> Kuniaki Mukai wrote: > On Mar 11, 2009, at 2:45 PM, William Davis wrote: > >> You need to do "sudo port -d selfupdate" before >> port outdated not after. > > Thank you for help. I will do so henceforth. > > I thought, without reading manual in details, 'selfupdate' means > updating both MacPorts base and port index, and > 'sync' updating only port index. That's correct, but in the log you posted, you ran `port outdated` before you ran sync or selfupdate, but not between sync and running Porticus. - Josh From mukai at sfc.keio.ac.jp Wed Mar 11 02:30:50 2009 From: mukai at sfc.keio.ac.jp (Kuniaki Mukai) Date: Wed, 11 Mar 2009 18:30:50 +0900 Subject: port outdated command works propely after Porticus being installed. In-Reply-To: <49B76455.6010405@macports.org> References: <6952B5E9-1E99-4081-BC6E-AC093F261409@sfc.keio.ac.jp> <49B6974D.2090800@macports.org> <8AFCCD75-B227-4192-971A-3F2227ED0FD2@bellsouth.net> <49B76455.6010405@macports.org> Message-ID: <7F2B9D3B-2D4F-4450-9F68-63006A6F9668@sfc.keio.ac.jp> On Mar 11, 2009, at 4:12 PM, Joshua Root wrote: > Kuniaki Mukai wrote: >> On Mar 11, 2009, at 2:45 PM, William Davis wrote: >> >>> You need to do "sudo port -d selfupdate" before >>> port outdated not after. >> >> Thank you for help. I will do so henceforth. >> >> I thought, without reading manual in details, 'selfupdate' means >> updating both MacPorts base and port index, and >> 'sync' updating only port index. > > That's correct, but in the log you posted, you ran `port outdated` > before you ran sync or selfupdate, but not between sync and running > Porticus. Thank you for clarifying. Yes, I agree on that the log is not to the point. However I have found there is still something wrong with MacPorts on my mac. Here is a new log of 'port outdated'. % sudo port sync Password: % sudo port selfupdate MacPorts base version 1.700 installed Downloaded MacPorts base version 1.700 The MacPorts installation is not outdated so it was not updated ( Porticus menu item 'Self Update' being done) % port outdated The following installed ports are outdated: bash 4.0.0_0 < 4.0.10_0 mpfr 2.4.1-p2_0 < 2.4.1-p4_0 The new log keeps me confused. Why does 'port outdated' command work correct only after selfupdating by Porticus , even after 'sudo port sync' or 'sudo port selfupdate.' Kuniaki Mukai > > - Josh > From milosh at macports.org Wed Mar 11 02:50:45 2009 From: milosh at macports.org (Emmanuel Hainry) Date: Wed, 11 Mar 2009 10:50:45 +0100 Subject: port outdated command works propely after Porticus being installed. In-Reply-To: <7F2B9D3B-2D4F-4450-9F68-63006A6F9668@sfc.keio.ac.jp> References: <6952B5E9-1E99-4081-BC6E-AC093F261409@sfc.keio.ac.jp> <49B6974D.2090800@macports.org> <8AFCCD75-B227-4192-971A-3F2227ED0FD2@bellsouth.net> <49B76455.6010405@macports.org> <7F2B9D3B-2D4F-4450-9F68-63006A6F9668@sfc.keio.ac.jp> Message-ID: <20090311095045.GA3046@velsheda.lateralis.org> Citando Kuniaki Mukai : > > However I have found there is still something wrong > with MacPorts on my mac. Here is a new log > of 'port outdated'. > > % sudo port sync > Password: > % sudo port selfupdate > > MacPorts base version 1.700 installed > Downloaded MacPorts base version 1.700 > > The MacPorts installation is not outdated so it was not updated > > ( Porticus menu item 'Self Update' being done) > > % port outdated > The following installed ports are outdated: > bash 4.0.0_0 < 4.0.10_0 > mpfr 2.4.1-p2_0 < 2.4.1-p4_0 > > > The new log keeps me confused. Why does 'port outdated' command work correct > only after selfupdating by Porticus , even after 'sudo port sync' or 'sudo port selfupdate.' > > Kuniaki Mukai 'sync' updates the port index which means the port definitions. 'selfupdate' does 'sync' and updates macports itself (the "port" command). None of them do upgrade the ports themselves. So port sync; port outdated will list the ports whose definitions have been updated. If you want to upgrade those ports, you need to port update bash then port outdated will only list the ports for which there is still a definition (portfile) newer than what you have installed. To sum up, there are portfile which are definitions of ports, that you can sync with the 'sync' command; and there are softwares themselves (port installed will list what you have installed, port outdated what you can upgrade). Porticus does nothing else than using those commands. Best, Emmanuel -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature URL: From jpg at gmx.com Wed Mar 11 02:54:30 2009 From: jpg at gmx.com (Jamie Griffin) Date: Wed, 11 Mar 2009 09:54:30 +0000 Subject: offlineimap/ssl problem Message-ID: <20090311095430.GA299@Macbook> Hi The earlier problem i had with md5 import was sorted by Brians advice to install the py25-hashlib port. Now, i've got an issue when the option ssl = yes is set in the .offlinimaprc Here's the error output: ----------------------------------------------------------------------- Thread 'Account sync GMX' terminated with exception: Traceback (most recent call last): File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/offlineimap/threadutil.py", line 149, in run Thread.run(self) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/threading.py", line 446, in run self.__target(*self.__args, **self.__kwargs) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/offlineimap/accounts.py", line 108, in syncrunner self.sync() File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/offlineimap/accounts.py", line 142, in sync remoterepos.syncfoldersto(localrepos, [statusrepos]) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/offlineimap/repository/Base.py", line 135, in syncfoldersto srcfolders = src.getfolders() File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/offlineimap/repository/IMAP.py", line 194, in getfolders imapobj = self.imapserver.acquireconnection() File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/offlineimap/imapserver.py", line 224, in acquireconnection self.sslclientkey, self.sslclientcert) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/imaplib.py", line 1128, in __init__ IMAP4.__init__(self, host, port) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/imaplib.py", line 163, in __init__ self.open(host, port) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/offlineimap/imapserver.py", line 65, in open imaplibutil.new_open_ssl(self, host, port) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/offlineimap/imaplibutil.py", line 172, in new_open_ssl self.sslobj = socket.ssl(self.sock._sock, self.keyfile, self.certfile) AttributeError: 'module' object has no attribute 'ssl' -------------------------------------------------------------------------- I'm not sure what might be causing this, again, is anyone able to give any advice. I understand i may need to ask on the 'offlineimap list', any information would b appreciated. Jamie From jmr at macports.org Wed Mar 11 04:09:23 2009 From: jmr at macports.org (Joshua Root) Date: Wed, 11 Mar 2009 22:09:23 +1100 Subject: offlineimap/ssl problem In-Reply-To: <20090311095430.GA299@Macbook> References: <20090311095430.GA299@Macbook> Message-ID: <49B79BE3.3000005@macports.org> Jamie Griffin wrote: > Hi > > The earlier problem i had with md5 import was sorted by Brians advice to install the py25-hashlib port. > > Now, i've got an issue when the option ssl = yes is set in the .offlinimaprc > > Here's the error output: > ----------------------------------------------------------------------- > Thread 'Account sync GMX' terminated with exception: > Traceback (most recent call last): > File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/offlineimap/threadutil.py", line 149, in run > Thread.run(self) > File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/threading.py", line 446, in run > self.__target(*self.__args, **self.__kwargs) > File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/offlineimap/accounts.py", line 108, in syncrunner > self.sync() > File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/offlineimap/accounts.py", line 142, in sync > remoterepos.syncfoldersto(localrepos, [statusrepos]) > File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/offlineimap/repository/Base.py", line 135, in syncfoldersto > srcfolders = src.getfolders() > File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/offlineimap/repository/IMAP.py", line 194, in getfolders > imapobj = self.imapserver.acquireconnection() > File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/offlineimap/imapserver.py", line 224, in acquireconnection > self.sslclientkey, self.sslclientcert) > File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/imaplib.py", line 1128, in __init__ > IMAP4.__init__(self, host, port) > File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/imaplib.py", line 163, in __init__ > self.open(host, port) > File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/offlineimap/imapserver.py", line 65, in open > imaplibutil.new_open_ssl(self, host, port) > File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/offlineimap/imaplibutil.py", line 172, in new_open_ssl > self.sslobj = socket.ssl(self.sock._sock, self.keyfile, self.certfile) > AttributeError: 'module' object has no attribute 'ssl' > -------------------------------------------------------------------------- > > I'm not sure what might be causing this, again, is anyone able to give any advice. I understand i may need to ask on the 'offlineimap list', any information would b appreciated. Looks like it needs py25-socket-ssl. This should be added as a dependency along with py25-hashlib. - Josh From jpg at gmx.com Wed Mar 11 04:38:50 2009 From: jpg at gmx.com (Jamie Griffin) Date: Wed, 11 Mar 2009 11:38:50 +0000 Subject: offlineimap/ssl problem In-Reply-To: <49B79BE3.3000005@macports.org> References: <20090311095430.GA299@Macbook> <49B79BE3.3000005@macports.org> Message-ID: <20090311113850.GA10284@Macbook> On Wed 11.Mar'09 at 22:09:23 +1100, Joshua Root wrote: > Looks like it needs py25-socket-ssl. This should be added as a > dependency along with py25-hashlib. > > - Josh That did the trick. Thanks for your help. Jamie -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 194 bytes Desc: not available URL: From mukai at sfc.keio.ac.jp Wed Mar 11 06:21:03 2009 From: mukai at sfc.keio.ac.jp (Kuniaki Mukai) Date: Wed, 11 Mar 2009 22:21:03 +0900 Subject: port outdated command works propely after Porticus being installed. In-Reply-To: <20090311095045.GA3046@velsheda.lateralis.org> References: <6952B5E9-1E99-4081-BC6E-AC093F261409@sfc.keio.ac.jp> <49B6974D.2090800@macports.org> <8AFCCD75-B227-4192-971A-3F2227ED0FD2@bellsouth.net> <49B76455.6010405@macports.org> <7F2B9D3B-2D4F-4450-9F68-63006A6F9668@sfc.keio.ac.jp> <20090311095045.GA3046@velsheda.lateralis.org> Message-ID: <28FA9BF1-1F89-4A1D-80F0-2327E988E421@sfc.keio.ac.jp> Now everything is OK. Thank you very much. > Porticus does nothing else than using those commands. I am grateful for important information. It makes sure that at least Porticus does nothing harmful to MacPorts. Kuniaki On Mar 11, 2009, at 6:50 PM, Emmanuel Hainry wrote: > Citando Kuniaki Mukai : >> >> However I have found there is still something wrong >> with MacPorts on my mac. Here is a new log >> of 'port outdated'. >> >> % sudo port sync >> Password: >> % sudo port selfupdate >> >> MacPorts base version 1.700 installed >> Downloaded MacPorts base version 1.700 >> >> The MacPorts installation is not outdated so it was not updated >> >> ( Porticus menu item 'Self Update' being done) >> >> % port outdated >> The following installed ports are outdated: >> bash 4.0.0_0 < 4.0.10_0 >> mpfr 2.4.1-p2_0 < 2.4.1-p4_0 >> >> >> The new log keeps me confused. Why does 'port outdated' command work correct >> only after selfupdating by Porticus , even after 'sudo port sync' or 'sudo port selfupdate.' >> >> Kuniaki Mukai > > > 'sync' updates the port index which means the port definitions. > 'selfupdate' does 'sync' and updates macports itself (the "port" > command). None of them do upgrade the ports themselves. > > So > > port sync; port outdated > > will list the ports whose definitions have been updated. If you want to > upgrade those ports, you need to > > port update bash > > then port outdated will only list the ports for which there is still a > definition (portfile) newer than what you have installed. > > To sum up, there are portfile which are definitions of ports, that you > can sync with the 'sync' command; and there are softwares themselves > (port installed will list what you have installed, port outdated what > you can upgrade). > > Porticus does nothing else than using those commands. > > Best, > > Emmanuel > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From mukai at sfc.keio.ac.jp Wed Mar 11 12:00:09 2009 From: mukai at sfc.keio.ac.jp (Kuniaki Mukai) Date: Thu, 12 Mar 2009 04:00:09 +0900 Subject: Can't install cadabra Message-ID: <4A126E05-F755-4EEE-8AE9-A1186667D35C@sfc.keio.ac.jp> I can't install cadabra. Here is the debug mode log with error message. I am sorry for the full long log text. I could not snip any irrelevant part of it because of my little knowledge on installation. I appreciate any help for installing cadabra. Kuniaki Mukai % sudo port -d install cadabra DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/math/cadabra DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/math/cadabra DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: adding the default universal variant DEBUG: Requested variant darwin is not provided by port cadabra. DEBUG: Requested variant i386 is not provided by port cadabra. DEBUG: Requested variant macosx is not provided by port cadabra. DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/modglue DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/modglue DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: adding the default universal variant DEBUG: Requested variant darwin is not provided by port modglue. DEBUG: Requested variant i386 is not provided by port modglue. DEBUG: Requested variant macosx is not provided by port modglue. DEBUG: Searching for dependency: modglue DEBUG: Found Dependency: receipt exists for modglue DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/pcre DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/pcre DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: adding the default universal variant DEBUG: Requested variant darwin is not provided by port pcre. DEBUG: Requested variant i386 is not provided by port pcre. DEBUG: Requested variant macosx is not provided by port pcre. DEBUG: Searching for dependency: pcre DEBUG: Found Dependency: receipt exists for pcre DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/gmp DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/gmp DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: Using group file /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/group/muniversal-1.0.tcl DEBUG: universal variant already exists, so not adding the default one DEBUG: Requested variant darwin is not provided by port gmp. DEBUG: Requested variant i386 is not provided by port gmp. DEBUG: Requested variant macosx is not provided by port gmp. DEBUG: Searching for dependency: gmp DEBUG: Found Dependency: receipt exists for gmp DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/math/LiE DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/math/LiE DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: not using configure, so not adding the default universal variant DEBUG: Requested variant darwin is not provided by port LiE. DEBUG: Requested variant i386 is not provided by port LiE. DEBUG: Requested variant macosx is not provided by port LiE. DEBUG: Searching for dependency: LiE DEBUG: Found Dependency: receipt exists for LiE DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/gtkmm DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/x11/gtkmm DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: adding the default universal variant DEBUG: Requested variant darwin is not provided by port gtkmm. DEBUG: Requested variant i386 is not provided by port gtkmm. DEBUG: Requested variant macosx is not provided by port gtkmm. DEBUG: Searching for dependency: gtkmm DEBUG: Found Dependency: receipt exists for gtkmm DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/tex/texlive DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/tex/texlive DEBUG: setting option os.universal_supported to yes DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: not using configure, so not adding the default universal variant DEBUG: Requested variant darwin is not provided by port texlive. DEBUG: Requested variant i386 is not provided by port texlive. DEBUG: Requested variant macosx is not provided by port texlive. DEBUG: Searching for dependency: texlive DEBUG: Found Dependency: receipt exists for texlive DEBUG: Executing org.macports.main (cadabra) ---> Fetching cadabra DEBUG: Executing org.macports.fetch (cadabra) ---> cadabra-1.08.tar.gz doesn't seem to exist in /opt/local/var/macports/distfiles/cadabra DEBUG: Pinging www.aei.mpg.de... DEBUG: Pinging distfiles.macports.org... DEBUG: Pinging trd.no.distfiles.macports.org... DEBUG: Pinging arn.se.distfiles.macports.org... DEBUG: www.aei.mpg.de ping time is 266.527 DEBUG: distfiles.macports.org ping time is 111.092 DEBUG: trd.no.distfiles.macports.org ping time is 290.975 DEBUG: arn.se.distfiles.macports.org ping time is 241.649 ---> Attempting to fetch cadabra-1.08.tar.gz from http://distfiles.macports.org/cadabra % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 764k 100 764k 0 0 386k 0 0:00:01 0:00:01 --:--:-- 475k ---> Verifying checksum(s) for cadabra DEBUG: Executing org.macports.checksum (cadabra) ---> Checksumming cadabra-1.08.tar.gz DEBUG: Correct (md5) checksum for cadabra-1.08.tar.gz DEBUG: Correct (sha1) checksum for cadabra-1.08.tar.gz DEBUG: Correct (rmd160) checksum for cadabra-1.08.tar.gz ---> Extracting cadabra DEBUG: Executing org.macports.extract (cadabra) ---> Extracting cadabra-1.08.tar.gz DEBUG: setting option extract.args to /opt/local/var/macports/distfiles/cadabra/cadabra-1.08.tar.gz DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.5' DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_cadabra/work" && gzip -dc /opt/local/var/macports/distfiles/cadabra/cadabra-1.08.tar.gz | /usr/bin/gnutar --no-same-owner -xf -' DEBUG: Executing org.macports.patch (cadabra) ---> Applying patches to cadabra ---> Applying /opt/local/var/macports/sources/rsync.macports.org/release/ports/math/cadabra/files/patch-Makefile.in.diff DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.5' DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_cadabra/work/cadabra-1.08" && patch -p0' patching file Makefile.in ---> Configuring cadabra DEBUG: Using compiler 'Mac OS X gcc 4.0' DEBUG: Executing org.macports.configure (cadabra) DEBUG: Environment: CFLAGS='-O2' CPPFLAGS='-I/opt/local/include' CXXFLAGS='-O2' MACOSX_DEPLOYMENT_TARGET='10.5' CPP='/usr/bin/cpp-4.0' CXX='/usr/bin/g++-4.0' F90FLAGS='-O2' LDFLAGS='-L/opt/local/lib' FCFLAGS='-O2' OBJC='/usr/bin/gcc-4.0' INSTALL='/usr/bin/install -c' OBJCFLAGS='-O2' FFLAGS='-O2' CC='/usr/bin/gcc-4.0' DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_cadabra/work/cadabra-1.08" && ./configure --prefix=/opt/local' checking for gcc... /usr/bin/gcc-4.0 checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether /usr/bin/gcc-4.0 accepts -g... yes checking for /usr/bin/gcc-4.0 option to accept ISO C89... none needed checking whether we are using the GNU C++ compiler... yes checking whether /usr/bin/g++-4.0 accepts -g... yes checking whether ln -s works... yes checking whether make sets $(MAKE)... yes checking for a BSD-compatible install... /usr/bin/install -c checking CFLAGS for maximum warnings... -Wall checking for lie... yes checking how to run the C++ preprocessor... /usr/bin/g++-4.0 -E checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking pcre.h usability... yes checking pcre.h presence... yes checking for pcre.h... yes checking gmpxx.h usability... yes checking gmpxx.h presence... yes checking for gmpxx.h... yes checking pcrecpp.h usability... yes checking pcrecpp.h presence... yes checking for pcrecpp.h... yes checking for pkg-config... /opt/local/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for sigc... yes checking for modglue... yes checking for ptywrap... yes checking system type... Darwin -n Checking whether to use -fnested-functions... no checking whether to build the GUI... yes checking for sigc... yes checking for gtk... yes checking for pango... yes checking for GTKMM... yes checking for GLIBMM... yes checking for pangomm... yes checking for dvipng... yes checking for latex... yes checking for breqn package... yes configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating src/modules/Makefile config.status: creating tests/Makefile config.status: creating gui/Makefile config.status: creating doc/Makefile config.status: creating src/config.h config.status: src/config.h is unchanged ---> Building cadabra DEBUG: Executing org.macports.build (cadabra) DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.5' CC='gcc' CXX='g++' DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_cadabra/work/cadabra-1.08" && make all' ( cd src && make ); Makefile:167: .depend: No such file or directory rm -f .depend for i in `find . -name "*.cc"`; \ do /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -E -MM -MT `echo $i | sed -e 's/\.\///' -e 's/\.cc/\.o/'` $i >> .depend; \ done /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o preprocessor.o preprocessor.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o storage.o storage.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o display.o display.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o parser.o parser.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/algebra.o modules/algebra.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/pertstring.o modules/pertstring.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/convert.o modules/convert.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/gamma.o modules/gamma.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/field_theory.o modules/field_theory.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/select.o modules/select.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/dummies.o modules/dummies.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/output.o modules/output.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/properties.o modules/properties.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/relativity.o modules/relativity.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/substitute.o modules/substitute.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/tableaux.o modules/tableaux.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/diff_geometry.o modules/diff_geometry.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/numerical.o modules/numerical.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/linear.o modules/linear.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/combinat.o modules/combinat.cc /usr/bin/gcc-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/xperm.o modules/xperm.c modules/xperm.c: In function 'double_coset_rep': modules/xperm.c:1438: error: nested functions are disabled, use -fnested-functions to re-enable modules/xperm.c:1453: error: nested functions are disabled, use -fnested-functions to re-enable modules/xperm.c:1467: error: nested functions are disabled, use -fnested-functions to re-enable modules/xperm.c:1513: error: nested functions are disabled, use -fnested-functions to re-enable modules/xperm.c:1595: error: nested functions are disabled, use -fnested-functions to re-enable make[1]: *** [modules/xperm.o] Error 1 make: *** [program] Error 2 Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_cadabra/work/cadabra-1.08" && make all " returned error 2 Command output: done /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o preprocessor.o preprocessor.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o storage.o storage.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o display.o display.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o parser.o parser.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/algebra.o modules/algebra.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/pertstring.o modules/pertstring.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/convert.o modules/convert.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/gamma.o modules/gamma.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/field_theory.o modules/field_theory.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/select.o modules/select.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/dummies.o modules/dummies.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/output.o modules/output.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/properties.o modules/properties.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/relativity.o modules/relativity.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/substitute.o modules/substitute.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/tableaux.o modules/tableaux.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/diff_geometry.o modules/diff_geometry.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/numerical.o modules/numerical.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/linear.o modules/linear.cc /usr/bin/g++-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/combinat.o modules/combinat.cc /usr/bin/gcc-4.0 -O2 -Wall -I. -I../src `pkg-config modglue --cflags` -D"RELEASE=\"1.08\"" -D"DATETIME=\"`date | sed -e 's/ / /'`\"" -DHOSTNAME=\"`hostname`\" -c -o modules/xperm.o modules/xperm.c modules/xperm.c: In function 'double_coset_rep': modules/xperm.c:1438: error: nested functions are disabled, use -fnested-functions to re-enable modules/xperm.c:1453: error: nested functions are disabled, use -fnested-functions to re-enable modules/xperm.c:1467: error: nested functions are disabled, use -fnested-functions to re-enable modules/xperm.c:1513: error: nested functions are disabled, use -fnested-functions to re-enable modules/xperm.c:1595: error: nested functions are disabled, use -fnested-functions to re-enable make[1]: *** [modules/xperm.o] Error 1 make: *** [program] Error 2 Warning: the following items did not execute (for cadabra): org.macports.activate org.macports.build org.macports.destroot org.macports.install Error: Status 1 encountered during processing. % From deliverable at gmail.com Wed Mar 11 12:36:38 2009 From: deliverable at gmail.com (Alexy Khrabrov) Date: Wed, 11 Mar 2009 15:36:38 -0400 Subject: Why ar doesn't call ranlib on Mac? In-Reply-To: <49B520CF.8000708@pogma.com> References: <6E56105F-260A-4CC7-AF11-05E366589191@gmail.com> <49AE9BC7.3060006@pogma.com> <7c737f300903082301q6946adf1h2e49cdc5727a9674@mail.gmail.com> <49B520CF.8000708@pogma.com> Message-ID: <7c737f300903111236x615fad15qd44dbe37d0659f7@mail.gmail.com> Peter -- you are right: On Mon, Mar 9, 2009 at 9:59 AM, Peter O'Gorman wrote: > ... > If you find that ranlib is indeed not being run on 10.5 (as I said, I > can not currently check 10.5), then ensure that your COMMAND_MODE > environment variable is unset and file a bug at > http://bugreporter.apple.com. > > (btw, a quick way to check if ranlib has been run is to check for a > __SYMDEF SORTED file in the archive with ar t). This was a good way to learn about COMMAND_MODE -- that was what the strange get_unix_standard_mode() did in that code. For some reason my zsh sets COMMAND_MODE to "legacy", although I can't find where yet. Since that's my shell and is not so common for others, I was getting on the bad old ranlib-less side of ar where many others were getting the good behavior from it. But, recompiling Apple's stuff felt refreshing -- and the size shrinks to 1/2 as I don't need universal on Intel. So I wonder about recompiling all of it. Can we have MacPorts do Apple? :) Cheers, Alexy From dluke at geeklair.net Wed Mar 11 12:46:00 2009 From: dluke at geeklair.net (Daniel J. Luke) Date: Wed, 11 Mar 2009 15:46:00 -0400 Subject: Why ar doesn't call ranlib on Mac? In-Reply-To: <7c737f300903111236x615fad15qd44dbe37d0659f7@mail.gmail.com> References: <6E56105F-260A-4CC7-AF11-05E366589191@gmail.com> <49AE9BC7.3060006@pogma.com> <7c737f300903082301q6946adf1h2e49cdc5727a9674@mail.gmail.com> <49B520CF.8000708@pogma.com> <7c737f300903111236x615fad15qd44dbe37d0659f7@mail.gmail.com> Message-ID: <8B5346CF-1537-456E-B819-692E1E7F433B@geeklair.net> On Mar 11, 2009, at 3:36 PM, Alexy Khrabrov wrote: > But, recompiling Apple's stuff felt refreshing -- and the size shrinks > to 1/2 as I don't need universal on Intel. ... but you don't need to recompile to do that (see man lipo) > So I wonder about > recompiling all of it. Can we have MacPorts do Apple? :) If you want to build the opensource parts of Mac OS X, you'll want darwinbuild (http://darwinbuild.macosforge.org/) -- Daniel J. Luke +========================================================+ | *---------------- dluke at geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 194 bytes Desc: This is a digitally signed message part URL: From bobnielsen at clearwire.net Wed Mar 11 13:51:19 2009 From: bobnielsen at clearwire.net (Bob Nielsen) Date: Wed, 11 Mar 2009 13:51:19 -0700 Subject: Cannot upgrade perl5.8 - registry error Message-ID: <3F0E2F9B-73C6-4E9E-947C-5AB06A5A6FED@clearwire.net> When I try to upgrade perl5.8 to version 5.8.9_2, I get the following error: Error: Checking installed version failed: Registry error: perl5.8 @5.8.8_0+darwin_8 not registered as installed. perl -v says I have version 5.8.6. Using port -f doesn't help. A lot of other actions seem to be affected by this. How can I get around this error? From msavory1 at nzbox.com Wed Mar 11 14:20:32 2009 From: msavory1 at nzbox.com (Mike Savory) Date: Wed, 11 Mar 2009 14:20:32 -0700 Subject: port outdated command works propely after Porticus being installed. In-Reply-To: <28FA9BF1-1F89-4A1D-80F0-2327E988E421@sfc.keio.ac.jp> References: <6952B5E9-1E99-4081-BC6E-AC093F261409@sfc.keio.ac.jp> <49B6974D.2090800@macports.org> <8AFCCD75-B227-4192-971A-3F2227ED0FD2@bellsouth.net> <49B76455.6010405@macports.org> <7F2B9D3B-2D4F-4450-9F68-63006A6F9668@sfc.keio.ac.jp> <20090311095045.GA3046@velsheda.lateralis.org> <28FA9BF1-1F89-4A1D-80F0-2327E988E421@sfc.keio.ac.jp> Message-ID: <11399D4D-00A5-41E0-80B4-1EC315CF22FC@nzbox.com> Also when you do # sudo port selfupdate The line that comes back >The MacPorts installation is not outdated so it was not updated is referring to the install of the port command itself, not that no installed ports are outdated! so doing a port outdated after a selfudate is all you need (sans porticus) $ sudo port selfupdate; port outdated MacPorts base version 1.700 installed Downloaded MacPorts base version 1.700 The MacPorts installation is not outdated so it was not updated The following installed ports are outdated: autoconf213 2.13_0 < 2.13_1 bzip2 1.0.5_1 < 1.0.5_2 etc... Mike From kalinski at amei.se Wed Mar 11 14:56:38 2009 From: kalinski at amei.se (kalinski) Date: Wed, 11 Mar 2009 22:56:38 +0100 Subject: compiling libpangocairo Message-ID: <49B83396.7050301@amei.se> hello, i switched from linux to macosx (?h shame on me) and i am used to compile stuff myself with the well known configure, make, make install so for the nice program jamin (an audio tool) i got a binary which doesnt work because it cannot somehow find the pango fonts, instead it shows blocks. then i compiled it myself from source and it gave: Incompatible library version: jamin requires version 2204.0.0 or later, but libpangocairo-1.0.0.dylib provides version 2201.0.0 i went on and fetched cairo (latest source) which compiled and went into: /usr/local/lib which shouldn't interfere with macports right because the older version is in /opt/local/lib ? that's good because i don't wanna break my universal binaries nor macports then i fetched pango tried to compile it but it says (after a clean configure): /opt/local/include/cairo/cairo-xlib.h:97:3: error: #error Cairo was not compiled with support for the xlib backend viewer-cairo.c: In function 'cairo_x_view_create_surface': viewer-cairo.c:38: warning: implicit declaration of function 'cairo_xlib_surface_create' viewer-cairo.c:40: warning: return makes pointer from integer without a cast now: how can i tell automake on macosx to use my /usr/local/lib instead of /opt/local/lib? or better how can i get libpangocairo.1.0.0.dylib 2204.0.0 on macosx? i guess the macports version is 2203.0.0 right? any help very much appreciated cheers mart From admin2 at enabled.com Wed Mar 11 17:53:19 2009 From: admin2 at enabled.com (Noah) Date: Wed, 11 Mar 2009 17:53:19 -0700 Subject: freetype mailing to build Message-ID: <49B85CFF.2010308@enabled.com> Any clues why freetype is failing to build and how can I fix this issue? running OSX 10.5.5 ---> Building freetype Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_print_freetype/work/freetype-2.3.8" && make all " returned error 2 Command output: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_print_freetype/work/freetype-2.3.8/include/freetype/internal/ftstream.h:488: error: syntax error before 'FT_Stream_ReadFields' /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_print_freetype/work/freetype-2.3.8/include/freetype/internal/ftstream.h:490: warning: data definition has no type or storage class builds/unix/ftsystem.c:97: error: syntax error before 'ft_alloc' builds/unix/ftsystem.c: In function 'ft_alloc': builds/unix/ftsystem.c:102: warning: return makes integer from pointer without a cast builds/unix/ftsystem.c: At top level: builds/unix/ftsystem.c:127: error: syntax error before 'ft_realloc' builds/unix/ftsystem.c: In function 'ft_realloc': builds/unix/ftsystem.c:135: warning: return makes integer from pointer without a cast builds/unix/ftsystem.c: At top level: builds/unix/ftsystem.c:153: error: syntax error before 'ft_free' builds/unix/ftsystem.c:195: error: syntax error before 'ft_close_stream_by_munmap' builds/unix/ftsystem.c:217: error: syntax error before 'ft_close_stream_by_free' builds/unix/ftsystem.c:230: error: syntax error before 'FT_Stream_Open' builds/unix/ftsystem.c: In function 'FT_Stream_Open': builds/unix/ftsystem.c:278: error: 'LONG_MAX' undeclared (first use in this function) builds/unix/ftsystem.c:278: error: (Each undeclared identifier is reported only once builds/unix/ftsystem.c:278: error: for each function it appears in.) builds/unix/ftsystem.c:301: warning: assignment from incompatible pointer type builds/unix/ftsystem.c:342: warning: assignment from incompatible pointer type builds/unix/ftsystem.c: At top level: builds/unix/ftsystem.c:386: error: syntax error before 'FT_New_Memory' builds/unix/ftsystem.c: In function 'FT_New_Memory': builds/unix/ftsystem.c:395: warning: assignment from incompatible pointer type builds/unix/ftsystem.c:396: warning: assignment from incompatible pointer type builds/unix/ftsystem.c:397: warning: assignment from incompatible pointer type builds/unix/ftsystem.c:403: warning: return makes integer from pointer without a cast builds/unix/ftsystem.c: At top level: builds/unix/ftsystem.c:410: error: syntax error before 'FT_Done_Memory' make: *** [/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_print_freetype/work/freetype-2.3.8/objs/ftsystem.lo] Error 1 From talklists at newgeo.com Wed Mar 11 17:53:37 2009 From: talklists at newgeo.com (Scott Haneda) Date: Wed, 11 Mar 2009 17:53:37 -0700 Subject: Cannot upgrade perl5.8 - registry error In-Reply-To: <3F0E2F9B-73C6-4E9E-947C-5AB06A5A6FED@clearwire.net> References: <3F0E2F9B-73C6-4E9E-947C-5AB06A5A6FED@clearwire.net> Message-ID: <914A22D1-63C6-498A-AAEB-B2B20A2B033E@newgeo.com> On Mar 11, 2009, at 1:51 PM, Bob Nielsen wrote: > When I try to upgrade perl5.8 to version 5.8.9_2, I get the > following error: > > Error: Checking installed version failed: Registry error: perl5.8 > @5.8.8_0+darwin_8 not registered as installed. > > perl -v says I have version 5.8.6. Using port -f doesn't help. A > lot of other actions seem to be affected by this. How can I get > around this error? Maybe your perl -v is telling you the Mac OS X version? Try /opt/local/ bin/perl -v instead. You can also issue `port installed | grep perl` and see what version Mac Ports has installed. I would not at all be surprised if you had 5.8.9_2 already, as I do, and made no real efforts to instal it. If you still do need to get it working, you could remove it, and then install it again, maybe also first try to activate it, if it is not listed as active in the installed list. Show the output to the command above, and probably someone can point you what to do next. -- Scott * If you contact me off list replace talklists@ with scott@ * From deliverable at gmail.com Wed Mar 11 17:58:51 2009 From: deliverable at gmail.com (Alexy Khrabrov) Date: Wed, 11 Mar 2009 20:58:51 -0400 Subject: qt4-mac Message-ID: <9549B287-83BF-4045-8F0B-C09B4B22D29D@gmail.com> Anybody built qt4-mac? I get a horrible, horrible mess when trying to build it -- it pulls MySQL and other databases, then doesn't find them, dying on SQLite, tries to use a command 'c' which is then undefined, etc. Is it supposed to build or just like be there? Cheers, Alexy From sven.haiges at googlemail.com Wed Mar 11 18:13:58 2009 From: sven.haiges at googlemail.com (Sven Haiges) Date: Wed, 11 Mar 2009 18:13:58 -0700 Subject: Failed to fetch patch-bind.diff for php5 Message-ID: <45ac42bc0903111813p361b74f3k41ac3ff2e91d4a2e@mail.gmail.com> Hello everybody, I am trying to reinstall php5 on my mac and I succeed yesterday using the same command: sudo port install php5 Since then I created a local repository as I need to make a small change in the way php5 is compiled (I needed to include the mysqli option in the build). Other than having a slightly changed Portfile locally now, nothing has changed. This is what I get today (I strongly believe before I used the local rep it was showing the same issue): costopenout-lm:~ haiges$ sudo port install php5 Password: Portfile changed since last build; discarding previous state. ---> Fetching php5 ---> Attempting to fetch patch-bind.diff from http://distfiles.macports.org/php5 ---> Attempting to fetch patch-bind.diff from http://arn.se.distfiles.macports.org/php5 ---> Attempting to fetch patch-bind.diff from http://trd.no.distfiles.macports.org/php5 ---> Attempting to fetch patch-bind.diff from http://svn.macports.org/repository/macports/distfiles/php5 ---> Attempting to fetch patch-bind.diff from http://svn.macports.org/repository/macports/distfiles/general/ ---> Attempting to fetch patch-bind.diff from http://svn.macports.org/repository/macports/downloads/php5 Error: Target org.macports.fetch returned: fetch failed Error: Status 1 encountered during processing. I checked the directory on that server, there is no such patch file. Is this a current issue or user error? Thanx Sven -- Sven Haiges sven.haiges at googlemail.com Yahoo Messenger / Skype: hansamann Personal Homepage, Wiki & Blog: http://www.svenhaiges.de Subscribe to the Grails Podcast: http://feeds.grailspodcast.com/grailspodcast http://www.grailspodcast.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcalhoun at macports.org Wed Mar 11 18:35:36 2009 From: mcalhoun at macports.org (Marcus Calhoun-Lopez) Date: Thu, 12 Mar 2009 01:35:36 +0000 (UTC) Subject: qt4-mac References: <9549B287-83BF-4045-8F0B-C09B4B22D29D@gmail.com> Message-ID: Alexy Khrabrov gmail.com> writes: > > Anybody built qt4-mac? I get a horrible, horrible mess when trying to > build it -- it pulls MySQL and other databases, then doesn't find > them, dying on SQLite, tries to use a command 'c' which is then > undefined, etc. Is it supposed to build or just like be there? > > Cheers, > Alexy > > When qt4-mac is next updated, it will not pull in so many SQL databases without a variant. This is the first report of a failure concerning the databases that I know of. If you open a ticket with the exact error messages (port -d install qt4-mac) and the system you are trying to build on, we could try to figure out what the problem is. -Marcus From blb at macports.org Wed Mar 11 18:49:51 2009 From: blb at macports.org (Bryan Blackburn) Date: Wed, 11 Mar 2009 19:49:51 -0600 Subject: Failed to fetch patch-bind.diff for php5 In-Reply-To: <45ac42bc0903111813p361b74f3k41ac3ff2e91d4a2e@mail.gmail.com> References: <45ac42bc0903111813p361b74f3k41ac3ff2e91d4a2e@mail.gmail.com> Message-ID: <20090312014951.GG660@ninagal.withay.com> On Wed, Mar 11, 2009 at 06:13:58PM -0700, Sven Haiges said: > Hello everybody, > > I am trying to reinstall php5 on my mac and I succeed yesterday using the > same command: > > sudo port install php5 > > Since then I created a local repository as I need to make a small change in > the way php5 is compiled (I needed to include the mysqli option in the > build). Other than having a slightly changed Portfile locally now, nothing > has changed. That file is in the files/ directory with the Portfile. If your port isn't seeing it, and you created a local php5 at some point, make sure that you've either removed php5 from that local repo, or that it also contains the files/ directory from the original. Bryan [...] > > Thanx > Sven > > -- > Sven Haiges > sven.haiges at googlemail.com > > Yahoo Messenger / Skype: hansamann > Personal Homepage, Wiki & Blog: http://www.svenhaiges.de > > Subscribe to the Grails Podcast: > http://feeds.grailspodcast.com/grailspodcast > http://www.grailspodcast.com From bobnielsen at clearwire.net Wed Mar 11 20:39:54 2009 From: bobnielsen at clearwire.net (Bob Nielsen) Date: Wed, 11 Mar 2009 20:39:54 -0700 Subject: Cannot upgrade perl5.8 - registry error In-Reply-To: <914A22D1-63C6-498A-AAEB-B2B20A2B033E@newgeo.com> References: <3F0E2F9B-73C6-4E9E-947C-5AB06A5A6FED@clearwire.net> <914A22D1-63C6-498A-AAEB-B2B20A2B033E@newgeo.com> Message-ID: <86390542-373A-4584-B750-9EC67A3A2EE3@clearwire.net> On Mar 11, 2009, at 5:53 PM, Scott Haneda wrote: > On Mar 11, 2009, at 1:51 PM, Bob Nielsen wrote: > >> When I try to upgrade perl5.8 to version 5.8.9_2, I get the >> following error: >> >> Error: Checking installed version failed: Registry error: perl5.8 >> @5.8.8_0+darwin_8 not registered as installed. >> >> perl -v says I have version 5.8.6. Using port -f doesn't help. A >> lot of other actions seem to be affected by this. How can I get >> around this error? > > > Maybe your perl -v is telling you the Mac OS X version? Try /opt/ > local/bin/perl -v instead. You can also issue `port installed | > grep perl` and see what version Mac Ports has installed. I would > not at all be surprised if you had 5.8.9_2 already, as I do, and > made no real efforts to instal it. > > If you still do need to get it working, you could remove it, and > then install it again, maybe also first try to activate it, if it > is not listed as active in the installed list. > > Show the output to the command above, and probably someone can > point you what to do next. mac:~ bob$ /opt/local/bin/perl -v This is perl, v5.8.6 built for darwin-thread-multi-2level (with 5 registered patches, see perl -V for more detail) and: mac:~ bob$ port installed |grep perl Error: port installed failed: Registry error: perl5.8 @5.8.8_0 +darwin_8 not registered as installed. When I try to remove perl altogether I get the same error message. I need to get past the registry error before I can anything. From talklists at newgeo.com Thu Mar 12 00:02:06 2009 From: talklists at newgeo.com (Scott Haneda) Date: Thu, 12 Mar 2009 00:02:06 -0700 Subject: Cannot upgrade perl5.8 - registry error In-Reply-To: <86390542-373A-4584-B750-9EC67A3A2EE3@clearwire.net> References: <3F0E2F9B-73C6-4E9E-947C-5AB06A5A6FED@clearwire.net> <914A22D1-63C6-498A-AAEB-B2B20A2B033E@newgeo.com> <86390542-373A-4584-B750-9EC67A3A2EE3@clearwire.net> Message-ID: <028A08F2-6CA4-4E3B-8ED3-19982D483B26@newgeo.com> On Mar 11, 2009, at 8:39 PM, Bob Nielsen wrote: > On Mar 11, 2009, at 5:53 PM, Scott Haneda wrote: >> On Mar 11, 2009, at 1:51 PM, Bob Nielsen wrote: >> >>> When I try to upgrade perl5.8 to version 5.8.9_2, I get the >>> following error: >>> >>> Error: Checking installed version failed: Registry error: perl5.8 >>> @5.8.8_0+darwin_8 not registered as installed. >>> >>> perl -v says I have version 5.8.6. Using port -f doesn't help. A >>> lot of other actions seem to be affected by this. How can I get >>> around this error? >> >> >> Maybe your perl -v is telling you the Mac OS X version? Try /opt/ >> local/bin/perl -v instead. You can also issue `port installed | >> grep perl` and see what version Mac Ports has installed. I would >> not at all be surprised if you had 5.8.9_2 already, as I do, and >> made no real efforts to instal it. >> >> If you still do need to get it working, you could remove it, and >> then install it again, maybe also first try to activate it, if it >> is not listed as active in the installed list. >> >> Show the output to the command above, and probably someone can >> point you what to do next. > > mac:~ bob$ /opt/local/bin/perl -v > > This is perl, v5.8.6 built for darwin-thread-multi-2level > (with 5 registered patches, see perl -V for more detail) > > and: > > mac:~ bob$ port installed |grep perl > Error: port installed failed: Registry error: perl5.8 > @5.8.8_0+darwin_8 not registered as installed. > > When I try to remove perl altogether I get the same error message. > I need to get past the registry error before I can anything. I am making a huge guess in an effort to get you past this, maybe look in /opt/local/var/macports/receipts for perl, and move that aside. Another suggestion would be sudo port -u upgrade perl5 You may want to try this first, before messing with the receipts, as I am not sure that is the right path to go down. -- Scott * If you contact me off list replace talklists@ with scott@ * From jmr at macports.org Thu Mar 12 01:05:11 2009 From: jmr at macports.org (Joshua Root) Date: Thu, 12 Mar 2009 19:05:11 +1100 Subject: qt4-mac In-Reply-To: <9549B287-83BF-4045-8F0B-C09B4B22D29D@gmail.com> References: <9549B287-83BF-4045-8F0B-C09B4B22D29D@gmail.com> Message-ID: <49B8C237.9090009@macports.org> Alexy Khrabrov wrote: > Anybody built qt4-mac? I get a horrible, horrible mess when trying to > build it -- it pulls MySQL and other databases, then doesn't find them, > dying on SQLite, tries to use a command 'c' which is then undefined, > etc. Is it supposed to build or just like be there? This sounds a lot like a bug that was worked around in MacPorts 1.7.0. If you're not yet running that version, running `sudo port selfupdate` will get it for you. You'll want to clean the failed port after upgrading. - Josh From jmr at macports.org Thu Mar 12 01:09:42 2009 From: jmr at macports.org (Joshua Root) Date: Thu, 12 Mar 2009 19:09:42 +1100 Subject: Cannot upgrade perl5.8 - registry error In-Reply-To: <86390542-373A-4584-B750-9EC67A3A2EE3@clearwire.net> References: <3F0E2F9B-73C6-4E9E-947C-5AB06A5A6FED@clearwire.net> <914A22D1-63C6-498A-AAEB-B2B20A2B033E@newgeo.com> <86390542-373A-4584-B750-9EC67A3A2EE3@clearwire.net> Message-ID: <49B8C346.2040703@macports.org> Bob Nielsen wrote: > mac:~ bob$ port installed |grep perl > Error: port installed failed: Registry error: perl5.8 @5.8.8_0+darwin_8 > not registered as installed. > > When I try to remove perl altogether I get the same error message. I > need to get past the registry error before I can anything. One or more of your receipts is missing or malformed, but if it's missing, its parent directory is still present. If you delete /opt/local/var/macports/receipts/perl5.8/5.8.8_0, the registry error should go away, but all of that port's files will be orphaned. This means you'll have to force activate the first new version you install. - Josh From admin2 at enabled.com Thu Mar 12 05:24:22 2009 From: admin2 at enabled.com (Noah) Date: Thu, 12 Mar 2009 05:24:22 -0700 Subject: freetype mailing to build Message-ID: <49B8FEF6.7070209@enabled.com> Any clues why freetype is failing to build and how can I fix this issue? running OSX 10.5.5 ---> Building freetype Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_print_freetype/work/freetype-2.3.8" && make all " returned error 2 Command output: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_print_freetype/work/freetype-2.3.8/include/freetype/internal/ftstream.h:488: error: syntax error before 'FT_Stream_ReadFields' /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_print_freetype/work/freetype-2.3.8/include/freetype/internal/ftstream.h:490: warning: data definition has no type or storage class builds/unix/ftsystem.c:97: error: syntax error before 'ft_alloc' builds/unix/ftsystem.c: In function 'ft_alloc': builds/unix/ftsystem.c:102: warning: return makes integer from pointer without a cast builds/unix/ftsystem.c: At top level: builds/unix/ftsystem.c:127: error: syntax error before 'ft_realloc' builds/unix/ftsystem.c: In function 'ft_realloc': builds/unix/ftsystem.c:135: warning: return makes integer from pointer without a cast builds/unix/ftsystem.c: At top level: builds/unix/ftsystem.c:153: error: syntax error before 'ft_free' builds/unix/ftsystem.c:195: error: syntax error before 'ft_close_stream_by_munmap' builds/unix/ftsystem.c:217: error: syntax error before 'ft_close_stream_by_free' builds/unix/ftsystem.c:230: error: syntax error before 'FT_Stream_Open' builds/unix/ftsystem.c: In function 'FT_Stream_Open': builds/unix/ftsystem.c:278: error: 'LONG_MAX' undeclared (first use in this function) builds/unix/ftsystem.c:278: error: (Each undeclared identifier is reported only once builds/unix/ftsystem.c:278: error: for each function it appears in.) builds/unix/ftsystem.c:301: warning: assignment from incompatible pointer type builds/unix/ftsystem.c:342: warning: assignment from incompatible pointer type builds/unix/ftsystem.c: At top level: builds/unix/ftsystem.c:386: error: syntax error before 'FT_New_Memory' builds/unix/ftsystem.c: In function 'FT_New_Memory': builds/unix/ftsystem.c:395: warning: assignment from incompatible pointer type builds/unix/ftsystem.c:396: warning: assignment from incompatible pointer type builds/unix/ftsystem.c:397: warning: assignment from incompatible pointer type builds/unix/ftsystem.c:403: warning: return makes integer from pointer without a cast builds/unix/ftsystem.c: At top level: builds/unix/ftsystem.c:410: error: syntax error before 'FT_Done_Memory' make: *** [/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_print_freetype/work/freetype-2.3.8/objs/ftsystem.lo] Error 1 From mukai at sfc.keio.ac.jp Thu Mar 12 06:04:45 2009 From: mukai at sfc.keio.ac.jp (Kuniaki Mukai) Date: Thu, 12 Mar 2009 22:04:45 +0900 Subject: Can't install cadabra Message-ID: Failing to build cadabra via MacPorts as reported in my previous message, I have made a try to build cadabra from source as follows on MacOSX 10.5.6. % git clone git://repo.or.cz/cadabra.git % cd cadabra/ % git pull % export LDFLAGS=-L/opt/local/lib % export CFLAGS=-I/opt/local/include % ./configure % make % sudo make install % cadabra Cadabra 1.08 (built on Thu Mar 12 20:25:46 JST 2009) Copyright (C) 2001-2008 Kasper Peeters Info at http://www.aei.mpg.de/~peekas/cadabra/ Available under the terms of the GNU General Public License. >{n, m}::Indices. Assigning list property Indices to n, m. ... It seems successful, though I am not familiar with software building enough to be able to explain to others what I did. However I still want to build the cadabra via MacPorts, because I wand to build all neccessary softwares via MacPorts as possible as MacPorts has the port for the software. So I still wait for any help to build cadabra via MacPorts. Thanks Kuniaki > I can't install cadabra. > Here is the debug mode log with error message. > I am sorry for the full long log text. I could not snip any irrelevant > part of it because of my little knowledge on installation. > > I appreciate any help for installing cadabra. > > Kuniaki Mukai From hansamann at yahoo.de Thu Mar 12 10:54:07 2009 From: hansamann at yahoo.de (Sven Haiges) Date: Thu, 12 Mar 2009 10:54:07 -0700 Subject: Failed to fetch patch-bind.diff for php5 In-Reply-To: <20090312014951.GG660@ninagal.withay.com> References: <45ac42bc0903111813p361b74f3k41ac3ff2e91d4a2e@mail.gmail.com> <20090312014951.GG660@ninagal.withay.com> Message-ID: <45ac42bc0903121054l4767a8c0yd007334919d57907@mail.gmail.com> Bryan, thanx for the reply first. I am not completely getting it though, probably because I use MacPorts only now and then. I checked http://distfiles.macports.org/php5/files and it does not exist... so I still want to use my local Portfile, I undestand I have to create a /files directory where my local Portfile is (it is in a local repo) and then copy that diff file into there... right? Can you link to the diff file? Thanx Sven On Wed, Mar 11, 2009 at 6:49 PM, Bryan Blackburn wrote: > On Wed, Mar 11, 2009 at 06:13:58PM -0700, Sven Haiges said: > > Hello everybody, > > > > I am trying to reinstall php5 on my mac and I succeed yesterday using the > > same command: > > > > sudo port install php5 > > > > Since then I created a local repository as I need to make a small change > in > > the way php5 is compiled (I needed to include the mysqli option in the > > build). Other than having a slightly changed Portfile locally now, > nothing > > has changed. > > That file is in the files/ directory with the Portfile. If your port isn't > seeing it, and you created a local php5 at some point, make sure that > you've > either removed php5 from that local repo, or that it also contains the > files/ directory from the original. > > Bryan > > [...] > > > > Thanx > > Sven > > > > -- > > Sven Haiges > > sven.haiges at googlemail.com > > > > Yahoo Messenger / Skype: hansamann > > Personal Homepage, Wiki & Blog: http://www.svenhaiges.de > > > > Subscribe to the Grails Podcast: > > http://feeds.grailspodcast.com/grailspodcast > > http://www.grailspodcast.com > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > -- Sven Haiges sven.haiges at googlemail.com Yahoo Messenger / Skype: hansamann Personal Homepage, Wiki & Blog: http://www.svenhaiges.de Subscribe to the Grails Podcast: http://feeds.grailspodcast.com/grailspodcast http://www.grailspodcast.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From brad at pixilla.com Thu Mar 12 11:17:58 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Thu, 12 Mar 2009 11:17:58 -0700 Subject: Failed to fetch patch-bind.diff for php5 In-Reply-To: <45ac42bc0903121054l4767a8c0yd007334919d57907@mail.gmail.com> References: <45ac42bc0903111813p361b74f3k41ac3ff2e91d4a2e@mail.gmail.com> <20090312014951.GG660@ninagal.withay.com> <45ac42bc0903121054l4767a8c0yd007334919d57907@mail.gmail.com> Message-ID: <393A77AA-BB48-4371-870D-4C6A55BCEC3B@pixilla.com> Hi Bryan, I usually start by coping the port to my local repo: cd /path/to/local/repo mkdir -p ./www cp -R `port dir php5` ./www/ portindex cd www/php5 Then do your thing. If your just wondering how to use patch files port will look for them in the ./files/ directory so just drop them in ./files/ and add something like this to your Portfile: patchfiles patch-bind.diff //Brad On Mar 12, 2009, at 10:54 AM, Sven Haiges wrote: > Bryan, thanx for the reply first. I am not completely getting it > though, probably because I use MacPorts only now and then. > > I checked > http://distfiles.macports.org/php5/files and it does not exist... so > I still want to use my local Portfile, I undestand I have to create > a /files directory where my local Portfile is (it is in a local > repo) and then copy that diff file into there... right? Can you link > to the diff file? > > Thanx > Sven > > On Wed, Mar 11, 2009 at 6:49 PM, Bryan Blackburn > wrote: > On Wed, Mar 11, 2009 at 06:13:58PM -0700, Sven Haiges said: > > Hello everybody, > > > > I am trying to reinstall php5 on my mac and I succeed yesterday > using the > > same command: > > > > sudo port install php5 > > > > Since then I created a local repository as I need to make a small > change in > > the way php5 is compiled (I needed to include the mysqli option in > the > > build). Other than having a slightly changed Portfile locally now, > nothing > > has changed. > > That file is in the files/ directory with the Portfile. If your > port isn't > seeing it, and you created a local php5 at some point, make sure > that you've > either removed php5 from that local repo, or that it also contains the > files/ directory from the original. > > Bryan > > [...] > > > > Thanx > > Sven > > > > -- > > Sven Haiges > > sven.haiges at googlemail.com > > > > Yahoo Messenger / Skype: hansamann > > Personal Homepage, Wiki & Blog: http://www.svenhaiges.de > > > > Subscribe to the Grails Podcast: > > http://feeds.grailspodcast.com/grailspodcast > > http://www.grailspodcast.com > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > > > > -- > Sven Haiges > sven.haiges at googlemail.com > > Yahoo Messenger / Skype: hansamann > Personal Homepage, Wiki & Blog: http://www.svenhaiges.de > > Subscribe to the Grails Podcast: > http://feeds.grailspodcast.com/grailspodcast > http://www.grailspodcast.com > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From wa0tjt at gmail.com Thu Mar 12 12:58:26 2009 From: wa0tjt at gmail.com (Keith Kaiser) Date: Thu, 12 Mar 2009 14:58:26 -0500 Subject: Installing lesstif Message-ID: <7668FF69-6805-4422-8E9F-BD458EBEDA23@gmail.com> Below is what was returned when I tried to install lesstif anyone know what I should do next? sudo port install lesstif ---> Configuring xorg-libX11 Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_x11_xorg-libX11/work/libX11-1.2" && ./ configure --prefix=/opt/local --without-xcb " returned error 1 Command output: checking if /usr/bin/g++-4.0 static flag -static works... no checking if /usr/bin/g++-4.0 supports -c -o file.o... yes checking whether the /usr/bin/g++-4.0 linker (/usr/libexec/gcc/i686- apple-darwin9/4.0.1/ld) supports shared libraries... yes checking dynamic linker characteristics... darwin9.6.0 dyld (cached) (cached) checking how to hardcode library paths into programs... immediate appending configuration tag "F77" to libtool checking for bash... /bin/bash checking if dolt supports this host... yes, replacing libtool checking for gcc... (cached) /usr/bin/gcc-4.0 checking whether we are using the GNU C compiler... (cached) yes checking whether /usr/bin/gcc-4.0 accepts -g... (cached) yes checking for /usr/bin/gcc-4.0 option to accept ISO C89... (cached) none needed checking dependency style of /usr/bin/gcc-4.0... (cached) gcc3 checking for cpp... /usr/bin/cpp checking if /usr/bin/cpp requires -undef... no checking if /usr/bin/cpp requires -traditional... no checking whether to use XCB... (cached) no checking for pkg-config... /opt/local/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for XPROTO... configure: error: Package requirements (xproto >= 7.0.13) were not met: Requested 'xproto >= 7.0.13' but version of Xproto is 7.0.11 Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables XPROTO_CFLAGS and XPROTO_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. Error: The following dependencies failed to build: xorg-libX11 xorg- libXext xorg-libXp xorg-printproto xorg-libXt xorg-libsm xorg-libice Error: Status 1 encountered during processing. From jmr at macports.org Thu Mar 12 13:39:38 2009 From: jmr at macports.org (Joshua Root) Date: Fri, 13 Mar 2009 07:39:38 +1100 Subject: Installing lesstif In-Reply-To: <7668FF69-6805-4422-8E9F-BD458EBEDA23@gmail.com> References: <7668FF69-6805-4422-8E9F-BD458EBEDA23@gmail.com> Message-ID: <49B9730A.7040902@macports.org> Keith Kaiser wrote: > Below is what was returned when I tried to install lesstif anyone know > what I should do next? > > > sudo port install lesstif > ---> Configuring xorg-libX11 > Error: Target org.macports.configure returned: configure failure: shell > command " cd [...] > checking for XPROTO... configure: error: Package requirements (xproto >= > 7.0.13) were not met: > > Requested 'xproto >= 7.0.13' but version of Xproto is 7.0.11 `sudo port upgrade outdated` - Josh From deliverable at gmail.com Thu Mar 12 18:18:58 2009 From: deliverable at gmail.com (Alexy Khrabrov) Date: Thu, 12 Mar 2009 21:18:58 -0400 Subject: qt4-mac In-Reply-To: <49B8C237.9090009@macports.org> References: <9549B287-83BF-4045-8F0B-C09B4B22D29D@gmail.com> <49B8C237.9090009@macports.org> Message-ID: <7c737f300903121818o4ac7ffd6m8d6c82d2262f51cb@mail.gmail.com> On Thu, Mar 12, 2009 at 4:05 AM, Joshua Root wrote: > Alexy Khrabrov wrote: >> Anybody built qt4-mac? ?I get a horrible, horrible mess when trying to >> build it -- it pulls MySQL and other databases, then doesn't find them, >> dying on SQLite, tries to use a command 'c' which is then undefined, >> etc. ?Is it supposed to build or just like be there? > > This sounds a lot like a bug that was worked around in MacPorts 1.7.0. > If you're not yet running that version, running `sudo port selfupdate` > will get it for you. You'll want to clean the failed port after upgrading. Thanks Josh -- that did the trick; I already had selfupdate'd, but needed to clean as well. Now I found I had qt4-mac @4.3.3_0+dbus+docs, while the @4.3.3_1 has no such variants. Was it the part of the workaround? What does the dbus actually do on Mac and is it a part of qt4_mac @4.3.3_1? Cheers, Alexy From jmr at macports.org Thu Mar 12 18:33:16 2009 From: jmr at macports.org (Joshua Root) Date: Fri, 13 Mar 2009 12:33:16 +1100 Subject: qt4-mac In-Reply-To: <7c737f300903121818o4ac7ffd6m8d6c82d2262f51cb@mail.gmail.com> References: <9549B287-83BF-4045-8F0B-C09B4B22D29D@gmail.com> <49B8C237.9090009@macports.org> <7c737f300903121818o4ac7ffd6m8d6c82d2262f51cb@mail.gmail.com> Message-ID: <49B9B7DC.1060501@macports.org> Alexy Khrabrov wrote: > On Thu, Mar 12, 2009 at 4:05 AM, Joshua Root wrote: >> Alexy Khrabrov wrote: >>> Anybody built qt4-mac? I get a horrible, horrible mess when trying to >>> build it -- it pulls MySQL and other databases, then doesn't find them, >>> dying on SQLite, tries to use a command 'c' which is then undefined, >>> etc. Is it supposed to build or just like be there? >> This sounds a lot like a bug that was worked around in MacPorts 1.7.0. >> If you're not yet running that version, running `sudo port selfupdate` >> will get it for you. You'll want to clean the failed port after upgrading. > > Thanks Josh -- that did the trick; I already had selfupdate'd, but > needed to clean as well. > > Now I found I had qt4-mac @4.3.3_0+dbus+docs, while the @4.3.3_1 has > no such variants. Was it the part of the workaround? No, the workaround is in the MacPorts base code, not in any specific port. > What does the > dbus actually do on Mac and is it a part of qt4_mac @4.3.3_1? D-Bus does the same thing on the Mac as it does on any other platform. Use Google if you're interested. :-) There are no dbus or doc variants in the new version of qt4-mac because dbus is now always used and the docs are now always built. - Josh From deliverable at gmail.com Thu Mar 12 19:47:05 2009 From: deliverable at gmail.com (Alexy Khrabrov) Date: Thu, 12 Mar 2009 22:47:05 -0400 Subject: qt4-mac In-Reply-To: <49B9B7DC.1060501@macports.org> References: <9549B287-83BF-4045-8F0B-C09B4B22D29D@gmail.com> <49B8C237.9090009@macports.org> <7c737f300903121818o4ac7ffd6m8d6c82d2262f51cb@mail.gmail.com> <49B9B7DC.1060501@macports.org> Message-ID: OK, so I want to compile a package using qt4, and it pulls libglut from port mesa, which depends on libX11. But then various X and gl things are undefined... Which GL is supposed to work with qt4-mac without X11? Cheers, Alexy From bobnielsen at clearwire.net Thu Mar 12 21:10:32 2009 From: bobnielsen at clearwire.net (Bob Nielsen) Date: Thu, 12 Mar 2009 21:10:32 -0700 Subject: Cannot upgrade perl5.8 - registry error In-Reply-To: <028A08F2-6CA4-4E3B-8ED3-19982D483B26@newgeo.com> References: <3F0E2F9B-73C6-4E9E-947C-5AB06A5A6FED@clearwire.net> <914A22D1-63C6-498A-AAEB-B2B20A2B033E@newgeo.com> <86390542-373A-4584-B750-9EC67A3A2EE3@clearwire.net> <028A08F2-6CA4-4E3B-8ED3-19982D483B26@newgeo.com> Message-ID: <28948221-A0BA-420F-8E5C-87837303636D@clearwire.net> On Mar 12, 2009, at 12:02 AM, Scott Haneda wrote: > On Mar 11, 2009, at 8:39 PM, Bob Nielsen wrote: >> On Mar 11, 2009, at 5:53 PM, Scott Haneda wrote: >>> On Mar 11, 2009, at 1:51 PM, Bob Nielsen wrote: >>> >>>> When I try to upgrade perl5.8 to version 5.8.9_2, I get the >>>> following error: >>>> >>>> Error: Checking installed version failed: Registry error: >>>> perl5.8 @5.8.8_0+darwin_8 not registered as installed. >>>> >>>> perl -v says I have version 5.8.6. Using port -f doesn't help. >>>> A lot of other actions seem to be affected by this. How can I >>>> get around this error? >>> >>> >>> Maybe your perl -v is telling you the Mac OS X version? Try /opt/ >>> local/bin/perl -v instead. You can also issue `port installed | >>> grep perl` and see what version Mac Ports has installed. I would >>> not at all be surprised if you had 5.8.9_2 already, as I do, and >>> made no real efforts to instal it. >>> >>> If you still do need to get it working, you could remove it, and >>> then install it again, maybe also first try to activate it, if it >>> is not listed as active in the installed list. >>> >>> Show the output to the command above, and probably someone can >>> point you what to do next. >> >> mac:~ bob$ /opt/local/bin/perl -v >> >> This is perl, v5.8.6 built for darwin-thread-multi-2level >> (with 5 registered patches, see perl -V for more detail) >> >> and: >> >> mac:~ bob$ port installed |grep perl >> Error: port installed failed: Registry error: perl5.8 @5.8.8_0 >> +darwin_8 not registered as installed. >> >> When I try to remove perl altogether I get the same error >> message. I need to get past the registry error before I can >> anything. > > > I am making a huge guess in an effort to get you past this, maybe > look in /opt/local/var/macports/receipts for perl, and move that > aside. > > Another suggestion would be > sudo port -u upgrade perl5 > You may want to try this first, before messing with the receipts, > as I am not sure that is the right path to go down. Trying to upgrade gave me the same error. Deleting the receipts entry worked, however. Thanks. From deliverable at gmail.com Thu Mar 12 21:45:11 2009 From: deliverable at gmail.com (Alexy Khrabrov) Date: Fri, 13 Mar 2009 00:45:11 -0400 Subject: Why ar doesn't call ranlib on Mac? In-Reply-To: <8B5346CF-1537-456E-B819-692E1E7F433B@geeklair.net> References: <6E56105F-260A-4CC7-AF11-05E366589191@gmail.com> <49AE9BC7.3060006@pogma.com> <7c737f300903082301q6946adf1h2e49cdc5727a9674@mail.gmail.com> <49B520CF.8000708@pogma.com> <7c737f300903111236x615fad15qd44dbe37d0659f7@mail.gmail.com> <8B5346CF-1537-456E-B819-692E1E7F433B@geeklair.net> Message-ID: <7c737f300903122145r7bc3f05bpdae11d111269ca9e@mail.gmail.com> And in the semi-final analysis, it turns out it's the terminal program, iTerm, which set COMMAND_MODE=legacy. As opposed to the regular Terminal which sets it to unix2003. Now the only question is to read Japanese to understand the explanations at http://d.hatena.ne.jp/moriyoshi/20090208/1234108045 Anyone? Does it have to do with compiling for Leopard? BTW the iterm port is still at 0.8.2, seemingly abandoned. I guess if it were compiled by MacPorts it's set COMMAND_MODE to "unix2003" by default, not "legacy"... Cheers, Alexy From lanceboyle at qwest.net Thu Mar 12 21:57:17 2009 From: lanceboyle at qwest.net (Jerry) Date: Thu, 12 Mar 2009 21:57:17 -0700 Subject: Re-do MacPorts after upgrading from Tiger to Leopard on PPC? Message-ID: <95D3529F-FC9B-42F2-BDDD-70D90CE40692@qwest.net> I just upgraded the OS from Tiger to Leopard on PPC. Do I need to re- install any or all of my MacPorts stuff? Jerry From blb at macports.org Thu Mar 12 22:43:40 2009 From: blb at macports.org (Bryan Blackburn) Date: Thu, 12 Mar 2009 23:43:40 -0600 Subject: Re-do MacPorts after upgrading from Tiger to Leopard on PPC? In-Reply-To: <95D3529F-FC9B-42F2-BDDD-70D90CE40692@qwest.net> References: <95D3529F-FC9B-42F2-BDDD-70D90CE40692@qwest.net> Message-ID: <20090313054340.GN836@ninagal.withay.com> On Thu, Mar 12, 2009 at 09:57:17PM -0700, Jerry said: > I just upgraded the OS from Tiger to Leopard on PPC. Do I need to re- > install any or all of my MacPorts stuff? Yes, unfortunately MacPorts doesn't handle that case well since many ports you have installed were probably built with 10.4-specific bits. The safest method is to move /opt/local aside (eg, to /opt/local-10.4), do a new MacPorts install then install those ports you want/need. You can use 'port installed' prior to moving /opt/local aside to see what you currently have. Bryan > > Jerry From trog24 at comcast.net Fri Mar 13 06:17:51 2009 From: trog24 at comcast.net (Frank J. R. Hanstick) Date: Fri, 13 Mar 2009 06:17:51 -0700 Subject: Error upgrading evolution-data-server Message-ID: <45F2D9D8-540A-40DC-B7F1-D5BA6C955E23@comcast.net> Hello, The following error occurred when upgrading evolution-data-server via sudo port upgrade installed: /usr/bin/gcc-4.0 ${wl}-undefined ${wl}dynamic_lookup -o .libs/ libcamelpop3.so -bundle .libs/camel-pop3-engine.o .libs/camel-pop3- folder.o .libs/camel-pop3-provider.o .libs/camel-pop3-stream.o .libs/ camel-pop3-store.o -L/opt/local/lib ../../../libedataserver/.libs/ libedataserver-1.2.dylib /opt/local/lib/libbonobo-2.dylib /opt/local/ lib/libbonobo-activation.dylib /opt/local/lib/ libORBitCosNaming-2.dylib /opt/local/lib/libgconf-2.dylib /opt/local/ lib/libdbus-glib-1.dylib /opt/local/lib/libORBit-2.dylib /opt/local/ lib/libdbus-1.dylib /opt/local/lib/libsoup-2.4.dylib /opt/local/lib/ libxml2.dylib /opt/local/lib/libgnutls.dylib /opt/local/lib/ libz.dylib /opt/local/lib/libtasn1.dylib /opt/local/lib/ libgcrypt.dylib /opt/local/lib/libgpg-error.dylib ../../../ camel/.libs/libcamel-provider-1.2.dylib /opt/local/lib/ libcamel-1.2.dylib /opt/local/lib/libedataserver-1.2.dylib -L/usr/ lib ../../../camel/.libs/libcamel-1.2.dylib /opt/local/lib/ libgio-2.0.dylib /opt/local/lib/libgobject-2.0.dylib /opt/local/lib/ libgmodule-2.0.dylib /opt/local/lib/libsqlite3.dylib /opt/local/lib/ libgthread-2.0.dylib /opt/local/lib/libglib-2.0.dylib /opt/local/lib/ libintl.dylib /opt/local/lib/libiconv.dylib -lz -lpthread -lkrb5 - lk5crypto -lcom_err -lgssapi_krb5 /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: Undefined symbols: _camel_db_flush_in_memory_transactions referenced from libcamel- provider-1.2.14 expected to be defined in libcamel-1.2.14 _camel_db_get_folder_uids_flags referenced from libcamel- provider-1.2.14 expected to be defined in libcamel-1.2.14 _camel_db_start_in_memory_transactions referenced from libcamel- provider-1.2.14 expected to be defined in libcamel-1.2.14 _camel_db_write_fresh_message_info_record referenced from libcamel- provider-1.2.14 expected to be defined in libcamel-1.2.14 collect2: ld returned 1 exit status make[4]: *** [libcamelpop3.la] Error 1 make[3]: *** [all-recursive] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Error: Unable to upgrade port: 1 libcamel is where it is suppose to be; but, if it required updating, then had not done so yet. Frank J. R. Hanstick trog24 at comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From brad at pixilla.com Fri Mar 13 08:35:46 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Fri, 13 Mar 2009 08:35:46 -0700 Subject: Re-do MacPorts after upgrading from Tiger to Leopard on PPC? In-Reply-To: <20090313054340.GN836@ninagal.withay.com> References: <95D3529F-FC9B-42F2-BDDD-70D90CE40692@qwest.net> <20090313054340.GN836@ninagal.withay.com> Message-ID: <3C38030F-4812-4129-818A-FC2BD6CA31B8@pixilla.com> On Mar 12, 2009, at 10:43 PM, Bryan Blackburn wrote: > On Thu, Mar 12, 2009 at 09:57:17PM -0700, Jerry said: >> I just upgraded the OS from Tiger to Leopard on PPC. Do I need to re- >> install any or all of my MacPorts stuff? > > Yes, unfortunately MacPorts doesn't handle that case well since many > ports > you have installed were probably built with 10.4-specific bits. The > safest > method is to move /opt/local aside (eg, to /opt/local-10.4), do a new > MacPorts install then install those ports you want/need. You can > use 'port > installed' prior to moving /opt/local aside to see what you > currently have. > > Bryan Could you force a rebuild? port -f upgrade installed Or list all your installed ports, uninstall ports them and then reinstall the ports. I don't know what Jerry has installed but moving /opt/local aside would mean losing things like databases and conf files. This MAY be a big deal to Jerry. //Brad From jmr at macports.org Fri Mar 13 08:44:39 2009 From: jmr at macports.org (Joshua Root) Date: Sat, 14 Mar 2009 02:44:39 +1100 Subject: Re-do MacPorts after upgrading from Tiger to Leopard on PPC? In-Reply-To: <3C38030F-4812-4129-818A-FC2BD6CA31B8@pixilla.com> References: <95D3529F-FC9B-42F2-BDDD-70D90CE40692@qwest.net> <20090313054340.GN836@ninagal.withay.com> <3C38030F-4812-4129-818A-FC2BD6CA31B8@pixilla.com> Message-ID: <49BA7F67.9030904@macports.org> Bradley Giesbrecht wrote: > On Mar 12, 2009, at 10:43 PM, Bryan Blackburn wrote: > >> On Thu, Mar 12, 2009 at 09:57:17PM -0700, Jerry said: >>> I just upgraded the OS from Tiger to Leopard on PPC. Do I need to re- >>> install any or all of my MacPorts stuff? >> >> Yes, unfortunately MacPorts doesn't handle that case well since many >> ports >> you have installed were probably built with 10.4-specific bits. The >> safest >> method is to move /opt/local aside (eg, to /opt/local-10.4), do a new >> MacPorts install then install those ports you want/need. You can use >> 'port >> installed' prior to moving /opt/local aside to see what you currently >> have. >> >> Bryan > > > Could you force a rebuild? > > port -f upgrade installed Nope. Selected darwin_8* variants would be preserved. This is fixed in trunk. - Josh From brad at pixilla.com Fri Mar 13 09:17:26 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Fri, 13 Mar 2009 09:17:26 -0700 Subject: Re-do MacPorts after upgrading from Tiger to Leopard on PPC? In-Reply-To: <49BA7F67.9030904@macports.org> References: <95D3529F-FC9B-42F2-BDDD-70D90CE40692@qwest.net> <20090313054340.GN836@ninagal.withay.com> <3C38030F-4812-4129-818A-FC2BD6CA31B8@pixilla.com> <49BA7F67.9030904@macports.org> Message-ID: On Mar 13, 2009, at 8:44 AM, Joshua Root wrote: > Bradley Giesbrecht wrote: >> On Mar 12, 2009, at 10:43 PM, Bryan Blackburn wrote: >> >>> On Thu, Mar 12, 2009 at 09:57:17PM -0700, Jerry said: >>>> I just upgraded the OS from Tiger to Leopard on PPC. Do I need to >>>> re- >>>> install any or all of my MacPorts stuff? >>> >>> Yes, unfortunately MacPorts doesn't handle that case well since many >>> ports >>> you have installed were probably built with 10.4-specific bits. The >>> safest >>> method is to move /opt/local aside (eg, to /opt/local-10.4), do a >>> new >>> MacPorts install then install those ports you want/need. You can >>> use >>> 'port >>> installed' prior to moving /opt/local aside to see what you >>> currently >>> have. >>> >>> Bryan >> >> >> Could you force a rebuild? >> >> port -f upgrade installed > > Nope. Selected darwin_8* variants would be preserved. This is fixed in > trunk. Would this work or is there another shorter path to achieving the same thing. port installed | sed '1d' | awk '{print $1$2}' > installed.txt port -f uninstall installed for item in $(cat installed.txt); do port install $item done //Brad From brad at pixilla.com Fri Mar 13 09:27:33 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Fri, 13 Mar 2009 09:27:33 -0700 Subject: Re-do MacPorts after upgrading from Tiger to Leopard on PPC? In-Reply-To: References: <95D3529F-FC9B-42F2-BDDD-70D90CE40692@qwest.net> <20090313054340.GN836@ninagal.withay.com> <3C38030F-4812-4129-818A-FC2BD6CA31B8@pixilla.com> <49BA7F67.9030904@macports.org> Message-ID: On Mar 13, 2009, at 9:17 AM, Bradley Giesbrecht wrote: > > On Mar 13, 2009, at 8:44 AM, Joshua Root wrote: > >> Bradley Giesbrecht wrote: >>> On Mar 12, 2009, at 10:43 PM, Bryan Blackburn wrote: >>> >>>> On Thu, Mar 12, 2009 at 09:57:17PM -0700, Jerry said: >>>>> I just upgraded the OS from Tiger to Leopard on PPC. Do I need >>>>> to re- >>>>> install any or all of my MacPorts stuff? >>>> >>>> Yes, unfortunately MacPorts doesn't handle that case well since >>>> many >>>> ports >>>> you have installed were probably built with 10.4-specific bits. >>>> The >>>> safest >>>> method is to move /opt/local aside (eg, to /opt/local-10.4), do a >>>> new >>>> MacPorts install then install those ports you want/need. You can >>>> use >>>> 'port >>>> installed' prior to moving /opt/local aside to see what you >>>> currently >>>> have. >>>> >>>> Bryan >>> >>> >>> Could you force a rebuild? >>> >>> port -f upgrade installed >> >> Nope. Selected darwin_8* variants would be preserved. This is fixed >> in >> trunk. > > Would this work or is there another shorter path to achieving the > same thing. > > port installed | sed '1d' | awk '{print $1$2}' > installed.txt > port -f uninstall installed > for item in $(cat installed.txt); do port install $item done Whoops, need to remove +darwin_8. port installed | sed '1d' | sed 's|+darwin_[0-9]||g' | awk '{print $1$2}' > installed.txt //Brad From jmr at macports.org Fri Mar 13 10:17:16 2009 From: jmr at macports.org (Joshua Root) Date: Sat, 14 Mar 2009 04:17:16 +1100 Subject: Re-do MacPorts after upgrading from Tiger to Leopard on PPC? In-Reply-To: References: <95D3529F-FC9B-42F2-BDDD-70D90CE40692@qwest.net> <20090313054340.GN836@ninagal.withay.com> <3C38030F-4812-4129-818A-FC2BD6CA31B8@pixilla.com> <49BA7F67.9030904@macports.org> Message-ID: <49BA951C.5030207@macports.org> Bradley Giesbrecht wrote: > > On Mar 13, 2009, at 9:17 AM, Bradley Giesbrecht wrote: > >> >> On Mar 13, 2009, at 8:44 AM, Joshua Root wrote: >> >>> Bradley Giesbrecht wrote: >>>> On Mar 12, 2009, at 10:43 PM, Bryan Blackburn wrote: >>>> >>>>> On Thu, Mar 12, 2009 at 09:57:17PM -0700, Jerry said: >>>>>> I just upgraded the OS from Tiger to Leopard on PPC. Do I need to re- >>>>>> install any or all of my MacPorts stuff? >>>>> >>>>> Yes, unfortunately MacPorts doesn't handle that case well since many >>>>> ports >>>>> you have installed were probably built with 10.4-specific bits. The >>>>> safest >>>>> method is to move /opt/local aside (eg, to /opt/local-10.4), do a new >>>>> MacPorts install then install those ports you want/need. You can use >>>>> 'port >>>>> installed' prior to moving /opt/local aside to see what you currently >>>>> have. >>>>> >>>>> Bryan >>>> >>>> >>>> Could you force a rebuild? >>>> >>>> port -f upgrade installed >>> >>> Nope. Selected darwin_8* variants would be preserved. This is fixed in >>> trunk. >> >> Would this work or is there another shorter path to achieving the same >> thing. >> >> port installed | sed '1d' | awk '{print $1$2}' > installed.txt >> port -f uninstall installed >> for item in $(cat installed.txt); do port install $item done > > Whoops, need to remove +darwin_8. > > port installed | sed '1d' | sed 's|+darwin_[0-9]||g' | awk '{print > $1$2}' > installed.txt That will miss darwin_8_powerpc/darwin_8_i386. - Josh From brad at pixilla.com Fri Mar 13 13:59:42 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Fri, 13 Mar 2009 13:59:42 -0700 Subject: Re-do MacPorts after upgrading from Tiger to Leopard on PPC? In-Reply-To: <49BA951C.5030207@macports.org> References: <95D3529F-FC9B-42F2-BDDD-70D90CE40692@qwest.net> <20090313054340.GN836@ninagal.withay.com> <3C38030F-4812-4129-818A-FC2BD6CA31B8@pixilla.com> <49BA7F67.9030904@macports.org> <49BA951C.5030207@macports.org> Message-ID: On Mar 13, 2009, at 10:17 AM, Joshua Root wrote: > Bradley Giesbrecht wrote: >> >> On Mar 13, 2009, at 9:17 AM, Bradley Giesbrecht wrote: >> >>> >>> On Mar 13, 2009, at 8:44 AM, Joshua Root wrote: >>> >>>> Bradley Giesbrecht wrote: >>>>> On Mar 12, 2009, at 10:43 PM, Bryan Blackburn wrote: >>>>> >>>>>> On Thu, Mar 12, 2009 at 09:57:17PM -0700, Jerry said: >>>>>>> I just upgraded the OS from Tiger to Leopard on PPC. Do I need >>>>>>> to re- >>>>>>> install any or all of my MacPorts stuff? >>>>>> >>>>>> Yes, unfortunately MacPorts doesn't handle that case well since >>>>>> many >>>>>> ports >>>>>> you have installed were probably built with 10.4-specific >>>>>> bits. The >>>>>> safest >>>>>> method is to move /opt/local aside (eg, to /opt/local-10.4), do >>>>>> a new >>>>>> MacPorts install then install those ports you want/need. You >>>>>> can use >>>>>> 'port >>>>>> installed' prior to moving /opt/local aside to see what you >>>>>> currently >>>>>> have. >>>>>> >>>>>> Bryan >>>>> >>>>> >>>>> Could you force a rebuild? >>>>> >>>>> port -f upgrade installed >>>> >>>> Nope. Selected darwin_8* variants would be preserved. This is >>>> fixed in >>>> trunk. >>> >>> Would this work or is there another shorter path to achieving the >>> same >>> thing. >>> >>> port installed | sed '1d' | awk '{print $1$2}' > installed.txt >>> port -f uninstall installed >>> for item in $(cat installed.txt); do port install $item done >> >> Whoops, need to remove +darwin_8. >> >> port installed | sed '1d' | sed 's|+darwin_[0-9]||g' | awk '{print >> $1$2}' > installed.txt > > That will miss darwin_8_powerpc/darwin_8_i386. Thanks. Where would I look to find all the arch variants? //Brad From serra at atmo.arizona.edu Fri Mar 13 14:12:34 2009 From: serra at atmo.arizona.edu (Yolande Serra) Date: Fri, 13 Mar 2009 14:12:34 -0700 Subject: hdf5 and gcc43 option? Message-ID: Hi, has anyone gotten the hdf5 port with the gcc43 and fortran variants to compile on an intel mac running 10.5.6? thanks, Yolande From raimue at macports.org Fri Mar 13 14:30:02 2009 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Fri, 13 Mar 2009 22:30:02 +0100 Subject: Re-do MacPorts after upgrading from Tiger to Leopard on PPC? In-Reply-To: References: <95D3529F-FC9B-42F2-BDDD-70D90CE40692@qwest.net> <20090313054340.GN836@ninagal.withay.com> <3C38030F-4812-4129-818A-FC2BD6CA31B8@pixilla.com> <49BA7F67.9030904@macports.org> <49BA951C.5030207@macports.org> Message-ID: <49BAD05A.2060309@macports.org> On 13.03.2009 21:59 Uhr, Bradley Giesbrecht wrote: > Where would I look to find all the arch variants? Basically everything is possible. They are set using a platform statement, documented in the guide [1]. platform os [version] [arch] {} If you are on a darwin system, you should only find selected variants darwin_* or macosx. Most of these variants are listed in variant_descriptions.conf [2], but this list is not meant to be complete. Rainer [1] http://guide.macports.org/#reference.variants.platform [2] http://trac.macports.org/browser/trunk/dports/_resources/port1.0/variant_descriptions.conf From mtrumpis at berkeley.edu Fri Mar 13 15:29:22 2009 From: mtrumpis at berkeley.edu (M Trumpis) Date: Fri, 13 Mar 2009 15:29:22 -0700 Subject: readline 6 and (i)python Message-ID: There's something funny going on with python's readline module when I upgrade to a new readline 6 (and subsequently rebuild py25-readline). When I'm using ipython (which takes advantage of tab completion), the tab completion appends a space character at the end of the completed string. This shouldn't happen, and in fact should be controlled by the preprocessor logic here in readline.c: #ifdef HAVE_RL_COMPLETION_APPEND_CHARACTER rl_completion_append_character ='\0'; #endif Sure enough if I grep HAVE_RL_COMPLETION_APPEND_CHARACTER path-to-python-headers/*.h, it shows up as defined in pyconfig.h So I think this means that the Python system is configured correctly, and that readline must be misbehaving. When I roll back to readline 5 and rebuild py25-readline against that, everything's cool again. Here's some more research done previously on a related readline bug. http://mail.python.org/pipermail/pythonmac-sig/2005-April/013607.html Mike From frstan at bellsouth.net Fri Mar 13 19:05:59 2009 From: frstan at bellsouth.net (William Davis) Date: Fri, 13 Mar 2009 22:05:59 -0400 Subject: hdf5 and gcc43 option? In-Reply-To: References: Message-ID: On Mar 13, 2009, at 5:12 PM, Yolande Serra wrote: > Hi, has anyone gotten the hdf5 port with the gcc43 and fortran > variants to compile on an intel mac running 10.5.6? > > thanks, Yolande > Just did. smooth as silk. First time I've used gcc43 and Im impressed. William Davis frstanATbellsouthDOTnet Mac OS X.5.6 Darwin 9.5.0 XQuartz 2.3.3_rc1 (xorg-server 1.4.2-apple36) Mac Mini Intel Duo @ 1.86 GHz Mundus vult decepi, ego non From allencmcbride at gmail.com Fri Mar 13 20:26:28 2009 From: allencmcbride at gmail.com (Allen McBride) Date: Fri, 13 Mar 2009 23:26:28 -0400 Subject: general advice about making a portfile and a binary package? Message-ID: Hello all, Even though I'm not a developer, I've been looking for ways to help make it easier for Mac users to install GNU Solfege. If one has the dependencies (I have them thanks to all the MacPorts stuff I've installed, I think), Solfege will compile with ./configure, make, sudo make install. So I thought I might try to make a Portfile for it, even though I've never done anything like that before. But I followed the instructions, and it worked. MacPorts installed a working executable in /opt/local/bin. Then I got greedy. I saw in the MacPorts documentation that MacPorts can make .dmg files. So even though I've never done anything like that before either, I tried it. I just typed "sudo port -f destroot" (got that from some Googling) and then "sudo port dmg" from the same directory as my Portfile. Given how far over my head I was at this point, I really didn't expect it to work, but it did. I got a .dmg and a .pkg, which I installed, and the new executable it put into /opt/local/bin works. My question is, is there any chance the .dmg file I created will work for other people? Could I distribute it to brave testers, with warning that it was created by someone who doesn't know what they're doing? Or would that be guaranteed to fail? (After I did all this I looked at the archives a bit, and found a message warning that one needs to make the thing install somewhere other than /opt/local/bin. Is that just a matter of putting "destroot /usr/local/bin" in the Portfile? And speaking of the archives, is there a way to search them without going through one month at a time?) Any advice would be great, whether it's about MacPorts, or about my overall approach, or about things I ought to understand before attempting things like this. Thanks, Allen McBride From brad at pixilla.com Fri Mar 13 20:46:55 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Fri, 13 Mar 2009 20:46:55 -0700 Subject: Re-do MacPorts after upgrading from Tiger to Leopard on PPC? In-Reply-To: <49BAD05A.2060309@macports.org> References: <95D3529F-FC9B-42F2-BDDD-70D90CE40692@qwest.net> <20090313054340.GN836@ninagal.withay.com> <3C38030F-4812-4129-818A-FC2BD6CA31B8@pixilla.com> <49BA7F67.9030904@macports.org> <49BA951C.5030207@macports.org> <49BAD05A.2060309@macports.org> Message-ID: <8589CF4F-70A6-4E0A-A8F6-48D475F52D5D@pixilla.com> On Mar 13, 2009, at 2:30 PM, Rainer M?ller wrote: > On 13.03.2009 21:59 Uhr, Bradley Giesbrecht wrote: >> Where would I look to find all the arch variants? > > Basically everything is possible. They are set using a platform > statement, documented in the guide [1]. > > platform os [version] [arch] {} > > If you are on a darwin system, you should only find selected variants > darwin_* or macosx. > > Most of these variants are listed in variant_descriptions.conf [2], > but > this list is not meant to be complete. > > Rainer > > [1] http://guide.macports.org/#reference.variants.platform > [2] > http://trac.macports.org/browser/trunk/dports/_resources/port1.0/variant_descriptions.conf Thank you Rainer. Is the command that resulted in the installation recorded anywhere? //Brad From raimue at macports.org Fri Mar 13 21:03:37 2009 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Sat, 14 Mar 2009 05:03:37 +0100 Subject: general advice about making a portfile and a binary package? In-Reply-To: References: Message-ID: <49BB2C99.6080607@macports.org> On 14.03.2009 4:26 Uhr, Allen McBride wrote: > Even though I'm not a developer, I've been looking for ways to help > make it easier for Mac users to install GNU Solfege. If one has the > dependencies (I have them thanks to all the MacPorts stuff I've > installed, I think), Solfege will compile with ./configure, make, sudo > make install. So I thought I might try to make a Portfile for it, > even though I've never done anything like that before. But I followed > the instructions, and it worked. MacPorts installed a working > executable in /opt/local/bin. Nice to hear that. Now to make that available to the wide public, I would encourage you to submit it via Trac so we can include it in the official ports tree. See http://guide.macports.org/#project.tickets http://guide.macports.org/#project.contributing > [...] > My question is, is there any chance the .dmg file I created will work > for other people? Could I distribute it to brave testers, with > warning that it was created by someone who doesn't know what they're > doing? Or would that be guaranteed to fail? (After I did all this I > looked at the archives a bit, and found a message warning that one > needs to make the thing install somewhere other than /opt/local/bin. If you are going to distribute a package as dmg/pkg or whatever, please do not use /opt/local as prefix. This gives conflicts if the person is also using MacPorts. The file installed by a dmg/pkg are not tracked by MacPorts and therefore could prevent ports being installed. Also note that dmg/pkg do not offer an easy way for uninstallation. > Is that just a matter of putting "destroot /usr/local/bin" in the > Portfile? No, you would have to install MacPorts to a different prefix and create the package from there. Download the MacPorts source and use './configure --prefix=/opt/whatever' followed by the usual make && make install. Then create the dmg from this port installation (use /opt/whatever/bin/port). You would also have to create binary packages of all dependencies being used. > And speaking of the archives, is there a way to search them > without going through one month at a time?) The mailman archive does not support any advanced searching mechanisms. The lists are also mirrored by Gmane, which allows access over NNTP, and different web-based interfaces including search. http://dir.gmane.org/gmane.os.apple.macports.user http://dir.gmane.org/gmane.os.apple.macports.devel Rainer From raimue at macports.org Fri Mar 13 21:37:39 2009 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Sat, 14 Mar 2009 05:37:39 +0100 Subject: Re-do MacPorts after upgrading from Tiger to Leopard on PPC? In-Reply-To: <8589CF4F-70A6-4E0A-A8F6-48D475F52D5D@pixilla.com> References: <95D3529F-FC9B-42F2-BDDD-70D90CE40692@qwest.net> <20090313054340.GN836@ninagal.withay.com> <3C38030F-4812-4129-818A-FC2BD6CA31B8@pixilla.com> <49BA7F67.9030904@macports.org> <49BA951C.5030207@macports.org> <49BAD05A.2060309@macports.org> <8589CF4F-70A6-4E0A-A8F6-48D475F52D5D@pixilla.com> Message-ID: <49BB3493.6070909@macports.org> On 14.03.2009 4:46 Uhr, Bradley Giesbrecht wrote: > Thank you Rainer. > > Is the command that resulted in the installation recorded anywhere? You lost me on that one. What do you mean by "command"? Rainer From serra at atmo.arizona.edu Fri Mar 13 21:59:49 2009 From: serra at atmo.arizona.edu (Yolande Serra) Date: Fri, 13 Mar 2009 21:59:49 -0700 Subject: hdf5 and gcc43 option? In-Reply-To: References: Message-ID: <09D154D9-722B-419C-9F93-1F40D1B51F49@atmo.arizona.edu> Did you install hdf5-18 or hdf5? -Y. On Mar 13, 2009, at 7:05 PM, William Davis wrote: > > On Mar 13, 2009, at 5:12 PM, Yolande Serra wrote: > >> Hi, has anyone gotten the hdf5 port with the gcc43 and fortran >> variants to compile on an intel mac running 10.5.6? >> >> thanks, Yolande >> > > > Just did. smooth as silk. First time I've used gcc43 and Im > impressed. > > William Davis > frstanATbellsouthDOTnet > Mac OS X.5.6 Darwin 9.5.0 > XQuartz 2.3.3_rc1 (xorg-server 1.4.2-apple36) > Mac Mini Intel Duo @ 1.86 GHz > > Mundus vult decepi, ego non Dr. Yolande Serra, Assoc. Research Faculty Institute of Atmospheric Physics University of Arizona (520) 621-6619 serra at atmo.arizona.edu From frstan at bellsouth.net Fri Mar 13 22:17:03 2009 From: frstan at bellsouth.net (William Davis) Date: Sat, 14 Mar 2009 01:17:03 -0400 Subject: hdf5 and gcc43 option? In-Reply-To: <09D154D9-722B-419C-9F93-1F40D1B51F49@atmo.arizona.edu> References: <09D154D9-722B-419C-9F93-1F40D1B51F49@atmo.arizona.edu> Message-ID: On Mar 14, 2009, at 12:59 AM, Yolande Serra wrote: > Did you install hdf5-18 or hdf5? > > -Y. > On Mar 13, 2009, at 7:05 PM, William Davis wrote: > >> >> On Mar 13, 2009, at 5:12 PM, Yolande Serra wrote: >> >>> Hi, has anyone gotten the hdf5 port with the gcc43 and fortran >>> variants to compile on an intel mac running 10.5.6? >>> >>> thanks, Yolande >>> >> >> >> Just did. smooth as silk. First time I've used gcc43 and Im >> impressed. >> >> William Davis >> frstanATbellsouthDOTnet >> Mac OS X.5.6 Darwin 9.5.0 >> XQuartz 2.3.3_rc1 (xorg-server 1.4.2-apple36) >> Mac Mini Intel Duo @ 1.86 GHz >> >> Mundus vult decepi, ego non > > Dr. Yolande Serra, Assoc. Research Faculty > Institute of Atmospheric Physics > University of Arizona > (520) 621-6619 > serra at atmo.arizona.edu > > > hdf5 @1.6.8_0+fortran+gcc43 William Davis frstanATbellsouthDOTnet Mac OS X.5.6 Darwin 9.5.0 XQuartz 2.3.3_rc1 (xorg-server 1.4.2-apple36) Mac Mini Intel Duo @ 1.86 GHz Mundus vult decepi, ego non From ryandesign at macports.org Fri Mar 13 22:27:16 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 14 Mar 2009 00:27:16 -0500 Subject: Re-do MacPorts after upgrading from Tiger to Leopard on PPC? In-Reply-To: <49BB3493.6070909@macports.org> References: <95D3529F-FC9B-42F2-BDDD-70D90CE40692@qwest.net> <20090313054340.GN836@ninagal.withay.com> <3C38030F-4812-4129-818A-FC2BD6CA31B8@pixilla.com> <49BA7F67.9030904@macports.org> <49BA951C.5030207@macports.org> <49BAD05A.2060309@macports.org> <8589CF4F-70A6-4E0A-A8F6-48D475F52D5D@pixilla.com> <49BB3493.6070909@macports.org> Message-ID: <65C6DA19-CD28-4CDA-A453-3F9D7FBA56B3@macports.org> On Mar 13, 2009, at 23:37, Rainer M?ller wrote: > On 14.03.2009 4:46 Uhr, Bradley Giesbrecht wrote: >> Thank you Rainer. >> >> Is the command that resulted in the installation recorded anywhere? > > You lost me on that one. What do you mean by "command"? I think he means if you have a port, say zlib, that is installed, is it recorded anywhere why zlib is there? e.g. did it get installed because someone typed "sudo port install zlib" or because someone typed "sudo port install freetype +universal"? And no, that is not recorded anywhere. From ryandesign at macports.org Fri Mar 13 22:47:58 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 14 Mar 2009 00:47:58 -0500 Subject: Re-do MacPorts after upgrading from Tiger to Leopard on PPC? In-Reply-To: References: <95D3529F-FC9B-42F2-BDDD-70D90CE40692@qwest.net> <20090313054340.GN836@ninagal.withay.com> <3C38030F-4812-4129-818A-FC2BD6CA31B8@pixilla.com> <49BA7F67.9030904@macports.org> Message-ID: <538D04B3-AF0B-49D1-A90F-4E15862EACBE@macports.org> On Mar 13, 2009, at 11:17, Bradley Giesbrecht wrote: > port installed | sed '1d' | awk '{print $1$2}' > installed.txt > port -f uninstall installed > for item in $(cat installed.txt); do port install $item done On Mar 13, 2009, at 11:27, Bradley Giesbrecht wrote: > Whoops, need to remove +darwin_8. > > port installed | sed '1d' | sed 's|+darwin_[0-9]||g' | awk '{print > $1$2}' > installed.txt It's a noble effort, but this will cause ports to be reinstalled in alphabetical order, which is almost certainly not dependency order. For example, consider someone who has the ports mediawiki, php5 +apache2+mysql5, and mysql5 +server installed. mediawiki depends on php5 and mysql5, and php5 +mysql5 depends on mysql5. mediawiki is alphabetically before php5 and mysql5 so your script will install it first. MacPorts will go and build the dependencies php5 and mysql5 with their default variants, meaning php5 will not have mysql5 support, and mysql5 will not have its server startup item. Then later in the list you will come to mysql5 +server and ask MacPorts to install it and it will go and build the whole thing again, only it won't be able to activate mysql5 +server because mysql5 with no variants is already active. Same for php5, which will already be active with its default +apache2 variant so the new +apache2+mysql5 won't be able to be activated. You would have to replicate the MacPorts dependency engine in your script if you wanted to handle this correctly. But then why not implement it inside MacPorts itself. Which you would be welcome to do. But it's not something users need to do all that often. There are other issues in MacPorts base that might be more important to fix. But if you feel drawn to provide a solution for this issue in MacPorts base, we could start by discussing how it might work and what the command might be called. From ryandesign at macports.org Fri Mar 13 22:54:08 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 14 Mar 2009 00:54:08 -0500 Subject: Cannot upgrade perl5.8 - registry error In-Reply-To: <914A22D1-63C6-498A-AAEB-B2B20A2B033E@newgeo.com> References: <3F0E2F9B-73C6-4E9E-947C-5AB06A5A6FED@clearwire.net> <914A22D1-63C6-498A-AAEB-B2B20A2B033E@newgeo.com> Message-ID: <1197C2A9-490E-4E82-9574-238260CCE4DF@macports.org> On Mar 11, 2009, at 19:53, Scott Haneda wrote: > You can also issue `port installed | grep perl` and see what > version Mac Ports has installed. Or more simply: port installed perl* From ryandesign at macports.org Fri Mar 13 22:59:11 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 14 Mar 2009 00:59:11 -0500 Subject: freetype mailing to build In-Reply-To: <49B8FEF6.7070209@enabled.com> References: <49B8FEF6.7070209@enabled.com> Message-ID: <2241CDC4-4821-40A9-A205-E248DFFA8175@macports.org> On Mar 12, 2009, at 07:24, Noah wrote: > Any clues why freetype is failing to build and how can I fix this > issue? This issue has been reported to me a handful of times. See e.g. http://trac.macports.org/ticket/18232 Unfortunately, I have absolutely no idea why it occurs. I recommend you write to the freetype mailing list and ask them for help. If you find out what was causing it, please let me know. From ryandesign at macports.org Fri Mar 13 23:02:18 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 14 Mar 2009 01:02:18 -0500 Subject: Failed to fetch patch-bind.diff for php5 In-Reply-To: <45ac42bc0903111813p361b74f3k41ac3ff2e91d4a2e@mail.gmail.com> References: <45ac42bc0903111813p361b74f3k41ac3ff2e91d4a2e@mail.gmail.com> Message-ID: <7D6BBFFC-7CEC-4125-A128-0CEE250B41F9@macports.org> On Mar 11, 2009, at 20:13, Sven Haiges wrote: > Since then I created a local repository as I need to make a small > change in the way php5 is compiled (I needed to include the mysqli > option in the build). php5 already includes mysqli support. Simply use the +mysql5 variant. From ryandesign at macports.org Fri Mar 13 23:20:01 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 14 Mar 2009 01:20:01 -0500 Subject: compiling libpangocairo In-Reply-To: <49B83396.7050301@amei.se> References: <49B83396.7050301@amei.se> Message-ID: <647D1376-1679-4038-AF7D-2D46F5EA57C6@macports.org> On Mar 11, 2009, at 16:56, kalinski wrote: > i switched from linux to macosx (?h shame on me) Not at all -- Welcome to Macintosh! > and i am used to compile stuff myself with the > well known configure, make, make install > > so for the nice program jamin (an audio tool) > i got a binary which doesnt work because it cannot > somehow find the pango fonts, instead it shows blocks. > > then i compiled it myself from source > and it gave: > > Incompatible library version: jamin requires version 2204.0.0 or > later, but libpangocairo-1.0.0.dylib provides version 2201.0.0 > > i went on and fetched cairo (latest source) > which compiled and went into: > > /usr/local/lib > > which shouldn't interfere with macports right > because the older version is in /opt/local/lib ? > > that's good because i don't wanna break my universal binaries nor > macports Software installed in /usr/local unfortunately can interfere with software installed by MacPorts, so please do not install things in / usr/local while using MacPorts. Please see: http://trac.macports.org/ticket/15077 > then i fetched pango > > tried to compile it but it says (after a clean configure): > > /opt/local/include/cairo/cairo-xlib.h:97:3: error: #error Cairo was > not compiled with support for the xlib backend > viewer-cairo.c: In function 'cairo_x_view_create_surface': > viewer-cairo.c:38: warning: implicit declaration of function > 'cairo_xlib_surface_create' > viewer-cairo.c:40: warning: return makes pointer from integer > without a cast > > now: how can i tell automake on macosx to use my /usr/local/lib > instead > of /opt/local/lib? Since we already have working ports for cairo and pango I would refer you to those rather than expending effort troubleshooting your manual installation. That is, after all, what MacPorts is for: to make it unnecessary for you to have to figure out how to compile things manually. > or better how can i get libpangocairo.1.0.0.dylib 2204.0.0 > on macosx? > i guess the macports version is 2203.0.0 > right? With cairo @1.8.6_4 and pango @1.22.4_3 installed, I do see libpangocairo-1.0.0.2203.1.dylib. With cairo @1.8.6_4 and pango-devel @1.23.0_0 (to which I just updated the pango-devel port) I see libpangocairo-1.0.0.dylib. So I don't know what version that is. Try pango-devel instead of pango. You'll have to wait an hour from the time of this message and then "sudo port sync" first. Then "sudo port deactivate pango" and "sudo port install pango-devel". Then see if jamin compiles. If it still produces the same message, you'll have to ask on the pango mailing list what version of pango provides version 2204.0.0 of libpangocairo. Or ask the developers of jamin what version of pango and cairo they require. From ryandesign at macports.org Fri Mar 13 23:27:13 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 14 Mar 2009 01:27:13 -0500 Subject: Error in mod_wsgi Portfile? In-Reply-To: <49FD50C6-CCC9-4EEE-A52E-9DA1F8D32D99@devrx.org> References: <49FD50C6-CCC9-4EEE-A52E-9DA1F8D32D99@devrx.org> Message-ID: On Mar 10, 2009, at 12:20, Francis Devereux wrote: > I think that the message printed by www/mod_wsgi/Portfile is > incorrect. The line that currently reads: > ui_msg "# LoadModule python_module modules/mod_wsgi.so" > should read: > ui_msg "# LoadModule wsgi_module modules/mod_wsgi.so" > > If the current instructions are followed, attempting to start > Apache gives the following error: > jupiter LaunchDaemons # /opt/local/apache2/bin/apachectl start > httpd: Syntax error on line 116 of /opt/local/apache2/conf/ > httpd.conf: Can't locate API module structure `python_module' in > file /opt/local/apache2/modules/mod_wsgi.so: dlsym(0x404e10, > python_module): symbol not found I assume you are correct. As for all bugs, can you please file a ticket in the issue tracker? http://guide.macports.org/#project.tickets From ryandesign at macports.org Fri Mar 13 23:32:08 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 14 Mar 2009 01:32:08 -0500 Subject: slapd In-Reply-To: <19FE36AB-75BF-435E-8BE7-5B7D2FF31EA2@gmail.com> References: <19FE36AB-75BF-435E-8BE7-5B7D2FF31EA2@gmail.com> Message-ID: <4843C53B-0FE9-4215-9CA3-E512D7598357@macports.org> On Mar 8, 2009, at 10:57, C#4/135 D4/w!~ wrote: > I have here Port openldap contains: > /Library/LaunchDaemons/org.macports.slapd.plist > /Volumes/?/opt/etc/LaunchDaemons/org.macports.slapd/ > org.macports.slapd.plist > and some more. Picking one and trying: > $ launchctl load /Volumes/?/opt/etc/LaunchDaemons/ > org.macports.slapd/org.macports.slapd.plist > nothing found to load > $ > > chaning > OnDemand > OnDemand > doesn't help either. Any idea? The correct plist to use is the one in /Library/LaunchDaemons. You also need to use "sudo" to launch the service as root. I usually use the -w flag to launchctl, like this: sudo launchctl load -w /Library/LaunchDaemons/org.macports.slapd.plist From the launchctl manpage: -w Remove the disabled key and write the configuration files back out to disk. From blb at macports.org Sat Mar 14 00:14:42 2009 From: blb at macports.org (Bryan Blackburn) Date: Sat, 14 Mar 2009 01:14:42 -0600 Subject: compiling libpangocairo In-Reply-To: <647D1376-1679-4038-AF7D-2D46F5EA57C6@macports.org> References: <49B83396.7050301@amei.se> <647D1376-1679-4038-AF7D-2D46F5EA57C6@macports.org> Message-ID: <20090314071442.GJ1007@ninagal.withay.com> On Sat, Mar 14, 2009 at 01:20:01AM -0500, Ryan Schmidt said: [...] >> or better how can i get libpangocairo.1.0.0.dylib 2204.0.0 >> on macosx? >> i guess the macports version is 2203.0.0 >> right? > > With cairo @1.8.6_4 and pango @1.22.4_3 installed, I do see > libpangocairo-1.0.0.2203.1.dylib. > > With cairo @1.8.6_4 and pango-devel @1.23.0_0 (to which I just updated the > pango-devel port) I see libpangocairo-1.0.0.dylib. So I don't know what > version that is. Try an 'otool -L' on the dylib, the first entry will tell you compat/current version: /mp/lib/libpangocairo-1.0.0.dylib (compatibility version 2204.0.0, current version 2204.1.0) That's for pango 1.22.4_1 (so current pango version, slightly old for the port). Bryan From trog24 at comcast.net Sat Mar 14 00:31:48 2009 From: trog24 at comcast.net (Frank J. R. Hanstick) Date: Sat, 14 Mar 2009 00:31:48 -0700 Subject: Boost installation Message-ID: <6A1187BB-F94D-4CEE-B8C8-1055D624D0D4@comcast.net> Hello, When trying to link the installed Boost to openvrml, I ran into the following: g++ -D_THREAD_SAFE -g -O2 -o .libs/browser browser.o -Wl,- bind_at_load -L/usr/local/spidermonkey/lib/ -L/opt/local/lib ./.libs/ libtest-openvrml.a /Users/frank/FirefoxDownloads/openvrml-0.17.11/src/ libopenvrml/.libs/libopenvrml.dylib -L/sw/lib/firefox2 /opt/local/lib/ libjpeg.dylib /opt/local/lib/libpng12.dylib /opt/local/lib/ libfontconfig.dylib /opt/local/lib/libiconv.dylib /opt/local/lib/ libexpat.dylib /opt/local/lib/libfreetype.dylib -lz -lmozjs -lplds4 - lplc4 -lnspr4 -ldl -lboost_thread-mt -lboost_unit_test_framework-mt - lboost_filesystem-mt /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: Undefined symbols: boost::system::get_system_category() boost::system::get_generic_category() collect2: ld returned 1 exit status make[2]: *** [browser] Error 1 make[2]: Leaving directory `/Users/frank/FirefoxDownloads/ openvrml-0.17.11/tests' make[1]: *** [check-am] Error 2 make[1]: Leaving directory `/Users/frank/FirefoxDownloads/ openvrml-0.17.11/tests' make: *** [check-recursive] Error 1 On an earlier attempt to link Boost to openvrml, I ran into the following: g++ -D_THREAD_SAFE -g -O2 -o .libs/browser browser.o -Wl,- bind_at_load -L/usr/local/spidermonkey/lib/ ./.libs/libtest- openvrml.a /Users/frank/FirefoxDownloads/openvrml-0.17.11/src/ libopenvrml/.libs/libopenvrml.dylib -L/opt/local/lib -L/sw/lib/ firefox2 /opt/local/lib/libjpeg.dylib /opt/local/lib/libpng12.dylib / opt/local/lib/libfontconfig.dylib /opt/local/lib/libiconv.dylib /opt/ local/lib/libexpat.dylib /opt/local/lib/libfreetype.dylib -lz -lmozjs -lplds4 -lplc4 -lnspr4 -ldl -lboost_thread-xgcc40-mt - lboost_unit_test_framework-xgcc40-mt -lboost_filesystem-xgcc40-mt /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: warning can't open dynamic library: libboost_system-xgcc40-mt-1_37.dylib referenced from: /usr/local/lib/libboost_filesystem-xgcc40-mt.dylib (checking for undefined symbols may be affected) (No such file or directory, errno = 2) /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: Undefined symbols: boost::system::get_system_category() boost::system::get_generic_category() boost::system::get_system_category() referenced from libboost expected to be defined in libboost_system-xgcc40-mt-1_37.dylib boost::system::get_generic_category() referenced from libboost expected to be defined in libboost_system-xgcc40-mt-1_37.dylib collect2: ld returned 1 exit status make[2]: *** [browser] Error 1 make[2]: Leaving directory `/Users/frank/FirefoxDownloads/ openvrml-0.17.11/tests' make[1]: *** [check-am] Error 2 make[1]: Leaving directory `/Users/frank/FirefoxDownloads/ openvrml-0.17.11/tests' make: *** [check-recursive] Error 1 Though the earlier attempt had the Boost libraries in /usr/local/ lib, the earlier attempt is related to the MacPorts installed attempt with one difference, the earlier recognized that the dependency of libboost_system-xgcc40-mt.dylib by libboost_filesystem-xgcc40- mt.dylib was needed; however, sought the wrong libboost_system-xgcc40- mt.dylib. The MacPorts installation did not have such recognition before hand. Quite obviously, the problem is that a library dependent on another library within its own set of libraries should automatically be able to link to the dependent library and in one case did not while in the other tried to link to an incorrect version. Frank J. R. Hanstick trog24 at comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeremyhu at macports.org Sat Mar 14 02:02:47 2009 From: jeremyhu at macports.org (Jeremy Huddleston) Date: Sat, 14 Mar 2009 02:02:47 -0700 Subject: Updated quartz-wm for Tiger Message-ID: I've built an updated quartz-wm for Tiger (don't try using this on Leopard) for use with the new xorg-server in MacPorts. This quartz-wm will fix the "100% CPU issue when pasteboard proxying is enabled" issue and fixes the dock interaction bug that was present in the 1.0.0 version that I built a few weeks ago. This also brings Tiger users all the fixes that have gone into quartz-wm on Leopard (gravity hints, fullscreen hints, etc). http://static.macosforge.org/xquartz/downloads/quartz-wm-1.0.1-Tiger.bz2 download it, decompress it, and place it at /opt/local/bin/quartz-wm (or change /opt/local/bin to be your prefix). You will also need to 'sudo port -v upgrade xinit' to get xinitrc to use this quartz-wm instead of the system one. --Jeremy From wa0tjt at gmail.com Sat Mar 14 08:37:38 2009 From: wa0tjt at gmail.com (Keith Kaiser) Date: Sat, 14 Mar 2009 10:37:38 -0500 Subject: ports installed Message-ID: <66760579-F89D-467F-B6F3-1D7B10575C06@gmail.com> When I do a ports installed I get the list below; but when I do a sudo port upgrade outdated I get this; Error: No ports found Anyone have an idea why? Also, how do I get rid of non-active ports? Thanks guys. The following ports are currently installed: autoconf @2.63_0 (active) automake @1.10.2_0 (active) boehmgc @7.1_0+darwin_9 (active) bzip2 @1.0.4_1 bzip2 @1.0.5_2 (active) cairo @1.4.14_0 cairo @1.8.6_4+macosx (active) coreutils @6.10_0+darwin_9 coreutils @6.12_2 (active) curl @7.18.0_0 curl @7.19.3_0 (active) expat @2.0.1_0 (active) fontconfig @2.5.0_0+macosx fontconfig @2.6.0_2+macosx (active) freetype @2.3.5_1 freetype @2.3.8_0+macosx (active) gd2 @2.0.35_1 gd2 @2.0.35_4 (active) gettext @0.17_3 gettext @0.17_4 (active) ghostscript @8.62_0 ghostscript @8.64_1 (active) glib1 @1.2.10_5 glib1 @1.2.10_6 (active) glib2 @2.16.1_0+darwin_9 glib2 @2.18.3_0+darwin_9 (active) gperf @3.0.4_0 (active) GraphicsMagick @1.1.7_0 GraphicsMagick @1.3.3_0+q8 (active) gtk1 @1.2.10_6 gtk1 @1.2.10_8 (active) help2man @1.36.4_1 (active) ImageMagick @6.3.9-7_0+q16 ImageMagick @6.4.0-2_0+q16 jpeg @6b_2 jpeg @6b_3 (active) kermit @8.0.209_0 kermit @8.0.211_0 (active) lesstif @0.95.0_3 (active) libgeotiff @1.2.1_0 (active) libiconv @1.12_0 libiconv @1.12_2 (active) libpixman @0.14.0_0 (active) libpng @1.2.25_0 libpng @1.2.35_0 (active) libtool @2.2.6a_0 (active) libxml2 @2.6.31_0 libxml2 @2.7.3_0 (active) lrzsz @0.12.20_1 (active) m4 @1.4.12_1 (active) minicom @2.1_2+darwin_9 minicom @2.3_0 (active) mrtg @2.15.2_0 (active) mrtg-ping-probe @2.2.0_0 (active) ncurses @5.6_0 ncurses @5.7_0 (active) ncursesw @5.6_1 ncursesw @5.7_0 (active) openssl @0.9.8g_0 openssl @0.9.8j_0 (active) p5-locale-gettext @1.05_0 (active) pango @1.20.0_1 pango @1.22.4_3+macosx (active) pcre @7.6_0 pcre @7.8_1 (active) perl5 @5.8.9_0 (active) perl5.8 @5.8.9_2 (active) pkgconfig @0.23_0 pkgconfig @0.23_1 (active) proj @4.6.0_0 proj @4.6.1_0 (active) putty @0.60_0 (active) readline @6.0.000_1 (active) render @0.9_1 (active) tiff @3.8.2_1+macosx tiff @3.8.2_2+darwin_9+macosx (active) urw-fonts @1.0.7pre44_0 (active) w3m @0.5.2_1 (active) wget @1.11_0 wget @1.11.1_0 wget @1.11.4_3 (active) Xft2 @2.1.12_0 Xft2 @2.1.13_1 (active) xorg-bigreqsproto @1.0.2_0 (active) xorg-inputproto @1.5.0_0 (active) xorg-kbproto @1.0.3_0 (active) xorg-libice @1.0.5_0 (active) xorg-libsm @1.1.0_0 (active) xorg-libX11 @1.2_0 (active) xorg-libXau @1.0.4_0 (active) xorg-libXdmcp @1.0.2_0 (active) xorg-libXext @1.0.5_0 (active) xorg-libXp @1.0.0_2 (active) xorg-libXt @1.0.5_1 (active) xorg-printproto @1.0.4_0 (active) xorg-renderproto @0.9.3_0 (active) xorg-util-macros @1.1.5_0 xorg-util-macros @1.2.1_1 (active) xorg-xcmiscproto @1.1.2_0 (active) xorg-xextproto @7.0.5_0 (active) xorg-xf86bigfontproto @1.1.2_0 (active) xorg-xproto @7.0.11_1 xorg-xproto @7.0.14_1 (active) xorg-xtrans @1.2.3_0 (active) xpm @3.5.7_0 (active) xrender @0.9.4_5 (active) zlib @1.2.3_1 zlib @1.2.3_2 (active) From allencmcbride at gmail.com Sat Mar 14 09:06:39 2009 From: allencmcbride at gmail.com (Allen McBride) Date: Sat, 14 Mar 2009 12:06:39 -0400 Subject: general advice about making a portfile and a binary package? In-Reply-To: <49BB2C99.6080607@macports.org> References: <49BB2C99.6080607@macports.org> Message-ID: <687F25EF-1103-4627-A1B2-BDA3F4FA8CAE@gmail.com> On Mar 14, 2009, at 12:03 AM, Rainer M?ller wrote: > Nice to hear that. Now to make that available to the wide public, I > would encourage you to submit it via Trac so we can include it in the > official ports tree. > > See > http://guide.macports.org/#project.tickets > http://guide.macports.org/#project.contributing Great, I would love to do this. I just have a few questions to get my Portfile written correctly, even though it already works for me: 1) Among the dependencies the author lists for Solfege are MIDI, GCC, and GNU Make. Any Mac has MIDI, and anyone who has installed MacPorts will have the other two, right? Do I need to include them as non-port dependencies, or can I ignore them? 2) X11 isn't listed as a dependency, but building Solfege for Aqua sounds like a whole other project. But again, any MacPorts user should have X11. Do I need to list X11 as a dependency? If so, how? "depends_lib lib:libX11:xorg-libX11"? 3) Certain versions of dependencies are required (but not cutting-edge or anything). I don't see anything in the MacPorts Guide about specifying dependency versions. Am I supposed to do this? 4) Python is a run dependency, and the python header files are a build dependency. From http://trac.macports.org/ticket/18055, it looks like there is no port of just the headers. Can I just list python as a run dependency and assume the headers will therefore be there for the build? > No, you would have to install MacPorts to a different prefix and > create > the package from there. Download the MacPorts source and use > './configure --prefix=/opt/whatever' followed by the usual make && > make > install. Then create the dmg from this port installation (use > /opt/whatever/bin/port). You would also have to create binary packages > of all dependencies being used. Thanks, this is helpful too. I'll first get my Portfile in order and then see about making binaries I can distribute. In searching the web and the list archives, I see references to a "port mdmg" command that can create just one file with all dependencies. But there's nothing in the MacPorts Guide about it. Where can I find more information about port mdmg? --Allen From brad at pixilla.com Sat Mar 14 09:13:16 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Sat, 14 Mar 2009 09:13:16 -0700 Subject: Re-do MacPorts after upgrading from Tiger to Leopard on PPC? In-Reply-To: <65C6DA19-CD28-4CDA-A453-3F9D7FBA56B3@macports.org> References: <95D3529F-FC9B-42F2-BDDD-70D90CE40692@qwest.net> <20090313054340.GN836@ninagal.withay.com> <3C38030F-4812-4129-818A-FC2BD6CA31B8@pixilla.com> <49BA7F67.9030904@macports.org> <49BA951C.5030207@macports.org> <49BAD05A.2060309@macports.org> <8589CF4F-70A6-4E0A-A8F6-48D475F52D5D@pixilla.com> <49BB3493.6070909@macports.org> <65C6DA19-CD28-4CDA-A453-3F9D7FBA56B3@macports.org> Message-ID: <976AF4CB-0DA8-42A5-99E8-1D5DD832684E@pixilla.com> On Mar 13, 2009, at 10:27 PM, Ryan Schmidt wrote: > > On Mar 13, 2009, at 23:37, Rainer M?ller wrote: > >> On 14.03.2009 4:46 Uhr, Bradley Giesbrecht wrote: >>> Thank you Rainer. >>> >>> Is the command that resulted in the installation recorded anywhere? >> >> You lost me on that one. What do you mean by "command"? > > I think he means if you have a port, say zlib, that is installed, is > it recorded anywhere why zlib is there? e.g. did it get installed > because someone typed "sudo port install zlib" or because someone > typed "sudo port install freetype +universal"? And no, that is not > recorded anywhere. Yes, that's what I meant. Logging of port install and port upgrade commands that resulted in file system changes. //Brad From raimue at macports.org Sat Mar 14 09:38:09 2009 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Sat, 14 Mar 2009 17:38:09 +0100 Subject: general advice about making a portfile and a binary package? In-Reply-To: <687F25EF-1103-4627-A1B2-BDA3F4FA8CAE@gmail.com> References: <49BB2C99.6080607@macports.org> <687F25EF-1103-4627-A1B2-BDA3F4FA8CAE@gmail.com> Message-ID: <49BBDD71.9080900@macports.org> On 14.03.2009 17:06 Uhr, Allen McBride wrote: > Great, I would love to do this. I just have a few questions to get my > Portfile written correctly, even though it already works for me: > > 1) Among the dependencies the author lists for Solfege are MIDI, GCC, > and GNU Make. Any Mac has MIDI, and anyone who has installed MacPorts > will have the other two, right? Do I need to include them as non-port > dependencies, or can I ignore them? Yes, gcc and make is assumed to be available. > 2) X11 isn't listed as a dependency, but building Solfege for Aqua > sounds like a whole other project. But again, any MacPorts user > should have X11. Do I need to list X11 as a dependency? If so, how? > "depends_lib lib:libX11:xorg-libX11"? It looks like Solfege uses GTK. In this case, simply add a dependency on port:gtk2 which itself depends on X11 if necessary, so you don't have to care about that. It is recommended to run trace mode to find all dependencies. sudo port -t destroot It will report access to files which do not belong to any port in the dependency chain. Note that a build using trace mode may fail due to the inaccessibility of files. > 3) Certain versions of dependencies are required (but not cutting-edge > or anything). I don't see anything in the MacPorts Guide about > specifying dependency versions. Am I supposed to do this? No, version information is not tracked. > 4) Python is a run dependency, and the python header files are a build > dependency. From http://trac.macports.org/ticket/18055, it looks like > there is no port of just the headers. Can I just list python as a run > dependency and assume the headers will therefore be there for the build? If a port is required at build and runtime, list it in depends_lib. >> No, you would have to install MacPorts to a different prefix and >> create >> the package from there. Download the MacPorts source and use >> './configure --prefix=/opt/whatever' followed by the usual make && >> make >> install. Then create the dmg from this port installation (use >> /opt/whatever/bin/port). You would also have to create binary packages >> of all dependencies being used. > > Thanks, this is helpful too. I'll first get my Portfile in order and > then see about making binaries I can distribute. In searching the web > and the list archives, I see references to a "port mdmg" command that > can create just one file with all dependencies. But there's nothing > in the MacPorts Guide about it. Where can I find more information > about port mdmg? Hm, probably nowhere. I am not aware of any more documentation for packaging. Rainer From macsforever2000 at macports.org Sat Mar 14 09:38:39 2009 From: macsforever2000 at macports.org (Frank Schima) Date: Sat, 14 Mar 2009 10:38:39 -0600 Subject: ports installed In-Reply-To: <66760579-F89D-467F-B6F3-1D7B10575C06@gmail.com> References: <66760579-F89D-467F-B6F3-1D7B10575C06@gmail.com> Message-ID: <8A62B6B3-5F7F-4B19-AF0F-C54B3F779D41@macports.org> Hi Keith, On Mar 14, 2009, at 9:37 AM, Keith Kaiser wrote: > When I do a ports installed I get the list below; but when I do a > sudo port upgrade outdated I get this; Error: No ports found > > Anyone have an idea why? Because your local portindex says you are up to date. You need to first run: sudo port selfupdate > Also, how do I get rid of non-active ports? sudo port uninstall inactive Cheers! Frank From brad at pixilla.com Sat Mar 14 09:50:32 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Sat, 14 Mar 2009 09:50:32 -0700 Subject: Re-do MacPorts after upgrading from Tiger to Leopard on PPC? In-Reply-To: <538D04B3-AF0B-49D1-A90F-4E15862EACBE@macports.org> References: <95D3529F-FC9B-42F2-BDDD-70D90CE40692@qwest.net> <20090313054340.GN836@ninagal.withay.com> <3C38030F-4812-4129-818A-FC2BD6CA31B8@pixilla.com> <49BA7F67.9030904@macports.org> <538D04B3-AF0B-49D1-A90F-4E15862EACBE@macports.org> Message-ID: On Mar 13, 2009, at 10:47 PM, Ryan Schmidt wrote: > On Mar 13, 2009, at 11:17, Bradley Giesbrecht wrote: > >> port installed | sed '1d' | awk '{print $1$2}' > installed.txt >> port -f uninstall installed >> for item in $(cat installed.txt); do port install $item done > > On Mar 13, 2009, at 11:27, Bradley Giesbrecht wrote: > >> Whoops, need to remove +darwin_8. >> >> port installed | sed '1d' | sed 's|+darwin_[0-9]||g' | awk '{print >> $1$2}' > installed.txt > > It's a noble effort, but this will cause ports to be reinstalled in > alphabetical order, which is almost certainly not dependency order. > > For example, consider someone who has the ports mediawiki, php5 > +apache2+mysql5, and mysql5 +server installed. mediawiki depends on > php5 and mysql5, and php5 +mysql5 depends on mysql5. > > mediawiki is alphabetically before php5 and mysql5 so your script > will install it first. MacPorts will go and build the dependencies > php5 and mysql5 with their default variants, meaning php5 will not > have mysql5 support, and mysql5 will not have its server startup item. > > Then later in the list you will come to mysql5 +server and ask > MacPorts to install it and it will go and build the whole thing > again, only it won't be able to activate mysql5 +server because > mysql5 with no variants is already active. > > Same for php5, which will already be active with its default > +apache2 variant so the new +apache2+mysql5 won't be able to be > activated. > > > You would have to replicate the MacPorts dependency engine in your > script if you wanted to handle this correctly. But then why not > implement it inside MacPorts itself. Which you would be welcome to > do. But it's not something users need to do all that often. It makes testing things like the perl5 port easier in my opinion. If I can make changes to a Portfile, uninstall everything that might touch it and then reinstall everything I'm more likely to do more thorough testing. > There are other issues in MacPorts base that might be more important > to fix. But if you feel drawn to provide a solution for this issue > in MacPorts base, we could start by discussing how it might work and > what the command might be called. If this can't be done in 30 minutes of hacking I'd say let it go. I won't be learning tcl to add this feature. Not this weekend at any rate. I'd be happy with logging install, upgrade and uninstall commands that resulted in file system changes. This isn't a big deal. It seems to me that there are probably six or so places in the port code that would need to have a function call added and then write or use an existing function or two for formating and writing the output. If it's more complicated then this then let it go unless you want this too. u=user driven command d=depends driven command /opt/local/var/log/port.log: u,timestamp,command+args d,timestamp,command+args d,timestamp,command+args u,timestamp,command+args //Brad From brad at pixilla.com Sat Mar 14 09:57:45 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Sat, 14 Mar 2009 09:57:45 -0700 Subject: ports installed In-Reply-To: <8A62B6B3-5F7F-4B19-AF0F-C54B3F779D41@macports.org> References: <66760579-F89D-467F-B6F3-1D7B10575C06@gmail.com> <8A62B6B3-5F7F-4B19-AF0F-C54B3F779D41@macports.org> Message-ID: <4313952C-67AE-4528-9747-3F48B9765EEF@pixilla.com> On Mar 14, 2009, at 9:38 AM, Frank Schima wrote: > Hi Keith, > > > On Mar 14, 2009, at 9:37 AM, Keith Kaiser wrote: > >> When I do a ports installed I get the list below; but when I do a >> sudo port upgrade outdated I get this; Error: No ports found >> >> Anyone have an idea why? > > Because your local portindex says you are up to date. You need to > first run: > > sudo port selfupdate Also, to see what would be upgraded: port outdated >> Also, how do I get rid of non-active ports? > > sudo port uninstall inactive > > > Cheers! > Frank > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From ryandesign at macports.org Sat Mar 14 10:06:42 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 14 Mar 2009 12:06:42 -0500 Subject: Re-do MacPorts after upgrading from Tiger to Leopard on PPC? In-Reply-To: References: <95D3529F-FC9B-42F2-BDDD-70D90CE40692@qwest.net> <20090313054340.GN836@ninagal.withay.com> <3C38030F-4812-4129-818A-FC2BD6CA31B8@pixilla.com> <49BA7F67.9030904@macports.org> <538D04B3-AF0B-49D1-A90F-4E15862EACBE@macports.org> Message-ID: On Mar 14, 2009, at 11:50, Bradley Giesbrecht wrote: > On Mar 13, 2009, at 10:47 PM, Ryan Schmidt wrote: > >> You would have to replicate the MacPorts dependency engine in your >> script if you wanted to handle this correctly. But then why not >> implement it inside MacPorts itself. Which you would be welcome to >> do. But it's not something users need to do all that often. > > It makes testing things like the perl5 port easier in my opinion. > If I can make changes to a Portfile, uninstall everything that > might touch it and then reinstall everything I'm more likely to do > more thorough testing. Perhaps, but we shouldn't be encouraging people to nuke their entire MacPorts installation just to test new ports. We should have better ways. For example trace mode was intended to help. > I'd be happy with logging install, upgrade and uninstall commands > that resulted in file system changes. > > This isn't a big deal. It seems to me that there are probably six > or so places in the port code that would need to have a function > call added and then write or use an existing function or two for > formating and writing the output. If it's more complicated then > this then let it go unless you want this too. > > u=user driven command > d=depends driven command > > /opt/local/var/log/port.log: > u,timestamp,command+args > d,timestamp,command+args > d,timestamp,command+args > u,timestamp,command+args We do have the existing logging proposal here: http://trac.macports.org/wiki/LoggingProposal From jmr at macports.org Sat Mar 14 10:19:53 2009 From: jmr at macports.org (Joshua Root) Date: Sun, 15 Mar 2009 04:19:53 +1100 Subject: ports installed In-Reply-To: <66760579-F89D-467F-B6F3-1D7B10575C06@gmail.com> References: <66760579-F89D-467F-B6F3-1D7B10575C06@gmail.com> Message-ID: <49BBE739.5080000@macports.org> Keith Kaiser wrote: > When I do a ports installed I get the list below; but when I do a sudo > port upgrade outdated I get this; Error: No ports found > > Anyone have an idea why? If you have synced or selfupdated just prior to this, it simply means that the 'outdated' pseudo-port expanded to the empty set, i.e. there are no outdated ports. - Josh From allencmcbride at gmail.com Sat Mar 14 10:59:16 2009 From: allencmcbride at gmail.com (Allen McBride) Date: Sat, 14 Mar 2009 13:59:16 -0400 Subject: general advice about making a portfile and a binary package? In-Reply-To: <49BBDD71.9080900@macports.org> References: <49BB2C99.6080607@macports.org> <687F25EF-1103-4627-A1B2-BDA3F4FA8CAE@gmail.com> <49BBDD71.9080900@macports.org> Message-ID: <6E41B969-4DBB-4381-9FD9-455F342ACBD7@gmail.com> On Mar 14, 2009, at 12:38 PM, Rainer M?ller wrote: > It is recommended to run trace mode to find all dependencies. > sudo port -t destroot > It will report access to files which do not belong to any port in the > dependency chain. Note that a build using trace mode may fail due to > the > inaccessibility of files. Thanks for all the answers. I ran "sudo port -t destroot", and it seems to have revealed some problems, but I don't know how to interpret the output. Here's the relevant-seeming part of what I got: trace: access denied to /opt/local/bin/python (*unknown*) trace: access denied to /opt/local/bin/python (*unknown*) trace: access denied to /opt/local/bin/rsvg (librsvg) trace: access denied to /opt/local/bin/gs (ghostscript) trace: access denied to /opt/local/bin/pkg-config (pkgconfig) Warning: An activity was attempted outside sandbox: /var/ root/.CFUserTextEncoding Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/ _Users_allencmcbride_Allen_computer_portfiletest/work/solfege-3.14.0" && ./configure --prefix=/opt/local " returned error 1 Is it trying to tell me that I should add librsvg and ghostscript (which depends on pkgconfig) to my list of dependencies? That would seem odd, since they're not listed by the author as dependencies. Maybe they're optional, and I can still leave them out? And the python part is a mystery to me, because I did declare python25 as a dependency. As for the "outside sandbox" thing, I found a post where you said you get that all the time, so I'm guessing it's not a big deal. Everything still works fine if I don't use trace mode. Sorry to keep asking questions, but I can't find any info about trace mode in the MacPorts Guide. Thanks, Allen From brad at pixilla.com Sat Mar 14 11:57:10 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Sat, 14 Mar 2009 11:57:10 -0700 Subject: Re-do MacPorts after upgrading from Tiger to Leopard on PPC? In-Reply-To: References: <95D3529F-FC9B-42F2-BDDD-70D90CE40692@qwest.net> <20090313054340.GN836@ninagal.withay.com> <3C38030F-4812-4129-818A-FC2BD6CA31B8@pixilla.com> <49BA7F67.9030904@macports.org> <538D04B3-AF0B-49D1-A90F-4E15862EACBE@macports.org> Message-ID: <5B5E450E-9A9B-4D29-B4E3-99EFD1E5A184@pixilla.com> On Mar 14, 2009, at 10:06 AM, Ryan Schmidt wrote: > On Mar 14, 2009, at 11:50, Bradley Giesbrecht wrote: > >> On Mar 13, 2009, at 10:47 PM, Ryan Schmidt wrote: >> >>> You would have to replicate the MacPorts dependency engine in your >>> script if you wanted to handle this correctly. But then why not >>> implement it inside MacPorts itself. Which you would be welcome to >>> do. But it's not something users need to do all that often. >> >> It makes testing things like the perl5 port easier in my opinion. >> If I can make changes to a Portfile, uninstall everything that >> might touch it and then reinstall everything I'm more likely to do >> more thorough testing. > > Perhaps, but we shouldn't be encouraging people to nuke their entire > MacPorts installation just to test new ports. We should have better > ways. For example trace mode was intended to help. That sounds good to me. Since it's possible that the next perl5.8 port revision will move man and modules to new locations I wanted to test it on a clean install and also as an upgrade of an existing system. I want to verify that on the upgrade of perl5.8 the p5 files that have been -f installed are not removed when the perl5.8 port is upgraded. I also would like to be able to put my system back to it's previous state after each test. How would you suggest I do this? I'd be very happy to learn a better way. This doesn't need to occupy our time. I'm just offering ideas and features I would like. Things are working great as is. >> I'd be happy with logging install, upgrade and uninstall commands >> that resulted in file system changes. >> >> This isn't a big deal. It seems to me that there are probably six >> or so places in the port code that would need to have a function >> call added and then write or use an existing function or two for >> formating and writing the output. If it's more complicated then >> this then let it go unless you want this too. >> >> u=user driven command >> d=depends driven command >> >> /opt/local/var/log/port.log: >> u,timestamp,command+args >> d,timestamp,command+args >> d,timestamp,command+args >> u,timestamp,command+args > > We do have the existing logging proposal here: > > http://trac.macports.org/wiki/LoggingProposal +1 Nice to able to parse data into db for analysis. I don't know that this happens a lot but if I am installing a port that has deps on another port and I intend to build that other port a different way knowing why and when the port was built helps me get my build order correct. gentoo emerge has -p (pretend) which reports what emerge would do and in what order without actually doing anything. This can be useful. //Brad -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Sat Mar 14 12:17:19 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 14 Mar 2009 14:17:19 -0500 Subject: Re-do MacPorts after upgrading from Tiger to Leopard on PPC? In-Reply-To: <5B5E450E-9A9B-4D29-B4E3-99EFD1E5A184@pixilla.com> References: <95D3529F-FC9B-42F2-BDDD-70D90CE40692@qwest.net> <20090313054340.GN836@ninagal.withay.com> <3C38030F-4812-4129-818A-FC2BD6CA31B8@pixilla.com> <49BA7F67.9030904@macports.org> <538D04B3-AF0B-49D1-A90F-4E15862EACBE@macports.org> <5B5E450E-9A9B-4D29-B4E3-99EFD1E5A184@pixilla.com> Message-ID: <39C162E6-F89B-4676-A112-2ED1C67AE035@macports.org> On Mar 14, 2009, at 13:57, Bradley Giesbrecht wrote: > On Mar 14, 2009, at 10:06 AM, Ryan Schmidt wrote: > >> On Mar 14, 2009, at 11:50, Bradley Giesbrecht wrote: >> >>> It makes testing things like the perl5 port easier in my opinion. >>> If I can make changes to a Portfile, uninstall everything that >>> might touch it and then reinstall everything I'm more likely to >>> do more thorough testing. >> >> Perhaps, but we shouldn't be encouraging people to nuke their >> entire MacPorts installation just to test new ports. We should >> have better ways. For example trace mode was intended to help. > > That sounds good to me. > > Since it's possible that the next perl5.8 port revision will move > man and modules to new locations I wanted to test it on a clean > install and also as an upgrade of an existing system. I want to > verify that on the upgrade of perl5.8 the p5 files that have been - > f installed are not removed when the perl5.8 port is upgraded. > > I also would like to be able to put my system back to it's previous > state after each test. > > How would you suggest I do this? I'd be very happy to learn a > better way. You could create a new MacPorts install, side by side with your existing install. Download the MacPorts source and then: PREFIX=$HOME/macportsclean ./configure \ --prefix=$PREFIX \ --with-tclpackage=$PREFIX/Library/Tcl \ --with-applications-dir=$PREFIX/Applications \ --with-frameworks-dir=$PREFIX/Library/Frameworks \ --with-install-user=$(id -u -n) \ --with-install-group=$(id -g -n) \ --enable-readline make make install Assuming the ports you're testing are well-behaved and write only into the destroot and don't need to write to system locations, things you install with this second MacPorts install shouldn't affect what's installed in your primary MacPorts install. By installing this secondary MacPorts with a non-root user, and running your port commands without sudo, you ensure that it cannot overwrite things in your primary MacPorts install, which is presumably installed as root and therefore requires root permission to overwrite. In this way you can test whether the ports you're installing are behaving properly. Erasing this secondary MacPorts is as easy as deleting the directory $PREFIX. From jmr at macports.org Sat Mar 14 14:35:14 2009 From: jmr at macports.org (Joshua Root) Date: Sun, 15 Mar 2009 08:35:14 +1100 Subject: Re-do MacPorts after upgrading from Tiger to Leopard on PPC? In-Reply-To: <5B5E450E-9A9B-4D29-B4E3-99EFD1E5A184@pixilla.com> References: <95D3529F-FC9B-42F2-BDDD-70D90CE40692@qwest.net> <20090313054340.GN836@ninagal.withay.com> <3C38030F-4812-4129-818A-FC2BD6CA31B8@pixilla.com> <49BA7F67.9030904@macports.org> <538D04B3-AF0B-49D1-A90F-4E15862EACBE@macports.org> <5B5E450E-9A9B-4D29-B4E3-99EFD1E5A184@pixilla.com> Message-ID: <49BC2312.3070205@macports.org> Bradley Giesbrecht wrote: > gentoo emerge has -p (pretend) which reports what emerge would do and in > what order without actually doing anything. This can be useful. MP trunk has a -y (dry run) option. - Josh From t_condonia at comcast.net Sun Mar 15 09:31:03 2009 From: t_condonia at comcast.net (Tom Condon) Date: Sun, 15 Mar 2009 09:31:03 -0700 Subject: Gimp2->libgnomecanvase->gail Problem Message-ID: <49BD2D47.7080607@comcast.net> Folks, Running MacPorts on a Powerbook 2.4GHz Intel Core 2 Duo w/4GB SDRAM with OS X 10.5.6. I felt it was time to check for upgrades and kicked off the update process. Before long I noticed that there was a problem building "gail". With a little tracing I found that this appears to be looking for libgail-gnome (version 1.20.1 seems to be the current one), but there is a dependency that calls for "gail" which does not exist in macports. I did a self-update, but everything seems to be good there. When I try to build gimp2 this is the response: ------------------------------------------- sudo port install gimp2 Password: ---> Configuring libgnomecanvas Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_libgnomecanvas/work/libgnomecanvas-2.20.1.1" && ./configure --prefix=/opt/local " returned error 1 Command output: checking locale.h usability... yes checking locale.h presence... yes checking for locale.h... yes checking for LC_MESSAGES... yes checking libintl.h usability... yes checking libintl.h presence... yes checking for libintl.h... yes checking for ngettext in libc... no checking for bindtextdomain in -lintl... yes checking for ngettext in -lintl... yes checking for dgettext in -lintl... yes checking for bind_textdomain_codeset... yes checking for msgfmt... /opt/local/bin/msgfmt checking for dcgettext... yes checking if msgfmt accepts -c... yes checking for gmsgfmt... /opt/local/bin/msgfmt checking for xgettext... /opt/local/bin/xgettext checking for pkg-config... /opt/local/bin/pkg-config checking pkg-config is at least version 0.18... yes checking for LIBGNOMECANVAS... configure: error: Package requirements ( gtk+-2.0 >= 2.0.3 gail >= 1.9.0 libart-2.0 >= 2.3.8 pango >= 1.0.1 pangoft2 >= 1.0.1) were not met: No package 'gail' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables LIBGNOMECANVAS_CFLAGS and LIBGNOMECANVAS_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. Error: The following dependencies failed to build: libgnomeui libbonoboui libgnomecanvas Error: Status 1 encountered during processing. ---------------------------------------------------- Is there a problem with the dependencies here or am I missing something? In A Chord, Tom Condon Bass, Agate Passage Quartet Treasurer, Bass & Proud Member, Kitsap Chordsmen It's so hard when I have to, And so easy when I want to. - Sondra Anice Barnes From jmr at macports.org Sun Mar 15 09:39:55 2009 From: jmr at macports.org (Joshua Root) Date: Mon, 16 Mar 2009 03:39:55 +1100 Subject: Gimp2->libgnomecanvase->gail Problem In-Reply-To: <49BD2D47.7080607@comcast.net> References: <49BD2D47.7080607@comcast.net> Message-ID: <49BD2F5B.2070201@macports.org> Tom Condon wrote: > > Folks, > > Running MacPorts on a Powerbook 2.4GHz Intel Core 2 Duo w/4GB SDRAM with > OS X 10.5.6. I felt it was time to check for upgrades and kicked off > the update process. Before long I noticed that there was a problem > building "gail". With a little tracing I found that this appears to be > looking for libgail-gnome (version 1.20.1 seems to be the current one), > but there is a dependency that calls for "gail" which does not exist in > macports. I did a self-update, but everything seems to be good there. There used to be a gail port, but it is now part of gtk2 (upstream change). It's not the same thing as libgail-gnome. Upgrade your outdated ports. - Josh From wa0tjt at gmail.com Sun Mar 15 10:48:35 2009 From: wa0tjt at gmail.com (Keith Kaiser) Date: Sun, 15 Mar 2009 12:48:35 -0500 Subject: Mac (OSX) Error: Unresolved inheritance operation Message-ID: <798D022E-86C7-4CB1-BDED-A6B6523E118D@gmail.com> Mac users, Recently I decided to move from OpenMotif to lesstif in hopes of fixing the menu issues in Xastir. The first thing I did was selfupdate MacPorts, then I upgraded all installed ports, after which I used MacPorts to install lesstif (lesstif @0.95.0_3 (active)). After all this prep work I went back to the source files for Xastir (v1.9.5) and re-installed it. I used; './configure' and followed it with; 'make && sudo make install && sudo chmod 4755 /usr/local/bin/xastir' No errors were kicked up until I tried to run Xastir, that is when I got the following error: 'Error: Unresolved inheritance operation' I tried Xastir again turning on all logging (xastir -v 2047 &), below is the bottom of the log up to this error. ... Code #1126 data hotkey <> Code #1127 data hotkey <> Code #1128 data hotkey <> Code #1129 data hotkey <> Code #1130 data hotkey <> LANG 1131 Error: Unresolved inheritance operation The cursor is not returned until I do a control C at which time I get; [1]+ Exit 1 xastir -v 2047 My understanding is that an "unresolved inheritance operation" is due to a version mismatch of some kind, some component of Xastir is expecting some version of something else (maybe xfig) but it can't find it. What I need is someone much closer to the Unix roots of Mac to help me figure out where to start looking for the problem. I'm sorry this is such a long post but I wanted to give as much useful information as possible to the Mac community out there in hopes of getting Xastir up and running again. Thanks in advance for any and all who can shed some light on this. From d.l.tDeContes at free.fr Sun Mar 15 15:36:28 2009 From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=) Date: Sun, 15 Mar 2009 23:36:28 +0100 Subject: checking for gcc Message-ID: <675B1A6E-67F6-4E53-93B6-5C5EB56F7B07@free.fr> hi :-) i updade MacPorts, and at the step "port upgrade outdated" it always sets checking for gcc... /usr/bin/gcc-4.0 whereas /usr/bin/gcc-4.0 does not exist and /usr/bin/gcc points on gcc-3.3 what is the problem ? -- T?l?assistance / T?l?maintenance http://www.portparallele.com/ThomasDECONTES/ From ryandesign at macports.org Sun Mar 15 16:05:39 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 15 Mar 2009 18:05:39 -0500 Subject: checking for gcc In-Reply-To: <675B1A6E-67F6-4E53-93B6-5C5EB56F7B07@free.fr> References: <675B1A6E-67F6-4E53-93B6-5C5EB56F7B07@free.fr> Message-ID: On Mar 15, 2009, at 17:36, Thomas De Contes wrote: > i updade MacPorts, and at the step "port upgrade outdated" it > always sets > checking for gcc... /usr/bin/gcc-4.0 > > whereas /usr/bin/gcc-4.0 does not exist and /usr/bin/gcc points on > gcc-3.3 > > > what is the problem ? /usr/bin/gcc-4.0 should exist, and /usr/bin/gcc should point to it, on Tiger and later. MacPorts will use /usr/bin/gcc-4.0 on Tiger and later, and /usr/bin/gcc-3.3 on Panther. What OS version do you have? What version of Xcode? Try reinstalling the latest version of Xcode for your OS. From urkapd at libero.it Mon Mar 16 02:33:33 2009 From: urkapd at libero.it (MAS!) Date: Mon, 16 Mar 2009 10:33:33 +0100 Subject: piding: where is located the 'system.log' Message-ID: I'm trying to find where piding save the system log. it's not on ~/.purple/logs (I found a dir for each im system, but nothing for the system.log) any help? thank you in advance bye MAS! From francis at devrx.org Mon Mar 16 06:03:56 2009 From: francis at devrx.org (Francis Devereux) Date: Mon, 16 Mar 2009 13:03:56 +0000 Subject: Error in mod_wsgi Portfile? In-Reply-To: References: <49FD50C6-CCC9-4EEE-A52E-9DA1F8D32D99@devrx.org> Message-ID: On 14 Mar 2009, at 06:27, Ryan Schmidt wrote: > On Mar 10, 2009, at 12:20, Francis Devereux wrote: > >> I think that the message printed by www/mod_wsgi/Portfile is >> incorrect. The line that currently reads: >> ui_msg "# LoadModule python_module modules/mod_wsgi.so" >> should read: >> ui_msg "# LoadModule wsgi_module modules/mod_wsgi.so" >> >> If the current instructions are followed, attempting to start >> Apache gives the following error: >> jupiter LaunchDaemons # /opt/local/apache2/bin/apachectl start >> httpd: Syntax error on line 116 of /opt/local/apache2/conf/ >> httpd.conf: Can't locate API module structure `python_module' in >> file /opt/local/apache2/modules/mod_wsgi.so: dlsym(0x404e10, >> python_module): symbol not found > > I assume you are correct. As for all bugs, can you please file a > ticket in the issue tracker? > > http://guide.macports.org/#project.tickets OK. My ticket is http://trac.macports.org/ticket/18864. By the way, there is another problem with the mod_wsgi port, on my machine mod_wsgi.so ends up being linked against the system Python 2.5 instead of the Macports-installed Python 2.4. I will file a ticket for this too although it may be a while because I am very busy with non-Python stuff at work. Thanks, Francis From frstan at bellsouth.net Mon Mar 16 07:24:39 2009 From: frstan at bellsouth.net (William Davis) Date: Mon, 16 Mar 2009 10:24:39 -0400 Subject: xorg-server and Xorg-libAppleWM config errors Message-ID: <6B956C5E-837D-45F8-8E04-06D02026943F@bellsouth.net> Xorg-libAppleWM: ---> Configuring xorg-libAppleWM DEBUG: Using compiler 'Mac OS X gcc 4.0' DEBUG: Executing org.macports.configure (xorg-libAppleWM) DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.5' DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_x11_xorg-libAppleWM/work/libAppleWM-1.2.0" && autoreconf --install -fvi' autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --force /opt/local/share/aclocal/smpeg.m4:13: warning: underquoted definition of AM_PATH_SMPEG /opt/local/share/aclocal/smpeg.m4:13: run info '(automake)Extending aclocal' /opt/local/share/aclocal/smpeg.m4:13: or see http://sources.redhat.com/automake/automake.html#Extending-aclocal autoreconf: configure.ac: tracing autoreconf: running: glibtoolize --copy --force glibtoolize: putting auxiliary files in `.'. glibtoolize: copying file `./ltmain.sh' glibtoolize: You should add the contents of the following files to `aclocal.m4': glibtoolize: `/opt/local/share/aclocal/libtool.m4' glibtoolize: `/opt/local/share/aclocal/ltversion.m4' glibtoolize: `/opt/local/share/aclocal/ltsugar.m4' glibtoolize: `/opt/local/share/aclocal/lt~obsolete.m4' glibtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and glibtoolize: rerunning glibtoolize, to keep the correct libtool macros in-tree. glibtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. /opt/local/share/aclocal/smpeg.m4:13: warning: underquoted definition of AM_PATH_SMPEG /opt/local/share/aclocal/smpeg.m4:13: run info '(automake)Extending aclocal' /opt/local/share/aclocal/smpeg.m4:13: or see http://sources.redhat.com/automake/automake.html#Extending-aclocal autoreconf: running: /opt/local/bin/autoconf --force autoreconf: running: /opt/local/bin/autoheader --force autoreconf: running: automake --add-missing --copy --force-missing autoreconf: Leaving directory `.' DEBUG: Environment: CFLAGS='-O2' CPPFLAGS='-I/opt/local/include' CXXFLAGS='-O2' MACOSX_DEPLOYMENT_TARGET='10.5' CPP='/usr/bin/cpp-4.0' CXX='/usr/bin/g++-4.0' F90FLAGS='-O2' LDFLAGS='-L/opt/local/lib' FCFLAGS='-O2' OBJC='/usr/bin/gcc-4.0' INSTALL='/usr/bin/install -c' OBJCFLAGS='-O2' FFLAGS='-O2' CC='/usr/bin/gcc-4.0' DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_x11_xorg-libAppleWM/work/libAppleWM-1.2.0" && ./configure --prefix=/opt/local' checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /opt/local/bin/gmkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking if xorg-macros used to generate configure is at least 1.2... yes, 1.2.1 checking for gcc... /usr/bin/gcc-4.0 checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether /usr/bin/gcc-4.0 accepts -g... yes checking for /usr/bin/gcc-4.0 option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of /usr/bin/gcc-4.0... gcc3 ./configure: line 3733: syntax error near unexpected token `build_libtool_libs,' ./configure: line 3733: ` _LT_DECL(build_libtool_libs, enable_shared, 0,' Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_x11_xorg-libAppleWM/work/libAppleWM-1.2.0" && ./configure --prefix=/opt/local " returned error 2 Command output: checking for a BSD-compatible install... /usr/bin/ install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /opt/local/bin/gmkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking if xorg-macros used to generate configure is at least 1.2... yes, 1.2.1 checking for gcc... /usr/bin/gcc-4.0 checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether /usr/bin/gcc-4.0 accepts -g... yes checking for /usr/bin/gcc-4.0 option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of /usr/bin/gcc-4.0... gcc3 ./configure: line 3733: syntax error near unexpected token `build_libtool_libs,' ./configure: line 3733: ` _LT_DECL(build_libtool_libs, enable_shared, 0,' Warning: the following items did not execute (for xorg-libAppleWM): org.macports.destroot org.macports.configure org.macports.build DEBUG: invalid command name "::ui_init" while executing "::ui_init $priority $prefix $channels $message" ("uplevel" body line 2) invoked from within "uplevel 1 $body" Error: Unable to upgrade port: 1 xorg-server: Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_x11_xorg-server/work/xorg-server-1.4.2- apple37" && ./configure --prefix=/opt/local --with-mesa-source=/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_x11_xorg-server/work/xorg-server-1.4.2- apple37/../Mesa-7.0.4 --with-apple-applications-dir=/Applications/ MacPorts --with-fontdir=/opt/local/share/fonts --with-apple- application-id=org.macports.X11 " returned error 1 Command output: checking for XDMCP... yes checking for XdmcpWrap in -lXdmcp... yes checking for XSERVERCFLAGS... yes checking for XSERVERLIBS... yes checking for clock_gettime... no checking for clock_gettime in -lrt... no checking for a useful monotonic clock ...... no checking if SVR4 needs to be defined... no checking whether to build Xdmx DDX... checking for DMXMODULES... yes no checking whether to build Xvfb DDX... no checking whether to build Xnest DDX... checking for XNESTMODULES... yes no checking whether to build Xorg DDX... no checking whether to build Xgl DDX... no checking whether to build Xegl DDX... no checking whether to build Xglx DDX... no checking whether to build XWin DDX... no checking for xp_init in -lXplugin... yes checking for XPBPROXY... configure: error: Package requirements (applewmproto >= 1.2 applewm >= 1.2 xfixes fixesproto x11) were not met: Requested 'applewm >= 1.2' but version of AppleWM is 1.0.0 Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables XPBPROXY_CFLAGS and XPBPROXY_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. Warning: the following items did not execute (for xorg-server): org.macports.destroot org.macports.configure org.macports.build DEBUG: Registry error: perl5 not registered as installed & active. invoked from within "registry_active ${portname}" invoked from within "$workername eval registry_active \${portname}" Error: Unable to upgrade port: 1 William Davis frstanATbellsouthDOTnet Mac OS X.5.6 Darwin 9.5.0 XQuartz 2.3.3_rc2 (xorg-server 1.4.2-apple37) Mac Mini Intel Duo @ 1.86 GHz Mundus vult decepi, ego non William Davis frstanATbellsouthDOTnet Mac OS X.5.6 Darwin 9.5.0 XQuartz 2.3.3_rc2 (xorg-server 1.4.2-apple37) Mac Mini Intel Duo @ 1.86 GHz Mundus vult decepi, ego non From allencmcbride at gmail.com Mon Mar 16 10:58:53 2009 From: allencmcbride at gmail.com (Allen McBride) Date: Mon, 16 Mar 2009 13:58:53 -0400 Subject: general advice about making a portfile and a binary package? In-Reply-To: <6E41B969-4DBB-4381-9FD9-455F342ACBD7@gmail.com> References: <49BB2C99.6080607@macports.org> <687F25EF-1103-4627-A1B2-BDA3F4FA8CAE@gmail.com> <49BBDD71.9080900@macports.org> <6E41B969-4DBB-4381-9FD9-455F342ACBD7@gmail.com> Message-ID: <1A1163A3-FAA2-4FDA-9289-08724C5409D2@gmail.com> I wrote the developer of Solfege, and he said these "dependencies" that trace mode was showing me (librsvg, ghostscript) are things that he uses to create the release tarball; they're not needed to build from the tarball. But configure still checks for them, so that's why they were showing up in trace mode. And as for the Python thing, I'm guessing that somehow trace mode couldn't figure out that opt/local/ bin/python was part of the python25 port, even though I know it is. So, I'm thinking I can go ahead and submit my Portfile to MacPorts despite these "access denied" messages from trace mode. Any suggestions to the contrary? Also, a question about the "maintainer" field of the Portfile... since I don't have commit privileges, I assume I should leave this as "nomaintainer" rather than putting my own e-mail in, correct? Thanks, Allen On Mar 14, 2009, at 1:59 PM, Allen McBride wrote: > Thanks for all the answers. I ran "sudo port -t destroot", and it > seems to have revealed some problems, but I don't know how to > interpret the output. Here's the relevant-seeming part of what I got: > > trace: access denied to /opt/local/bin/python (*unknown*) > trace: access denied to /opt/local/bin/python (*unknown*) > trace: access denied to /opt/local/bin/rsvg (librsvg) > trace: access denied to /opt/local/bin/gs (ghostscript) > trace: access denied to /opt/local/bin/pkg-config (pkgconfig) > Warning: An activity was attempted outside sandbox: /var/ > root/.CFUserTextEncoding > Error: Target org.macports.configure returned: configure failure: > shell command " cd "/opt/local/var/macports/build/ > _Users_allencmcbride_Allen_computer_portfiletest/work/ > solfege-3.14.0" && ./configure --prefix=/opt/local " returned error 1 > > Is it trying to tell me that I should add librsvg and ghostscript > (which depends on pkgconfig) to my list of dependencies? That would > seem odd, since they're not listed by the author as dependencies. > Maybe they're optional, and I can still leave them out? And the > python part is a mystery to me, because I did declare python25 as a > dependency. As for the "outside sandbox" thing, I found a post > where you said you get that all the time, so I'm guessing it's not a > big deal. > > Everything still works fine if I don't use trace mode. > > Sorry to keep asking questions, but I can't find any info about > trace mode in the MacPorts Guide. > > Thanks, > Allen > From rjweber at ieee.org Mon Mar 16 11:30:45 2009 From: rjweber at ieee.org (bobnox) Date: Mon, 16 Mar 2009 11:30:45 -0700 (PDT) Subject: kdepimlibs4 fails on missing symbols Message-ID: <22541469.post@talk.nabble.com> I'm a noob to macports, so maybe I'm missing something obvious, but I couldn't find this in the forum. I'm trying to install kdebase4 using macports 1.7.0. I've XCode is version 3.1.2, which I recently downloaded form apple, so I have gcc 4.2 and 4.0 installed. After installing macports, I ran update and sync, and then installed kdebase4. I get to kdepimlibs4, and it fails on missing symbols. I suspect there's a dependency problem. The error is pasted below. ---> Building kdepimlibs4 Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_kde_kdepimlibs4/work/build" && make all " returned error 2 Command output: KCal::ICalTimeZoneData::~ICalTimeZoneData()in icaltimezones.o KCal::ICalTimeZoneSource::parse(icalcomponent_impl*) in icaltimezones.o KCal::ICalTimeZoneSource::parse(QString const&, KCal::ICalTimeZones&)in icaltimezones.o "_icalproperty_get_x_name", referenced from: KCal::ICalFormatImpl::Private::readCustomProperties(icalcomponent_impl*, KCal::CustomProperties*) in icalformat_p.o KCal::ICalTimeZoneData::ICalTimeZoneData(KTimeZoneData const&, KTimeZone const&, QDate const&)in icaltimezones.o KCal::ICalTimeZoneSource::parse(icalcomponent_impl*) in icaltimezones.o "_icalproperty_new_location", referenced from: KCal::ICalFormatImpl::writeLocation(QString const&, bool)in icalformat_p.o "_icalvalue_isa", referenced from: KCal::ICalFormatImpl::readAttachment(icalproperty_impl*) in icalformat_p.o "_icaltimezone_get_builtin_timezone_from_tzid", referenced from: KCal::ICalTimeZoneSource::standardZone(QString const&, bool)in icaltimezones.o "_icalparser_parse_string", referenced from: KCal::ICalFormat::parseFreeBusy(QString const&) in icalformat.o KCal::ICalFormat::parseScheduleMessage(KCal::Calendar*, QString const&)in icalformat.o "_icalproperty_get_tzid", referenced from: KCal::ICalTimeZoneSource::parse(icalcomponent_impl*) in icaltimezones.o "_icalparameter_new_x", referenced from: KCal::ICalFormatImpl::writeAttachment(KCal::Attachment*) in icalformat_p.o KCal::ICalFormatImpl::writeAttachment(KCal::Attachment*) in icalformat_p.o KCal::ICalFormatImpl::writeAttachment(KCal::Attachment*) in icalformat_p.o KCal::ICalFormatImpl::writeAttendee(KCal::Attendee*) in icalformat_p.o "_icalproperty_get_completed", referenced from: KCal::ICalFormatImpl::readICalDateTimeProperty(icalproperty_impl*, KCal::ICalTimeZones*, bool)in icalformat_p.o ld: symbol(s) not found collect2: ld returned 1 exit status make[2]: *** [lib/libkcal.4.2.0.dylib] Error 1 make[1]: *** [kcal/CMakeFiles/kcal.dir/all] Error 2 make: *** [all] Error 2 Error: The following dependencies failed to build: kdebase4-runtime kdepimlibs4 qimageblitz Error: Status 1 encountered during processing. -- View this message in context: http://www.nabble.com/kdepimlibs4-fails-on-missing-symbols-tp22541469p22541469.html Sent from the MacPorts - Users mailing list archive at Nabble.com. From dluke at geeklair.net Mon Mar 16 11:31:55 2009 From: dluke at geeklair.net (Daniel J. Luke) Date: Mon, 16 Mar 2009 14:31:55 -0400 Subject: general advice about making a portfile and a binary package? In-Reply-To: <1A1163A3-FAA2-4FDA-9289-08724C5409D2@gmail.com> References: <49BB2C99.6080607@macports.org> <687F25EF-1103-4627-A1B2-BDA3F4FA8CAE@gmail.com> <49BBDD71.9080900@macports.org> <6E41B969-4DBB-4381-9FD9-455F342ACBD7@gmail.com> <1A1163A3-FAA2-4FDA-9289-08724C5409D2@gmail.com> Message-ID: On Mar 16, 2009, at 1:58 PM, Allen McBride wrote: > I wrote the developer of Solfege, and he said these "dependencies" > that trace mode was showing me (librsvg, ghostscript) are things > that he uses to create the release tarball; they're not needed to > build from the tarball. But configure still checks for them, so > that's why they were showing up in trace mode. And as for the > Python thing, I'm guessing that somehow trace mode couldn't figure > out that opt/local/bin/python was part of the python25 port, even > though I know it is. you can do 'port provides foo' to find out what port provides foo: % port provides /opt/local/bin/python /opt/local/bin/python is provided by: python_select If you can tell the configure script to use ${prefix}/python2.5 instead of ${prefix}/python, that would be good. > So, I'm thinking I can go ahead and submit my Portfile to MacPorts > despite these "access denied" messages from trace mode. Any > suggestions to the contrary? > > Also, a question about the "maintainer" field of the Portfile... > since I don't have commit privileges, I assume I should leave this > as "nomaintainer" rather than putting my own e-mail in, correct? No, you can put your own email address in the field. For a little while you'll need to bug a committer to actually commit any changes to your port, but after you've done it for a while you should apply for commit access so you can update it yourself. -- Daniel J. Luke +========================================================+ | *---------------- dluke at geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 194 bytes Desc: This is a digitally signed message part URL: From frstan at bellsouth.net Mon Mar 16 11:55:20 2009 From: frstan at bellsouth.net (William Davis) Date: Mon, 16 Mar 2009 14:55:20 -0400 Subject: xorg-server and Xorg-libAppleWM config errors In-Reply-To: <1E5BF970-6FC6-4B65-A365-F9116E7EF14D@apple.com> References: <6B956C5E-837D-45F8-8E04-06D02026943F@bellsouth.net> <1E5BF970-6FC6-4B65-A365-F9116E7EF14D@apple.com> Message-ID: On Mar 16, 2009, at 1:48 PM, Jeremy Huddleston wrote: > Do you have both libtool and libtool1 ports installed? > > http://trac.macports.org/ticket/18601 > > Uninstall libtool1 Yes, that fixed it. Thanks jeremy! WSD > On Mar 16, 2009, at 07:24, William Davis wrote: > >> Xorg-libAppleWM: >> >> ---> Configuring xorg-libAppleWM >> /snip >> checking dependency style of /usr/bin/gcc-4.0... gcc3 >> ./configure: line 3733: syntax error near unexpected token >> `build_libtool_libs,' >> ./configure: line 3733: ` _LT_DECL(build_libtool_libs, >> enable_shared, 0,' >> >> Warning: the following items did not execute (for xorg-libAppleWM): >> org.macports.destroot org.macports.configure org.macports.build >> DEBUG: invalid command name "::ui_init" >> while executing >> "::ui_init $priority $prefix $channels $message" >> ("uplevel" body line 2) >> invoked from within >> "uplevel 1 $body" >> Error: Unable to upgrade port: 1 >> >> xorg-server: >> >> >> Error: Target org.macports.configure returned: configure failure: >> shell command " cd "/opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_x11_xorg-server/work/xorg-server-1.4.2- >> apple37" && ./configure --prefix=/opt/local --with-mesa-source=/opt/ >> local/var/macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_x11_xorg-server/work/xorg-server-1.4.2- >> apple37/../Mesa-7.0.4 --with-apple-applications-dir=/Applications/ >> MacPorts --with-fontdir=/opt/local/share/fonts --with-apple- >> application-id=org.macports.X11 " returned error 1 >> Command output: checking for XDMCP... yes >> checking for XdmcpWrap in -lXdmcp... yes >> /snip/ >> checking for xp_init in -lXplugin... yes >> checking for XPBPROXY... configure: error: Package requirements >> (applewmproto >= 1.2 applewm >= 1.2 xfixes fixesproto x11) were not >> met: >> >> Requested 'applewm >= 1.2' but version of AppleWM is 1.0.0 >> >> Consider adjusting the PKG_CONFIG_PATH environment variable if you >> installed software in a non-standard prefix. >> >> Alternatively, you may set the environment variables XPBPROXY_CFLAGS >> and XPBPROXY_LIBS to avoid the need to call pkg-config. >> See the pkg-config man page for more details. >> >> >> Warning: the following items did not execute (for xorg-server): >> org.macports.destroot org.macports.configure org.macports.build >> DEBUG: Registry error: perl5 not registered as installed & active. >> invoked from within >> "registry_active ${portname}" >> invoked from within >> "$workername eval registry_active \${portname}" >> Error: Unable to upgrade port: 1 >> William Davis frstanATbellsouthDOTnet Mac OS X.5.6 Darwin 9.5.0 XQuartz 2.3.3_rc2 (xorg-server 1.4.2-apple37) Mac Mini Intel Duo @ 1.86 GHz Mundus vult decepi, ego non From serra at atmo.arizona.edu Mon Mar 16 12:15:06 2009 From: serra at atmo.arizona.edu (Yolande Serra) Date: Mon, 16 Mar 2009 12:15:06 -0700 Subject: netcdf 4.0 lib not linking In-Reply-To: References: Message-ID: I've written previously about this issue and got no reply. I'm trying again after trying everything I could think of to get my netcdf 4.0 library installed with macport to work with the gcc43 also installed with macport. I made a local port for netcdf in which I compiled it with gcc43 after having installed gcc43 from macport. The build worked and I configured it with gfortran so that the fortran libs were also installed with my netcdf libs. I selected to not have separate fortran libraries and did not configure with shared libraries so everything is in libnetcdf.a. I checked using otool and all the right references are in libnetcdf.a, at least if I compare it to a working version of netcdf 4.0 on my old powerpc mac. No netcdf 4.0 options were turned on so I did not have to install netcdf with hdf5, zlib or szlib (as this is what I tried at first and did not get it to work). So, the question is why do I get linking errors when I try to compile fortran code that calls the netcdf libs? I compile the code with gfortran-mp-4.3 and use the same options as when I built netcdf 4.0 (- fno-second-underscore -O2 -g). I also have provided the location of the include file and library explicitly in the compile command line (- I/opt/local/include and -L/opt/local/lib -lnetcdf). I also call some udunits functions which do not give any errors and udunits was also installed using macports and is in /opt/local. Do I need to recompile the gcc43 using the same options (-fno-second- underscore)?? I tried compiling netcdf libs without this option, but this also did not work. I tried compiling my code without that option as well and it did not work. I also tried -fno-underscoring - no luck. I have a netcdf 4.0 library installed on my powerpc mac and can use gcc4.3 with that library with no problem but neither of these packages were installed with macports. I'd like to use macports for the new mac (intel), as it seems more convenient than building source code myself all the time. However, I desperately need a working netcdf library as all my data is stored this way. Thanks for any help, Yolande From allencmcbride at gmail.com Mon Mar 16 12:46:50 2009 From: allencmcbride at gmail.com (Allen McBride) Date: Mon, 16 Mar 2009 15:46:50 -0400 Subject: sorting out trace mode "access denied" messages In-Reply-To: References: <49BB2C99.6080607@macports.org> <687F25EF-1103-4627-A1B2-BDA3F4FA8CAE@gmail.com> <49BBDD71.9080900@macports.org> <6E41B969-4DBB-4381-9FD9-455F342ACBD7@gmail.com> <1A1163A3-FAA2-4FDA-9289-08724C5409D2@gmail.com> Message-ID: <1367D7AD-C8F7-4B3D-9835-1E455C22C1A9@gmail.com> Thanks for the hints. I changed the subject line to be more descriptive. Two things: First, I added the line "configure.env PYTHON=${prefix}/bin/python2.5" to my portfile. And now when I do a "sudo port -v configure", I see configure is clearly finding python2.5, not python. Yet, now when I do "sudo port -t destroot", I get the following two lines repeated 14 times: trace: access denied to /opt/local/Library/Frameworks/Python.framework/ Versions/2.5/lib/python2.5/os.py (*unknown*) trace: access denied to /opt/local/Library/Frameworks/Python.framework/ Versions/2.5/lib/python2.5/os.pyc (*unknown*) But "port provides" says these two files are provided by python25. Second... and I don't know if this is important, but... "port provides /opt/local/bin/python", for me, returns "/opt/local/bin/ python is not provided by a MacPorts port." Yet /opt/local/bin/python, which is a symlink to python2.5, was definitely created by python_select (I ran python_select again just to be sure). And "port provides" does confirm that "python_select" is provided by python_select and python2.5 is provided by python25. As always, though, "sudo port install" still works fine. Thanks, Allen On Mar 16, 2009, at 2:31 PM, Daniel J. Luke wrote: > you can do 'port provides foo' to find out what port provides foo: > > % port provides /opt/local/bin/python > /opt/local/bin/python is provided by: python_select > > If you can tell the configure script to use ${prefix}/python2.5 > instead of ${prefix}/python, that would be good. > >> So, I'm thinking I can go ahead and submit my Portfile to MacPorts >> despite these "access denied" messages from trace mode. Any >> suggestions to the contrary? >> >> Also, a question about the "maintainer" field of the Portfile... >> since I don't have commit privileges, I assume I should leave this >> as "nomaintainer" rather than putting my own e-mail in, correct? > > > No, you can put your own email address in the field. For a little > while you'll need to bug a committer to actually commit any changes > to your port, but after you've done it for a while you should apply > for commit access so you can update it yourself. > > -- > Daniel J. Luke > +========================================================+ > | *---------------- dluke at geeklair.net ----------------* | > | *-------------- http://www.geeklair.net -------------* | > +========================================================+ > | Opinions expressed are mine and do not necessarily | > | reflect the opinions of my employer. | > +========================================================+ > > > From raimue at macports.org Mon Mar 16 13:39:25 2009 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Mon, 16 Mar 2009 21:39:25 +0100 Subject: sorting out trace mode "access denied" messages In-Reply-To: <1367D7AD-C8F7-4B3D-9835-1E455C22C1A9@gmail.com> References: <49BB2C99.6080607@macports.org> <687F25EF-1103-4627-A1B2-BDA3F4FA8CAE@gmail.com> <49BBDD71.9080900@macports.org> <6E41B969-4DBB-4381-9FD9-455F342ACBD7@gmail.com> <1A1163A3-FAA2-4FDA-9289-08724C5409D2@gmail.com> <1367D7AD-C8F7-4B3D-9835-1E455C22C1A9@gmail.com> Message-ID: <49BEB8FD.2000302@macports.org> On 2009-03-16 20:46, Allen McBride wrote: > First, I added the line "configure.env PYTHON=${prefix}/bin/python2.5" > to my portfile. And now when I do a "sudo port -v configure", I see > configure is clearly finding python2.5, not python. > Yet, now when I do "sudo port -t destroot", I get the following two > lines repeated 14 times: > trace: access denied to /opt/local/Library/Frameworks/Python.framework/ > Versions/2.5/lib/python2.5/os.py (*unknown*) > trace: access denied to /opt/local/Library/Frameworks/Python.framework/ > Versions/2.5/lib/python2.5/os.pyc (*unknown*) > But "port provides" says these two files are provided by python25. $ port provides /opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/os.py /opt/local/lib/python2.5/os.py is provided by: python25 The path /opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5 is a symlink to /opt/local/lib/python2.5. Trace mode does not seem to follow or honor the symlink. But actually trace mode is correct. The path /opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/os.py is not associated with any port. Ideally, it would check that the given path resolves to a valid path and is only using symlinks which belong to ports in the dependency chain. I would say you found a bug in trace mode. > Second... and I don't know if this is important, but... > "port provides /opt/local/bin/python", for me, returns "/opt/local/bin/ > python is not provided by a MacPorts port." > Yet /opt/local/bin/python, which is a symlink to python2.5, was > definitely created by python_select (I ran python_select again just to > be sure). > And "port provides" does confirm that "python_select" is provided by > python_select and python2.5 is provided by python25. This is normal behavior. As the symlink can be added/removed or changed using python_select, it does not belong to the port. To use MacPorts terms, it is created directly in prefix by running python_select, not in the destroot. Rainer From allencmcbride at gmail.com Mon Mar 16 14:46:09 2009 From: allencmcbride at gmail.com (Allen McBride) Date: Mon, 16 Mar 2009 17:46:09 -0400 Subject: sorting out trace mode "access denied" messages In-Reply-To: <49BEB8FD.2000302@macports.org> References: <49BB2C99.6080607@macports.org> <687F25EF-1103-4627-A1B2-BDA3F4FA8CAE@gmail.com> <49BBDD71.9080900@macports.org> <6E41B969-4DBB-4381-9FD9-455F342ACBD7@gmail.com> <1A1163A3-FAA2-4FDA-9289-08724C5409D2@gmail.com> <1367D7AD-C8F7-4B3D-9835-1E455C22C1A9@gmail.com> <49BEB8FD.2000302@macports.org> Message-ID: Thanks again! It sounds like my portfile is probably about as good as it's going to get. I'll submit it soon. --Allen On Mar 16, 2009, at 4:39 PM, Rainer M?ller wrote: [...] > But actually trace mode is correct. The path > /opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/ > python2.5/os.py > is not associated with any port. Ideally, it would check that the > given > path resolves to a valid path and is only using symlinks which > belong to > ports in the dependency chain. I would say you found a bug in trace > mode. [...] > This is normal behavior. As the symlink can be added/removed or > changed > using python_select, it does not belong to the port. To use MacPorts > terms, it is created directly in prefix by running python_select, > not in > the destroot. > > Rainer From ryandesign at macports.org Mon Mar 16 16:17:04 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 16 Mar 2009 18:17:04 -0500 Subject: netcdf 4.0 lib not linking In-Reply-To: References: Message-ID: On Mar 16, 2009, at 14:15, Yolande Serra wrote: > I've written previously about this issue and got no reply. I'm > trying again after trying everything I could think of to get my > netcdf 4.0 library installed with macport to work with the gcc43 > also installed with macport. I made a local port for netcdf in > which I compiled it with gcc43 after having installed gcc43 from > macport. The build worked and I configured it with gfortran so > that the fortran libs were also installed with my netcdf libs. I > selected to not have separate fortran libraries and did not > configure with shared libraries so everything is in libnetcdf.a. I > checked using otool and all the right references are in > libnetcdf.a, at least if I compare it to a working version of > netcdf 4.0 on my old powerpc mac. No netcdf 4.0 options were > turned on so I did not have to install netcdf with hdf5, zlib or > szlib (as this is what I tried at first and did not get it to work). > > So, the question is why do I get linking errors when I try to > compile fortran code that calls the netcdf libs? I compile the > code with gfortran-mp-4.3 and use the same options as when I built > netcdf 4.0 (-fno-second-underscore -O2 -g). I also have provided > the location of the include file and library explicitly in the > compile command line (-I/opt/local/include and -L/opt/local/lib - > lnetcdf). I also call some udunits functions which do not give any > errors and udunits was also installed using macports and is in /opt/ > local. > > Do I need to recompile the gcc43 using the same options (-fno- > second-underscore)?? I tried compiling netcdf libs without this > option, but this also did not work. I tried compiling my code > without that option as well and it did not work. I also tried -fno- > underscoring - no luck. I have a netcdf 4.0 library installed on my > powerpc mac and can use gcc4.3 with that library with no problem > but neither of these packages were installed with macports. I'd > like to use macports for the new mac (intel), as it seems more > convenient than building source code myself all the time. However, > I desperately need a working netcdf library as all my data is > stored this way. I'm afraid your specific questions are beyond my expertise. I'm curious why you cannot use the netcdf port unmodified as it exists in MacPorts today. If it does not meet your needs, have you discussed your needs with the maintainer of the netcdf port to see if the port can be enhanced to meet your needs? From ryandesign at macports.org Mon Mar 16 16:18:05 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 16 Mar 2009 18:18:05 -0500 Subject: piding: where is located the 'system.log' In-Reply-To: References: Message-ID: On Mar 16, 2009, at 04:33, MAS! wrote: > I'm trying to find where piding save the system log. > > it's not on ~/.purple/logs (I found a dir for each im system, but > nothing for the system.log) > > any help? I haven't used pidgin specifically. Does it perhaps write to "the" system.log which is at /var/log/system.log? From ryandesign at macports.org Mon Mar 16 16:20:51 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 16 Mar 2009 18:20:51 -0500 Subject: Updated quartz-wm for Tiger In-Reply-To: References: Message-ID: <219A01B0-F6C9-4E24-9363-BFE85BFE1D15@macports.org> On Mar 14, 2009, at 04:02, Jeremy Huddleston wrote: > I've built an updated quartz-wm for Tiger (don't try using this on > Leopard) for use with the new xorg-server in MacPorts. This quartz- > wm will fix the "100% CPU issue when pasteboard proxying is > enabled" issue and fixes the dock interaction bug that was present > in the 1.0.0 version that I built a few weeks ago. This also > brings Tiger users all the fixes that have gone into quartz-wm on > Leopard (gravity hints, fullscreen hints, etc). > > http://static.macosforge.org/xquartz/downloads/quartz-wm-1.0.1- > Tiger.bz2 > > download it, decompress it, and place it at /opt/local/bin/quartz- > wm (or change /opt/local/bin to be your prefix). > > You will also need to 'sudo port -v upgrade xinit' to get xinitrc > to use this quartz-wm instead of the system one. You are recommending people download and install something into the MacPorts prefix, without using MacPorts? Why can this not be installed with a MacPorts port? From ryandesign at macports.org Mon Mar 16 16:28:38 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 16 Mar 2009 18:28:38 -0500 Subject: Boost installation In-Reply-To: <6A1187BB-F94D-4CEE-B8C8-1055D624D0D4@comcast.net> References: <6A1187BB-F94D-4CEE-B8C8-1055D624D0D4@comcast.net> Message-ID: On Mar 14, 2009, at 02:31, Frank J. R. Hanstick wrote: > When trying to link the installed Boost to openvrml, I ran into > the following: > > g++ -D_THREAD_SAFE -g -O2 -o .libs/browser browser.o -Wl,- > bind_at_load -L/usr/local/spidermonkey/lib/ -L/opt/local/ > lib ./.libs/libtest-openvrml.a /Users/frank/FirefoxDownloads/ > openvrml-0.17.11/src/libopenvrml/.libs/libopenvrml.dylib -L/sw/lib/ > firefox2 /opt/local/lib/libjpeg.dylib /opt/local/lib/ > libpng12.dylib /opt/local/lib/libfontconfig.dylib /opt/local/lib/ > libiconv.dylib /opt/local/lib/libexpat.dylib /opt/local/lib/ > libfreetype.dylib -lz -lmozjs -lplds4 -lplc4 -lnspr4 -ldl - > lboost_thread-mt -lboost_unit_test_framework-mt -lboost_filesystem-mt > /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: Undefined symbols: > boost::system::get_system_category() > boost::system::get_generic_category() > collect2: ld returned 1 exit status > make[2]: *** [browser] Error 1 > make[2]: Leaving directory `/Users/frank/FirefoxDownloads/ > openvrml-0.17.11/tests' > make[1]: *** [check-am] Error 2 > make[1]: Leaving directory `/Users/frank/FirefoxDownloads/ > openvrml-0.17.11/tests' > make: *** [check-recursive] Error 1 > > On an earlier attempt to link Boost to openvrml, I ran into the > following: > > g++ -D_THREAD_SAFE -g -O2 -o .libs/browser browser.o -Wl,- > bind_at_load -L/usr/local/spidermonkey/lib/ ./.libs/libtest- > openvrml.a /Users/frank/FirefoxDownloads/openvrml-0.17.11/src/ > libopenvrml/.libs/libopenvrml.dylib -L/opt/local/lib -L/sw/lib/ > firefox2 /opt/local/lib/libjpeg.dylib /opt/local/lib/ > libpng12.dylib /opt/local/lib/libfontconfig.dylib /opt/local/lib/ > libiconv.dylib /opt/local/lib/libexpat.dylib /opt/local/lib/ > libfreetype.dylib -lz -lmozjs -lplds4 -lplc4 -lnspr4 -ldl - > lboost_thread-xgcc40-mt -lboost_unit_test_framework-xgcc40-mt - > lboost_filesystem-xgcc40-mt > /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: warning can't open > dynamic library: libboost_system-xgcc40-mt-1_37.dylib referenced > from: /usr/local/lib/libboost_filesystem-xgcc40-mt.dylib (checking > for undefined symbols may be affected) (No such file or directory, > errno = 2) > /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: Undefined symbols: > boost::system::get_system_category() > boost::system::get_generic_category() > boost::system::get_system_category() referenced from libboost > expected to be defined in libboost_system-xgcc40-mt-1_37.dylib > boost::system::get_generic_category() referenced from libboost > expected to be defined in libboost_system-xgcc40-mt-1_37.dylib > collect2: ld returned 1 exit status > make[2]: *** [browser] Error 1 > make[2]: Leaving directory `/Users/frank/FirefoxDownloads/ > openvrml-0.17.11/tests' > make[1]: *** [check-am] Error 2 > make[1]: Leaving directory `/Users/frank/FirefoxDownloads/ > openvrml-0.17.11/tests' > make: *** [check-recursive] Error 1 > > Though the earlier attempt had the Boost libraries in /usr/local/ > lib, the earlier attempt is related to the MacPorts installed > attempt with one difference, the earlier recognized that the > dependency of libboost_system-xgcc40-mt.dylib by > libboost_filesystem-xgcc40-mt.dylib was needed; however, sought the > wrong libboost_system-xgcc40-mt.dylib. The MacPorts installation > did not have such recognition before hand. Quite obviously, the > problem is that a library dependent on another library within its > own set of libraries should automatically be able to link to the > dependent library and in one case did not while in the other tried > to link to an incorrect version. I don't know about your specific question, but in both sets of output you quote above I see -L/usr/local/spidermonkey/lib/ and -L/sw/lib/firefox2 So presumably you have libraries in /usr/local and /sw, neither of which is recommended or supported when using MacPorts. Please try again after you have removed or moved aside /usr/local and /sw. From jeremyhu at macports.org Mon Mar 16 16:53:41 2009 From: jeremyhu at macports.org (Jeremy Huddleston) Date: Mon, 16 Mar 2009 16:53:41 -0700 Subject: Updated quartz-wm for Tiger In-Reply-To: <219A01B0-F6C9-4E24-9363-BFE85BFE1D15@macports.org> References: <219A01B0-F6C9-4E24-9363-BFE85BFE1D15@macports.org> Message-ID: <085B221D-407A-4578-BD0F-637818DD5418@macports.org> On Mar 16, 2009, at 16:20, Ryan Schmidt wrote: > > On Mar 14, 2009, at 04:02, Jeremy Huddleston wrote: > >> I've built an updated quartz-wm for Tiger (don't try using this on >> Leopard) for use with the new xorg-server in MacPorts. This quartz- >> wm will fix the "100% CPU issue when pasteboard proxying is >> enabled" issue and fixes the dock interaction bug that was present >> in the 1.0.0 version that I built a few weeks ago. This also >> brings Tiger users all the fixes that have gone into quartz-wm on >> Leopard (gravity hints, fullscreen hints, etc). >> >> http://static.macosforge.org/xquartz/downloads/quartz-wm-1.0.1-Tiger.bz2 >> >> download it, decompress it, and place it at /opt/local/bin/quartz- >> wm (or change /opt/local/bin to be your prefix). >> >> You will also need to 'sudo port -v upgrade xinit' to get xinitrc >> to use this quartz-wm instead of the system one. > > You are recommending people download and install something into the > MacPorts prefix, without using MacPorts? > > Why can this not be installed with a MacPorts port? Well, quartz-wm isn't open source, so I thought I can't make a port for it. If that's not the case, I'll gladly make a port for this, since it'll make things work nicer. From ryandesign at macports.org Mon Mar 16 17:39:19 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 16 Mar 2009 19:39:19 -0500 Subject: Updated quartz-wm for Tiger In-Reply-To: <085B221D-407A-4578-BD0F-637818DD5418@macports.org> References: <219A01B0-F6C9-4E24-9363-BFE85BFE1D15@macports.org> <085B221D-407A-4578-BD0F-637818DD5418@macports.org> Message-ID: On Mar 16, 2009, at 18:53, Jeremy Huddleston wrote: > On Mar 16, 2009, at 16:20, Ryan Schmidt wrote: > >> On Mar 14, 2009, at 04:02, Jeremy Huddleston wrote: >> >>> I've built an updated quartz-wm for Tiger (don't try using this >>> on Leopard) for use with the new xorg-server in MacPorts. This >>> quartz-wm will fix the "100% CPU issue when pasteboard proxying >>> is enabled" issue and fixes the dock interaction bug that was >>> present in the 1.0.0 version that I built a few weeks ago. This >>> also brings Tiger users all the fixes that have gone into quartz- >>> wm on Leopard (gravity hints, fullscreen hints, etc). >>> >>> http://static.macosforge.org/xquartz/downloads/quartz-wm-1.0.1- >>> Tiger.bz2 >>> >>> download it, decompress it, and place it at /opt/local/bin/quartz- >>> wm (or change /opt/local/bin to be your prefix). >>> >>> You will also need to 'sudo port -v upgrade xinit' to get xinitrc >>> to use this quartz-wm instead of the system one. >> >> You are recommending people download and install something into >> the MacPorts prefix, without using MacPorts? >> >> Why can this not be installed with a MacPorts port? > > Well, quartz-wm isn't open source, so I thought I can't make a port > for it. If that's not the case, I'll gladly make a port for this, > since it'll make things work nicer. I have a few non-open-source ports in MacPorts already: oracle- instantclient, isightcapture. As long as it's free software I don't see a problem with making ports of non-open-source software especially if it's a dependency of another port we want to have (e.g. oracle-instantclient is there so that there can be a +oracle variant of the php5 port). From jeremyhu at macports.org Mon Mar 16 18:51:19 2009 From: jeremyhu at macports.org (Jeremy Huddleston) Date: Mon, 16 Mar 2009 18:51:19 -0700 Subject: Updated quartz-wm for Tiger In-Reply-To: References: <219A01B0-F6C9-4E24-9363-BFE85BFE1D15@macports.org> <085B221D-407A-4578-BD0F-637818DD5418@macports.org> Message-ID: On Mar 16, 2009, at 17:39, Ryan Schmidt wrote: > > On Mar 16, 2009, at 18:53, Jeremy Huddleston wrote: > >> On Mar 16, 2009, at 16:20, Ryan Schmidt wrote: >> >>> On Mar 14, 2009, at 04:02, Jeremy Huddleston wrote: >>> >>>> I've built an updated quartz-wm for Tiger (don't try using this >>>> on Leopard) for use with the new xorg-server in MacPorts. This >>>> quartz-wm will fix the "100% CPU issue when pasteboard proxying >>>> is enabled" issue and fixes the dock interaction bug that was >>>> present in the 1.0.0 version that I built a few weeks ago. This >>>> also brings Tiger users all the fixes that have gone into quartz- >>>> wm on Leopard (gravity hints, fullscreen hints, etc). >>>> >>>> http://static.macosforge.org/xquartz/downloads/quartz-wm-1.0.1-Tiger.bz2 >>>> >>>> download it, decompress it, and place it at /opt/local/bin/quartz- >>>> wm (or change /opt/local/bin to be your prefix). >>>> >>>> You will also need to 'sudo port -v upgrade xinit' to get xinitrc >>>> to use this quartz-wm instead of the system one. >>> >>> You are recommending people download and install something into >>> the MacPorts prefix, without using MacPorts? >>> >>> Why can this not be installed with a MacPorts port? >> >> Well, quartz-wm isn't open source, so I thought I can't make a port >> for it. If that's not the case, I'll gladly make a port for this, >> since it'll make things work nicer. > > I have a few non-open-source ports in MacPorts already: oracle- > instantclient, isightcapture. As long as it's free software I don't > see a problem with making ports of non-open-source software > especially if it's a dependency of another port we want to have > (e.g. oracle-instantclient is there so that there can be a +oracle > variant of the php5 port). Excellent. Then with that blessing, I shall run off and create a quartz-wm port! From jeremyhu at macports.org Mon Mar 16 19:55:23 2009 From: jeremyhu at macports.org (Jeremy Huddleston) Date: Mon, 16 Mar 2009 19:55:23 -0700 Subject: Updated quartz-wm for Tiger In-Reply-To: References: <219A01B0-F6C9-4E24-9363-BFE85BFE1D15@macports.org> <085B221D-407A-4578-BD0F-637818DD5418@macports.org> Message-ID: <53CD79B4-974C-4BF0-9158-520C17987C44@macports.org> Ok, the port 'quartz-wm' is now available (and a runtime dependency of the xorg meta-port). I compiled the latest quartz-wm for both Leopard and Tiger against MacPorts. --Jeremy On Mar 16, 2009, at 18:51, Jeremy Huddleston wrote: > > On Mar 16, 2009, at 17:39, Ryan Schmidt wrote: > >> >> On Mar 16, 2009, at 18:53, Jeremy Huddleston wrote: >> >>> On Mar 16, 2009, at 16:20, Ryan Schmidt wrote: >>> >>>> On Mar 14, 2009, at 04:02, Jeremy Huddleston wrote: >>>> >>>>> I've built an updated quartz-wm for Tiger (don't try using this >>>>> on Leopard) for use with the new xorg-server in MacPorts. This >>>>> quartz-wm will fix the "100% CPU issue when pasteboard proxying >>>>> is enabled" issue and fixes the dock interaction bug that was >>>>> present in the 1.0.0 version that I built a few weeks ago. This >>>>> also brings Tiger users all the fixes that have gone into quartz- >>>>> wm on Leopard (gravity hints, fullscreen hints, etc). >>>>> >>>>> http://static.macosforge.org/xquartz/downloads/quartz-wm-1.0.1-Tiger.bz2 >>>>> >>>>> download it, decompress it, and place it at /opt/local/bin/ >>>>> quartz-wm (or change /opt/local/bin to be your prefix). >>>>> >>>>> You will also need to 'sudo port -v upgrade xinit' to get >>>>> xinitrc to use this quartz-wm instead of the system one. >>>> >>>> You are recommending people download and install something into >>>> the MacPorts prefix, without using MacPorts? >>>> >>>> Why can this not be installed with a MacPorts port? >>> >>> Well, quartz-wm isn't open source, so I thought I can't make a >>> port for it. If that's not the case, I'll gladly make a port for >>> this, since it'll make things work nicer. >> >> I have a few non-open-source ports in MacPorts already: oracle- >> instantclient, isightcapture. As long as it's free software I don't >> see a problem with making ports of non-open-source software >> especially if it's a dependency of another port we want to have >> (e.g. oracle-instantclient is there so that there can be a +oracle >> variant of the php5 port). > > Excellent. Then with that blessing, I shall run off and create a > quartz-wm port! > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From trog24 at comcast.net Mon Mar 16 23:31:36 2009 From: trog24 at comcast.net (Frank J. R. Hanstick) Date: Mon, 16 Mar 2009 23:31:36 -0700 Subject: Boost installation In-Reply-To: References: <6A1187BB-F94D-4CEE-B8C8-1055D624D0D4@comcast.net> Message-ID: <10953DD2-FD02-403C-95AB-D40E48325513@comcast.net> On Mar 16, 2009, at 4:28 PM, Ryan Schmidt wrote: > On Mar 14, 2009, at 02:31, Frank J. R. Hanstick wrote: > >> When trying to link the installed Boost to openvrml, I ran into >> the following: >> >> g++ -D_THREAD_SAFE -g -O2 -o .libs/browser browser.o -Wl,- >> bind_at_load -L/usr/local/spidermonkey/lib/ -L/opt/local/ >> lib ./.libs/libtest-openvrml.a /Users/frank/FirefoxDownloads/ >> openvrml-0.17.11/src/libopenvrml/.libs/libopenvrml.dylib -L/sw/lib/ >> firefox2 /opt/local/lib/libjpeg.dylib /opt/local/lib/ >> libpng12.dylib /opt/local/lib/libfontconfig.dylib /opt/local/lib/ >> libiconv.dylib /opt/local/lib/libexpat.dylib /opt/local/lib/ >> libfreetype.dylib -lz -lmozjs -lplds4 -lplc4 -lnspr4 -ldl - >> lboost_thread-mt -lboost_unit_test_framework-mt -lboost_filesystem-mt >> /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: Undefined symbols: >> boost::system::get_system_category() >> boost::system::get_generic_category() >> collect2: ld returned 1 exit status >> make[2]: *** [browser] Error 1 >> make[2]: Leaving directory `/Users/frank/FirefoxDownloads/ >> openvrml-0.17.11/tests' >> make[1]: *** [check-am] Error 2 >> make[1]: Leaving directory `/Users/frank/FirefoxDownloads/ >> openvrml-0.17.11/tests' >> make: *** [check-recursive] Error 1 >> >> On an earlier attempt to link Boost to openvrml, I ran into the >> following: >> >> g++ -D_THREAD_SAFE -g -O2 -o .libs/browser browser.o -Wl,- >> bind_at_load -L/usr/local/spidermonkey/lib/ ./.libs/libtest- >> openvrml.a /Users/frank/FirefoxDownloads/openvrml-0.17.11/src/ >> libopenvrml/.libs/libopenvrml.dylib -L/opt/local/lib -L/sw/lib/ >> firefox2 /opt/local/lib/libjpeg.dylib /opt/local/lib/ >> libpng12.dylib /opt/local/lib/libfontconfig.dylib /opt/local/lib/ >> libiconv.dylib /opt/local/lib/libexpat.dylib /opt/local/lib/ >> libfreetype.dylib -lz -lmozjs -lplds4 -lplc4 -lnspr4 -ldl - >> lboost_thread-xgcc40-mt -lboost_unit_test_framework-xgcc40-mt - >> lboost_filesystem-xgcc40-mt >> /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: warning can't >> open dynamic library: libboost_system-xgcc40-mt-1_37.dylib >> referenced from: /usr/local/lib/libboost_filesystem-xgcc40- >> mt.dylib (checking for undefined symbols may be affected) (No such >> file or directory, errno = 2) >> /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: Undefined symbols: >> boost::system::get_system_category() >> boost::system::get_generic_category() >> boost::system::get_system_category() referenced from libboost >> expected to be defined in libboost_system-xgcc40-mt-1_37.dylib >> boost::system::get_generic_category() referenced from libboost >> expected to be defined in libboost_system-xgcc40-mt-1_37.dylib >> collect2: ld returned 1 exit status >> make[2]: *** [browser] Error 1 >> make[2]: Leaving directory `/Users/frank/FirefoxDownloads/ >> openvrml-0.17.11/tests' >> make[1]: *** [check-am] Error 2 >> make[1]: Leaving directory `/Users/frank/FirefoxDownloads/ >> openvrml-0.17.11/tests' >> make: *** [check-recursive] Error 1 >> >> Though the earlier attempt had the Boost libraries in /usr/local/ >> lib, the earlier attempt is related to the MacPorts installed >> attempt with one difference, the earlier recognized that the >> dependency of libboost_system-xgcc40-mt.dylib by >> libboost_filesystem-xgcc40-mt.dylib was needed; however, sought >> the wrong libboost_system-xgcc40-mt.dylib. The MacPorts >> installation did not have such recognition before hand. Quite >> obviously, the problem is that a library dependent on another >> library within its own set of libraries should automatically be >> able to link to the dependent library and in one case did not >> while in the other tried to link to an incorrect version. > > I don't know about your specific question, but in both sets of > output you quote above I see > > -L/usr/local/spidermonkey/lib/ > > and > > -L/sw/lib/firefox2 > > So presumably you have libraries in /usr/local and /sw, neither of > which is recommended or supported when using MacPorts. Please try > again after you have removed or moved aside /usr/local and /sw. > > I need those two libraries to create the Moziila plug-ins. What having those two libraries has to do with libboost_filesystem- xgcc40-mt.dylib or libboost_filesystem-mt.dylib not being able to find their respective libboost_system dependency is beyond me. One would think that when a library depends on another library in order to not create undefined symbols when referenced, the library depending on the other library would be not only know the identity of the library it needs; but, also know where that particular library is located. Such a dependency should have been resolved at library build time and not need to be addressed during the building of a program referencing the library; thus, the referencing of the required libraries to make the plug-ins is not relevant. In this particular case libboost_filesystem referenced get_system_category() and get_generic_category() which are defined in libboost_system. Why was that dependency not addressed during libboost build time? Frank J. R. Hanstick trog24 at comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Mon Mar 16 23:41:58 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 17 Mar 2009 01:41:58 -0500 Subject: Boost installation In-Reply-To: <10953DD2-FD02-403C-95AB-D40E48325513@comcast.net> References: <6A1187BB-F94D-4CEE-B8C8-1055D624D0D4@comcast.net> <10953DD2-FD02-403C-95AB-D40E48325513@comcast.net> Message-ID: <81F84604-132B-4535-A5C6-9C434FDD63AB@macports.org> On Mar 17, 2009, at 01:31, Frank J. R. Hanstick wrote: > On Mar 16, 2009, at 4:28 PM, Ryan Schmidt wrote: > >> I don't know about your specific question, but in both sets of >> output you quote above I see >> >> -L/usr/local/spidermonkey/lib/ >> >> and >> >> -L/sw/lib/firefox2 >> >> So presumably you have libraries in /usr/local and /sw, neither of >> which is recommended or supported when using MacPorts. Please try >> again after you have removed or moved aside /usr/local and /sw. > >> > I need those two libraries to create the Moziila plug-ins. > What having those two libraries has to do with libboost_filesystem- > xgcc40-mt.dylib or libboost_filesystem-mt.dylib not being able to > find their respective libboost_system dependency is beyond me. One > would think that when a library depends on another library in order > to not create undefined symbols when referenced, the library > depending on the other library would be not only know the identity > of the library it needs; but, also know where that particular > library is located. Such a dependency should have been resolved at > library build time and not need to be addressed during the building > of a program referencing the library; thus, the referencing of the > required libraries to make the plug-ins is not relevant. > In this particular case libboost_filesystem referenced > get_system_category() and get_generic_category() which are defined > in libboost_system. Why was that dependency not addressed during > libboost build time? I can't comment on such specifics. All I do know is that we cannot guarantee the correct functioning of MacPorts and MacPorts-installed software when you also have things installed in /usr/local and/or /sw. Therefore we recommend you do not have anything installed in /usr/local or /sw when using MacPorts and MacPorts-installed software. Instead, install that software using MacPorts. For example, we have a spidermonkey port which I have used and it seems to work. We also have a firefox-x11 port; I have not tried that one myself. From groups.2009 at grandfenwick.net Tue Mar 17 00:54:25 2009 From: groups.2009 at grandfenwick.net (Dave Howell) Date: Tue, 17 Mar 2009 00:54:25 -0700 Subject: Re-do MacPorts after upgrading from Tiger to Leopard on PPC? In-Reply-To: <538D04B3-AF0B-49D1-A90F-4E15862EACBE@macports.org> References: <95D3529F-FC9B-42F2-BDDD-70D90CE40692@qwest.net> <20090313054340.GN836@ninagal.withay.com> <3C38030F-4812-4129-818A-FC2BD6CA31B8@pixilla.com> <49BA7F67.9030904@macports.org> <538D04B3-AF0B-49D1-A90F-4E15862EACBE@macports.org> Message-ID: On Mar 13, 2009, at 22:47 , Ryan Schmidt wrote: > Then later in the list you will come to mysql5 +server and ask > MacPorts to install it and it will go and build the whole thing > again, only it won't be able to activate mysql5 +server because > mysql5 with no variants is already active. > > Same for php5, which will already be active with its default > +apache2 variant so the new +apache2+mysql5 won't be able to be > activated. > > > You would have to replicate the MacPorts dependency engine in your > script if you wanted to handle this correctly. But then why not > implement it inside MacPorts itself. Which you would be welcome to > do. But it's not something users need to do all that often. There > are other issues in MacPorts base that might be more important to > fix. But if you feel drawn to provide a solution for this issue in > MacPorts base, we could start by discussing how it might work and > what the command might be called. I've kind of lost track of what's being discussed here, so if what I'm about to say isn't actually a similar case, then we can just move it to a new subject heading, but having to rebuild, oh, more or less everything can be required in other circumstances than just upgrading the OS. I spend not quite four full days trying to get MacPorts to install 'ntop.' One of the most exasperating failures was, after MacPorts had spent most of the day downloading and installing all but one or two of the 30+ dependent programs, it stopped cold because this particular program was all bent out of shape because my OSX 10.4 system didn't have the very most recent version of the DevTools installed. (2.4.1, if I recall correctly). So I get them, and install them, and ask MacPorts to carry on. But now I'm getting some other error, which turns out to reflect some kind of library link failure. After a few hours of trying to blindly figure out who needed to be uninstalled and reinstalled in order to get the libraries to line up, I give up and uninstall everything. Even that failed; apparently MacPorts was linking to some part of itself. Only scrubbing the entire installation and reinstalling MacPorts from scratch allowed me to get past that problem. Sadly, even that wasn't enough to get me a working installation of ntop. Ntop's port scripts are very badly broken. After MacPorts got all the dependencies installed, I had to then install ntop itself by hand. But I definitely would have appreciated being able to tell MacPorts "No, I don't care if you *think* that everything's up to date. Please reinstall X, and trust me when I tell you that you need to recompile the entire tree of dependencies, too." From jmr at macports.org Tue Mar 17 01:23:00 2009 From: jmr at macports.org (Joshua Root) Date: Tue, 17 Mar 2009 19:23:00 +1100 Subject: Re-do MacPorts after upgrading from Tiger to Leopard on PPC? In-Reply-To: References: <95D3529F-FC9B-42F2-BDDD-70D90CE40692@qwest.net> <20090313054340.GN836@ninagal.withay.com> <3C38030F-4812-4129-818A-FC2BD6CA31B8@pixilla.com> <49BA7F67.9030904@macports.org> <538D04B3-AF0B-49D1-A90F-4E15862EACBE@macports.org> Message-ID: <49BF5DE4.3040703@macports.org> Dave Howell wrote: > > On Mar 13, 2009, at 22:47 , Ryan Schmidt wrote: > >> Then later in the list you will come to mysql5 +server and ask >> MacPorts to install it and it will go and build the whole thing again, >> only it won't be able to activate mysql5 +server because mysql5 with >> no variants is already active. >> >> Same for php5, which will already be active with its default +apache2 >> variant so the new +apache2+mysql5 won't be able to be activated. >> >> >> You would have to replicate the MacPorts dependency engine in your >> script if you wanted to handle this correctly. But then why not >> implement it inside MacPorts itself. Which you would be welcome to do. >> But it's not something users need to do all that often. There are >> other issues in MacPorts base that might be more important to fix. But >> if you feel drawn to provide a solution for this issue in MacPorts >> base, we could start by discussing how it might work and what the >> command might be called. > > I've kind of lost track of what's being discussed here, so if what I'm > about to say isn't actually a similar case, then we can just move it to > a new subject heading, but having to rebuild, oh, more or less > everything can be required in other circumstances than just upgrading > the OS. I spend not quite four full days trying to get MacPorts to > install 'ntop.' One of the most exasperating failures was, after > MacPorts had spent most of the day downloading and installing all but > one or two of the 30+ dependent programs, it stopped cold because this > particular program was all bent out of shape because my OSX 10.4 system > didn't have the very most recent version of the DevTools installed. > (2.4.1, if I recall correctly). > > So I get them, and install them, and ask MacPorts to carry on. But now > I'm getting some other error, which turns out to reflect some kind of > library link failure. After a few hours of trying to blindly figure out > who needed to be uninstalled and reinstalled in order to get the > libraries to line up, I give up and uninstall everything. Even that > failed; apparently MacPorts was linking to some part of itself. Only > scrubbing the entire installation and reinstalling MacPorts from scratch > allowed me to get past that problem. > > Sadly, even that wasn't enough to get me a working installation of ntop. > Ntop's port scripts are very badly broken. After MacPorts got all the > dependencies installed, I had to then install ntop itself by hand. > > But I definitely would have appreciated being able to tell MacPorts "No, > I don't care if you *think* that everything's up to date. Please > reinstall X, and trust me when I tell you that you need to recompile the > entire tree of dependencies, too." sudo port -f upgrade X - Josh From trog24 at comcast.net Tue Mar 17 02:32:02 2009 From: trog24 at comcast.net (Frank J. R. Hanstick) Date: Tue, 17 Mar 2009 02:32:02 -0700 Subject: Boost installation In-Reply-To: <81F84604-132B-4535-A5C6-9C434FDD63AB@macports.org> References: <6A1187BB-F94D-4CEE-B8C8-1055D624D0D4@comcast.net> <10953DD2-FD02-403C-95AB-D40E48325513@comcast.net> <81F84604-132B-4535-A5C6-9C434FDD63AB@macports.org> Message-ID: <940AC5F4-8F1A-4243-A2DF-841755188048@comcast.net> Forgot to cc to MacPorts Users. On Mar 16, 2009, at 11:41 PM, Ryan Schmidt wrote: > On Mar 17, 2009, at 01:31, Frank J. R. Hanstick wrote: > >> On Mar 16, 2009, at 4:28 PM, Ryan Schmidt wrote: >> >>> I don't know about your specific question, but in both sets of >>> output you quote above I see >>> >>> -L/usr/local/spidermonkey/lib/ >>> >>> and >>> >>> -L/sw/lib/firefox2 >>> >>> So presumably you have libraries in /usr/local and /sw, neither >>> of which is recommended or supported when using MacPorts. Please >>> try again after you have removed or moved aside /usr/local and /sw. >> >>> >> I need those two libraries to create the Moziila plug-ins. >> What having those two libraries has to do with >> libboost_filesystem-xgcc40-mt.dylib or libboost_filesystem- >> mt.dylib not being able to find their respective libboost_system >> dependency is beyond me. One would think that when a library >> depends on another library in order to not create undefined >> symbols when referenced, the library depending on the other >> library would be not only know the identity of the library it >> needs; but, also know where that particular library is located. >> Such a dependency should have been resolved at library build time >> and not need to be addressed during the building of a program >> referencing the library; thus, the referencing of the required >> libraries to make the plug-ins is not relevant. >> In this particular case libboost_filesystem referenced >> get_system_category() and get_generic_category() which are defined >> in libboost_system. Why was that dependency not addressed during >> libboost build time? > > I can't comment on such specifics. > > All I do know is that we cannot guarantee the correct functioning > of MacPorts and MacPorts-installed software when you also have > things installed in /usr/local and/or /sw. Therefore we recommend > you do not have anything installed in /usr/local or /sw when using > MacPorts and MacPorts-installed software. > > Instead, install that software using MacPorts. For example, we have > a spidermonkey port which I have used and it seems to work. We also > have a firefox-x11 port; I have not tried that one myself. > The retry without references to /usr/local/lib resulted in the following: g++ -D_THREAD_SAFE -g -O2 -o .libs/browser browser.o -Wl,- bind_at_load -L/opt/local/lib ./.libs/libtest-openvrml.a /Users/ frank/FirefoxDownloads/openvrml-0.17.12/src/libopenvrml/.libs/ libopenvrml.dylib -L/opt/local/lib/firefox-2.0.0.20 /opt/local/lib/ libjpeg.dylib /opt/local/lib/libpng12.dylib /opt/local/lib/ libfontconfig.dylib /opt/local/lib/libiconv.dylib /opt/local/lib/ libexpat.dylib /opt/local/lib/libfreetype.dylib -lz -lmozjs -lplds4 - lplc4 -lnspr4 -lboost_thread-mt -lboost_unit_test_framework-mt - lboost_filesystem-mt /usr/bin/ld: Undefined symbols: boost::system::get_system_category() boost::system::get_generic_category() collect2: ld returned 1 exit status make[2]: *** [browser] Error 1 make[2]: Leaving directory `/Users/frank/FirefoxDownloads/ openvrml-0.17.12/tests' make[1]: *** [check-am] Error 2 make[1]: Leaving directory `/Users/frank/FirefoxDownloads/ openvrml-0.17.12/tests' I told you the references to the other libraries was not relevant to the problem. This is a problem internal to the Boost library build where libboost_filesystem references get_system() and get_generic() which are defined within libboost_system, both of which are Boost library modules.. A dependency that should be taken care of in the build process of the Boost libraries Frank J. R. Hanstick trog24 at comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From serra at atmo.arizona.edu Tue Mar 17 13:06:48 2009 From: serra at atmo.arizona.edu (Yolande Serra) Date: Tue, 17 Mar 2009 13:06:48 -0700 Subject: maintainer no longer at email address Message-ID: <08CAA406-B7B9-4667-BF85-F69F8672DD9E@atmo.arizona.edu> I'm new to macports and have been trying to solve a netcdf library problem. I tried writing the maintainer directly but the email bounced back stating there was nobody with that user name at that address. Where is the correct place to report this issue? Yolande From blb at macports.org Tue Mar 17 13:53:24 2009 From: blb at macports.org (Bryan Blackburn) Date: Tue, 17 Mar 2009 14:53:24 -0600 Subject: maintainer no longer at email address In-Reply-To: <08CAA406-B7B9-4667-BF85-F69F8672DD9E@atmo.arizona.edu> References: <08CAA406-B7B9-4667-BF85-F69F8672DD9E@atmo.arizona.edu> Message-ID: <20090317205324.GG1022@ninagal.withay.com> On Tue, Mar 17, 2009 at 01:06:48PM -0700, Yolande Serra said: > I'm new to macports and have been trying to solve a netcdf library > problem. I tried writing the maintainer directly but the email bounced > back stating there was nobody with that user name at that address. Where > is the correct place to report this issue? I've confirmed that that email definitely bounces; there is a possibility of another email address for that person, so I've sent a message to find out. Otherwise, that port will go nomaintainer until someone interested steps up to take it over. As far as reporting issues the best place for it not to get lost is a trac ticket: Note there is one netcdf ticket currently: Bryan > > Yolande From serra at atmo.arizona.edu Tue Mar 17 14:01:13 2009 From: serra at atmo.arizona.edu (Yolande Serra) Date: Tue, 17 Mar 2009 14:01:13 -0700 Subject: maintainer no longer at email address In-Reply-To: <20090317205324.GG1022@ninagal.withay.com> References: <08CAA406-B7B9-4667-BF85-F69F8672DD9E@atmo.arizona.edu> <20090317205324.GG1022@ninagal.withay.com> Message-ID: <5E84781F-F976-483B-9231-9211F1D15332@atmo.arizona.edu> thanks Bryan, I checked the ticket but that is not the problem I am having. the port installs just fine. they must have fixed it. my problem is the libraries won't link to my fortran code when I try to compile. Y. On Mar 17, 2009, at 1:53 PM, Bryan Blackburn wrote: > On Tue, Mar 17, 2009 at 01:06:48PM -0700, Yolande Serra said: >> I'm new to macports and have been trying to solve a netcdf library >> problem. I tried writing the maintainer directly but the email >> bounced >> back stating there was nobody with that user name at that address. >> Where >> is the correct place to report this issue? > > I've confirmed that that email definitely bounces; there is a > possibility of > another email address for that person, so I've sent a message to > find out. > > Otherwise, that port will go nomaintainer until someone interested > steps up > to take it over. As far as reporting issues the best place for it > not to get > lost is a trac ticket: > > > > Note there is one netcdf ticket currently: > > > > Bryan > > >> >> Yolande > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From deliverable at gmail.com Tue Mar 17 14:11:30 2009 From: deliverable at gmail.com (Alexy Khrabrov) Date: Tue, 17 Mar 2009 17:11:30 -0400 Subject: qt4-mac and OpenGL Message-ID: I've got a package for graph layout visualization, called Pigale, which uses qt4 and GL via GLUT. It turns out the latter wants X11, while I was able to get a qt4-mac port to build nicely. Pigale builds fine under qt4-x11. Now I started poking around to see how those things are configured, and my hunch is that I can use PKG_CONFIG_PATH to have only one of /opt/local/libexec/qt4-mac/lib/pkgconfig /opt/local/libexec/qt4-x11/lib/pkgconfig -- and everything will be done for the right Qt flavor, right? Pigale uses --with-qt-includes=... switch to its configure, and giving it either the Aqua's or X11's .../include/ worked to build the right widgets. Apparently one can do things by QT4DIR, too -- so that would be the right libexec subdir then? What I am wondering about is the GL compatibility. Pigale uses libfreeglut to label the graph, and that wanted X11. However, under / opt/local/Frameworks/, it turns out, qt4-mac deposits a bunch of its frameworks, including a QtOpenGL. Does anyone know how those correspond to OpenGL, and why are the frameworks there only for qt4- mac and not qt4-x11? Is it just a packaging choice to keep qt4-x11 linuxy-like and thus framework-less? Cheers, Alexy From talklists at newgeo.com Tue Mar 17 14:39:40 2009 From: talklists at newgeo.com (Scott Haneda) Date: Tue, 17 Mar 2009 14:39:40 -0700 Subject: maintainer no longer at email address In-Reply-To: <08CAA406-B7B9-4667-BF85-F69F8672DD9E@atmo.arizona.edu> References: <08CAA406-B7B9-4667-BF85-F69F8672DD9E@atmo.arizona.edu> Message-ID: <91FCCE83-1035-449E-9B31-50711A13226E@newgeo.com> I would read all of section 7.3, which will tell you what to do in this case: http://guide.macports.org/#project.update-policies On Mar 17, 2009, at 1:06 PM, Yolande Serra wrote: > I'm new to macports and have been trying to solve a netcdf library > problem. I tried writing the maintainer directly but the email > bounced back stating there was nobody with that user name at that > address. Where is the correct place to report this issue? -- Scott * If you contact me off list replace talklists@ with scott@ * From serra at atmo.arizona.edu Tue Mar 17 15:13:04 2009 From: serra at atmo.arizona.edu (Yolande Serra) Date: Tue, 17 Mar 2009 15:13:04 -0700 Subject: maintainer no longer at email address In-Reply-To: <91FCCE83-1035-449E-9B31-50711A13226E@newgeo.com> References: <08CAA406-B7B9-4667-BF85-F69F8672DD9E@atmo.arizona.edu> <91FCCE83-1035-449E-9B31-50711A13226E@newgeo.com> Message-ID: ok, thanks. if I figure out what is wrong I'll go from there. I was hoping you guys could help me though! ;) -Y On Mar 17, 2009, at 2:39 PM, Scott Haneda wrote: > I would read all of section 7.3, which will tell you what to do in > this case: > http://guide.macports.org/#project.update-policies > > On Mar 17, 2009, at 1:06 PM, Yolande Serra wrote: > >> I'm new to macports and have been trying to solve a netcdf library >> problem. I tried writing the maintainer directly but the email >> bounced back stating there was nobody with that user name at that >> address. Where is the correct place to report this issue? > > -- > Scott * If you contact me off list replace talklists@ with scott@ * From urkapd at libero.it Tue Mar 17 15:47:09 2009 From: urkapd at libero.it (MAS!) Date: Tue, 17 Mar 2009 23:47:09 +0100 Subject: piding: where is located the 'system.log' In-Reply-To: References: Message-ID: >> I'm trying to find where piding save the system log. >> it's not on ~/.purple/logs (I found a dir for each im system, but >> nothing for the system.log) >> any help? > I haven't used pidgin specifically. Does it perhaps write to "the" > system.log > which is at /var/log/system.log? no it's different; but I was able to find in an hidden dir in ~/.purple/logs/$protocol/$screen_name/.system/ have a nice day! bye! MAS! From blb at macports.org Tue Mar 17 16:45:09 2009 From: blb at macports.org (Bryan Blackburn) Date: Tue, 17 Mar 2009 17:45:09 -0600 Subject: maintainer no longer at email address In-Reply-To: <5E84781F-F976-483B-9231-9211F1D15332@atmo.arizona.edu> References: <08CAA406-B7B9-4667-BF85-F69F8672DD9E@atmo.arizona.edu> <20090317205324.GG1022@ninagal.withay.com> <5E84781F-F976-483B-9231-9211F1D15332@atmo.arizona.edu> Message-ID: <20090317234509.GK1022@ninagal.withay.com> On Tue, Mar 17, 2009 at 02:01:13PM -0700, Yolande Serra said: > thanks Bryan, I checked the ticket but that is not the problem I am > having. the port installs just fine. they must have fixed it. my > problem is the libraries won't link to my fortran code when I try to > compile. FYI, netcdf is now unmaintained. For fortran issues, the only thing I'd ask is if you installed netcdf with +g95 variant since that should enable fortran bits for it. If you already did, then I have no other ideas. Bryan > > Y. > > On Mar 17, 2009, at 1:53 PM, Bryan Blackburn wrote: > >> On Tue, Mar 17, 2009 at 01:06:48PM -0700, Yolande Serra said: >>> I'm new to macports and have been trying to solve a netcdf library >>> problem. I tried writing the maintainer directly but the email >>> bounced >>> back stating there was nobody with that user name at that address. >>> Where >>> is the correct place to report this issue? >> >> I've confirmed that that email definitely bounces; there is a >> possibility of >> another email address for that person, so I've sent a message to find >> out. >> >> Otherwise, that port will go nomaintainer until someone interested >> steps up >> to take it over. As far as reporting issues the best place for it not >> to get >> lost is a trac ticket: >> >> >> >> Note there is one netcdf ticket currently: >> >> >> >> Bryan >> >> >>> >>> Yolande From mcalhoun at macports.org Tue Mar 17 17:16:00 2009 From: mcalhoun at macports.org (Marcus Calhoun-Lopez) Date: Wed, 18 Mar 2009 00:16:00 +0000 (UTC) Subject: qt4-mac and OpenGL References: Message-ID: Alexy Khrabrov gmail.com> writes: > I've got a package for graph layout visualization, called Pigale, > which uses qt4 and GL via GLUT. It turns out the latter wants X11, > while I was able to get a qt4-mac port to build nicely. Pigale builds > fine under qt4-x11. Now I started poking around to see how those > things are configured, and my hunch is that I can use PKG_CONFIG_PATH > to have only one of > /opt/local/libexec/qt4-mac/lib/pkgconfig > /opt/local/libexec/qt4-x11/lib/pkgconfig -- and everything will be done for the right Qt flavor, right? Yes, setting only one should allow you to find the correct Qt libraries. > Pigale uses --with-qt-includes=... switch to its configure, and giving it > either the Aqua's or X11's .../include/ worked to build the right > widgets. Apparently one can do things by QT4DIR, too -- so that would > be the right libexec subdir then? Although I am not familiar with Pigale, setting QT4DIR to the correct libexec directory should work. > What I am wondering about is the GL compatibility. Pigale uses > libfreeglut to label the graph, and that wanted X11. However, under / > opt/local/Frameworks/, it turns out, qt4-mac deposits a bunch of its > frameworks, including a QtOpenGL. Does anyone know how those > correspond to OpenGL, and why are the frameworks there only for qt4- > mac and not qt4-x11? Is it just a packaging choice to keep qt4-x11 > linuxy-like and thus framework-less? qt4-x11 is more closely related to the Linux version of Qt than to the Mac version. There is no way for qt4-x11 to install frameworks. Given that there would be no conflict, the frameworks from qt4-mac are put into the ${frameworks_dir} directory. They are soft links, however, to the actual installation location. qt4-mac and qt4-x11 should both have the same libraries (one .dylib and one .framework) in ${prefix}/libexec/${name}/lib They should also have the same OpenGL capability. Neither, of course, has anything to do with GLUT. -Marcus From dluke at geeklair.net Tue Mar 17 20:13:51 2009 From: dluke at geeklair.net (Daniel J. Luke) Date: Tue, 17 Mar 2009 23:13:51 -0400 Subject: maintainer no longer at email address In-Reply-To: <20090317234509.GK1022@ninagal.withay.com> References: <08CAA406-B7B9-4667-BF85-F69F8672DD9E@atmo.arizona.edu> <20090317205324.GG1022@ninagal.withay.com> <5E84781F-F976-483B-9231-9211F1D15332@atmo.arizona.edu> <20090317234509.GK1022@ninagal.withay.com> Message-ID: On Mar 17, 2009, at 7:45 PM, Bryan Blackburn wrote: > On Tue, Mar 17, 2009 at 02:01:13PM -0700, Yolande Serra said: >> thanks Bryan, I checked the ticket but that is not the problem I am >> having. the port installs just fine. they must have fixed it. my >> problem is the libraries won't link to my fortran code when I try to >> compile. > > FYI, netcdf is now unmaintained. For fortran issues, the only thing > I'd ask > is if you installed netcdf with +g95 variant since that should enable > fortran bits for it. If you already did, then I have no other ideas. It's also possible that someone here could help but we haven't seen very much detail about what is wrong (other than that it doesn't work). Is the fortran code looking for some symbol that's not in the library? -- Daniel J. Luke +========================================================+ | *---------------- dluke at geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 194 bytes Desc: This is a digitally signed message part URL: From lanceboyle at qwest.net Tue Mar 17 20:29:57 2009 From: lanceboyle at qwest.net (Jerry) Date: Tue, 17 Mar 2009 20:29:57 -0700 Subject: Re-do MacPorts after upgrading from Tiger to Leopard on PPC? In-Reply-To: <49BF5DE4.3040703@macports.org> References: <95D3529F-FC9B-42F2-BDDD-70D90CE40692@qwest.net> <20090313054340.GN836@ninagal.withay.com> <3C38030F-4812-4129-818A-FC2BD6CA31B8@pixilla.com> <49BA7F67.9030904@macports.org> <538D04B3-AF0B-49D1-A90F-4E15862EACBE@macports.org> <49BF5DE4.3040703@macports.org> Message-ID: <80D53A20-2D9E-4147-A154-9A4EE24850EC@qwest.net> > I just upgraded the OS from Tiger to Leopard on PPC. Do I need to > re- install any or all of my MacPorts stuff? > Jerry OP here. I don't know why I didn't get all the other posts in this thread--I just got the last two today and that's all. Thanks for all the answers. Even before I saw them today, I solved all my MacPorts problems by uninstall everything. I'm not being ungrateful because believe me, I'm just the opposite. However, I would like to offer a bit of feedback. My experience with MacPorts has been pretty bad. If I had really _needed_ any of the software that I tried to install, as opposed to just evaluating it, I would have been pretty hosed, I'm afraid. I mostly appreciate the ambitious goal of MacPorts and I might try again later, but not soon. As I recall, I was mainly interested in wxMaxima (a symbolic math program), gcc with Ada (GNAT), and LyX (a technical word processor). I never succeeded in installing any of these from MacPorts. The level of support I got was mostly very good but still variable, and with way too much mucking around for someone who doesn't see these things as essential. I once again tried Fink with slightly better results--a working wxMaxima and a LyX that sort of worked but lacked basic functionality such as printing and exporting. So between the MacPorts and Fink, I recovered my 9 GB of disk space and called it good for now. I can (and have) downloaded a binary of Sage which gives me browser interface to Maxima and if I'm still interested when I next get a chance, I'll download the binary of LyX. If I were on an Intel machine, the new $250 full version of Mathematica would solve all my problems in these areas (but not GNAT, to which problem I found another solution). So thanks once again. I'll revert to lurk mode for a while. Jerry From serra at atmo.arizona.edu Tue Mar 17 20:52:45 2009 From: serra at atmo.arizona.edu (Yolande Serra) Date: Tue, 17 Mar 2009 20:52:45 -0700 Subject: maintainer no longer at email address In-Reply-To: References: <08CAA406-B7B9-4667-BF85-F69F8672DD9E@atmo.arizona.edu> <20090317205324.GG1022@ninagal.withay.com> <5E84781F-F976-483B-9231-9211F1D15332@atmo.arizona.edu> <20090317234509.GK1022@ninagal.withay.com> Message-ID: On Mar 17, 2009, at 8:13 PM, Daniel J. Luke wrote: > On Mar 17, 2009, at 7:45 PM, Bryan Blackburn wrote: >> On Tue, Mar 17, 2009 at 02:01:13PM -0700, Yolande Serra said: >>> thanks Bryan, I checked the ticket but that is not the problem I am >>> having. the port installs just fine. they must have fixed it. my >>> problem is the libraries won't link to my fortran code when I try to >>> compile. >> >> FYI, netcdf is now unmaintained. For fortran issues, the only >> thing I'd ask >> is if you installed netcdf with +g95 variant since that should enable >> fortran bits for it. If you already did, then I have no other ideas. > > > It's also possible that someone here could help but we haven't seen > very much detail about what is wrong (other than that it doesn't > work). > > Is the fortran code looking for some symbol that's not in the library? yes, all of them. it cannot find any of the fortran routines like nf_open, nf_get_vara_float, etc. All the netcdf nf_ routines are listed that I call in my program when I try to compile. I think it may be an underscore issue, at least it seems that way since it is just not possible that the code does not know where libnetcdf.a is. Perhaps I should be writing the netcdf creators at this point as I've tried everything I can to get it to work and I've built it myself on my powerpc mac and had no trouble. Yolande > > > -- > Daniel J. Luke > +========================================================+ > | *---------------- dluke at geeklair.net ----------------* | > | *-------------- http://www.geeklair.net -------------* | > +========================================================+ > | Opinions expressed are mine and do not necessarily | > | reflect the opinions of my employer. | > +========================================================+ > > > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users Dr. Yolande Serra, Assoc. Research Faculty Institute of Atmospheric Physics University of Arizona (520) 621-6619 serra at atmo.arizona.edu From dluke at geeklair.net Wed Mar 18 06:18:00 2009 From: dluke at geeklair.net (Daniel J. Luke) Date: Wed, 18 Mar 2009 09:18:00 -0400 Subject: maintainer no longer at email address In-Reply-To: References: <08CAA406-B7B9-4667-BF85-F69F8672DD9E@atmo.arizona.edu> <20090317205324.GG1022@ninagal.withay.com> <5E84781F-F976-483B-9231-9211F1D15332@atmo.arizona.edu> <20090317234509.GK1022@ninagal.withay.com> Message-ID: On Mar 17, 2009, at 11:52 PM, Yolande Serra wrote: >> Is the fortran code looking for some symbol that's not in the >> library? > yes, all of them. it cannot find any of the fortran routines like > nf_open, nf_get_vara_float, etc. All the netcdf nf_ routines are > listed that I call in my program when I try to compile. I think it > may be an underscore issue, at least it seems that way since it is > just not possible that the code does not know where libnetcdf.a is. you can use 'nm' to look at the symbol table of the library and at least get a hint at what is going on. > Perhaps I should be writing the netcdf creators at this point as > I've tried everything I can to get it to work and I've built it > myself on my powerpc mac and had no trouble. I don't use fortran myself, so I'm not sure what the conventions might be for symbol mangling/decoration/lookup. -- Daniel J. Luke +========================================================+ | *---------------- dluke at geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 194 bytes Desc: This is a digitally signed message part URL: From michel.gagnon at polymtl.ca Wed Mar 18 06:52:31 2009 From: michel.gagnon at polymtl.ca (Michel Gagnon) Date: Wed, 18 Mar 2009 09:52:31 -0400 Subject: Unable to activate port expat Message-ID: <49C0FC9F.8080809@polymtl.ca> Hello everybody, Whenever I try to install something with Macports on my Leopard, I get the same error: Error: Target org.macports.activate returned: Image error: /opt/local/lib/libexpat.0.dylib already exists and does not belong to a registered port. Unable to activate port expat. Some idea of the problem? MG From macsforever2000 at macports.org Wed Mar 18 08:04:16 2009 From: macsforever2000 at macports.org (Frank Schima) Date: Wed, 18 Mar 2009 09:04:16 -0600 Subject: Unable to activate port expat In-Reply-To: <49C0FC9F.8080809@polymtl.ca> References: <49C0FC9F.8080809@polymtl.ca> Message-ID: <2A2A3761-2916-4828-8BB2-A62EA65B10B4@macports.org> On Mar 18, 2009, at 7:52 AM, Michel Gagnon wrote: > Whenever I try to install something with Macports on my Leopard, I > get the same error: > > > Error: Target org.macports.activate returned: Image error: /opt/ > local/lib/libexpat.0.dylib already exists and does not belong to a > registered port. Unable to activate port expat. > > > Some idea of the problem? Somehow your registry got confused about a previous attempt to install expat. That file is part of expat so I suggest the following: sudo port -f activate expat Cheers! Frank From brad at pixilla.com Wed Mar 18 08:05:44 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Wed, 18 Mar 2009 08:05:44 -0700 Subject: maintainer no longer at email address In-Reply-To: References: <08CAA406-B7B9-4667-BF85-F69F8672DD9E@atmo.arizona.edu> <20090317205324.GG1022@ninagal.withay.com> <5E84781F-F976-483B-9231-9211F1D15332@atmo.arizona.edu> <20090317234509.GK1022@ninagal.withay.com> Message-ID: <79BB6795-883E-4FCD-A520-3BD804A24128@pixilla.com> On Mar 17, 2009, at 8:52 PM, Yolande Serra wrote: > > On Mar 17, 2009, at 8:13 PM, Daniel J. Luke wrote: > >> On Mar 17, 2009, at 7:45 PM, Bryan Blackburn wrote: >>> On Tue, Mar 17, 2009 at 02:01:13PM -0700, Yolande Serra said: [...] >> Is the fortran code looking for some symbol that's not in the >> library? > yes, all of them. it cannot find any of the fortran routines like > nf_open, nf_get_vara_float, etc. All the netcdf nf_ routines are > listed that I call in my program when I try to compile. I think it > may be an underscore issue, at least it seems that way since it is > just not possible that the code does not know where libnetcdf.a is. > Perhaps I should be writing the netcdf creators at this point as > I've tried everything I can to get it to work and I've built it > myself on my powerpc mac and had no trouble. You might try compiling something else that's somewhat similar. If it compiles look at your code. If it doesn't look at your compiler env. //Brad From brad at pixilla.com Wed Mar 18 08:23:06 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Wed, 18 Mar 2009 08:23:06 -0700 Subject: man pages plus {with cached sample code} In-Reply-To: References: Message-ID: <4FE4F5DB-DB01-4A08-88F1-27D47CD3A8AD@pixilla.com> Bill, I'd like to see your script. Thank you, Brad On Mar 2, 2009, at 12:10 PM, Bill Hernandez wrote: > Over time I have written a bunch of shell scripts. Some I use > frequently, some I never use. > > One of the handy ones is called bh_man. It creates a small hierarchy > of directories if they don't exist, checks the $PATH in ./ > bash_profile, and sets it if necessary. > > The gist of it, is that it would be nice to be able to add > {comments, notes, sample code, urls, etc} to man pages, but I don't > know of an easy way to do that, so with that in mind I wrote "bh_man". > > When bh_man is called with an argument (unix_command_name) it first > determines if I already have that command in my personal cache, if > it exists then it pulls it up instead of the actual man page, if it > does not exist in the cache, it copies the man page, strips out all > the bizarre characters, and opens it in BBEdit. > > The huge advantage is that the cached document pulls up instantly, > is easily editable with BBEdit, or any other text editor, and the > best thing is that I can add/modify {comments, notes, sample code, > urls, etc} for each man page I choose to. Consequently most of the > commands I have already cached have a lot of example code included. > The example code is right at the top, so once I have added some > snippets, I don't even have to scroll through the document. The > examples are right there... > > The hierarchy below shows that a dir is created that provides a > starting place at "~/unix_scripts". > > The "bh_man" script does the following : > > ( 1 ) checks the "~/unix_scripts" hierarchy, and creates it, if it > does not exist. > ( 2 ) checks "~/.bash_profile", and creates it, if it does not exist. > ( 3 ) checks "~/.bash_profile" to make sure "~/unix_scripts/bin" > exists in the path, and adds it to the $PATH, if it does not exist. > ( 4 ) creates the "bh_open" shell script in "~/unix_scripts/bin" > ( 5 ) when finished with steps ( 1 ) thru ( 4 ) above, it moves > (itself) "bh_man" to "~/unix_scripts/bin" as shown below. > > Note : The hierarchy below shows, for example, when you do "bh_man > open" it creates "open.txt" as shown below. > > I put the hierarchy in my home directory instead of /usr/local or / > opt/local, because it gets backed up more often that way. > > > unix_scripts > > admin > > bbedit > > bin > bh_man > bh_open > > docs > > manual > open.txt > > help > > history > > logs > > macports > > misc > > modules > > src > > These are the commands I have already, many of them contain sample > usage code, which for me, is what the man pages have always lacked, > even some simple examples would be nice. > > Anyway I figured out a way around the problem for myself. > > If anyone is interested in trying the script please reply. If there > is enough interest, I'll put it on my server. > > > > docs > > manual > addgroup.txt > adduser.txt > alias.txt > ascii.txt > awk.txt > bash.txt > bz2.txt > bzip2.txt > case.txt > cat.txt > chmod.txt > colrm.txt > curl.txt > cut.txt > date.txt > defaults.txt > diff.txt > DirectoryService.txt > dscl.txt > dseditgroup.txt > dsexport.txt > dsmemberutil.txt > echo.txt > egrep.txt > export.txt > file.txt > for.txt > format.txt > FUNCNAME.txt > functions.txt > getcwd.txt > getopts.txt > grep.txt > group.txt > id.txt > jot.txt > kill.txt > launchd.txt > lookupd.txt > loop.txt > ls.txt > mkdir.txt > mysql.basic_info.txt > mysql.GRANT.txt > mysql.mysqladmin.txt > nicl.txt > nidump.txt > niload.txt > nireport.txt > niutil.txt > open.txt > operator.txt > parameters.txt > passwd.txt > pgsql.txt > pidof.txt > port.txt > printf.txt > PS1.txt > psql.txt > rand.txt > read.txt > reboot.txt > redirection.txt > repl.txt > rm.txt > rmdir.txt > rpl.txt > rs.txt > security.txt > sed.txt > seq.txt > sh.txt > sort.txt > ssh.txt > str_repeat.txt > stty.txt > su.txt > sudo.txt > tar.txt > tee.txt > termcap.txt > test.txt > touch.txt > tr.txt > uname.txt > wc.txt > wget.txt > xargs.txt > > Best Regards, > > Bill Hernandez > Plano, Texas > > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From serra at atmo.arizona.edu Wed Mar 18 10:33:04 2009 From: serra at atmo.arizona.edu (Yolande Serra) Date: Wed, 18 Mar 2009 10:33:04 -0700 Subject: netcdf 4.0 lib not linking In-Reply-To: References: Message-ID: I just wanted to let the list know I fixed the problem with linking my netcdf 4.0 library to a fortran program. Note, the macports netcdf install works fine with C code calling netcdf routines, only fortran code seemed to be an issue (even with the +g95 variant). The steps I took were the following: build szlib as standard installation from macports build openmpi with the +gcc43 variant so that fortran is enabled build hdf5-18 with the +gcc43 variant, again so that fortran is enabled build netcdf using gcc43 with fortran enabled - I wrote my own Portfile to do this as I wanted netcdf 4 capabilities. The macports netcdf installation does not activate netcdf-4 (in which case you might as well just install netcdf-3.x). Then, when compiling code that references libnetcdf.a use >> gfortran -fsecond-underscore -I/opt/local/include program.f -o program -L/opt/local/lib -lnetcdf The -fsecond-underscore is critical, at least for my setup. Otherwise the code will not link to the netcdf library, which has second underscores. I suppose you could also build the netcdf library with FFLAG -fno-second-underscore. I did not try this. I'm curious why the gcc43 compiler suite built the netcdf library with second underscores but does not build my .f code with them. my Portfile (used macports netcdf portfile as a template): PortSystem 1.0 name netcdf version 4.0 maintainers serra at atmo.arizona.edu platforms darwin categories science description NetCDF - Network Common Data Form long_description NetCDF is an interface \ for array-oriented data access and a library that \ provides an implementation of the interface. The \ netCDF library also defines a machine- independent \ format for representing scientific data. Together, \ the interface, library, and format support the \ creation, access, and sharing of scientific data. \ The netCDF software was developed at the Unidata \ Program Center in Boulder, Colorado. homepage http://unidata.ucar.edu/packages/netcdf/ master_sites ftp://ftp.unidata.ucar.edu/pub/netcdf/ \ http://www.gfd-dennou.org/arch/netcdf/unidata-mirror/ \ ftp://www.gfd-dennou.org/arch/netcdf/unidata-mirror/ checksums sha1 bea99846265e55e54be2c200ae004acc3a221c0a depends_lib port:hdf5 \ port:szip configure.cppflags "-DNDEBUG -Df2cFortran" configure.cxxflags "-O2 -fno-common" configure.cflags "-O2 -fno-common" configure.args --disable-f77 \ # --enable-shared \ --enable-netcdf-4 \ --with-zlib=${prefix}/lib \ --with-szlib=${prefix}/lib \ --with-hdf5=${prefix}/lib test.run yes test.target check destroot.destdir prefix=${destroot}${prefix} \ MANDIR=\\\${prefix}/share/man post-destroot { file delete -force ${destroot}${prefix}/share/man/whatis.db } variant g95 { depends_lib port:g95 configure.args-delete --disable-f77 configure.fc ${prefix}/bin/g95 configure.env-append FCFLAGS=-O2 } variant gfortran43 { depends_lib port:gcc43 configure.args-delete --disable-f77 configure.cc ${prefix}/bin/gcc-mp-4.3 configure.cxx ${prefix}/bin/g++-mp-4.3 configure.fc ${prefix}/bin/gfortran-mp-4.3 } On Mar 16, 2009, at 12:15 PM, Yolande Serra wrote: > I've written previously about this issue and got no reply. I'm > trying again after trying everything I could think of to get my > netcdf 4.0 library installed with macport to work with the gcc43 > also installed with macport. I made a local port for netcdf in > which I compiled it with gcc43 after having installed gcc43 from > macport. The build worked and I configured it with gfortran so that > the fortran libs were also installed with my netcdf libs. I > selected to not have separate fortran libraries and did not > configure with shared libraries so everything is in libnetcdf.a. I > checked using otool and all the right references are in libnetcdf.a, > at least if I compare it to a working version of netcdf 4.0 on my > old powerpc mac. No netcdf 4.0 options were turned on so I did not > have to install netcdf with hdf5, zlib or szlib (as this is what I > tried at first and did not get it to work). > > So, the question is why do I get linking errors when I try to > compile fortran code that calls the netcdf libs? I compile the code > with gfortran-mp-4.3 and use the same options as when I built netcdf > 4.0 (-fno-second-underscore -O2 -g). I also have provided the > location of the include file and library explicitly in the compile > command line (-I/opt/local/include and -L/opt/local/lib -lnetcdf). > I also call some udunits functions which do not give any errors and > udunits was also installed using macports and is in /opt/local. > > Do I need to recompile the gcc43 using the same options (-fno-second- > underscore)?? I tried compiling netcdf libs without this option, > but this also did not work. I tried compiling my code without that > option as well and it did not work. I also tried -fno-underscoring > - no luck. I have a netcdf 4.0 library installed on my powerpc mac > and can use gcc4.3 with that library with no problem but neither of > these packages were installed with macports. I'd like to use > macports for the new mac (intel), as it seems more convenient than > building source code myself all the time. However, I desperately > need a working netcdf library as all my data is stored this way. > > Thanks for any help, Yolande > > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From tjb at unh.edu Wed Mar 18 13:11:22 2009 From: tjb at unh.edu (Thomas Baker) Date: Wed, 18 Mar 2009 16:11:22 -0400 Subject: Symbol not found: _gll_noop In-Reply-To: <49A9346D.2060705@lobraun.de> References: <49A79CE5.5090905@lobraun.de> <49A84BBB.9020709@macports.org> <1d6843d80902271454g59f6a53chb351991557bb83a5@mail.gmail.com> <49A9346D.2060705@lobraun.de> Message-ID: <3960155C-55AE-4576-9524-59A9420A9173@unh.edu> On Feb 28, 2009, at 7:56 AM, Lothar Braun wrote: > Hi, > > same thing for me: If I deactivate mesa, gnucash will start again. > Here > is my output for otool -L /opt/local/bin/gnucash-bin if mesa is > activated: > > /opt/local/bin/gnucash-bin: > /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio > (compatibility version 1.0.0, current version 1.0.0) > /opt/local/lib/libgnc-qof.1.dylib (compatibility version 2.0.0, > current > version 2.4.0) > /opt/local/lib/gnucash/libgncmod-engine.dylib (compatibility version > 0.0.0, current version 0.0.0) > /opt/local/lib/libgnc-gnome.0.dylib (compatibility version 1.0.0, > current version 1.0.0) > /opt/local/lib/gnucash/libgncmod-ledger-core.dylib (compatibility > version 0.0.0, current version 0.0.0) > /opt/local/lib/gnucash/libgncmod-register-gnome.dylib (compatibility > version 0.0.0, current version 0.0.0) > /opt/local/lib/gnucash/libgncmod-register-core.dylib (compatibility > version 0.0.0, current version 0.0.0) > /opt/local/lib/gnucash/libgncmod-report-gnome.dylib (compatibility > version 0.0.0, current version 0.0.0) > /opt/local/lib/gnucash/libgncmod-report-system.dylib (compatibility > version 0.0.0, current version 0.0.0) > /opt/local/lib/gnucash/libgncmod-gnome-search.dylib (compatibility > version 0.0.0, current version 0.0.0) > /opt/local/lib/gnucash/libgncmod-gnome-utils.dylib (compatibility > version 0.0.0, current version 0.0.0) > /opt/local/lib/libgnc-backend-file-utils.0.dylib (compatibility > version > 1.0.0, current version 1.0.0) > /opt/local/lib/gnucash/libgncmod-app-utils.dylib (compatibility > version > 0.0.0, current version 0.0.0) > /opt/local/lib/libgtkhtml-3.14.19.dylib (compatibility version > 21.0.0, > current version 21.0.0) > /usr/X11/lib/libSM.6.dylib (compatibility version 7.0.0, current > version 7.0.0) > /usr/X11/lib/libICE.6.dylib (compatibility version 10.0.0, current > version 10.0.0) > /usr/X11/lib/libXinerama.1.dylib (compatibility version 2.0.0, > current > version 2.0.0) > /usr/X11/lib/libXi.6.dylib (compatibility version 7.0.0, current > version 7.0.0) > /usr/X11/lib/libXrandr.2.dylib (compatibility version 4.0.0, current > version 4.0.0) > /usr/X11/lib/libXcursor.1.dylib (compatibility version 2.0.0, current > version 2.2.0) > /usr/X11/lib/libXcomposite.1.dylib (compatibility version 2.0.0, > current version 2.0.0) > /usr/X11/lib/libXext.6.dylib (compatibility version 11.0.0, current > version 11.0.0) > /usr/X11/lib/libXdamage.1.dylib (compatibility version 2.0.0, current > version 2.0.0) > /usr/X11/lib/libXfixes.3.dylib (compatibility version 5.0.0, current > version 5.0.0) > /opt/local/lib/libgnomeui-2.0.dylib (compatibility version 2401.0.0, > current version 2401.0.0) > /opt/local/lib/libenchant.1.dylib (compatibility version 6.0.0, > current > version 6.2.0) > /opt/local/lib/libgnome-keyring.0.dylib (compatibility version 2.0.0, > current version 2.1.0) > /opt/local/lib/libbonoboui-2.0.dylib (compatibility version 1.0.0, > current version 1.0.0) > /opt/local/lib/libSM.6.dylib (compatibility version 7.0.0, current > version 7.0.0) > /opt/local/lib/libICE.6.dylib (compatibility version 10.0.0, current > version 10.0.0) > /opt/local/lib/libgnomecanvas-2.0.dylib (compatibility version > 2002.0.0, current version 2002.0.0) > /opt/local/lib/libgnome-2.0.dylib (compatibility version 2401.0.0, > current version 2401.1.0) > /opt/local/lib/libgnomevfs-2.0.dylib (compatibility version 2401.0.0, > current version 2401.0.0) > /opt/local/lib/libssl.0.9.8.dylib (compatibility version 0.9.8, > current > version 0.9.8) > /opt/local/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, > current version 0.9.8) > /opt/local/lib/libesd.0.dylib (compatibility version 3.0.0, current > version 3.39.0) > /opt/local/lib/libbonobo-2.0.dylib (compatibility version 1.0.0, > current version 1.0.0) > /opt/local/lib/libaudiofile.0.dylib (compatibility version 1.0.0, > current version 1.2.0) > /opt/local/lib/libbonobo-activation.4.dylib (compatibility version > 5.0.0, current version 5.0.0) > /opt/local/lib/libORBitCosNaming-2.0.dylib (compatibility version > 2.0.0, current version 2.0.0) > /opt/local/lib/libgailutil.18.dylib (compatibility version 19.0.0, > current version 19.1.0) > /opt/local/lib/libXinerama.1.dylib (compatibility version 2.0.0, > current version 2.0.0) > /opt/local/lib/libXi.6.dylib (compatibility version 7.0.0, current > version 7.0.0) > /opt/local/lib/libXrandr.2.dylib (compatibility version 4.0.0, > current > version 4.0.0) > /opt/local/lib/libXcursor.1.dylib (compatibility version 2.0.0, > current > version 2.2.0) > /opt/local/lib/libXcomposite.1.dylib (compatibility version 2.0.0, > current version 2.0.0) > /opt/local/lib/libXext.6.dylib (compatibility version 11.0.0, current > version 11.0.0) > /opt/local/lib/libXdamage.1.dylib (compatibility version 3.0.0, > current > version 3.0.0) > /opt/local/lib/libXfixes.3.dylib (compatibility version 5.0.0, > current > version 5.0.0) > /opt/local/lib/libgoffice-0.6.6.dylib (compatibility version 7.0.0, > current version 7.5.0) > /usr/X11/lib/libXrender.1.dylib (compatibility version 5.0.0, current > version 5.0.0) > /usr/X11/lib/libX11.6.dylib (compatibility version 9.0.0, current > version 9.0.0) > /usr/X11/lib/libXau.6.dylib (compatibility version 7.0.0, current > version 7.0.0) > /usr/X11/lib/libXdmcp.6.dylib (compatibility version 7.0.0, current > version 7.0.0) > /opt/local/lib/libgsf-1.114.dylib (compatibility version 115.0.0, > current version 115.11.0) > /opt/local/lib/libbz2.1.0.dylib (compatibility version 1.0.0, current > version 1.0.5) > /opt/local/lib/libglade-2.0.0.dylib (compatibility version 1.0.0, > current version 1.7.0) > /opt/local/lib/libart_lgpl_2.2.dylib (compatibility version 6.0.0, > current version 6.20.0) > /opt/local/lib/libxml2.2.dylib (compatibility version 10.0.0, current > version 10.3.0) > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current > version 111.1.3) > /opt/local/lib/libgnc-module.0.dylib (compatibility version 1.0.0, > current version 1.0.0) > /opt/local/lib/gnucash/libgncmod-calculation.dylib (compatibility > version 0.0.0, current version 0.0.0) > /opt/local/lib/libgnc-core-utils.0.dylib (compatibility version > 1.0.0, > current version 1.0.0) > /opt/local/lib/libgconf-2.4.dylib (compatibility version 6.0.0, > current > version 6.5.0) > /opt/local/lib/libdbus-glib-1.2.dylib (compatibility version 4.0.0, > current version 4.0.0) > /opt/local/lib/libORBit-2.0.dylib (compatibility version 2.0.0, > current > version 2.0.0) > /usr/lib/libresolv.9.dylib (compatibility version 1.0.0, current > version 25.0.2) > /opt/local/lib/libdbus-1.3.dylib (compatibility version 8.0.0, > current > version 8.0.0) > /opt/local/lib/libgtk-x11-2.0.0.dylib (compatibility version > 1401.0.0, > current version 1401.7.0) > /opt/local/lib/libgdk-x11-2.0.0.dylib (compatibility version > 1401.0.0, > current version 1401.7.0) > /opt/local/lib/libatk-1.0.0.dylib (compatibility version 2410.0.0, > current version 2410.1.0) > /opt/local/lib/libgdk_pixbuf-2.0.0.dylib (compatibility version > 1401.0.0, current version 1401.7.0) > /opt/local/lib/libgio-2.0.0.dylib (compatibility version 1801.0.0, > current version 1801.3.0) > /opt/local/lib/libtiff.3.dylib (compatibility version 12.0.0, current > version 12.2.0) > /opt/local/lib/libjasper.1.dylib (compatibility version 2.0.0, > current > version 2.0.0) > /opt/local/lib/libjpeg.62.dylib (compatibility version 63.0.0, > current > version 63.0.0) > /opt/local/lib/libpangocairo-1.0.0.dylib (compatibility version > 2204.0.0, current version 2204.1.0) > /opt/local/lib/libcairo.2.dylib (compatibility version 10803.0.0, > current version 10803.6.0) > /opt/local/lib/libpangoft2-1.0.0.dylib (compatibility version > 2204.0.0, > current version 2204.1.0) > /opt/local/lib/libpixman-1.0.dylib (compatibility version 15.0.0, > current version 15.0.0) > /opt/local/lib/libpng12.0.dylib (compatibility version 36.0.0, > current > version 36.0.0) > /opt/local/lib/libXrender.1.dylib (compatibility version 5.0.0, > current > version 5.0.0) > /opt/local/lib/libX11.6.dylib (compatibility version 9.0.0, current > version 9.0.0) > /opt/local/lib/libXau.6.dylib (compatibility version 7.0.0, current > version 7.0.0) > /opt/local/lib/libXdmcp.6.dylib (compatibility version 7.0.0, current > version 7.0.0) > /opt/local/lib/libpango-1.0.0.dylib (compatibility version 2204.0.0, > current version 2204.1.0) > /opt/local/lib/libfontconfig.1.dylib (compatibility version 5.0.0, > current version 5.0.0) > /opt/local/lib/libexpat.1.dylib (compatibility version 7.0.0, current > version 7.2.0) > /opt/local/lib/libfreetype.6.dylib (compatibility version 10.0.0, > current version 10.19.0) > /opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current > version 1.2.3) > /opt/local/lib/libguile.12.dylib (compatibility version 16.0.0, > current > version 16.1.0) > /opt/local/lib/libguile-ltdl.1.dylib (compatibility version 2.0.0, > current version 2.1.0) > /opt/local/lib/libgthread-2.0.0.dylib (compatibility version > 1801.0.0, > current version 1801.3.0) > /opt/local/lib/libgobject-2.0.0.dylib (compatibility version > 1801.0.0, > current version 1801.3.0) > /opt/local/lib/libgmodule-2.0.0.dylib (compatibility version > 1801.0.0, > current version 1801.3.0) > /opt/local/lib/libglib-2.0.0.dylib (compatibility version 1801.0.0, > current version 1801.3.0) > /opt/local/lib/libpopt.0.dylib (compatibility version 1.0.0, current > version 1.0.0) > /opt/local/lib/libintl.8.dylib (compatibility version 9.0.0, current > version 9.2.0) > /opt/local/lib/libiconv.2.dylib (compatibility version 7.0.0, current > version 7.0.0) > /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current > version > 1.0.0) > > Best regards, > Lothar > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users So any continued thoughts on this? It hasn't gotten any better with subsequent releases of mesa. I still need to keep it deactivated for gnucash to run. Thanks, tjb -- ======================================================================= | Thomas Baker email: tjb at unh.edu | | Systems Programmer | | Research Computing Center voice: (603) 862-4490 | | University of New Hampshire fax: (603) 862-1761 | | 332 Morse Hall | | Durham, NH 03824 USA http://wintermute.sr.unh.edu/~tjb | ======================================================================= From davel at davel.org Wed Mar 18 13:47:02 2009 From: davel at davel.org (Dave Llopis) Date: Wed, 18 Mar 2009 13:47:02 -0700 Subject: Pidgin Menu weirdness with dual monitors Message-ID: My menus in Pidgin are doing various weird things when its windows are in the "secondary" monitor on my dual-monitor setup. The menus show up in the "primary" monitor, or they show up in the wrong place (and often mangled) in the "secondary" monitor. I'm not sure if this is a Pidgin issue or a GTK+ issue or a Quartz issue or what. I built Pidgin with +no_x11 and +quartz . Are there some GTK+ config parameters I need to fiddle with or something? -------------- next part -------------- An HTML attachment was scrubbed... URL: From raimue at macports.org Wed Mar 18 14:09:03 2009 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Wed, 18 Mar 2009 22:09:03 +0100 Subject: Re-do MacPorts after upgrading from Tiger to Leopard on PPC? In-Reply-To: <80D53A20-2D9E-4147-A154-9A4EE24850EC@qwest.net> References: <95D3529F-FC9B-42F2-BDDD-70D90CE40692@qwest.net> <20090313054340.GN836@ninagal.withay.com> <3C38030F-4812-4129-818A-FC2BD6CA31B8@pixilla.com> <49BA7F67.9030904@macports.org> <538D04B3-AF0B-49D1-A90F-4E15862EACBE@macports.org> <49BF5DE4.3040703@macports.org> <80D53A20-2D9E-4147-A154-9A4EE24850EC@qwest.net> Message-ID: <49C162EF.5080200@macports.org> Jerry wrote: > Thanks for all the answers. Even before I saw them today, I solved all > my MacPorts problems by uninstall everything. I'm not being ungrateful > because believe me, I'm just the opposite. However, I would like to > offer a bit of feedback. My experience with MacPorts has been pretty > bad. If I had really _needed_ any of the software that I tried to > install, as opposed to just evaluating it, I would have been pretty > hosed, I'm afraid. I mostly appreciate the ambitious goal of MacPorts > and I might try again later, but not soon. To interrupt here, for what would you _need_ it? You have to admit that MacPorts is an open source project limited to the resources the community offers. All developers and maintainers offer there free time. If you really _need_ something as in for work, you either have to invest time to resolve problems yourself or pay someone offering support for that. That might sound harsh now, but you should not base your business on something you got for free as a gift without support contract :-) Sorry that it turned out like this for you. There are people constantly trying to improve the experience using MacPorts. But as this is an open source you as users are our main QA department. Rainer From wa0tjt at gmail.com Wed Mar 18 14:30:02 2009 From: wa0tjt at gmail.com (Keith Kaiser) Date: Wed, 18 Mar 2009 16:30:02 -0500 Subject: How to run Message-ID: OK, I've installed an application using MacPorts. How do I run it? 73's Keith Kaiser wa0tjt at gmail.com From devans at macports.org Wed Mar 18 14:32:35 2009 From: devans at macports.org (David Evans) Date: Wed, 18 Mar 2009 14:32:35 -0700 Subject: How to run In-Reply-To: References: Message-ID: <49C16873.9010601@macports.org> Keith Kaiser wrote: > OK, I've installed an application using MacPorts. How do I run it? > Which one? From devans at macports.org Wed Mar 18 14:37:08 2009 From: devans at macports.org (David Evans) Date: Wed, 18 Mar 2009 14:37:08 -0700 Subject: How to run In-Reply-To: References: Message-ID: <49C16984.4030305@macports.org> Keith Kaiser wrote: > OK, I've installed an application using MacPorts. How do I run it? Actually, you can port info and go look at the homepage there for information about the software. Another possibility is to port contents to see what was installed (maybe documentation, binaries, etc) Dave From raimue at macports.org Wed Mar 18 14:41:19 2009 From: raimue at macports.org (=?UTF-8?B?UmFpbmVyIE3DvGxsZXI=?=) Date: Wed, 18 Mar 2009 22:41:19 +0100 Subject: Searching for tickets against a specific port Message-ID: <49C16A7F.5030507@macports.org> Hello, we had requests for searching for tickets against specific ports before. Now I created a report in Trac which allows you to do that. It searches the "Port" field which can be set when creating tickets. This being said, please always fill the field with the appropriate value! Example: http://trac.macports.org/report/16?PORT=python25 Please note that the PORT parameter name in the URL has to be upper-case. If someone cares it could be added as a link to the ports listed in the Available Ports section on . Some volunteer for a patch? :-) Rainer From t_condonia at comcast.net Thu Mar 19 00:55:21 2009 From: t_condonia at comcast.net (Tom Condon) Date: Thu, 19 Mar 2009 00:55:21 -0700 Subject: LibGnomeCanvas Dependency Problem Message-ID: <49C1FA69.5000108@comcast.net> Folks, I have run into a problem with the libgnomecanvas port dependencies. When I try to build it it says that libgnomecanvas is dependent on "gail" (error message below). =================== Package requirements ( gtk+-2.0 >= 2.0.3 gail >= 1.9.0 libart-2.0 >= 2.3.8 pango >= 1.0.1 pangoft2 >= 1.0.1) were not met: No package 'gail' found =================== However, when I try: port info libgnomecanvas it says: =================== Mac-The-Knife:~ Captain$ port info libgnomecanvas libgnomecanvas @2.20.1.1, Revision 2 (gnome) Variants: universal The GNOMECanvas library provides a number of features: Image loading facilities. Rendering of a GdkPixBuf into various formats: drawables (windows, pixmaps), GdkRGB buffers. A cache interface. Homepage: http://www.gnome.org/ Build Dependencies: pkgconfig, perl5, p5-xml-parser, intltool Library Dependencies: glib2, gtk2, pango, gettext, libiconv, libart_lgpl, libglade2 Platforms: darwin Maintainers: nomaintainer at macports.org =================== With, as you see, no mention of "gail". When I try: port search gail I get: =================== libgail-gnome @1.20.1 (gnome) An implementation of the ATK interfaces for GNOME widgets. =================== But an attempt to build libgail-gnome also finds a dependency on package "gail". It also returns the following error, which makes no sense to me due to a mismatch of quotes in the shell command: =================== ---> Configuring at-spi Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_at-spi/work/at-spi-1.24.1" && ./configure --prefix=/opt/local --enable-static --enable-platform-gnome-2 --disable-xevie --with-x " returned error 1 =================== Can someone please explain to me why some ports, including the only port that matches a search for "gail", are dependent on gail, and no gail exists? Is this a gnome "thing" that there is a clever way around? In A Chord, Tom Condon Bass, Agate Passage Quartet Treasurer, Bass & Proud Member, Kitsap Chordsmen It's so hard when I have to, And so easy when I want to. - Sondra Anice Barnes From blb at macports.org Thu Mar 19 01:17:34 2009 From: blb at macports.org (Bryan Blackburn) Date: Thu, 19 Mar 2009 02:17:34 -0600 Subject: LibGnomeCanvas Dependency Problem In-Reply-To: <49C1FA69.5000108@comcast.net> References: <49C1FA69.5000108@comcast.net> Message-ID: <20090319081733.GI568@ninagal.withay.com> On Thu, Mar 19, 2009 at 12:55:21AM -0700, Tom Condon said: > > Folks, > > I have run into a problem with the libgnomecanvas port dependencies. When > I try to build it it says that libgnomecanvas is dependent on "gail" > (error message below). gail was integrated into gtk2, so make sure your gtk2 install is current first; see, eg, Bryan [...] > > > In A Chord, > > Tom Condon > Bass, Agate Passage Quartet > Treasurer, Bass & Proud Member, Kitsap Chordsmen > > It's so hard when I have to, And so easy when I want to. > - Sondra Anice Barnes From kellert at ohsu.edu Thu Mar 19 09:52:44 2009 From: kellert at ohsu.edu (Thomas Keller) Date: Thu, 19 Mar 2009 09:52:44 -0700 Subject: selfupdate error Message-ID: <30181350-E653-4C26-A2BE-A78FE822DA70@ohsu.edu> Greetings, Could someone give me advice on what to do when selfupdate fails? Error: /opt/local/bin/port: port selfupdate failed: Couldn't sync the ports tree: Synchronization of 1 source(s) failed thanks, Tom K From jmr at macports.org Thu Mar 19 10:26:30 2009 From: jmr at macports.org (Joshua Root) Date: Fri, 20 Mar 2009 04:26:30 +1100 Subject: selfupdate error In-Reply-To: <30181350-E653-4C26-A2BE-A78FE822DA70@ohsu.edu> References: <30181350-E653-4C26-A2BE-A78FE822DA70@ohsu.edu> Message-ID: <49C28046.6070000@macports.org> Thomas Keller wrote: > Greetings, > Could someone give me advice on what to do when selfupdate fails? > Error: /opt/local/bin/port: port selfupdate failed: Couldn't sync the > ports tree: Synchronization of 1 source(s) failed Check that your network is working and not blocking traffic to either the rsync port (TCP/873) or Apple's network. PeerGuardian is notorious for doing the latter. - Josh From artie.ziff at gmail.com Thu Mar 19 13:03:09 2009 From: artie.ziff at gmail.com (Artie Ziff) Date: Thu, 19 Mar 2009 13:03:09 -0700 Subject: using dependency criteria before package removal Message-ID: <49C2A4FD.5050605@gmail.com> Hello, I noticed that my MacPort builds python 2.4. I probably do not need it. In an effort to learn how to better manage the MacPort tree (which must be huge by now), can I remove python 2.4? Here's some info: $ port -v deps python24 python24 has library dependencies on: port:gettext thank you! Art From jmr at macports.org Thu Mar 19 13:11:00 2009 From: jmr at macports.org (Joshua Root) Date: Fri, 20 Mar 2009 07:11:00 +1100 Subject: using dependency criteria before package removal In-Reply-To: <49C2A4FD.5050605@gmail.com> References: <49C2A4FD.5050605@gmail.com> Message-ID: <49C2A6D4.7000709@macports.org> Artie Ziff wrote: > Hello, > > I noticed that my MacPort builds python 2.4. I probably do not need it. > > In an effort to learn how to better manage the MacPort tree (which must > be huge by now), can I remove python 2.4? Here's some info: > > $ port -v deps python24 > python24 has library dependencies on: > port:gettext You will get an error message if you try to uninstall a port that has dependents. Or you can find out beforehand like this: port dependents python24 - Josh From kuepper.jochen at googlemail.com Thu Mar 19 15:53:44 2009 From: kuepper.jochen at googlemail.com (=?ISO-8859-1?Q?Jochen_K=FCpper?=) Date: Thu, 19 Mar 2009 23:53:44 +0100 Subject: netcdf 4.0 lib not linking In-Reply-To: References: Message-ID: On 18.03.2009, at 18:33, Yolande Serra wrote: > I just wanted to let the list know I fixed the problem with linking > my netcdf 4.0 library to a fortran program. Note, the macports > netcdf install works fine with C code calling netcdf routines, only > fortran code seemed to be an issue (even with the +g95 variant). > The steps I took were the following: > > build szlib as standard installation from macports > build openmpi with the +gcc43 variant so that fortran is enabled > build hdf5-18 with the +gcc43 variant, again so that fortran is > enabled > build netcdf using gcc43 with fortran enabled - I wrote my own > Portfile to do this as I wanted netcdf 4 capabilities. The macports > netcdf installation does not activate netcdf-4 (in which case you > might as well just install netcdf-3.x). > > Then, when compiling code that references libnetcdf.a use > > >> gfortran -fsecond-underscore -I/opt/local/include program.f -o > program -L/opt/local/lib -lnetcdf > > The -fsecond-underscore is critical, at least for my setup. > Otherwise the code will not link to the netcdf library, which has > second underscores. I suppose you could also build the netcdf > library with FFLAG -fno-second-underscore. I did not try this. I'm > curious why the gcc43 compiler suite built the netcdf library with > second underscores but does not build my .f code with them. Is gfortran actually gfortran-mp-4.3? > my Portfile (used macports netcdf portfile as a template): > > PortSystem 1.0 > name netcdf > version 4.0 > maintainers serra at atmo.arizona.edu > platforms darwin > categories science > > description NetCDF - Network Common Data Form > long_description NetCDF is an interface \ > for array-oriented data access and a library > that \ > provides an implementation of the interface. > The \ > netCDF library also defines a machine- > independent \ > format for representing scientific data. > Together, \ > the interface, library, and format support > the \ > creation, access, and sharing of scientific > data. \ > The netCDF software was developed at the > Unidata \ > Program Center in Boulder, Colorado. > > homepage http://unidata.ucar.edu/packages/netcdf/ > > master_sites ftp://ftp.unidata.ucar.edu/pub/netcdf/ \ > http://www.gfd-dennou.org/arch/netcdf/unidata-mirror/ \ > ftp://www.gfd-dennou.org/arch/netcdf/unidata-mirror/ > checksums sha1 bea99846265e55e54be2c200ae004acc3a221c0a > > depends_lib port:hdf5 \ > port:szip > > configure.cppflags "-DNDEBUG -Df2cFortran" > configure.cxxflags "-O2 -fno-common" > configure.cflags "-O2 -fno-common" > configure.args --disable-f77 \ > # --enable-shared \ > --enable-netcdf-4 \ > --with-zlib=${prefix}/lib \ > --with-szlib=${prefix}/lib \ > --with-hdf5=${prefix}/lib > > test.run yes > test.target check > > destroot.destdir prefix=${destroot}${prefix} \ > MANDIR=\\\${prefix}/share/man > > post-destroot { > file delete -force ${destroot}${prefix}/share/man/whatis.db > } > > variant g95 { > depends_lib port:g95 > configure.args-delete --disable-f77 > configure.fc ${prefix}/bin/g95 > configure.env-append FCFLAGS=-O2 > } > > variant gfortran43 { > depends_lib port:gcc43 > configure.args-delete --disable-f77 > configure.cc ${prefix}/bin/gcc-mp-4.3 > configure.cxx ${prefix}/bin/g++-mp-4.3 > configure.fc ${prefix}/bin/gfortran-mp-4.3 > } > > > > > On Mar 16, 2009, at 12:15 PM, Yolande Serra wrote: > >> I've written previously about this issue and got no reply. I'm >> trying again after trying everything I could think of to get my >> netcdf 4.0 library installed with macport to work with the gcc43 >> also installed with macport. I made a local port for netcdf in >> which I compiled it with gcc43 after having installed gcc43 from >> macport. The build worked and I configured it with gfortran so >> that the fortran libs were also installed with my netcdf libs. I >> selected to not have separate fortran libraries and did not >> configure with shared libraries so everything is in libnetcdf.a. I >> checked using otool and all the right references are in >> libnetcdf.a, at least if I compare it to a working version of >> netcdf 4.0 on my old powerpc mac. No netcdf 4.0 options were >> turned on so I did not have to install netcdf with hdf5, zlib or >> szlib (as this is what I tried at first and did not get it to work). >> >> So, the question is why do I get linking errors when I try to >> compile fortran code that calls the netcdf libs? I compile the >> code with gfortran-mp-4.3 and use the same options as when I built >> netcdf 4.0 (-fno-second-underscore -O2 -g). I also have provided >> the location of the include file and library explicitly in the >> compile command line (-I/opt/local/include and -L/opt/local/lib - >> lnetcdf). I also call some udunits functions which do not give any >> errors and udunits was also installed using macports and is in /opt/ >> local. >> >> Do I need to recompile the gcc43 using the same options (-fno- >> second-underscore)?? I tried compiling netcdf libs without this >> option, but this also did not work. I tried compiling my code >> without that option as well and it did not work. I also tried -fno- >> underscoring - no luck. I have a netcdf 4.0 library installed on my >> powerpc mac and can use gcc4.3 with that library with no problem >> but neither of these packages were installed with macports. I'd >> like to use macports for the new mac (intel), as it seems more >> convenient than building source code myself all the time. However, >> I desperately need a working netcdf library as all my data is >> stored this way. >> >> Thanks for any help, Yolande >> >> >> _______________________________________________ >> macports-users mailing list >> macports-users at lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users Sch?ne Gr??e, Jochen -- Einigkeit und Recht und Freiheit http://www.Jochen-Kuepper.de Libert?, ?galit?, Fraternit? GnuPG key: CC1B0B4D Sex, drugs and rock-n-roll -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 194 bytes Desc: This is a digitally signed message part URL: From mdwhite15 at woh.rr.com Thu Mar 19 17:26:13 2009 From: mdwhite15 at woh.rr.com (MD White) Date: Thu, 19 Mar 2009 20:26:13 -0400 Subject: Any ideas on getting gfortran? Message-ID: <4F03A8A5-34EB-4ED7-962E-6402490E6E53@woh.rr.com> Hi, I tried to get gfortran by grabbing the gcc44 (beta) port. It downloaded gcc-core-4.4.20090313.tar.bz2, gcc- fortran-4.4.20090313.tar.bz2, gcc-g++-4.4.20090313.tar.bz2, gcc- java-4.4.20090313.tar.bz2 and gcc-objc-4.4.20090313.tar.bz2 but then proceeded to just build gcc. There were no error messages, just that it installed gcc 4.4 and then cleaned up. It installed: cpp-mp-4.4 gcc-mp-4.4 gccbug-mp-4.4 gcov-mp-4.4 i386-apple-darwin9.6.0-gcc-4.4.0 i386-apple-darwin9.6.0-gcc-mp-4.4 c++-mp-4.4 g++-mp-4.4 i386-apple-darwin9.6.0-g++-4.4.0 i386-apple-darwin9.6.0-g++-mp-4.4 but, no gfortran (and no java for that matter). So does anyone have ideas on how to get gfortran 4.4 from macports? Is there a problem with the port? (I am running OS X 10.5.6 on an intel machine). Thanks, - M From blb at macports.org Thu Mar 19 17:34:09 2009 From: blb at macports.org (Bryan Blackburn) Date: Thu, 19 Mar 2009 18:34:09 -0600 Subject: Any ideas on getting gfortran? In-Reply-To: <4F03A8A5-34EB-4ED7-962E-6402490E6E53@woh.rr.com> References: <4F03A8A5-34EB-4ED7-962E-6402490E6E53@woh.rr.com> Message-ID: <20090320003409.GE1014@ninagal.withay.com> On Thu, Mar 19, 2009 at 08:26:13PM -0400, MD White said: > Hi, > > I tried to get gfortran by grabbing the gcc44 (beta) port. It downloaded > gcc-core-4.4.20090313.tar.bz2, gcc-fortran-4.4.20090313.tar.bz2, > gcc-g++-4.4.20090313.tar.bz2, gcc-java-4.4.20090313.tar.bz2 and > gcc-objc-4.4.20090313.tar.bz2 but then proceeded to just build gcc. There > were no error messages, just that it installed gcc 4.4 and then cleaned > up. It installed: > > cpp-mp-4.4 > gcc-mp-4.4 > gccbug-mp-4.4 > gcov-mp-4.4 > i386-apple-darwin9.6.0-gcc-4.4.0 > i386-apple-darwin9.6.0-gcc-mp-4.4 > c++-mp-4.4 > g++-mp-4.4 > i386-apple-darwin9.6.0-g++-4.4.0 > i386-apple-darwin9.6.0-g++-mp-4.4 > > but, no gfortran (and no java for that matter). So does anyone have > ideas on how to get gfortran 4.4 from macports? Is there a problem with > the port? (I am running OS X 10.5.6 on an intel machine). gcc44 has a variant for it (and for java), which states "this language will be enabled in the final version - this variant is completely untested!" so you may be successful or have issues. gcc43 builds it fine though, without variants. Bryan > > Thanks, > > - M From serra at atmo.arizona.edu Thu Mar 19 20:32:41 2009 From: serra at atmo.arizona.edu (Yolande Serra) Date: Thu, 19 Mar 2009 20:32:41 -0700 Subject: netcdf 4.0 lib not linking In-Reply-To: References: Message-ID: <3041668D-B2D3-498A-B3DE-C38CA7BCE47C@atmo.arizona.edu> On Mar 19, 2009, at 3:53 PM, Jochen K?pper wrote: > On 18.03.2009, at 18:33, Yolande Serra wrote: > >> I just wanted to let the list know I fixed the problem with linking >> my netcdf 4.0 library to a fortran program. Note, the macports >> netcdf install works fine with C code calling netcdf routines, only >> fortran code seemed to be an issue (even with the +g95 variant). >> The steps I took were the following: >> >> build szlib as standard installation from macports >> build openmpi with the +gcc43 variant so that fortran is enabled >> build hdf5-18 with the +gcc43 variant, again so that fortran is >> enabled >> build netcdf using gcc43 with fortran enabled - I wrote my own >> Portfile to do this as I wanted netcdf 4 capabilities. The >> macports netcdf installation does not activate netcdf-4 (in which >> case you might as well just install netcdf-3.x). >> >> Then, when compiling code that references libnetcdf.a use >> >> >> gfortran -fsecond-underscore -I/opt/local/include program.f -o >> program -L/opt/local/lib -lnetcdf >> >> The -fsecond-underscore is critical, at least for my setup. >> Otherwise the code will not link to the netcdf library, which has >> second underscores. I suppose you could also build the netcdf >> library with FFLAG -fno-second-underscore. I did not try this. >> I'm curious why the gcc43 compiler suite built the netcdf library >> with second underscores but does not build my .f code with them. > > Is gfortran actually gfortran-mp-4.3? Yes, that is how macports installs it. Probably so it won't override the default installation of gcc 4.0 on Macs that ships with Xcode. That installation has gcc but not gfortran. After you install gcc43 with macports check /opt/local/bin/ and you will see the compiler collection. > > >> my Portfile (used macports netcdf portfile as a template): >> >> PortSystem 1.0 >> name netcdf >> version 4.0 >> maintainers serra at atmo.arizona.edu >> platforms darwin >> categories science >> >> description NetCDF - Network Common Data Form >> long_description NetCDF is an interface \ >> for array-oriented data access and a library >> that \ >> provides an implementation of the interface. >> The \ >> netCDF library also defines a machine- >> independent \ >> format for representing scientific data. >> Together, \ >> the interface, library, and format support >> the \ >> creation, access, and sharing of scientific >> data. \ >> The netCDF software was developed at the >> Unidata \ >> Program Center in Boulder, Colorado. >> >> homepage http://unidata.ucar.edu/packages/netcdf/ >> >> master_sites ftp://ftp.unidata.ucar.edu/pub/netcdf/ \ >> http://www.gfd-dennou.org/arch/netcdf/unidata-mirror/ \ >> ftp://www.gfd-dennou.org/arch/netcdf/unidata-mirror/ >> checksums sha1 bea99846265e55e54be2c200ae004acc3a221c0a >> >> depends_lib port:hdf5 \ >> port:szip >> >> configure.cppflags "-DNDEBUG -Df2cFortran" >> configure.cxxflags "-O2 -fno-common" >> configure.cflags "-O2 -fno-common" >> configure.args --disable-f77 \ >> # --enable-shared \ >> --enable-netcdf-4 \ >> --with-zlib=${prefix}/lib \ >> --with-szlib=${prefix}/lib \ >> --with-hdf5=${prefix}/lib >> >> test.run yes >> test.target check >> >> destroot.destdir prefix=${destroot}${prefix} \ >> MANDIR=\\\${prefix}/share/man >> >> post-destroot { >> file delete -force ${destroot}${prefix}/share/man/whatis.db >> } >> >> variant g95 { >> depends_lib port:g95 >> configure.args-delete --disable-f77 >> configure.fc ${prefix}/bin/g95 >> configure.env-append FCFLAGS=-O2 >> } >> >> variant gfortran43 { >> depends_lib port:gcc43 >> configure.args-delete --disable-f77 >> configure.cc ${prefix}/bin/gcc-mp-4.3 >> configure.cxx ${prefix}/bin/g++-mp-4.3 >> configure.fc ${prefix}/bin/gfortran-mp-4.3 >> } >> >> >> >> >> On Mar 16, 2009, at 12:15 PM, Yolande Serra wrote: >> >>> I've written previously about this issue and got no reply. I'm >>> trying again after trying everything I could think of to get my >>> netcdf 4.0 library installed with macport to work with the gcc43 >>> also installed with macport. I made a local port for netcdf in >>> which I compiled it with gcc43 after having installed gcc43 from >>> macport. The build worked and I configured it with gfortran so >>> that the fortran libs were also installed with my netcdf libs. I >>> selected to not have separate fortran libraries and did not >>> configure with shared libraries so everything is in libnetcdf.a. >>> I checked using otool and all the right references are in >>> libnetcdf.a, at least if I compare it to a working version of >>> netcdf 4.0 on my old powerpc mac. No netcdf 4.0 options were >>> turned on so I did not have to install netcdf with hdf5, zlib or >>> szlib (as this is what I tried at first and did not get it to work). >>> >>> So, the question is why do I get linking errors when I try to >>> compile fortran code that calls the netcdf libs? I compile the >>> code with gfortran-mp-4.3 and use the same options as when I built >>> netcdf 4.0 (-fno-second-underscore -O2 -g). I also have provided >>> the location of the include file and library explicitly in the >>> compile command line (-I/opt/local/include and -L/opt/local/lib - >>> lnetcdf). I also call some udunits functions which do not give >>> any errors and udunits was also installed using macports and is >>> in /opt/local. >>> >>> Do I need to recompile the gcc43 using the same options (-fno- >>> second-underscore)?? I tried compiling netcdf libs without this >>> option, but this also did not work. I tried compiling my code >>> without that option as well and it did not work. I also tried - >>> fno-underscoring - no luck. I have a netcdf 4.0 library installed >>> on my powerpc mac and can use gcc4.3 with that library with no >>> problem but neither of these packages were installed with >>> macports. I'd like to use macports for the new mac (intel), as it >>> seems more convenient than building source code myself all the >>> time. However, I desperately need a working netcdf library as all >>> my data is stored this way. >>> >>> Thanks for any help, Yolande >>> >>> >>> _______________________________________________ >>> macports-users mailing list >>> macports-users at lists.macosforge.org >>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users >> >> _______________________________________________ >> macports-users mailing list >> macports-users at lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > > Sch?ne Gr??e, > Jochen > -- > Einigkeit und Recht und Freiheit http://www.Jochen-Kuepper.de > Libert?, ?galit?, Fraternit? GnuPG key: CC1B0B4D > Sex, drugs and rock-n-roll > > Dr. Yolande Serra, Assoc. Research Faculty Institute of Atmospheric Physics University of Arizona (520) 621-6619 serra at atmo.arizona.edu From ryandesign at macports.org Thu Mar 19 22:11:54 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 20 Mar 2009 00:11:54 -0500 Subject: LibGnomeCanvas Dependency Problem In-Reply-To: <49C1FA69.5000108@comcast.net> References: <49C1FA69.5000108@comcast.net> Message-ID: <4FA73B87-D548-42E4-9D5A-638F9B6F37EE@macports.org> On Mar 19, 2009, at 02:55, Tom Condon wrote: > I have run into a problem with the libgnomecanvas port > dependencies. When I try to build it it says that libgnomecanvas is > dependent on "gail" (error message below). > > =================== > Package requirements ( gtk+-2.0 >= 2.0.3 gail >= 1.9.0 > libart-2.0 >= 2.3.8 pango >= 1.0.1 pangoft2 >= 1.0.1) were not > met: > > No package 'gail' found > =================== > > However, when I try: > > port info libgnomecanvas > > it says: > > =================== > Mac-The-Knife:~ Captain$ port info libgnomecanvas > libgnomecanvas @2.20.1.1, Revision 2 (gnome) > Variants: universal > > The GNOMECanvas library provides a number of features: Image > loading facilities. > Rendering of a GdkPixBuf into various formats: drawables (windows, > pixmaps), > GdkRGB buffers. A cache interface. > Homepage: http://www.gnome.org/ > > Build Dependencies: pkgconfig, perl5, p5-xml-parser, intltool > Library Dependencies: glib2, gtk2, pango, gettext, libiconv, > libart_lgpl, > libglade2 > Platforms: darwin > Maintainers: nomaintainer at macports.org > =================== > > With, as you see, no mention of "gail". > > When I try: > > port search gail > > I get: > > =================== > libgail-gnome @1.20.1 (gnome) > An implementation of the ATK interfaces for GNOME widgets. > =================== > > But an attempt to build libgail-gnome also finds a dependency on > package "gail". I can find no port at this time that declares a dependency on the deleted port "gail". Try "sudo port sync" to update your ports. > It also returns the following error, which makes no sense to me due > to a mismatch of quotes in the shell command: > > =================== > ---> Configuring at-spi > Error: Target org.macports.configure returned: configure failure: > shell command " cd "/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome > _at-spi/work/at-spi-1.24.1" && ./configure --prefix=/opt/local -- > enable-static --enable-platform-gnome-2 --disable-xevie --with-x " > returned error 1 > =================== This line only tells us that an error occurred configuring the at-spi port. The specific error that occurred is located in the subsequent lines which you omitted to show us. From jmr at macports.org Fri Mar 20 03:56:41 2009 From: jmr at macports.org (Joshua Root) Date: Fri, 20 Mar 2009 21:56:41 +1100 Subject: LibGnomeCanvas Dependency Problem In-Reply-To: <4FA73B87-D548-42E4-9D5A-638F9B6F37EE@macports.org> References: <49C1FA69.5000108@comcast.net> <4FA73B87-D548-42E4-9D5A-638F9B6F37EE@macports.org> Message-ID: <49C37669.8040201@macports.org> Ryan Schmidt wrote: > On Mar 19, 2009, at 02:55, Tom Condon wrote: >> But an attempt to build libgail-gnome also finds a dependency on >> package "gail". > > I can find no port at this time that declares a dependency on the > deleted port "gail". Try "sudo port sync" to update your ports. That's not the issue, it's the configure script that is complaining about gail being missing. This almost certainly points to an outdated gtk2. - Josh From david.trem at gmail.com Fri Mar 20 05:28:03 2009 From: david.trem at gmail.com (David Trem) Date: Fri, 20 Mar 2009 13:28:03 +0100 Subject: Problem installing vtk Message-ID: <49C38BD3.4070309@gmail.com> May somebody help ? I have a problem installing vtk on MacBook OS X 10.5.6, using macports 1.700 (fresh install). See console output below. Thanks in advance, David ---> Building VTK Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK" && make all " returned error 2 Command output: [ 62%] Built target vtkexpat make -f IO/CMakeFiles/vtkIO.dir/build.make IO/CMakeFiles/vtkIO.dir/depend cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK && /opt/local/bin/cmake -E cmake_depends "Unix Makefiles" /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/IO /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/IO /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/IO/CMakeFiles/vtkIO.dir/DependInfo.cmake --color= make -f IO/CMakeFiles/vtkIO.dir/build.make IO/CMakeFiles/vtkIO.dir/build make[2]: Nothing to be done for `IO/CMakeFiles/vtkIO.dir/build'. /opt/local/bin/cmake -E cmake_progress_report /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/CMakeFiles 51 52 53 54 55 56 57 58 59 60 61 62 [ 74%] Built target vtkIO make -f Utilities/freetype/CMakeFiles/vtkfreetype.dir/build.make Utilities/freetype/CMakeFiles/vtkfreetype.dir/depend cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK && /opt/local/bin/cmake -E cmake_depends "Unix Makefiles" /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Utilities/freetype /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Utilities/freetype /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Utilities/freetype/CMakeFiles/vtkfreetype.dir/DependInfo.cmake --color= make -f Utilities/freetype/CMakeFiles/vtkfreetype.dir/build.make Utilities/freetype/CMakeFiles/vtkfreetype.dir/build make[2]: Nothing to be done for `Utilities/freetype/CMakeFiles/vtkfreetype.dir/build'. /opt/local/bin/cmake -E cmake_progress_report /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/CMakeFiles 92 93 94 [ 77%] Built target vtkfreetype make -f Utilities/ftgl/CMakeFiles/vtkftgl.dir/build.make Utilities/ftgl/CMakeFiles/vtkftgl.dir/depend cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK && /opt/local/bin/cmake -E cmake_depends "Unix Makefiles" /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Utilities/ftgl /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Utilities/ftgl /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Utilities/ftgl/CMakeFiles/vtkftgl.dir/DependInfo.cmake --color= make -f Utilities/ftgl/CMakeFiles/vtkftgl.dir/build.make Utilities/ftgl/CMakeFiles/vtkftgl.dir/build make[2]: Nothing to be done for `Utilities/ftgl/CMakeFiles/vtkftgl.dir/build'. /opt/local/bin/cmake -E cmake_progress_report /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/CMakeFiles 95 [ 78%] Built target vtkftgl make -f Rendering/CMakeFiles/vtkRendering.dir/build.make Rendering/CMakeFiles/vtkRendering.dir/depend cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK && /opt/local/bin/cmake -E cmake_depends "Unix Makefiles" /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Rendering /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Rendering /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Rendering/CMakeFiles/vtkRendering.dir/DependInfo.cmake --color= make -f Rendering/CMakeFiles/vtkRendering.dir/build.make Rendering/CMakeFiles/vtkRendering.dir/build /opt/local/bin/cmake -E cmake_progress_report /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/CMakeFiles [ 78%] Building CXX object Rendering/CMakeFiles/vtkRendering.dir/vtkCocoaRenderWindowInteractor.o cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Rendering && /usr/bin/c++ -DvtkRendering_EXPORTS -Wno-deprecated -no-cpp-precomp -fPIC -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Rendering -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Hybrid -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/IO -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Imaging -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Graphics -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Filtering -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Common -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Common/Testing/Cxx -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Utilities/zlib -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Utilities/jpeg -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Utilities/png -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Utilities/tiff -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Utilities/expat -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Utilities/DICOMParser -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Utilities/freetype/include -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Utilities/freetype -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Utilities/ftgl/src -I/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Utilities/ftgl -o CMakeFiles/vtkRendering.dir/vtkCocoaRenderWindowInteractor.o -c /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Rendering/vtkCocoaRenderWindowInteractor.mm /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_vtk/work/VTK/Rendering/vtkCocoaGLView.h:11: error: using typedef-name 'NSOpenGLPixelFormatAttribute' after 'enum' /System/Library/Frameworks/AppKit.framework/Headers/NSOpenGL.h:90: error: 'NSOpenGLPixelFormatAttribute' has a previous declaration here make[2]: *** [Rendering/CMakeFiles/vtkRendering.dir/vtkCocoaRenderWindowInteractor.o] Error 1 make[1]: *** [Rendering/CMakeFiles/vtkRendering.dir/all] Error 2 make: *** [all] Error 2 Error: Status 1 encountered during processing. From cerieljacobs at gmail.com Fri Mar 20 06:38:43 2009 From: cerieljacobs at gmail.com (Ceriel Jacobs) Date: Fri, 20 Mar 2009 14:38:43 +0100 Subject: r48332 openssl command line configure.optflags=-fast doesn't override (-O3) Message-ID: On Mon Feb 16 13:21:30 PST 2009 Marcus Calhoun-Lopez worte: >> You could write a shell script which overrides the default values >> >> You can also edit the file >> ${prefix}/share/macports/Tcl/port1.0/portconfigure.tcl >> These two actions only set the default value. >> A Portfile can override your value as well. On Mon Feb 16 17:01:33 PST 2009 Rainer M?ller wrote: > No, command line options override values given in the Portfile. When setting portconfigure.tcl to default configure.optflags=-fast openssl reverts the optflag back to -O3. When specifying one the command line, openssl still uses -O3. Besides the openssl port file [1] doesn't contain -O3 neither any text containing the word flag. [1] http://trac.macports.org/browser/trunk/dports/devel/openssl/Portfile Other port installs, like zlib, do honour the flag -fast. What am I missing that the command $ sudo /opt/local/bin/port -d install openssl +universal configure.optflags=-fast configure.march=nocona still uses -O3 instead of the specified -fast as flag? Or should I file a ticket? Is this a bug submission or a feature request? ~Ceriel Environment: universal=x86_64, compiler=gcc-4.2 --- DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/openssl DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/devel/openssl DEBUG: OS Platform: darwin DEBUG: OS Version: 9.6.0 DEBUG: Mac OS X Version: 10.5 DEBUG: System Arch: i386 DEBUG: setting option os.universal_supported to yes CFLAG =-fPIC -fno-common -DOPENSSL_PIC -DZLIB - DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -arch x86_64 - isysroot /Developer/SDKs/MacOSX10.5.sdk -O3 -fomit-frame-pointer - DL_ENDIAN -DMD32_REG_T=int -Wall From jmr at macports.org Fri Mar 20 07:19:08 2009 From: jmr at macports.org (Joshua Root) Date: Sat, 21 Mar 2009 01:19:08 +1100 Subject: r48332 openssl command line configure.optflags=-fast doesn't override (-O3) In-Reply-To: References: Message-ID: <49C3A5DC.9050304@macports.org> Ceriel Jacobs wrote: > On Mon Feb 16 13:21:30 PST 2009 Marcus Calhoun-Lopez worte: >>> You could write a shell script which overrides the default values >>> >>> You can also edit the file >>> ${prefix}/share/macports/Tcl/port1.0/portconfigure.tcl >>> These two actions only set the default value. >>> A Portfile can override your value as well. > > On Mon Feb 16 17:01:33 PST 2009 Rainer M?ller wrote: >> No, command line options override values given in the Portfile. > > When setting portconfigure.tcl to default configure.optflags=-fast > openssl reverts the optflag back to -O3. > > When specifying one the command line, openssl still uses -O3. > > Besides the openssl port file [1] doesn't contain -O3 neither any text > containing the word flag. > [1] http://trac.macports.org/browser/trunk/dports/devel/openssl/Portfile > > Other port installs, like zlib, do honour the flag -fast. > > What am I missing that the command > $ sudo /opt/local/bin/port -d install openssl +universal > configure.optflags=-fast configure.march=nocona > still uses -O3 instead of the specified -fast as flag? > > Or should I file a ticket? Is this a bug submission or a feature request? OpenSSL just doesn't use any old CFLAGS you set in the environment. This is an upstream bug / design decision. - Josh From esiegel at berkeley.edu Fri Mar 20 11:09:05 2009 From: esiegel at berkeley.edu (esiegel at berkeley.edu) Date: Fri, 20 Mar 2009 11:09:05 -0700 (PDT) Subject: Incorrect libjpeg.dylib after installing ImageMagick Message-ID: <52498.65.113.40.1.1237572545.squirrel@calmail.berkeley.edu> I have been trying to solve this problems for several hours now with many failed attempts. I found some answers from before, but they don't seem to work with me. Basically, after installing ImageMagick with macports, libjpeg was installed to /opt/local/lib/libjpeg.dylib, but now several executables (unrelated to Imagemagick) now point to this library instead of the OS X default. For example mate, php, and others all report this error message: dyld: Symbol not found: __cg_jpeg_resync_to_restart Referenced from: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO Expected in: /opt/local/lib/libJPEG.dylib >From a previous post, it was suggested that I copy the library from ImageIO folder into the opt/local folder, but this caused library incompatibility problems. I have tried uninstalling ImageMagick, but it didn't help. I have tried searching for every symbolic link hoping that I could change something to point back to the original library. I have looked at my .profile .bashrc, etc to see if there was anything that should be changed, but so far no go. AHHHH, I'm going crazy. eric From serra at atmo.arizona.edu Fri Mar 20 11:20:45 2009 From: serra at atmo.arizona.edu (Yolande Serra) Date: Fri, 20 Mar 2009 11:20:45 -0700 Subject: Incorrect libjpeg.dylib after installing ImageMagick In-Reply-To: <52498.65.113.40.1.1237572545.squirrel@calmail.berkeley.edu> References: <52498.65.113.40.1.1237572545.squirrel@calmail.berkeley.edu> Message-ID: <3BF90774-22DD-401B-8FE7-7864CB698D7A@atmo.arizona.edu> Not sure this will help, but if you defined a DYLD_LIBRARY_PATH in your .bashrc or .profile get rid of it. The libraries that macs point to are found assuming this variable is not defined. Somewhere buried in the system it has a path to its own libs. You mess this up when you define dynamic library paths. hope this helps, Yolande On Mar 20, 2009, at 11:09 AM, esiegel at berkeley.edu wrote: > I have been trying to solve this problems for several hours now with > many > failed attempts. I found some answers from before, but they don't > seem to > work with me. > > Basically, after installing ImageMagick with macports, libjpeg was > installed to /opt/local/lib/libjpeg.dylib, but now several executables > (unrelated to Imagemagick) now point to this library instead of the > OS X > default. > > For example mate, php, and others all report this error message: > > dyld: Symbol not found: __cg_jpeg_resync_to_restart > Referenced from: > /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ > Frameworks/ImageIO.framework/Versions/A/ImageIO > Expected in: /opt/local/lib/libJPEG.dylib > >> From a previous post, it was suggested that I copy the library from > ImageIO folder into the opt/local folder, but this caused library > incompatibility problems. > > I have tried uninstalling ImageMagick, but it didn't help. > > I have tried searching for every symbolic link hoping that I could > change > something to point back to the original library. > > I have looked at my .profile .bashrc, etc to see if there was anything > that should be changed, but so far no go. > > AHHHH, I'm going crazy. > > eric > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From kellert at ohsu.edu Fri Mar 20 13:30:58 2009 From: kellert at ohsu.edu (Thomas Keller) Date: Fri, 20 Mar 2009 13:30:58 -0700 Subject: selfupdate error feedback In-Reply-To: References: Message-ID: 1. I think its unlikely my G5 had a rsync port closed. There is no interface in system preferences -> sharing for turning off rsync. Also the rsync ports on the OHSU network should all be open as that is how we run the current backup solution. On Mar 20, 2009, at 7:06 AM, macports-users- request at lists.macosforge.org wrote: > Send macports-users mailing list submissions to > macports-users at lists.macosforge.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > or, via email, send a message with subject or body 'help' to > macports-users-request at lists.macosforge.org > > You can reach the person managing the list at > macports-users-owner at lists.macosforge.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of macports-users digest..." > > > Today's Topics: > > 1. selfupdate error (Thomas Keller) > 2. Re: selfupdate error (Joshua Root) > 3. using dependency criteria before package removal (Artie Ziff) > 4. Re: using dependency criteria before package removal (Joshua > Root) > 5. Re: netcdf 4.0 lib not linking (Jochen K?pper) > 6. Any ideas on getting gfortran? (MD White) > 7. Re: Any ideas on getting gfortran? (Bryan Blackburn) > 8. Re: netcdf 4.0 lib not linking (Yolande Serra) > 9. Re: LibGnomeCanvas Dependency Problem (Ryan Schmidt) > 10. Re: LibGnomeCanvas Dependency Problem (Joshua Root) > 11. Problem installing vtk (David Trem) > 12. r48332 openssl command line configure.optflags=-fast doesn't > override (-O3) (Ceriel Jacobs) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 19 Mar 2009 09:52:44 -0700 > From: Thomas Keller > Subject: selfupdate error > To: macports-users at lists.macosforge.org > Message-ID: <30181350-E653-4C26-A2BE-A78FE822DA70 at ohsu.edu> > Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes > > Greetings, > Could someone give me advice on what to do when selfupdate fails? > Error: /opt/local/bin/port: port selfupdate failed: Couldn't sync the > ports tree: Synchronization of 1 source(s) failed > > thanks, > Tom K > > > ------------------------------ > > Message: 2 > Date: Fri, 20 Mar 2009 04:26:30 +1100 > From: Joshua Root > Subject: Re: selfupdate error > To: Thomas Keller > Cc: macports-users at lists.macosforge.org > Message-ID: <49C28046.6070000 at macports.org> > Content-Type: text/plain; charset=ISO-8859-1 > > Thomas Keller wrote: >> Greetings, >> Could someone give me advice on what to do when selfupdate fails? >> Error: /opt/local/bin/port: port selfupdate failed: Couldn't sync the >> ports tree: Synchronization of 1 source(s) failed > > Check that your network is working and not blocking traffic to either > the rsync port (TCP/873) or Apple's network. PeerGuardian is notorious > for doing the latter. > > - Josh > > > ------------------------------ > > Message: 3 > Date: Thu, 19 Mar 2009 13:03:09 -0700 > From: Artie Ziff > Subject: using dependency criteria before package removal > To: MacPorts Users > Message-ID: <49C2A4FD.5050605 at gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hello, > > I noticed that my MacPort builds python 2.4. I probably do not need > it. > > In an effort to learn how to better manage the MacPort tree (which > must > be huge by now), can I remove python 2.4? Here's some info: > > $ port -v deps python24 > python24 has library dependencies on: > port:gettext > > > thank you! > Art > > > ------------------------------ > > Message: 4 > Date: Fri, 20 Mar 2009 07:11:00 +1100 > From: Joshua Root > Subject: Re: using dependency criteria before package removal > To: Artie Ziff > Cc: MacPorts Users > Message-ID: <49C2A6D4.7000709 at macports.org> > Content-Type: text/plain; charset=ISO-8859-1 > > Artie Ziff wrote: >> Hello, >> >> I noticed that my MacPort builds python 2.4. I probably do not need >> it. >> >> In an effort to learn how to better manage the MacPort tree (which >> must >> be huge by now), can I remove python 2.4? Here's some info: >> >> $ port -v deps python24 >> python24 has library dependencies on: >> port:gettext > > You will get an error message if you try to uninstall a port that has > dependents. Or you can find out beforehand like this: > > port dependents python24 > > - Josh > > > ------------------------------ > > Message: 5 > Date: Thu, 19 Mar 2009 23:53:44 +0100 > From: Jochen K?pper > Subject: Re: netcdf 4.0 lib not linking > To: Yolande Serra > Cc: macports-users at lists.macosforge.org > Message-ID: > Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"; > DelSp="yes" > > On 18.03.2009, at 18:33, Yolande Serra wrote: > >> I just wanted to let the list know I fixed the problem with linking >> my netcdf 4.0 library to a fortran program. Note, the macports >> netcdf install works fine with C code calling netcdf routines, only >> fortran code seemed to be an issue (even with the +g95 variant). >> The steps I took were the following: >> >> build szlib as standard installation from macports >> build openmpi with the +gcc43 variant so that fortran is enabled >> build hdf5-18 with the +gcc43 variant, again so that fortran is >> enabled >> build netcdf using gcc43 with fortran enabled - I wrote my own >> Portfile to do this as I wanted netcdf 4 capabilities. The macports >> netcdf installation does not activate netcdf-4 (in which case you >> might as well just install netcdf-3.x). >> >> Then, when compiling code that references libnetcdf.a use >> >>>> gfortran -fsecond-underscore -I/opt/local/include program.f -o >> program -L/opt/local/lib -lnetcdf >> >> The -fsecond-underscore is critical, at least for my setup. >> Otherwise the code will not link to the netcdf library, which has >> second underscores. I suppose you could also build the netcdf >> library with FFLAG -fno-second-underscore. I did not try this. I'm >> curious why the gcc43 compiler suite built the netcdf library with >> second underscores but does not build my .f code with them. > > Is gfortran actually gfortran-mp-4.3? > >> my Portfile (used macports netcdf portfile as a template): >> >> PortSystem 1.0 >> name netcdf >> version 4.0 >> maintainers serra at atmo.arizona.edu >> platforms darwin >> categories science >> >> description NetCDF - Network Common Data Form >> long_description NetCDF is an interface \ >> for array-oriented data access and a library >> that \ >> provides an implementation of the interface. >> The \ >> netCDF library also defines a machine- >> independent \ >> format for representing scientific data. >> Together, \ >> the interface, library, and format support >> the \ >> creation, access, and sharing of scientific >> data. \ >> The netCDF software was developed at the >> Unidata \ >> Program Center in Boulder, Colorado. >> >> homepage http://unidata.ucar.edu/packages/netcdf/ >> >> master_sites ftp://ftp.unidata.ucar.edu/pub/netcdf/ \ >> http://www.gfd-dennou.org/arch/netcdf/unidata-mirror/ \ >> ftp://www.gfd-dennou.org/arch/netcdf/unidata-mirror/ >> checksums sha1 bea99846265e55e54be2c200ae004acc3a221c0a >> >> depends_lib port:hdf5 \ >> port:szip >> >> configure.cppflags "-DNDEBUG -Df2cFortran" >> configure.cxxflags "-O2 -fno-common" >> configure.cflags "-O2 -fno-common" >> configure.args --disable-f77 \ >> # --enable-shared \ >> --enable-netcdf-4 \ >> --with-zlib=${prefix}/lib \ >> --with-szlib=${prefix}/lib \ >> --with-hdf5=${prefix}/lib >> >> test.run yes >> test.target check >> >> destroot.destdir prefix=${destroot}${prefix} \ >> MANDIR=\\\${prefix}/share/man >> >> post-destroot { >> file delete -force ${destroot}${prefix}/share/man/whatis.db >> } >> >> variant g95 { >> depends_lib port:g95 >> configure.args-delete --disable-f77 >> configure.fc ${prefix}/bin/g95 >> configure.env-append FCFLAGS=-O2 >> } >> >> variant gfortran43 { >> depends_lib port:gcc43 >> configure.args-delete --disable-f77 >> configure.cc ${prefix}/bin/gcc-mp-4.3 >> configure.cxx ${prefix}/bin/g++-mp-4.3 >> configure.fc ${prefix}/bin/gfortran-mp-4.3 >> } >> >> >> >> >> On Mar 16, 2009, at 12:15 PM, Yolande Serra wrote: >> >>> I've written previously about this issue and got no reply. I'm >>> trying again after trying everything I could think of to get my >>> netcdf 4.0 library installed with macport to work with the gcc43 >>> also installed with macport. I made a local port for netcdf in >>> which I compiled it with gcc43 after having installed gcc43 from >>> macport. The build worked and I configured it with gfortran so >>> that the fortran libs were also installed with my netcdf libs. I >>> selected to not have separate fortran libraries and did not >>> configure with shared libraries so everything is in libnetcdf.a. I >>> checked using otool and all the right references are in >>> libnetcdf.a, at least if I compare it to a working version of >>> netcdf 4.0 on my old powerpc mac. No netcdf 4.0 options were >>> turned on so I did not have to install netcdf with hdf5, zlib or >>> szlib (as this is what I tried at first and did not get it to work). >>> >>> So, the question is why do I get linking errors when I try to >>> compile fortran code that calls the netcdf libs? I compile the >>> code with gfortran-mp-4.3 and use the same options as when I built >>> netcdf 4.0 (-fno-second-underscore -O2 -g). I also have provided >>> the location of the include file and library explicitly in the >>> compile command line (-I/opt/local/include and -L/opt/local/lib - >>> lnetcdf). I also call some udunits functions which do not give any >>> errors and udunits was also installed using macports and is in /opt/ >>> local. >>> >>> Do I need to recompile the gcc43 using the same options (-fno- >>> second-underscore)?? I tried compiling netcdf libs without this >>> option, but this also did not work. I tried compiling my code >>> without that option as well and it did not work. I also tried -fno- >>> underscoring - no luck. I have a netcdf 4.0 library installed on my >>> powerpc mac and can use gcc4.3 with that library with no problem >>> but neither of these packages were installed with macports. I'd >>> like to use macports for the new mac (intel), as it seems more >>> convenient than building source code myself all the time. However, >>> I desperately need a working netcdf library as all my data is >>> stored this way. >>> >>> Thanks for any help, Yolande >>> >>> >>> _______________________________________________ >>> macports-users mailing list >>> macports-users at lists.macosforge.org >>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users >> >> _______________________________________________ >> macports-users mailing list >> macports-users at lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > > Sch?ne Gr??e, > Jochen > -- > Einigkeit und Recht und Freiheit http://www.Jochen-Kuepper.de > Libert?, ?galit?, Fraternit? GnuPG key: CC1B0B4D > Sex, drugs and rock-n-roll > > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: PGP.sig > Type: application/pgp-signature > Size: 194 bytes > Desc: This is a digitally signed message part > URL: > > > ------------------------------ > > Message: 6 > Date: Thu, 19 Mar 2009 20:26:13 -0400 > From: MD White > Subject: Any ideas on getting gfortran? > To: macports-users at lists.macosforge.org > Message-ID: <4F03A8A5-34EB-4ED7-962E-6402490E6E53 at woh.rr.com> > Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed > > Hi, > > I tried to get gfortran by grabbing the gcc44 (beta) port. It > downloaded gcc-core-4.4.20090313.tar.bz2, gcc- > fortran-4.4.20090313.tar.bz2, gcc-g++-4.4.20090313.tar.bz2, gcc- > java-4.4.20090313.tar.bz2 and gcc-objc-4.4.20090313.tar.bz2 but then > proceeded to just build gcc. There were no error messages, just that > it installed gcc 4.4 and then cleaned up. It installed: > > cpp-mp-4.4 > gcc-mp-4.4 > gccbug-mp-4.4 > gcov-mp-4.4 > i386-apple-darwin9.6.0-gcc-4.4.0 > i386-apple-darwin9.6.0-gcc-mp-4.4 > c++-mp-4.4 > g++-mp-4.4 > i386-apple-darwin9.6.0-g++-4.4.0 > i386-apple-darwin9.6.0-g++-mp-4.4 > > but, no gfortran (and no java for that matter). So does anyone have > ideas on how to get gfortran 4.4 from macports? Is there a problem > with the port? (I am running OS X 10.5.6 on an intel machine). > > Thanks, > > - M > > > > ------------------------------ > > Message: 7 > Date: Thu, 19 Mar 2009 18:34:09 -0600 > From: Bryan Blackburn > Subject: Re: Any ideas on getting gfortran? > To: macports-users at lists.macosforge.org > Message-ID: <20090320003409.GE1014 at ninagal.withay.com> > Content-Type: text/plain; charset=us-ascii > > On Thu, Mar 19, 2009 at 08:26:13PM -0400, MD White said: >> Hi, >> >> I tried to get gfortran by grabbing the gcc44 (beta) port. It >> downloaded >> gcc-core-4.4.20090313.tar.bz2, gcc-fortran-4.4.20090313.tar.bz2, >> gcc-g++-4.4.20090313.tar.bz2, gcc-java-4.4.20090313.tar.bz2 and >> gcc-objc-4.4.20090313.tar.bz2 but then proceeded to just build >> gcc. There >> were no error messages, just that it installed gcc 4.4 and then >> cleaned >> up. It installed: >> >> cpp-mp-4.4 >> gcc-mp-4.4 >> gccbug-mp-4.4 >> gcov-mp-4.4 >> i386-apple-darwin9.6.0-gcc-4.4.0 >> i386-apple-darwin9.6.0-gcc-mp-4.4 >> c++-mp-4.4 >> g++-mp-4.4 >> i386-apple-darwin9.6.0-g++-4.4.0 >> i386-apple-darwin9.6.0-g++-mp-4.4 >> >> but, no gfortran (and no java for that matter). So does anyone have >> ideas on how to get gfortran 4.4 from macports? Is there a >> problem with >> the port? (I am running OS X 10.5.6 on an intel machine). > > gcc44 has a variant for it (and for java), which states "this > language will > be enabled in the final version - this variant is completely > untested!" so > you may be successful or have issues. > > gcc43 builds it fine though, without variants. > > Bryan > > >> >> Thanks, >> >> - M > > > ------------------------------ > > Message: 8 > Date: Thu, 19 Mar 2009 20:32:41 -0700 > From: Yolande Serra > Subject: Re: netcdf 4.0 lib not linking > To: Jochen K?pper > Cc: macports-users at lists.macosforge.org > Message-ID: <3041668D-B2D3-498A-B3DE-C38CA7BCE47C at atmo.arizona.edu> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes > > > On Mar 19, 2009, at 3:53 PM, Jochen K?pper wrote: > >> On 18.03.2009, at 18:33, Yolande Serra wrote: >> >>> I just wanted to let the list know I fixed the problem with linking >>> my netcdf 4.0 library to a fortran program. Note, the macports >>> netcdf install works fine with C code calling netcdf routines, only >>> fortran code seemed to be an issue (even with the +g95 variant). >>> The steps I took were the following: >>> >>> build szlib as standard installation from macports >>> build openmpi with the +gcc43 variant so that fortran is enabled >>> build hdf5-18 with the +gcc43 variant, again so that fortran is >>> enabled >>> build netcdf using gcc43 with fortran enabled - I wrote my own >>> Portfile to do this as I wanted netcdf 4 capabilities. The >>> macports netcdf installation does not activate netcdf-4 (in which >>> case you might as well just install netcdf-3.x). >>> >>> Then, when compiling code that references libnetcdf.a use >>> >>>>> gfortran -fsecond-underscore -I/opt/local/include program.f -o >>> program -L/opt/local/lib -lnetcdf >>> >>> The -fsecond-underscore is critical, at least for my setup. >>> Otherwise the code will not link to the netcdf library, which has >>> second underscores. I suppose you could also build the netcdf >>> library with FFLAG -fno-second-underscore. I did not try this. >>> I'm curious why the gcc43 compiler suite built the netcdf library >>> with second underscores but does not build my .f code with them. >> >> Is gfortran actually gfortran-mp-4.3? > > Yes, that is how macports installs it. Probably so it won't override > the default installation of gcc 4.0 on Macs that ships with Xcode. > That installation has gcc but not gfortran. After you install gcc43 > with macports check /opt/local/bin/ and you will see the compiler > collection. > >> >> >>> my Portfile (used macports netcdf portfile as a template): >>> >>> PortSystem 1.0 >>> name netcdf >>> version 4.0 >>> maintainers serra at atmo.arizona.edu >>> platforms darwin >>> categories science >>> >>> description NetCDF - Network Common Data Form >>> long_description NetCDF is an interface \ >>> for array-oriented data access and a library >>> that \ >>> provides an implementation of the interface. >>> The \ >>> netCDF library also defines a machine- >>> independent \ >>> format for representing scientific data. >>> Together, \ >>> the interface, library, and format support >>> the \ >>> creation, access, and sharing of scientific >>> data. \ >>> The netCDF software was developed at the >>> Unidata \ >>> Program Center in Boulder, Colorado. >>> >>> homepage http://unidata.ucar.edu/packages/netcdf/ >>> >>> master_sites ftp://ftp.unidata.ucar.edu/pub/netcdf/ \ >>> http://www.gfd-dennou.org/arch/netcdf/unidata-mirror/ \ >>> ftp://www.gfd-dennou.org/arch/netcdf/unidata-mirror/ >>> checksums sha1 bea99846265e55e54be2c200ae004acc3a221c0a >>> >>> depends_lib port:hdf5 \ >>> port:szip >>> >>> configure.cppflags "-DNDEBUG -Df2cFortran" >>> configure.cxxflags "-O2 -fno-common" >>> configure.cflags "-O2 -fno-common" >>> configure.args --disable-f77 \ >>> # --enable-shared \ >>> --enable-netcdf-4 \ >>> --with-zlib=${prefix}/lib \ >>> --with-szlib=${prefix}/lib \ >>> --with-hdf5=${prefix}/lib >>> >>> test.run yes >>> test.target check >>> >>> destroot.destdir prefix=${destroot}${prefix} \ >>> MANDIR=\\\${prefix}/share/man >>> >>> post-destroot { >>> file delete -force ${destroot}${prefix}/share/man/whatis.db >>> } >>> >>> variant g95 { >>> depends_lib port:g95 >>> configure.args-delete --disable-f77 >>> configure.fc ${prefix}/bin/g95 >>> configure.env-append FCFLAGS=-O2 >>> } >>> >>> variant gfortran43 { >>> depends_lib port:gcc43 >>> configure.args-delete --disable-f77 >>> configure.cc ${prefix}/bin/gcc-mp-4.3 >>> configure.cxx ${prefix}/bin/g++-mp-4.3 >>> configure.fc ${prefix}/bin/gfortran-mp-4.3 >>> } >>> >>> >>> >>> >>> On Mar 16, 2009, at 12:15 PM, Yolande Serra wrote: >>> >>>> I've written previously about this issue and got no reply. I'm >>>> trying again after trying everything I could think of to get my >>>> netcdf 4.0 library installed with macport to work with the gcc43 >>>> also installed with macport. I made a local port for netcdf in >>>> which I compiled it with gcc43 after having installed gcc43 from >>>> macport. The build worked and I configured it with gfortran so >>>> that the fortran libs were also installed with my netcdf libs. I >>>> selected to not have separate fortran libraries and did not >>>> configure with shared libraries so everything is in libnetcdf.a. >>>> I checked using otool and all the right references are in >>>> libnetcdf.a, at least if I compare it to a working version of >>>> netcdf 4.0 on my old powerpc mac. No netcdf 4.0 options were >>>> turned on so I did not have to install netcdf with hdf5, zlib or >>>> szlib (as this is what I tried at first and did not get it to >>>> work). >>>> >>>> So, the question is why do I get linking errors when I try to >>>> compile fortran code that calls the netcdf libs? I compile the >>>> code with gfortran-mp-4.3 and use the same options as when I built >>>> netcdf 4.0 (-fno-second-underscore -O2 -g). I also have provided >>>> the location of the include file and library explicitly in the >>>> compile command line (-I/opt/local/include and -L/opt/local/lib - >>>> lnetcdf). I also call some udunits functions which do not give >>>> any errors and udunits was also installed using macports and is >>>> in /opt/local. >>>> >>>> Do I need to recompile the gcc43 using the same options (-fno- >>>> second-underscore)?? I tried compiling netcdf libs without this >>>> option, but this also did not work. I tried compiling my code >>>> without that option as well and it did not work. I also tried - >>>> fno-underscoring - no luck. I have a netcdf 4.0 library installed >>>> on my powerpc mac and can use gcc4.3 with that library with no >>>> problem but neither of these packages were installed with >>>> macports. I'd like to use macports for the new mac (intel), as it >>>> seems more convenient than building source code myself all the >>>> time. However, I desperately need a working netcdf library as all >>>> my data is stored this way. >>>> >>>> Thanks for any help, Yolande >>>> >>>> >>>> _______________________________________________ >>>> macports-users mailing list >>>> macports-users at lists.macosforge.org >>>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users >>> >>> _______________________________________________ >>> macports-users mailing list >>> macports-users at lists.macosforge.org >>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users >> >> Sch?ne Gr??e, >> Jochen >> -- >> Einigkeit und Recht und Freiheit http://www.Jochen-Kuepper.de >> Libert?, ?galit?, Fraternit? GnuPG key: CC1B0B4D >> Sex, drugs and rock-n-roll >> >> > > Dr. Yolande Serra, Assoc. Research Faculty > Institute of Atmospheric Physics > University of Arizona > (520) 621-6619 > serra at atmo.arizona.edu > > > > > > ------------------------------ > > Message: 9 > Date: Fri, 20 Mar 2009 00:11:54 -0500 > From: Ryan Schmidt > Subject: Re: LibGnomeCanvas Dependency Problem > To: tom at condonia.org > Cc: macports-users at lists.macosforge.org > Message-ID: <4FA73B87-D548-42E4-9D5A-638F9B6F37EE at macports.org> > Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed > > On Mar 19, 2009, at 02:55, Tom Condon wrote: > >> I have run into a problem with the libgnomecanvas port >> dependencies. When I try to build it it says that libgnomecanvas is >> dependent on "gail" (error message below). >> >> =================== >> Package requirements ( gtk+-2.0 >= 2.0.3 gail >= 1.9.0 >> libart-2.0 >= 2.3.8 pango >= 1.0.1 pangoft2 >= 1.0.1) were not >> met: >> >> No package 'gail' found >> =================== >> >> However, when I try: >> >> port info libgnomecanvas >> >> it says: >> >> =================== >> Mac-The-Knife:~ Captain$ port info libgnomecanvas >> libgnomecanvas @2.20.1.1, Revision 2 (gnome) >> Variants: universal >> >> The GNOMECanvas library provides a number of features: Image >> loading facilities. >> Rendering of a GdkPixBuf into various formats: drawables (windows, >> pixmaps), >> GdkRGB buffers. A cache interface. >> Homepage: http://www.gnome.org/ >> >> Build Dependencies: pkgconfig, perl5, p5-xml-parser, intltool >> Library Dependencies: glib2, gtk2, pango, gettext, libiconv, >> libart_lgpl, >> libglade2 >> Platforms: darwin >> Maintainers: nomaintainer at macports.org >> =================== >> >> With, as you see, no mention of "gail". >> >> When I try: >> >> port search gail >> >> I get: >> >> =================== >> libgail-gnome @1.20.1 (gnome) >> An implementation of the ATK interfaces for GNOME widgets. >> =================== >> >> But an attempt to build libgail-gnome also finds a dependency on >> package "gail". > > I can find no port at this time that declares a dependency on the > deleted port "gail". Try "sudo port sync" to update your ports. > > >> It also returns the following error, which makes no sense to me due >> to a mismatch of quotes in the shell command: >> >> =================== >> ---> Configuring at-spi >> Error: Target org.macports.configure returned: configure failure: >> shell command " cd "/opt/local/var/macports/build/ >> _opt_local_var_macports_sources_rsync >> .macports.org_release_ports_gnome >> _at-spi/work/at-spi-1.24.1" && ./configure --prefix=/opt/local -- >> enable-static --enable-platform-gnome-2 --disable-xevie --with-x " >> returned error 1 >> =================== > > This line only tells us that an error occurred configuring the at-spi > port. The specific error that occurred is located in the subsequent > lines which you omitted to show us. > > > > > ------------------------------ > > Message: 10 > Date: Fri, 20 Mar 2009 21:56:41 +1100 > From: Joshua Root > Subject: Re: LibGnomeCanvas Dependency Problem > To: Ryan Schmidt > Cc: macports-users at lists.macosforge.org > Message-ID: <49C37669.8040201 at macports.org> > Content-Type: text/plain; charset=ISO-8859-1 > > Ryan Schmidt wrote: >> On Mar 19, 2009, at 02:55, Tom Condon wrote: >>> But an attempt to build libgail-gnome also finds a dependency on >>> package "gail". >> >> I can find no port at this time that declares a dependency on the >> deleted port "gail". Try "sudo port sync" to update your ports. > > That's not the issue, it's the configure script that is complaining > about gail being missing. This almost certainly points to an > outdated gtk2. > > - Josh > > > ------------------------------ > > Message: 11 > Date: Fri, 20 Mar 2009 13:28:03 +0100 > From: David Trem > Subject: Problem installing vtk > To: MacPorts Users > Message-ID: <49C38BD3.4070309 at gmail.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > May somebody help ? > I have a problem installing vtk on MacBook OS X 10.5.6, using macports > 1.700 (fresh install). > See console output below. > > Thanks in advance, > > David > > ---> Building VTK > Error: Target org.macports.build returned: shell command " cd > "/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK" > && make all " returned error 2 > Command output: [ 62%] Built target vtkexpat > make -f IO/CMakeFiles/vtkIO.dir/build.make IO/CMakeFiles/vtkIO.dir/ > depend > cd > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK > && /opt/local/bin/cmake -E cmake_depends "Unix Makefiles" > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/IO > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/IO > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/IO/CMakeFiles/ > vtkIO.dir/DependInfo.cmake > --color= > make -f IO/CMakeFiles/vtkIO.dir/build.make IO/CMakeFiles/vtkIO.dir/ > build > make[2]: Nothing to be done for `IO/CMakeFiles/vtkIO.dir/build'. > /opt/local/bin/cmake -E cmake_progress_report > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/CMakeFiles > 51 52 53 54 55 56 57 58 59 60 61 62 > [ 74%] Built target vtkIO > make -f Utilities/freetype/CMakeFiles/vtkfreetype.dir/build.make > Utilities/freetype/CMakeFiles/vtkfreetype.dir/depend > cd > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK > && /opt/local/bin/cmake -E cmake_depends "Unix Makefiles" > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Utilities/freetype > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Utilities/freetype > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Utilities/freetype/ > CMakeFiles/vtkfreetype.dir/DependInfo.cmake > --color= > make -f Utilities/freetype/CMakeFiles/vtkfreetype.dir/build.make > Utilities/freetype/CMakeFiles/vtkfreetype.dir/build > make[2]: Nothing to be done for > `Utilities/freetype/CMakeFiles/vtkfreetype.dir/build'. > /opt/local/bin/cmake -E cmake_progress_report > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/CMakeFiles > 92 93 94 > [ 77%] Built target vtkfreetype > make -f Utilities/ftgl/CMakeFiles/vtkftgl.dir/build.make > Utilities/ftgl/CMakeFiles/vtkftgl.dir/depend > cd > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK > && /opt/local/bin/cmake -E cmake_depends "Unix Makefiles" > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Utilities/ftgl > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Utilities/ftgl > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Utilities/ftgl/ > CMakeFiles/vtkftgl.dir/DependInfo.cmake > --color= > make -f Utilities/ftgl/CMakeFiles/vtkftgl.dir/build.make > Utilities/ftgl/CMakeFiles/vtkftgl.dir/build > make[2]: Nothing to be done for > `Utilities/ftgl/CMakeFiles/vtkftgl.dir/build'. > /opt/local/bin/cmake -E cmake_progress_report > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/CMakeFiles > 95 > [ 78%] Built target vtkftgl > make -f Rendering/CMakeFiles/vtkRendering.dir/build.make > Rendering/CMakeFiles/vtkRendering.dir/depend > cd > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK > && /opt/local/bin/cmake -E cmake_depends "Unix Makefiles" > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Rendering > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Rendering > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Rendering/ > CMakeFiles/vtkRendering.dir/DependInfo.cmake > --color= > make -f Rendering/CMakeFiles/vtkRendering.dir/build.make > Rendering/CMakeFiles/vtkRendering.dir/build > /opt/local/bin/cmake -E cmake_progress_report > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/CMakeFiles > > [ 78%] Building CXX object > Rendering/CMakeFiles/vtkRendering.dir/vtkCocoaRenderWindowInteractor.o > cd > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Rendering > && /usr/bin/c++ -DvtkRendering_EXPORTS -Wno-deprecated > -no-cpp-precomp -fPIC > -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Rendering > -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK > -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Hybrid > -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/IO > -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Imaging > -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Graphics > -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Filtering > -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Common > -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Common/Testing/Cxx > -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Utilities/zlib > -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Utilities/jpeg > -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Utilities/png > -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Utilities/tiff > -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Utilities/expat > -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Utilities/ > DICOMParser > -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Utilities/freetype/ > include > -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Utilities/freetype > -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Utilities/ftgl/src > -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Utilities/ftgl > -o CMakeFiles/vtkRendering.dir/vtkCocoaRenderWindowInteractor.o -c > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Rendering/ > vtkCocoaRenderWindowInteractor.mm > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Rendering/ > vtkCocoaGLView.h:11: > error: using typedef-name 'NSOpenGLPixelFormatAttribute' after 'enum' > /System/Library/Frameworks/AppKit.framework/Headers/NSOpenGL.h:90: > error: 'NSOpenGLPixelFormatAttribute' has a previous declaration here > make[2]: *** > [Rendering/CMakeFiles/vtkRendering.dir/ > vtkCocoaRenderWindowInteractor.o] > Error 1 > make[1]: *** [Rendering/CMakeFiles/vtkRendering.dir/all] Error 2 > make: *** [all] Error 2 > > Error: Status 1 encountered during processing. > > > ------------------------------ > > Message: 12 > Date: Fri, 20 Mar 2009 14:38:43 +0100 > From: Ceriel Jacobs > Subject: r48332 openssl command line configure.optflags=-fast doesn't > override (-O3) > To: macports-users at lists.macosforge.org > Message-ID: > Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes > > On Mon Feb 16 13:21:30 PST 2009 Marcus Calhoun-Lopez worte: >>> You could write a shell script which overrides the default values >>> >>> You can also edit the file >>> ${prefix}/share/macports/Tcl/port1.0/portconfigure.tcl >>> These two actions only set the default value. >>> A Portfile can override your value as well. > > On Mon Feb 16 17:01:33 PST 2009 Rainer M?ller wrote: >> No, command line options override values given in the Portfile. > > When setting portconfigure.tcl to default configure.optflags=-fast > openssl reverts the optflag back to -O3. > > When specifying one the command line, openssl still uses -O3. > > Besides the openssl port file [1] doesn't contain -O3 neither any text > containing the word flag. > [1] http://trac.macports.org/browser/trunk/dports/devel/openssl/Portfile > > Other port installs, like zlib, do honour the flag -fast. > > What am I missing that the command > $ sudo /opt/local/bin/port -d install openssl +universal > configure.optflags=-fast configure.march=nocona > still uses -O3 instead of the specified -fast as flag? > > Or should I file a ticket? Is this a bug submission or a feature > request? > > ~Ceriel > > Environment: universal=x86_64, compiler=gcc-4.2 > --- > DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/openssl > DEBUG: Changing to port directory: /opt/local/var/macports/sources/ > rsync.macports.org/release/ports/devel/openssl > DEBUG: OS Platform: darwin > DEBUG: OS Version: 9.6.0 > DEBUG: Mac OS X Version: 10.5 > DEBUG: System Arch: i386 > DEBUG: setting option os.universal_supported to yes > > CFLAG =-fPIC -fno-common -DOPENSSL_PIC -DZLIB - > DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -arch > x86_64 - > isysroot /Developer/SDKs/MacOSX10.5.sdk -O3 -fomit-frame-pointer - > DL_ENDIAN -DMD32_REG_T=int -Wall > > > > > ------------------------------ > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > > > End of macports-users Digest, Vol 31, Issue 20 > ********************************************** From roland at quadsys.com Fri Mar 20 15:03:33 2009 From: roland at quadsys.com (Roland Besserer) Date: Fri, 20 Mar 2009 15:03:33 -0700 Subject: Port confused after 10.4 to 10.5 upgrade Message-ID: <4C183B58-71E7-4110-BF61-9E6FEA49409C@quadsys.com> After upgrading from OSX 10.4 server to OSX 10.5 server and running a "port selfupdate" I can no longer install new packages. I had MacPorts 1.5 installed on 10.4 and upgraded to 10.5 (both server) a while back, but didn't touch MacPorts. Attempting to install a couple of additional packages yesterday, I got library version mismatch errors and decided to run a selfupdate. That successfully upgraded the port installation to 1.7 Whenever I try to install a package now, I get the following error: error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.5" but "10.4" during configure Any way to fix this? From frstan at bellsouth.net Fri Mar 20 15:42:43 2009 From: frstan at bellsouth.net (William Davis) Date: Fri, 20 Mar 2009 18:42:43 -0400 Subject: nss build error Message-ID: <333F98BD-35CA-4E48-AB1E-269891DD6B3A@bellsouth.net> trying to upgrade nss gave this build error: cc -dynamiclib -compatibility_version 1 -current_version 1 - install_name /opt/local/lib/libssl3.dylib -headerpad_max_install_names -L/opt/local/lib -o Darwin9.6.0_DBG.OBJ/libssl3.dylib Darwin9.6.0_DBG.OBJ/derive.o Darwin9.6.0_DBG.OBJ/prelib.o Darwin9.6.0_DBG.OBJ/ssl3con.o Darwin9.6.0_DBG.OBJ/ssl3gthr.o Darwin9.6.0_DBG.OBJ/sslauth.o Darwin9.6.0_DBG.OBJ/sslcon.o Darwin9.6.0_DBG.OBJ/ssldef.o Darwin9.6.0_DBG.OBJ/sslenum.o Darwin9.6.0_DBG.OBJ/sslerr.o Darwin9.6.0_DBG.OBJ/ssl3ext.o Darwin9.6.0_DBG.OBJ/sslgathr.o Darwin9.6.0_DBG.OBJ/sslmutex.o Darwin9.6.0_DBG.OBJ/sslnonce.o Darwin9.6.0_DBG.OBJ/sslreveal.o Darwin9.6.0_DBG.OBJ/sslsecur.o Darwin9.6.0_DBG.OBJ/sslsnce.o Darwin9.6.0_DBG.OBJ/sslsock.o Darwin9.6.0_DBG.OBJ/ssltrace.o Darwin9.6.0_DBG.OBJ/sslver.o Darwin9.6.0_DBG.OBJ/authcert.o Darwin9.6.0_DBG.OBJ/cmpcert.o Darwin9.6.0_DBG.OBJ/nsskea.o Darwin9.6.0_DBG.OBJ/sslinfo.o Darwin9.6.0_DBG.OBJ/ssl3ecc.o Darwin9.6.0_DBG.OBJ/unix_err.o ../../../../dist/Darwin9.6.0_DBG.OBJ/ lib/libfreebl.a -L../../../../dist/Darwin9.6.0_DBG.OBJ/lib -lnss3 - lnssutil3 -L../../../../dist/Darwin9.6.0_DBG.OBJ/lib -lplc4 -lplds4 - lnspr4 -dylib_file /opt/local/lib/libsoftokn3.dylib:../../../../dist/ Darwin9.6.0_DBG.OBJ/lib/libsoftokn3.dylib Undefined symbols: "_CERT_NewTempCertificate", referenced from: _ssl3_HandleCertificate in ssl3con.o _ssl3_HandleCertificate in ssl3con.o _ssl2_ClientHandleServerCert in sslcon.o _ssl2_HandleClientCertificate in sslcon.o _ssl3_ServerHandleSessionTicketXtn in ssl3ext.o _ConvertToSID in sslsnce.o ld: symbol(s) not found collect2: ld returned 1 exit status make[2]: *** [Darwin9.6.0_DBG.OBJ/libssl3.dylib] Error 1 make[1]: *** [libs] Error 2 make: *** [libs] Error 2 Warning: the following items did not execute (for nss): org.macports.destroot org.macports.build DEBUG: invalid command name "::ui_init" while executing "::ui_init $priority $prefix $channels $message" ("uplevel" body line 2) invoked from within "uplevel 1 $body" Error: Unable to upgrade port: 1 William Davis frstanATbellsouthDOTnet Mac OS X.5.6 Darwin 9.5.0 XQuartz 2.3.3_rc2 (xorg-server 1.4.2-apple37) Mac Mini Intel Duo @ 1.86 GHz Mundus vult decepi, ego non From d.l.tDeContes at free.fr Fri Mar 20 15:53:55 2009 From: d.l.tDeContes at free.fr (=?ISO-8859-1?Q?Thomas_De=A0Contes?=) Date: Fri, 20 Mar 2009 23:53:55 +0100 Subject: checking for gcc In-Reply-To: References: <675B1A6E-67F6-4E53-93B6-5C5EB56F7B07@free.fr> Message-ID: Le 16 mars 09 ? 00:05, Ryan Schmidt a ?crit : > On Mar 15, 2009, at 17:36, Thomas De Contes wrote: > >> i updade MacPorts, and at the step "port upgrade outdated" it >> always sets >> checking for gcc... /usr/bin/gcc-4.0 >> >> whereas /usr/bin/gcc-4.0 does not exist and /usr/bin/gcc points on >> gcc-3.3 >> >> >> what is the problem ? > > /usr/bin/gcc-4.0 should exist, and /usr/bin/gcc should point to it, > on Tiger and later. ok if /usr/bin/gcc-4.0 exists but /usr/bin/gcc does not point to it, it's not right ? > MacPorts will use /usr/bin/gcc-4.0 on Tiger and later, and /usr/bin/ > gcc-3.3 on Panther. ok > What OS version do you have? What version of Xcode? checking Mac OS X version... 10.4.11 checking Xcode version... 2.4.1 > Try reinstalling the latest version of Xcode for your OS. ok i would like to install as less as possible which part of xcode do you think is necessary, please ? :-) developer tools software ? gcc 4.0 ? software development kits ? btw, why does it work fine to build MacPorts itself, with gcc 3.3, and not to build software ? why does it say : checking for gcc... /usr/bin/gcc-4.0 checking for C compiler default output... configure: error: C compiler cannot create executables rather than sth like checking for gcc... /usr/bin/gcc-4.0 not found ? and why not searh for gcc-4.0 in $PATH ? -- T?l?assistance / T?l?maintenance http://www.portparallele.com/ThomasDECONTES/ From ryandesign at macports.org Fri Mar 20 16:52:24 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 20 Mar 2009 18:52:24 -0500 Subject: checking for gcc In-Reply-To: References: <675B1A6E-67F6-4E53-93B6-5C5EB56F7B07@free.fr> Message-ID: <5BCA1EB2-FEC2-4296-A8F9-0A92330D006F@macports.org> On Mar 20, 2009, at 17:53, Thomas De Contes wrote: > Le 16 mars 09 ? 00:05, Ryan Schmidt a ?crit : > >> On Mar 15, 2009, at 17:36, Thomas De Contes wrote: >> >>> i updade MacPorts, and at the step "port upgrade outdated" it >>> always sets >>> checking for gcc... /usr/bin/gcc-4.0 >>> >>> whereas /usr/bin/gcc-4.0 does not exist and /usr/bin/gcc points >>> on gcc-3.3 >>> >>> >>> what is the problem ? >> >> /usr/bin/gcc-4.0 should exist, and /usr/bin/gcc should point to >> it, on Tiger and later. > > ok > if /usr/bin/gcc-4.0 exists but /usr/bin/gcc does not point to it, > it's not right ? If /usr/bin/gcc-4.0 exists but /usr/bin/gcc points to gcc-3.3 then you have most likely used the gcc_select program to select gcc 3.3. This should not affect the majority of ports since MacPorts tells ports to use /usr/bin/gcc-4.0 by default on Tiger and later. Specific ports may override this as needed. For example some very old software must compile with gcc-3.3 because gcc-4.0 is too new; in this case, those ports indicate this requirement and MacPorts allows them to use gcc-3.3 instead. Some ports do not pay attention to the compiler MacPorts tells them to use, and they instead use just "cc" or "gcc" in which case they will use whatever you have gcc_select'ed, so gcc_select'ing something other than the default gcc-4.0 can still cause problems. But it is a bug for ports to use "cc" or "gcc" instead of what MacPorts tells them to use, and if you find a port that does this, you should file a bug against that port. Because you are getting the message checking for gcc... /usr/bin/gcc-4.0 checking for C compiler default output... configure: error: C compiler cannot create executables I believe /usr/bin/gcc-4.0 either does not exist on your system or it is broken in some way (perhaps some of its support files are missing). >> MacPorts will use /usr/bin/gcc-4.0 on Tiger and later, and /usr/ >> bin/gcc-3.3 on Panther. > > ok > >> What OS version do you have? What version of Xcode? > > checking Mac OS X version... 10.4.11 > checking Xcode version... 2.4.1 Xcode 2.4.1 is probably fine on Tiger. 2.5 is the latest available but I used 2.4.1 for a long time and it works fine. And it certainly should provide /usr/bin/gcc-4.0. >> Try reinstalling the latest version of Xcode for your OS. > > ok > > i would like to install as less as possible > which part of xcode do you think is necessary, please ? :-) > > developer tools software ? > gcc 4.0 ? > software development kits ? I don't know specifically what component of Xcode provides gcc-4.0 but if it's missing on your system, then reinstall (all of) Xcode 2.4.1 or 2.5. > btw, > > why does it work fine to build MacPorts itself, with gcc 3.3, and > not to build software ? Port authors have limited resources with which to test ports. Usually people only have a single Mac, running either Leopard or Tiger, with either an Intel or PowerPC processor. This means most port authors are only testing on 1/4 of the supported systems. Problems can crop up on the remaining 3/4 of the supported systems the author did not test on. We do not want to increase the testing burden even further by allowing users to compile ports with a different compiler than the one the port author tested with. For this reason, MacPorts instructs ports to ignore what the user has gcc_selected'ed and instead to use a specific compiler on specific OS versions (3.3 on Panther, 4.0 on Tiger and Leopard). Individual ports can override this if it's necessary for those ports, but users are not supposed to override this. > why does it say : > checking for gcc... /usr/bin/gcc-4.0 > checking for C compiler default output... configure: error: C > compiler cannot create executables > rather than sth like > checking for gcc... /usr/bin/gcc-4.0 not found > ? > and why not searh for gcc-4.0 in $PATH ? Here you are asking about the configure script of the port you were trying to install. For questions about why that configure script does what it does, you'll have to ask the authors of that software, or probably the authors of autotools, since this looks like the output from a standard autotools-generated configure script. But as I understand it, "checking for gcc" does not mean "checking where on your system gcc is located". Instead, it means "checking if you have asked me to use a specific gcc" and the answer is "you have asked me to use /usr/bin/gcc-4.0" which is correct. The fact that / usr/bin/gcc-4.0 doesn't actually exist on your system is a problem on your system. As explained above, it is not desired in MacPorts to search for the compiler anywhere. It is desired to use a very specific compiler which is always located at a specific path (which may vary from port to port and OS to OS, but not from user to user). From ryandesign at macports.org Fri Mar 20 16:57:18 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 20 Mar 2009 18:57:18 -0500 Subject: Port confused after 10.4 to 10.5 upgrade In-Reply-To: <4C183B58-71E7-4110-BF61-9E6FEA49409C@quadsys.com> References: <4C183B58-71E7-4110-BF61-9E6FEA49409C@quadsys.com> Message-ID: <9725D63C-5A00-404F-AA6A-F3D6F7F3683D@macports.org> On Mar 20, 2009, at 17:03, Roland Besserer wrote: > After upgrading from OSX 10.4 server to OSX 10.5 server and running > a "port selfupdate" I can no longer install new packages. Many ports in MacPorts build differently depending on the major version of Mac OS X. So after upgrading to a new major version of Mac OS X you should rebuild all ports. Only you have to do that in dependency order. MacPorts doesn't include an automated way to do this. My recommendation is to move /opt/local aside (rename it to / opt/local-10.4 for example) and then reinstall the latest MacPorts and the ports you need. You may also have data and configuration files in /opt/local-10.4 you may need to move over to /opt/local. > I had MacPorts 1.5 installed on 10.4 and upgraded to 10.5 (both > server) a while back, but didn't touch MacPorts. Attempting to > install a couple of additional packages yesterday, I got library > version mismatch errors and decided to run a selfupdate. That > successfully upgraded the port installation to 1.7 > > Whenever I try to install a package now, I get the following error: > > error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.5" but "10.4" > during configure > > Any way to fix this? That sounds like you partially installed a port (i.e. got through the configure phase at least) while you were running Mac OS X 10.4 and are now trying to complete that installation with Mac OS X 10.5. Removing all of MacPorts as above will coincidentally fix this. Or you can try "sudo port clean"ing whatever port it is you're getting this error on, so that it will start over and run the configure phase again. From ryandesign at macports.org Fri Mar 20 17:00:35 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 20 Mar 2009 19:00:35 -0500 Subject: Incorrect libjpeg.dylib after installing ImageMagick In-Reply-To: <3BF90774-22DD-401B-8FE7-7864CB698D7A@atmo.arizona.edu> References: <52498.65.113.40.1.1237572545.squirrel@calmail.berkeley.edu> <3BF90774-22DD-401B-8FE7-7864CB698D7A@atmo.arizona.edu> Message-ID: <9D1705FA-9298-46A9-B967-7CCC70029516@macports.org> On Mar 20, 2009, at 13:20, Yolande Serra wrote: > Not sure this will help, but if you defined a DYLD_LIBRARY_PATH in > your .bashrc or .profile get rid of it. > > The libraries that macs point to are found assuming this variable > is not defined. Somewhere buried in the system it has a path to > its own libs. You mess this up when you define dynamic library paths. I agree with Yolande: it sounds like you have DYLD_LIBRARY_PATH set, and you should not. > On Mar 20, 2009, at 11:09 AM, esiegel at berkeley.edu wrote: > >> I have been trying to solve this problems for several hours now >> with many >> failed attempts. I found some answers from before, but they don't >> seem to >> work with me. >> >> Basically, after installing ImageMagick with macports, libjpeg was >> installed to /opt/local/lib/libjpeg.dylib, but now several >> executables >> (unrelated to Imagemagick) now point to this library instead of >> the OS X >> default. >> >> For example mate, php, and others all report this error message: >> >> dyld: Symbol not found: __cg_jpeg_resync_to_restart >> Referenced from: >> /System/Library/Frameworks/ApplicationServices.framework/Versions/ >> A/Frameworks/ImageIO.framework/Versions/A/ImageIO >> Expected in: /opt/local/lib/libJPEG.dylib Curious capitalization: The MacPorts jpeg port provides libjpeg.dylib, not libJPEG.dylib. >> From a previous post, it was suggested that I copy the library from >> ImageIO folder into the opt/local folder, but this caused library >> incompatibility problems. Yes, please do not copy libraries into /opt/local manually. >> I have tried uninstalling ImageMagick, but it didn't help. I wouldn't expect that to help, since ImageMagick has nothing to do with libjpeg.dylib, other than using it. The port that actually provides libjpeg.dylib is jpeg, so you could uninstall the jpeg port. Of course then you can't use any ports like ImageMagick that require libjpeg.dylib. >> I have tried searching for every symbolic link hoping that I could >> change >> something to point back to the original library. >> >> I have looked at my .profile .bashrc, etc to see if there was >> anything >> that should be changed, but so far no go. From ryandesign at macports.org Fri Mar 20 17:05:42 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 20 Mar 2009 19:05:42 -0500 Subject: Re-do MacPorts after upgrading from Tiger to Leopard on PPC? In-Reply-To: <80D53A20-2D9E-4147-A154-9A4EE24850EC@qwest.net> References: <95D3529F-FC9B-42F2-BDDD-70D90CE40692@qwest.net> <20090313054340.GN836@ninagal.withay.com> <3C38030F-4812-4129-818A-FC2BD6CA31B8@pixilla.com> <49BA7F67.9030904@macports.org> <538D04B3-AF0B-49D1-A90F-4E15862EACBE@macports.org> <49BF5DE4.3040703@macports.org> <80D53A20-2D9E-4147-A154-9A4EE24850EC@qwest.net> Message-ID: <667ED090-E628-459D-B5D6-09EE82E271C5@macports.org> On Mar 17, 2009, at 22:29, Jerry wrote: > I'm not being ungrateful because believe me, I'm just the opposite. > However, I would like to offer a bit of feedback. My experience > with MacPorts has been pretty bad. If I had really _needed_ any of > the software that I tried to install, as opposed to just evaluating > it, I would have been pretty hosed, I'm afraid. I mostly appreciate > the ambitious goal of MacPorts and I might try again later, but not > soon. As I recall, I was mainly interested in wxMaxima (a symbolic > math program), gcc with Ada (GNAT), and LyX (a technical word > processor). I never succeeded in installing any of these from > MacPorts. I'm sorry to hear you were unable to install these ports. If in the future you wish to try again and you run into problems, please do report the specific details of the failures to us either here on the list or in the issue tracker so that someone can look into it. From blb at macports.org Fri Mar 20 17:20:36 2009 From: blb at macports.org (Bryan Blackburn) Date: Fri, 20 Mar 2009 18:20:36 -0600 Subject: Incorrect libjpeg.dylib after installing ImageMagick In-Reply-To: <9D1705FA-9298-46A9-B967-7CCC70029516@macports.org> References: <52498.65.113.40.1.1237572545.squirrel@calmail.berkeley.edu> <3BF90774-22DD-401B-8FE7-7864CB698D7A@atmo.arizona.edu> <9D1705FA-9298-46A9-B967-7CCC70029516@macports.org> Message-ID: <20090321002036.GF805@ninagal.withay.com> On Fri, Mar 20, 2009 at 07:00:35PM -0500, Ryan Schmidt said: [...] >>> For example mate, php, and others all report this error message: >>> >>> dyld: Symbol not found: __cg_jpeg_resync_to_restart >>> Referenced from: >>> /System/Library/Frameworks/ApplicationServices.framework/Versions/ >>> A/Frameworks/ImageIO.framework/Versions/A/ImageIO >>> Expected in: /opt/local/lib/libJPEG.dylib > > Curious capitalization: The MacPorts jpeg port provides libjpeg.dylib, not > libJPEG.dylib. Probably because ImageIO links to libJPEG.dylib and that plus case-preserving but case-insensitive makes it see them as the same library (when DYLD env vars are messed with)... $ otool -L /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ImageIO.framework/ImageIO ... /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib (compatibility version 1.0.0, current version 1.0.0) ... Bryan [...] From ryandesign at macports.org Fri Mar 20 21:17:54 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 20 Mar 2009 23:17:54 -0500 Subject: nss build error In-Reply-To: <333F98BD-35CA-4E48-AB1E-269891DD6B3A@bellsouth.net> References: <333F98BD-35CA-4E48-AB1E-269891DD6B3A@bellsouth.net> Message-ID: <003AB4E6-8D67-4BCC-B35F-CB1F0250BAC9@macports.org> On Mar 20, 2009, at 17:42, William Davis wrote: > trying to upgrade nss gave this build error: > > cc -dynamiclib -compatibility_version 1 -current_version 1 - > install_name /opt/local/lib/libssl3.dylib - > headerpad_max_install_names -L/opt/local/lib -o > Darwin9.6.0_DBG.OBJ/libssl3.dylib Darwin9.6.0_DBG.OBJ/derive.o > Darwin9.6.0_DBG.OBJ/prelib.o Darwin9.6.0_DBG.OBJ/ssl3con.o > Darwin9.6.0_DBG.OBJ/ssl3gthr.o Darwin9.6.0_DBG.OBJ/sslauth.o > Darwin9.6.0_DBG.OBJ/sslcon.o Darwin9.6.0_DBG.OBJ/ssldef.o > Darwin9.6.0_DBG.OBJ/sslenum.o Darwin9.6.0_DBG.OBJ/sslerr.o > Darwin9.6.0_DBG.OBJ/ssl3ext.o Darwin9.6.0_DBG.OBJ/sslgathr.o > Darwin9.6.0_DBG.OBJ/sslmutex.o Darwin9.6.0_DBG.OBJ/sslnonce.o > Darwin9.6.0_DBG.OBJ/sslreveal.o Darwin9.6.0_DBG.OBJ/sslsecur.o > Darwin9.6.0_DBG.OBJ/sslsnce.o Darwin9.6.0_DBG.OBJ/sslsock.o > Darwin9.6.0_DBG.OBJ/ssltrace.o Darwin9.6.0_DBG.OBJ/sslver.o > Darwin9.6.0_DBG.OBJ/authcert.o Darwin9.6.0_DBG.OBJ/cmpcert.o > Darwin9.6.0_DBG.OBJ/nsskea.o Darwin9.6.0_DBG.OBJ/sslinfo.o > Darwin9.6.0_DBG.OBJ/ssl3ecc.o Darwin9.6.0_DBG.OBJ/ > unix_err.o ../../../../dist/Darwin9.6.0_DBG.OBJ/lib/libfreebl.a - > L../../../../dist/Darwin9.6.0_DBG.OBJ/lib -lnss3 -lnssutil3 - > L../../../../dist/Darwin9.6.0_DBG.OBJ/lib -lplc4 -lplds4 -lnspr4 - > dylib_file /opt/local/lib/libsoftokn3.dylib:../../../../dist/ > Darwin9.6.0_DBG.OBJ/lib/libsoftokn3.dylib > Undefined symbols: > "_CERT_NewTempCertificate", referenced from: > _ssl3_HandleCertificate in ssl3con.o > _ssl3_HandleCertificate in ssl3con.o > _ssl2_ClientHandleServerCert in sslcon.o > _ssl2_HandleClientCertificate in sslcon.o > _ssl3_ServerHandleSessionTicketXtn in ssl3ext.o > _ConvertToSID in sslsnce.o > ld: symbol(s) not found > collect2: ld returned 1 exit status > make[2]: *** [Darwin9.6.0_DBG.OBJ/libssl3.dylib] Error 1 > make[1]: *** [libs] Error 2 > make: *** [libs] Error 2 I see the same thing, on Mac OS X 10.5.6 Intel with Xcode 3.1.2 (iPhone SDK 2.2.1), if the previous version of the port is active. I was able to work around it by deactivating the old version first. You could file this as a bug in the issue tracker. From ryandesign at macports.org Sat Mar 21 02:37:59 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 21 Mar 2009 04:37:59 -0500 Subject: Problem installing vtk In-Reply-To: <49C38BD3.4070309@gmail.com> References: <49C38BD3.4070309@gmail.com> Message-ID: <3F6709DF-3F85-4F80-BF08-442C9FD0A365@macports.org> On Mar 20, 2009, at 07:28, David Trem wrote: > May somebody help ? > I have a problem installing vtk on MacBook OS X 10.5.6, using > macports 1.700 (fresh install). > See console output below. I get the same error on a MacBook Pro with 10.5.6, Xcode 3.1.2, MacPorts 1.7. Do you specifically need version 4 of vtk? If not, try the port vtk5, which provides version 5 of vtk. Still, VTK was just updated to 4.4.2 http://trac.macports.org/ticket/18696 so it is expected to build correctly somewhere. Please file a bug report for the problem you encountered. > Thanks in advance, > > David > > ---> Building VTK > Error: Target org.macports.build returned: shell command " cd "/opt/ > local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK" && make all " returned error 2 > Command output: [ 62%] Built target vtkexpat > make -f IO/CMakeFiles/vtkIO.dir/build.make IO/CMakeFiles/vtkIO.dir/ > depend > cd /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK && /opt/local/bin/cmake -E cmake_depends "Unix > Makefiles" /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/IO /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/IO /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/IO/CMakeFiles/vtkIO.dir/DependInfo.cmake --color= > make -f IO/CMakeFiles/vtkIO.dir/build.make IO/CMakeFiles/vtkIO.dir/ > build > make[2]: Nothing to be done for `IO/CMakeFiles/vtkIO.dir/build'. > /opt/local/bin/cmake -E cmake_progress_report /opt/local/var/ > macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/CMakeFiles 51 52 53 54 55 56 57 58 59 60 61 62 > [ 74%] Built target vtkIO > make -f Utilities/freetype/CMakeFiles/vtkfreetype.dir/build.make > Utilities/freetype/CMakeFiles/vtkfreetype.dir/depend > cd /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK && /opt/local/bin/cmake -E cmake_depends "Unix > Makefiles" /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Utilities/freetype /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Utilities/freetype /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Utilities/freetype/CMakeFiles/vtkfreetype.dir/ > DependInfo.cmake --color= > make -f Utilities/freetype/CMakeFiles/vtkfreetype.dir/build.make > Utilities/freetype/CMakeFiles/vtkfreetype.dir/build > make[2]: Nothing to be done for `Utilities/freetype/CMakeFiles/ > vtkfreetype.dir/build'. > /opt/local/bin/cmake -E cmake_progress_report /opt/local/var/ > macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/CMakeFiles 92 93 94 > [ 77%] Built target vtkfreetype > make -f Utilities/ftgl/CMakeFiles/vtkftgl.dir/build.make Utilities/ > ftgl/CMakeFiles/vtkftgl.dir/depend > cd /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK && /opt/local/bin/cmake -E cmake_depends "Unix > Makefiles" /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Utilities/ftgl /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Utilities/ftgl /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Utilities/ftgl/CMakeFiles/vtkftgl.dir/ > DependInfo.cmake --color= > make -f Utilities/ftgl/CMakeFiles/vtkftgl.dir/build.make Utilities/ > ftgl/CMakeFiles/vtkftgl.dir/build > make[2]: Nothing to be done for `Utilities/ftgl/CMakeFiles/ > vtkftgl.dir/build'. > /opt/local/bin/cmake -E cmake_progress_report /opt/local/var/ > macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/CMakeFiles 95 > [ 78%] Built target vtkftgl > make -f Rendering/CMakeFiles/vtkRendering.dir/build.make Rendering/ > CMakeFiles/vtkRendering.dir/depend > cd /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK && /opt/local/bin/cmake -E cmake_depends "Unix > Makefiles" /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Rendering /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Rendering /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Rendering/CMakeFiles/vtkRendering.dir/ > DependInfo.cmake --color= > make -f Rendering/CMakeFiles/vtkRendering.dir/build.make Rendering/ > CMakeFiles/vtkRendering.dir/build > /opt/local/bin/cmake -E cmake_progress_report /opt/local/var/ > macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/CMakeFiles > [ 78%] Building CXX object Rendering/CMakeFiles/vtkRendering.dir/ > vtkCocoaRenderWindowInteractor.o > cd /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Rendering && /usr/bin/c++ - > DvtkRendering_EXPORTS -Wno-deprecated -no-cpp-precomp -fPIC -I/ > opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Rendering -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Hybrid -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/IO -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Imaging -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Graphics -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Filtering -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Common -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Common/Testing/Cxx -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Utilities/zlib -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Utilities/jpeg -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Utilities/png -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Utilities/tiff -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Utilities/expat -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Utilities/DICOMParser -I/opt/local/var/macports/ > build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Utilities/freetype/include -I/opt/local/var/ > macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Utilities/freetype -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Utilities/ftgl/src -I/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Utilities/ftgl -o CMakeFiles/vtkRendering.dir/ > vtkCocoaRenderWindowInteractor.o -c /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Rendering/vtkCocoaRenderWindowInteractor.mm > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_graph > ics_vtk/work/VTK/Rendering/vtkCocoaGLView.h:11: error: using > typedef-name 'NSOpenGLPixelFormatAttribute' after 'enum' > /System/Library/Frameworks/AppKit.framework/Headers/NSOpenGL.h:90: > error: 'NSOpenGLPixelFormatAttribute' has a previous declaration here > make[2]: *** [Rendering/CMakeFiles/vtkRendering.dir/ > vtkCocoaRenderWindowInteractor.o] Error 1 > make[1]: *** [Rendering/CMakeFiles/vtkRendering.dir/all] Error 2 > make: *** [all] Error 2 > > Error: Status 1 encountered during processing. From admin2 at enabled.com Sat Mar 21 08:43:02 2009 From: admin2 at enabled.com (Noah) Date: Sat, 21 Mar 2009 08:43:02 -0700 Subject: freetype build failing Message-ID: <49C50B06.6090206@enabled.com> Hi there, Any clues why freetype is failing to build. Help please. 6 apps including xorg-libXfont depend on it. Thanks in advance, Noah ---> Building freetype Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_print_freetype/work/freetype-2.3.9" && make all " returned error 2 Command output: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_print_freetype/work/freetype-2.3.9/include/freetype/internal/ftstream.h:488: error: syntax error before 'FT_Stream_ReadFields' /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_print_freetype/work/freetype-2.3.9/include/freetype/internal/ftstream.h:490: warning: data definition has no type or storage class builds/unix/ftsystem.c:97: error: syntax error before 'ft_alloc' builds/unix/ftsystem.c: In function 'ft_alloc': builds/unix/ftsystem.c:102: warning: return makes integer from pointer without a cast builds/unix/ftsystem.c: At top level: builds/unix/ftsystem.c:127: error: syntax error before 'ft_realloc' builds/unix/ftsystem.c: In function 'ft_realloc': builds/unix/ftsystem.c:135: warning: return makes integer from pointer without a cast builds/unix/ftsystem.c: At top level: builds/unix/ftsystem.c:153: error: syntax error before 'ft_free' builds/unix/ftsystem.c:195: error: syntax error before 'ft_close_stream_by_munmap' builds/unix/ftsystem.c:217: error: syntax error before 'ft_close_stream_by_free' builds/unix/ftsystem.c:230: error: syntax error before 'FT_Stream_Open' builds/unix/ftsystem.c: In function 'FT_Stream_Open': builds/unix/ftsystem.c:278: error: 'LONG_MAX' undeclared (first use in this function) builds/unix/ftsystem.c:278: error: (Each undeclared identifier is reported only once builds/unix/ftsystem.c:278: error: for each function it appears in.) builds/unix/ftsystem.c:301: warning: assignment from incompatible pointer type builds/unix/ftsystem.c:342: warning: assignment from incompatible pointer type builds/unix/ftsystem.c: At top level: builds/unix/ftsystem.c:386: error: syntax error before 'FT_New_Memory' builds/unix/ftsystem.c: In function 'FT_New_Memory': builds/unix/ftsystem.c:395: warning: assignment from incompatible pointer type builds/unix/ftsystem.c:396: warning: assignment from incompatible pointer type builds/unix/ftsystem.c:397: warning: assignment from incompatible pointer type builds/unix/ftsystem.c:403: warning: return makes integer from pointer without a cast builds/unix/ftsystem.c: At top level: builds/unix/ftsystem.c:410: error: syntax error before 'FT_Done_Memory' make: *** [/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_print_freetype/work/freetype-2.3.9/objs/ftsystem.lo] Error 1 Error: Unable to upgrade port: 1 ---> Verifying checksum(s) for libxml2 Error: Checksum (md5) mismatch for libxml2-2.7.3.tar.gz Error: Checksum (sha1) mismatch for libxml2-2.7.3.tar.gz Error: Checksum (rmd160) mismatch for libxml2-2.7.3.tar.gz Error: Target org.macports.checksum returned: Unable to verify file checksums Error: Unable to upgrade port: 1 ---> Extracting tiff On Mac OS X 10.5, tiff 3.8.2 requires Xcode 3.1 or later but you have Xcode 3.0. Error: Target org.macports.extract returned: incompatible Xcode version Error: Unable to upgrade port: 1 sh-3.2# port uninstall freetype ---> Unable to uninstall freetype 2.3.7_3+macosx, the following ports depend on it: ---> fontconfig ---> gd2 ---> cairo ---> Xft2 ---> gtk2 ---> xorg-libXfont Error: port uninstall failed: Please uninstall the ports that depend on freetype first. From frstan at bellsouth.net Sat Mar 21 09:17:39 2009 From: frstan at bellsouth.net (William Davis) Date: Sat, 21 Mar 2009 12:17:39 -0400 Subject: freetype build failing In-Reply-To: <49C50B06.6090206@enabled.com> References: <49C50B06.6090206@enabled.com> Message-ID: <13695C1A-D90F-4D52-89E4-D7C3B5CDA5C9@bellsouth.net> On Mar 21, 2009, at 11:43 AM, Noah wrote: > Hi there, > > Any clues why freetype is failing to build. Help please. 6 apps > including xorg-libXfont depend on it. > > Thanks in advance, > > Noah > > > > ---> Building freetype > Error: Target org.macports.build returned: shell command " cd "/opt/ > local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_print_freetype/work/freetype-2.3.9" && > make all " returned error 2 > Command output: /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_print_freetype/work/freetype-2.3.9/ > include/freetype/internal/ftstream.h:488: error: syntax error before > 'FT_Stream_ReadFields' > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_print_freetype/work/freetype-2.3.9/ > include/freetype/internal/ftstream.h:490: warning: data definition > has no type or storage class > builds/unix/ftsystem.c:97: error: syntax error before 'ft_alloc' > builds/unix/ftsystem.c: In function 'ft_alloc': > builds/unix/ftsystem.c:102: warning: return makes integer from > pointer without a cast > builds/unix/ftsystem.c: At top level: > builds/unix/ftsystem.c:127: error: syntax error before 'ft_realloc' > builds/unix/ftsystem.c: In function 'ft_realloc': > builds/unix/ftsystem.c:135: warning: return makes integer from > pointer without a cast > builds/unix/ftsystem.c: At top level: > builds/unix/ftsystem.c:153: error: syntax error before 'ft_free' > builds/unix/ftsystem.c:195: error: syntax error before > 'ft_close_stream_by_munmap' > builds/unix/ftsystem.c:217: error: syntax error before > 'ft_close_stream_by_free' > builds/unix/ftsystem.c:230: error: syntax error before > 'FT_Stream_Open' > builds/unix/ftsystem.c: In function 'FT_Stream_Open': > builds/unix/ftsystem.c:278: error: 'LONG_MAX' undeclared (first use > in this function) > builds/unix/ftsystem.c:278: error: (Each undeclared identifier is > reported only once > builds/unix/ftsystem.c:278: error: for each function it appears in.) > builds/unix/ftsystem.c:301: warning: assignment from incompatible > pointer type > builds/unix/ftsystem.c:342: warning: assignment from incompatible > pointer type > builds/unix/ftsystem.c: At top level: > builds/unix/ftsystem.c:386: error: syntax error before 'FT_New_Memory' > builds/unix/ftsystem.c: In function 'FT_New_Memory': > builds/unix/ftsystem.c:395: warning: assignment from incompatible > pointer type > builds/unix/ftsystem.c:396: warning: assignment from incompatible > pointer type > builds/unix/ftsystem.c:397: warning: assignment from incompatible > pointer type > builds/unix/ftsystem.c:403: warning: return makes integer from > pointer without a cast > builds/unix/ftsystem.c: At top level: > builds/unix/ftsystem.c:410: error: syntax error before > 'FT_Done_Memory' > make: *** [/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_print_freetype/work/freetype-2.3.9/objs/ > ftsystem.lo] Error 1 > > Error: Unable to upgrade port: 1 > ---> Verifying checksum(s) for libxml2 > Error: Checksum (md5) mismatch for libxml2-2.7.3.tar.gz > Error: Checksum (sha1) mismatch for libxml2-2.7.3.tar.gz > Error: Checksum (rmd160) mismatch for libxml2-2.7.3.tar.gz > Error: Target org.macports.checksum returned: Unable to verify file > checksums > Error: Unable to upgrade port: 1 > ---> Extracting tiff > On Mac OS X 10.5, tiff 3.8.2 requires Xcode 3.1 or later but you > have Xcode 3.0. > Error: Target org.macports.extract returned: incompatible Xcode > version > Error: Unable to upgrade port: 1 > > sh-3.2# port uninstall freetype > ---> Unable to uninstall freetype 2.3.7_3+macosx, the following > ports depend on it: > ---> fontconfig > ---> gd2 > ---> cairo > ---> Xft2 > ---> gtk2 > ---> xorg-libXfont > Error: port uninstall failed: Please uninstall the ports that depend > on freetype first. > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users 1. Your XCode is out of date. You are 3.0 but current is 3.1.2. Download this from ADC. 2. Is your Macports uptodate? sudo port -d selfupdate. 3. on libxml2 you may have a bad download. DO: sudo port -d clean --all libxml2 Try this (in that order) and see how much of your problems that fixes. If you still need help be sure you give your OS and cpu type when you wrote back. It helps troubleshoot. good luck William Davis frstanATbellsouthDOTnet Mac OS X.5.6 Darwin 9.5.0 XQuartz 2.3.3_rc2 (xorg-server 1.4.2-apple37) Mac Mini Intel Duo @ 1.86 GHz Mundus vult decepi, ego non From jeremyhu at macports.org Sat Mar 21 11:04:37 2009 From: jeremyhu at macports.org (Jeremy Huddleston) Date: Sat, 21 Mar 2009 11:04:37 -0700 Subject: freetype build failing In-Reply-To: <49C50B06.6090206@enabled.com> References: <49C50B06.6090206@enabled.com> Message-ID: On Mar 21, 2009, at 08:43, Noah wrote: > Hi there, > > Any clues why freetype is failing to build. Help please. 6 apps > including xorg-libXfont depend on it. Can you try rebuilding with '-v' and report the errors above the 'Command outut:' line (including the last invocation of gcc that caused the errors)? > Thanks in advance, > > Noah > > > > ---> Building freetype > Error: Target org.macports.build returned: shell command " cd "/opt/ > local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_print_freetype/work/freetype-2.3.9" && > make all " returned error 2 > Command output: /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_print_freetype/work/freetype-2.3.9/ > include/freetype/internal/ftstream.h:488: error: syntax error before > 'FT_Stream_ReadFields' > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_print_freetype/work/freetype-2.3.9/ > include/freetype/internal/ftstream.h:490: warning: data definition > has no type or storage class > builds/unix/ftsystem.c:97: error: syntax error before 'ft_alloc' > builds/unix/ftsystem.c: In function 'ft_alloc': > builds/unix/ftsystem.c:102: warning: return makes integer from > pointer without a cast > builds/unix/ftsystem.c: At top level: > builds/unix/ftsystem.c:127: error: syntax error before 'ft_realloc' > builds/unix/ftsystem.c: In function 'ft_realloc': > builds/unix/ftsystem.c:135: warning: return makes integer from > pointer without a cast > builds/unix/ftsystem.c: At top level: > builds/unix/ftsystem.c:153: error: syntax error before 'ft_free' > builds/unix/ftsystem.c:195: error: syntax error before > 'ft_close_stream_by_munmap' > builds/unix/ftsystem.c:217: error: syntax error before > 'ft_close_stream_by_free' > builds/unix/ftsystem.c:230: error: syntax error before > 'FT_Stream_Open' > builds/unix/ftsystem.c: In function 'FT_Stream_Open': > builds/unix/ftsystem.c:278: error: 'LONG_MAX' undeclared (first use > in this function) > builds/unix/ftsystem.c:278: error: (Each undeclared identifier is > reported only once > builds/unix/ftsystem.c:278: error: for each function it appears in.) > builds/unix/ftsystem.c:301: warning: assignment from incompatible > pointer type > builds/unix/ftsystem.c:342: warning: assignment from incompatible > pointer type > builds/unix/ftsystem.c: At top level: > builds/unix/ftsystem.c:386: error: syntax error before 'FT_New_Memory' > builds/unix/ftsystem.c: In function 'FT_New_Memory': > builds/unix/ftsystem.c:395: warning: assignment from incompatible > pointer type > builds/unix/ftsystem.c:396: warning: assignment from incompatible > pointer type > builds/unix/ftsystem.c:397: warning: assignment from incompatible > pointer type > builds/unix/ftsystem.c:403: warning: return makes integer from > pointer without a cast > builds/unix/ftsystem.c: At top level: > builds/unix/ftsystem.c:410: error: syntax error before > 'FT_Done_Memory' > make: *** [/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_print_freetype/work/freetype-2.3.9/objs/ > ftsystem.lo] Error 1 > > Error: Unable to upgrade port: 1 > ---> Verifying checksum(s) for libxml2 > Error: Checksum (md5) mismatch for libxml2-2.7.3.tar.gz > Error: Checksum (sha1) mismatch for libxml2-2.7.3.tar.gz > Error: Checksum (rmd160) mismatch for libxml2-2.7.3.tar.gz > Error: Target org.macports.checksum returned: Unable to verify file > checksums > Error: Unable to upgrade port: 1 > ---> Extracting tiff > On Mac OS X 10.5, tiff 3.8.2 requires Xcode 3.1 or later but you > have Xcode 3.0. > Error: Target org.macports.extract returned: incompatible Xcode > version > Error: Unable to upgrade port: 1 > > sh-3.2# port uninstall freetype > ---> Unable to uninstall freetype 2.3.7_3+macosx, the following > ports depend on it: > ---> fontconfig > ---> gd2 > ---> cairo > ---> Xft2 > ---> gtk2 > ---> xorg-libXfont > Error: port uninstall failed: Please uninstall the ports that depend > on freetype first. > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From rps at salas.com Sat Mar 21 12:38:37 2009 From: rps at salas.com (R. Pito Salas) Date: Sat, 21 Mar 2009 15:38:37 -0400 Subject: Python, Tcl, Tix ... Message-ID: Hi, I am trying to get an application running which is in Python, and in turn invokes Tcl to use Tix. I've been struggling with path problems and am totally stuck. I admit that I don't know Python, nor Tcl nor Tix. But I am pretty good at following the patterns. I think that what's happening is that there are several versions of Tcl and Python on my machine, and the wrong one is getting invoked. Here are some details: Here's the command that gives an error: /mydev/politics/bb51$ python BBrowser.py Traceback (most recent call last): File "BBrowser.py", line 1456, in root = Tix.Tk() File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/ lib/python2.5/lib-tk/Tix.py", line 210, in __init__ self.tk.eval('package require Tix') _tkinter.TclError: can't find package Tix Here's the version of python that I am using: /mydev/politics/bb51$ which python /opt/local/bin/python From the command line here's the version of Tclsh that I get: /mydev/politics/bb51$ which tclsh /opt/local/bin/tclsh If I run a different version of Tcl then Tix does work: /usr/bin/tclsh % package require Tix It seems like I have Tix installed in the 'wrong' copy of Tcl. QUESTION: The most logical thing would be to install Tix with MacPorts, so that, in theory all will be tied together, but I don't think there's a MacPorts Tix Port, is there? Any assistance would be greatly appreciated! Pito From ryandesign at macports.org Sat Mar 21 15:40:13 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 21 Mar 2009 17:40:13 -0500 Subject: freetype build failing In-Reply-To: <49C50B06.6090206@enabled.com> References: <49C50B06.6090206@enabled.com> Message-ID: <144281DE-6876-4E59-8F6E-2D463C279A2D@macports.org> On Mar 21, 2009, at 10:43, Noah wrote: > Any clues why freetype is failing to build. You already asked this question on March 12 and I provided this answer: http://lists.macosforge.org/pipermail/macports-users/2009-March/ 014311.html In short, I have no idea and I need more information from you. In today's email you provided the additional information that you have Xcode 3.0. Please let me know if upgrading to Xcode 3.1.2 fixes the problem; if so, I can add a warning to the port. From ryandesign at macports.org Sat Mar 21 15:43:31 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 21 Mar 2009 17:43:31 -0500 Subject: Python, Tcl, Tix ... In-Reply-To: References: Message-ID: <96081377-E75A-427D-A9CD-02D8A5CD32A7@macports.org> On Mar 21, 2009, at 14:38, R. Pito Salas wrote: > I am trying to get an application running which is in Python, and > in turn invokes Tcl to use Tix. [snip] > The most logical thing would be to install Tix with MacPorts, so > that, in theory all will be tied together, but I don't think > there's a MacPorts Tix Port, is there? One has been submitted, but not committed: http://trac.macports.org/ticket/17191 Looking at it now, I see the port has several problems. I will try to fix them. Please check the ticket in a little bit. From t_condonia at comcast.net Sat Mar 21 17:02:03 2009 From: t_condonia at comcast.net (Tom Condon) Date: Sat, 21 Mar 2009 17:02:03 -0700 Subject: selfupdate error In-Reply-To: <30181350-E653-4C26-A2BE-A78FE822DA70@ohsu.edu> References: <30181350-E653-4C26-A2BE-A78FE822DA70@ohsu.edu> Message-ID: <49C57FFB.6020209@comcast.net> Thomas Keller wrote: > Greetings, > Could someone give me advice on what to do when selfupdate fails? > Error: /opt/local/bin/port: port selfupdate failed: Couldn't sync the > ports tree: Synchronization of 1 source(s) failed That sounds like you are not connecting to the internet correctly. The lack of a sync generally indicates that the current one on the internet is unavailable, doesn't it? In A Chord, Tom Condon Bass, Agate Passage Quartet Treasurer, Bass & Proud Member, Kitsap Chordsmen It's so hard when I have to, And so easy when I want to. - Sondra Anice Barnes From dweber at macports.org Sat Mar 21 20:10:26 2009 From: dweber at macports.org (Darren Weber) Date: Sat, 21 Mar 2009 20:10:26 -0700 Subject: port install efficiency issue Message-ID: What is up with port? It just ran for about 15 mins to build a package that is already installed. If I were to work on the same damn thing, repeating it all day, day after day, I would get the sack pretty quickly. Just think of the useless load on the network and the servers for all those futile downloads, etc. So tell me, why shouldn't I switch to fink? At least Debian has a decent package management system, geez! $ sudo port install gettext ---> Fetching gettext ---> Verifying checksum(s) for gettext ---> Extracting gettext ---> Applying patches to gettext ---> Configuring gettext ---> Building gettext ---> Staging gettext into destroot ---> Installing gettext @0.17_4 Error: Target org.macports.install returned: Registry error: gettext @0.17_4 already registered as installed. Please uninstall it first. Error: Status 1 encountered during processing. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dluke at geeklair.net Sat Mar 21 20:37:55 2009 From: dluke at geeklair.net (Daniel J. Luke) Date: Sat, 21 Mar 2009 23:37:55 -0400 Subject: port install efficiency issue In-Reply-To: References: Message-ID: <8C9CEA5F-8B76-4E91-807E-1AB109DCCC06@geeklair.net> On Mar 21, 2009, at 11:10 PM, Darren Weber wrote: > What is up with port? It just ran for about 15 mins to build a > package that is already installed. It doesn't usually do this for me. Are you running the current released version or are you running the development version? Perhaps you have discovered a bug? > If I were to work on the same damn thing, repeating it all day, day > after day, I would get the sack pretty quickly. Just think of the > useless load on the network and the servers for all those futile > downloads, etc. So tell me, why shouldn't I switch to fink? At > least Debian has a decent package management system, geez! If something else works better for you, you should probably use that. Macports is free and operated by volunteers. I'm sure we'd be happy to have your help fixing any problems you notice, though. -- Daniel J. Luke +========================================================+ | *---------------- dluke at geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 194 bytes Desc: This is a digitally signed message part URL: From ryandesign at macports.org Sat Mar 21 21:58:33 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 21 Mar 2009 23:58:33 -0500 Subject: port install efficiency issue In-Reply-To: References: Message-ID: <37F63397-3AC9-495B-B573-E1FA5D2853D3@macports.org> On Mar 21, 2009, at 22:10, Darren Weber wrote: > What is up with port? It just ran for about 15 mins to build a > package that is already installed. If I were to work on the same > damn thing, repeating it all day, day after day, I would get the > sack pretty quickly. Just think of the useless load on the network > and the servers for all those futile downloads, etc. So tell me, > why shouldn't I switch to fink? At least Debian has a decent > package management system, geez! > > $ sudo port install gettext > ---> Fetching gettext > ---> Verifying checksum(s) for gettext > ---> Extracting gettext > ---> Applying patches to gettext > ---> Configuring gettext > ---> Building gettext > ---> Staging gettext into destroot > ---> Installing gettext @0.17_4 > Error: Target org.macports.install returned: Registry error: > gettext @0.17_4 already registered as installed. Please uninstall > it first. > Error: Status 1 encountered during processing. We should keep our comments constructive. I'd like to minimize disparaging remarks about MacPorts coming from macports.org email addresses. MacPorts certainly has room for improvement in many areas. But I think it's unfair to say it's not a decent package management system. Over the many years I've used it so far, it has saved me from having to figure out how to compile many packages, so in that regard it succeeds. Regarding futile downloads and wasted resources, in this case you'll notice (from the absence of a line telling you what server it downloaded from) that it used an existing distfile already on your machine. No network bandwidth or server resources were used. Agreed, client CPU time was wasted. I would like to minimize client CPU usage, and we could make great advances there by finally distributing binaries instead of source and compilation recipes. Hopefully that will eventually occur. With MacPorts 1.7.0 I do see the same issue you describe -- sometimes. I'm don't know under what circumstances it happens. What *should* happen is the following: $ port install zlib ---> Fetching zlib ---> Verifying checksum(s) for zlib ---> Extracting zlib ---> Applying patches to zlib ---> Configuring zlib ---> Building zlib ---> Staging zlib into destroot ---> Installing zlib @1.2.3_2 ---> Activating zlib @1.2.3_2 ---> Cleaning zlib $ port install zlib Skipping org.macports.activate (zlib ) since this port is already active ---> Cleaning zlib $ There are valid reasons for wanting to rebuild a port that's already installed. But it's probably reasonable to require the use of the -f flag in those situations. And I believe that's what is supposed to be implemented. But there appears to be a bug somewhere. I don't know if a ticket is already filed about this. From frstan at bellsouth.net Sat Mar 21 22:32:39 2009 From: frstan at bellsouth.net (William Davis) Date: Sun, 22 Mar 2009 01:32:39 -0400 Subject: port install efficiency issue In-Reply-To: References: Message-ID: On Mar 21, 2009, at 11:10 PM, Darren Weber wrote: > > What is up with port? It just ran for about 15 mins to build a > package that is already installed. If I were to work on the same > damn thing, repeating it all day, day after day, I would get the > sack pretty quickly. Just think of the useless load on the network > and the servers for all those futile downloads, etc. So tell me, > why shouldn't I switch to fink? At least Debian has a decent > package management system, geez! > > $ sudo port install gettext > ---> Fetching gettext > ---> Verifying checksum(s) for gettext > ---> Extracting gettext > ---> Applying patches to gettext > ---> Configuring gettext > ---> Building gettext > ---> Staging gettext into destroot > ---> Installing gettext @0.17_4 > Error: Target org.macports.install returned: Registry error: gettext > @0.17_4 already registered as installed. Please uninstall it first. > Error: Status 1 encountered during processing. well for one thing it didn't download gettext, it fetched it from the distribution directory on your machine where it's been since the original install. For another, if you had told port to upgrade gettext port would have said: DEBUG: No need to upgrade! gettext 0.17_4 >= gettext 0.17_4 Maybe your boss should fire you, since your have a record of 1)jumping to false conclusions and 2) ignoring established procedures (ie, trak bug reports. ;) William Davis frstanATbellsouthDOTnet Mac OS X.5.6 Darwin 9.5.0 XQuartz 2.3.3_rc2 (xorg-server 1.4.2-apple37) Mac Mini Intel Duo @ 1.86 GHz Mundus vult decepi, ego non From talklists at newgeo.com Sun Mar 22 00:33:50 2009 From: talklists at newgeo.com (Scott Haneda) Date: Sun, 22 Mar 2009 00:33:50 -0700 Subject: port install efficiency issue In-Reply-To: <37F63397-3AC9-495B-B573-E1FA5D2853D3@macports.org> References: <37F63397-3AC9-495B-B573-E1FA5D2853D3@macports.org> Message-ID: On Mar 21, 2009, at 9:58 PM, Ryan Schmidt wrote: > On Mar 21, 2009, at 22:10, Darren Weber wrote: > >> What is up with port? It just ran for about 15 mins to build a >> package that is already installed. If I were to work on the same >> damn thing, repeating it all day, day after day, I would get the >> sack pretty quickly. Just think of the useless load on the network >> and the servers for all those futile downloads, etc. So tell me, >> why shouldn't I switch to fink? At least Debian has a decent >> package management system, geez! >> >> $ sudo port install gettext >> ---> Fetching gettext >> ---> Verifying checksum(s) for gettext >> ---> Extracting gettext >> ---> Applying patches to gettext >> ---> Configuring gettext >> ---> Building gettext >> ---> Staging gettext into destroot >> ---> Installing gettext @0.17_4 >> Error: Target org.macports.install returned: Registry error: >> gettext @0.17_4 already registered as installed. Please uninstall >> it first. >> Error: Status 1 encountered during processing. > > > We should keep our comments constructive. I'd like to minimize > disparaging remarks about MacPorts coming from macports.org email > addresses. Question of general curiosity here. I am asking this is all seriousness. How do you get a macports.org email address. My assumption was that you were a developer pf ports if you had that address. In this case, the OP does not appear to be, or I would assume were they, this would be a question they could answer and solve on their own. If it is a bug, they could report it. In this case, it look as though the user is not a ports dev/contributor. Just looking to understand the chain of command, for lack of a bette word. Thanks. * I was under the impression Mac Ports was sort of to replace Fink, is that not the case? What are the pros and cons, differences? Is Fink still active? -- Scott * If you contact me off list replace talklists@ with scott@ * From blb at macports.org Sun Mar 22 00:34:36 2009 From: blb at macports.org (Bryan Blackburn) Date: Sun, 22 Mar 2009 01:34:36 -0600 Subject: port install efficiency issue In-Reply-To: <37F63397-3AC9-495B-B573-E1FA5D2853D3@macports.org> References: <37F63397-3AC9-495B-B573-E1FA5D2853D3@macports.org> Message-ID: <20090322073436.GB8488@ninagal.withay.com> On Sat, Mar 21, 2009 at 11:58:33PM -0500, Ryan Schmidt said: [...] > > There are valid reasons for wanting to rebuild a port that's already > installed. But it's probably reasonable to require the use of the -f flag > in those situations. And I believe that's what is supposed to be > implemented. But there appears to be a bug somewhere. I don't know if a > ticket is already filed about this. I think port not only pays attention to epoch/version/revision but also the timestamp of Portfile; when Portfile is newer than the install, even when the versioning says it's already installed, it'll run again. Bryan From ryandesign at macports.org Sun Mar 22 00:54:55 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 22 Mar 2009 02:54:55 -0500 Subject: port install efficiency issue In-Reply-To: <20090322073436.GB8488@ninagal.withay.com> References: <37F63397-3AC9-495B-B573-E1FA5D2853D3@macports.org> <20090322073436.GB8488@ninagal.withay.com> Message-ID: <95ED8DF7-4414-45CE-8B77-E48B9C150950@macports.org> On Mar 22, 2009, at 02:34, Bryan Blackburn wrote: > On Sat, Mar 21, 2009 at 11:58:33PM -0500, Ryan Schmidt said: > [...] >> >> There are valid reasons for wanting to rebuild a port that's already >> installed. But it's probably reasonable to require the use of the - >> f flag >> in those situations. And I believe that's what is supposed to be >> implemented. But there appears to be a bug somewhere. I don't know >> if a >> ticket is already filed about this. > > I think port not only pays attention to epoch/version/revision but > also the > timestamp of Portfile; when Portfile is newer than the install, > even when > the versioning says it's already installed, it'll run again. I would not have expected that. If a rebuild is needed, the maintainer needs to increase the revision, version, or epoch. From ryandesign at macports.org Sun Mar 22 01:01:49 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 22 Mar 2009 03:01:49 -0500 Subject: port install efficiency issue In-Reply-To: References: <37F63397-3AC9-495B-B573-E1FA5D2853D3@macports.org> Message-ID: On Mar 22, 2009, at 02:33, Scott Haneda wrote: > On Mar 21, 2009, at 9:58 PM, Ryan Schmidt wrote: > >> We should keep our comments constructive. I'd like to minimize >> disparaging remarks about MacPorts coming from macports.org email >> addresses. > > Question of general curiosity here. I am asking this is all > seriousness. How do you get a macports.org email address. My > assumption was that you were a developer pf ports if you had that > address. In this case, the OP does not appear to be, or I would > assume were they, this would be a question they could answer and > solve on their own. If it is a bug, they could report it. > > In this case, it look as though the user is not a ports dev/ > contributor. > > Just looking to understand the chain of command, for lack of a > bette word. Thanks. Darren is a member of the MacPorts project. He has commit access and maintains two ports. All users with macports.org email addresses requested and were granted membership via the procedure outlined in the Guide: http://guide.macports.org/#project.membership > * I was under the impression Mac Ports was sort of to replace Fink, > is that not the case? What are the pros and cons, differences? Is > Fink still active? Fink and MacPorts are both package management systems for Mac OS X. I myself switched from Fink to what is now MacPorts years ago, because I started having problems with Fink when Tiger was released. But I think Fink is still alive. Their web site is: http://www.finkproject.org/ From afb at macports.org Sun Mar 22 02:01:25 2009 From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=) Date: Sun, 22 Mar 2009 10:01:25 +0100 Subject: port install efficiency issue In-Reply-To: References: <37F63397-3AC9-495B-B573-E1FA5D2853D3@macports.org> Message-ID: <3F1CEC06-94D6-4BB4-8FBF-3B7DF120B02E@macports.org> Ryan Schmidt wrote: >> * I was under the impression Mac Ports was sort of to replace >> Fink, is that not the case? What are the pros and cons, >> differences? Is Fink still active? > > Fink and MacPorts are both package management systems for Mac OS X. > I myself switched from Fink to what is now MacPorts years ago, > because I started having problems with Fink when Tiger was > released. But I think Fink is still alive. Their web site is: > > http://www.finkproject.org/ There's probably some communication issues between the projects here, since Fink also thinks that MacPorts is (barely) alive: http://www.finkproject.org/faq/relations.php?phpLang=en#darwinports "Q2.4: What is your relation with Darwinports?" "A: Darwinports and Fink are complementary projects. There is some overlap between the two projects, and several people contribute to both the Fink and DarwinPorts projects. [...]" (l.c. 14 March 2009) Both Fink and MacPorts are probably more of "software management" systems than "package management" systems, but that's another story. Fink uses DEB packages, while MacPorts uses more simplistic archives like tarballs. There's some earlier work to make MP use RPM instead. If you are careful, it is also possible to use both systems at once - since they use different install prefixes: /sw versus /opt/local... You can't have both of them in PATH or the rest of the System though, and linking e.g. libraries between them is not a good idea either. --anders From raimue at macports.org Sun Mar 22 06:34:18 2009 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Sun, 22 Mar 2009 14:34:18 +0100 Subject: port install efficiency issue In-Reply-To: <95ED8DF7-4414-45CE-8B77-E48B9C150950@macports.org> References: <37F63397-3AC9-495B-B573-E1FA5D2853D3@macports.org> <20090322073436.GB8488@ninagal.withay.com> <95ED8DF7-4414-45CE-8B77-E48B9C150950@macports.org> Message-ID: <49C63E5A.5090006@macports.org> Ryan Schmidt wrote: >> I think port not only pays attention to epoch/version/revision but >> also the >> timestamp of Portfile; when Portfile is newer than the install, >> even when >> the versioning says it's already installed, it'll run again. > > I would not have expected that. > > If a rebuild is needed, the maintainer needs to increase the > revision, version, or epoch. I reported this problem earlier: http://lists.macosforge.org/pipermail/macports-dev/2008-February/004563.html If nobody can think of a valid use for this check we should just drop it. Rainer From raimue at macports.org Sun Mar 22 06:56:10 2009 From: raimue at macports.org (=?UTF-8?B?UmFpbmVyIE3DvGxsZXI=?=) Date: Sun, 22 Mar 2009 14:56:10 +0100 Subject: port install efficiency issue In-Reply-To: References: Message-ID: <49C6437A.5040807@macports.org> Darren Weber wrote: > What is up with port? It just ran for about 15 mins to build a package > that is already installed. If I were to work on the same damn thing, > repeating it all day, day after day, I would get the sack pretty > quickly. Just think of the useless load on the network and the servers > for all those futile downloads, etc. I agree with you, that this is not ideal. But I also don't know why port was made to behave in this way. > So tell me, why shouldn't I switch > to fink? At least Debian has a decent package management system, geez! Uh, just a single bug or flaw gets you change to another system? I know and admit MacPorts is not perfect. But be aware that there are a few people working on the bugs you report. Ranting against MacPorts isn't helpful at all to get bugs fixed - especially it's not good for motivation. Please keep your reports specific and constructive. If you go on comparing MacPorts with other similar projects, I would hope it is no problem to say, "X is better at Y than MacPorts, because it does Z". Rainer From rps at salas.com Sun Mar 22 07:15:40 2009 From: rps at salas.com (R. Pito Salas) Date: Sun, 22 Mar 2009 10:15:40 -0400 Subject: Python, Tcl, Tix ... In-Reply-To: <96081377-E75A-427D-A9CD-02D8A5CD32A7@macports.org> References: <96081377-E75A-427D-A9CD-02D8A5CD32A7@macports.org> Message-ID: Ryan I saw your post on the ticket. Does it mean that I am SOL or are you looking at it still? Thanks, Pito On Mar 21, 2009, at 6:43 PM, Ryan Schmidt wrote: > > On Mar 21, 2009, at 14:38, R. Pito Salas wrote: > >> I am trying to get an application running which is in Python, and >> in turn invokes Tcl to use Tix. > > [snip] > >> The most logical thing would be to install Tix with MacPorts, so >> that, in theory all will be tied together, but I don't think >> there's a MacPorts Tix Port, is there? > > One has been submitted, but not committed: > > http://trac.macports.org/ticket/17191 > > Looking at it now, I see the port has several problems. I will try > to fix them. Please check the ticket in a little bit. > > From brad at pixilla.com Sun Mar 22 08:37:13 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Sun, 22 Mar 2009 08:37:13 -0700 Subject: port install efficiency issue In-Reply-To: References: Message-ID: On Mar 21, 2009, at 8:10 PM, Darren Weber wrote: > > What is up with port? It just ran for about 15 mins to build a > package that is already installed. If I were to work on the same > damn thing, repeating it all day, day after day, I would get the > sack pretty quickly. Just think of the useless load on the network > and the servers for all those futile downloads, etc. So tell me, > why shouldn't I switch to fink? At least Debian has a decent > package management system, geez! I presume because you say "decent package management system" you realize apt is not flawless. In my experience, all systems cause moments of frustration. Darren, thanks for reporting a possible bug. //Brad From t_condonia at comcast.net Sun Mar 22 08:47:25 2009 From: t_condonia at comcast.net (Tom Condon) Date: Sun, 22 Mar 2009 08:47:25 -0700 Subject: port install efficiency issue In-Reply-To: References: Message-ID: <49C65D8D.4070708@comcast.net> Darren Weber wrote: > What is up with port? It just ran for about 15 mins to build a package that > is already installed. If I were to work on the same damn thing, repeating > it all day, day after day, I would get the sack pretty quickly. Just think > of the useless load on the network and the servers for all those futile > downloads, etc. So tell me, why shouldn't I switch to fink? At least > Debian has a decent package management system, geez! Ah, how quickly we forget. OK, kiddies, time for a history lesson. When I first got a job out of college we had a computer. Yes, *a* computer. One. We scheduled time on that computer based on our customer's needs, and when that time came we got to use the computer. The computer time was scheduled anytime from 5am-11:30pm, and you used the computer whenever you were scheduled. If we wanted any compilations done off-line (when our customers were not there waiting to use the computer) we did them in "batch". They ran batch from 12:00-12:30 pm and from 11:30pm-12:00am. If there were too many jobs to run all of them (virtually always), some didn't get run until the next batch session. My particular project had four different compilations that took 30+ minutes, so I frequently had long turnaround times. So I have little sympathy for those who complain that something five magnitudes of complexity greater than what we were working on takes 15 whole minutes. I agree with the other respondent. Add something positive with your comments, don't complain about how it isn't faster than a speeding bullet. Oh, and lest you think what we were doing in those dark ages of computing wasn't critically important, my project was the 747/Space Shuttle mated flight and separation simulation. You know, when they land the Shuttle in the desert at Edwards AFB they put it on the back of a 747 to ferry it back to Cape Canaveral (now called Cape Kennedy). We made that ferry system work. We also trained the astronauts to launch the Shuttle from the back of the 747 in flight so they could practice landing it before they ever shot it up into space. In A Chord, Tom Condon Fossilized Software Engineer It's so hard when I have to, And so easy when I want to. - Sondra Anice Barnes PS I did fudge a bit there. We had a second computer. You programmed it with patch-cords. You may need to see the wikipedia for an explanation of those. From trog24 at comcast.net Sun Mar 22 10:06:24 2009 From: trog24 at comcast.net (Frank J. R. Hanstick) Date: Sun, 22 Mar 2009 10:06:24 -0700 Subject: port install efficiency issue In-Reply-To: <49C6437A.5040807@macports.org> References: <49C6437A.5040807@macports.org> Message-ID: <2C269F10-9498-4759-8668-4603FBAB6524@comcast.net> Hello, Wouldn't it be better and faster to do the check at request time rather than wait until everything has been done and then request if an update is wanted rather than an install? Frank On Mar 22, 2009, at 6:56 AM, Rainer M?ller wrote: > Darren Weber wrote: >> What is up with port? It just ran for about 15 mins to build a >> package >> that is already installed. If I were to work on the same damn thing, >> repeating it all day, day after day, I would get the sack pretty >> quickly. Just think of the useless load on the network and the >> servers >> for all those futile downloads, etc. > > I agree with you, that this is not ideal. But I also don't know why > port > was made to behave in this way. > >> So tell me, why shouldn't I switch >> to fink? At least Debian has a decent package management system, >> geez! > > Uh, just a single bug or flaw gets you change to another system? > > I know and admit MacPorts is not perfect. But be aware that there > are a > few people working on the bugs you report. Ranting against MacPorts > isn't helpful at all to get bugs fixed - especially it's not good for > motivation. > > Please keep your reports specific and constructive. If you go on > comparing MacPorts with other similar projects, I would hope it is no > problem to say, "X is better at Y than MacPorts, because it does Z". > > Rainer > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users Frank J. R. Hanstick trog24 at comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From dweber at macports.org Sun Mar 22 11:19:35 2009 From: dweber at macports.org (Darren Weber) Date: Sun, 22 Mar 2009 11:19:35 -0700 Subject: port install efficiency issue In-Reply-To: <2C269F10-9498-4759-8668-4603FBAB6524@comcast.net> References: <49C6437A.5040807@macports.org> <2C269F10-9498-4759-8668-4603FBAB6524@comcast.net> Message-ID: 2009/3/22 Frank J. R. Hanstick > Hello, > Wouldn't it be better and faster to do the check at request time rather > than wait until everything has been done and then request if an update is > wanted rather than an install? > Frank > Yes, sounds reasonable. Also, my apologies! Macports is great and so much so that I like to contribute to it whenever I can! http://trac.macports.org/wiki/dweber Yes, fink has some issues too! Nevertheless, I have used Debian (mostly Ubuntu) for a few years and I've lived to appreciate that system (despite some initial headaches with stable, unstable, ouch-bleeding on the testing stuff). For the most part, I think the dependency resolution and the upgrade process is amazing. I am very pleased to see this system available for OSX and I do hope it lives on in all it's wonder. I've made a move over to OSX for a new job and I guessed that macports would be the right way to go, basically because I guessed it would be a BSD system (or darwinports system) and I assumed that would be totally rock solid and efficient because it's been around for decades (even in those days of scheduled compilation). I'm a novice when it comes to BSD and OSX, so this is a great learning opportunity for me (even if I lose it sometimes). On balance, I'm both impressed and disappointed with the complexity of the macports system to date. For example, dependency resolution needs a lot of work during upgrades, binary distributions are a great idea in the making (perhaps forever in the making), and the whole issue of dependency on variants is a massive conference debate. I've certainly come across these issues and tried to submit reasonable trac suggestions for enhancements, etc. on a couple of ports. My main issue seems to be in getting a few ports with a lot of dependencies to cooperate, esp. with regard to variants (eg, Qt, Postgresql, MySQL, VTK, etc.). I do think that package maintainers should think very carefully about their default variants and try to provide as many options as possible - that seems to be the way with Debian packages. It seems to me that Debian uses a different set of packages for every major release, whereas macports tries to accommodate all the OSX flavours into every Portfile. Perhaps one way to reduce the confusion is to create branches in the port tree for each major OSX release and platform (PowerPC, intel, iphone; what's next?). Perhaps some of these things are rightly compiler variants or something, but how much easier it might be if you just choose the right branch for your platform to work on? I guess that raises the problem of where to edit the Portfile and management of multiple files in different branches - ouch. I don't know how that's done in Debian. Nevertheless, I will push on with macports and I'm trying to do my part to both support and encourage open-source systems. That's the bigger picture here and I'm very sorry that my frustration on this thread raised a relatively minor quibble about distribution systems. Unfortnately, my comments were emotional, but that's how it is sometimes and that's when you really feel that there has to be a better way. Patience is a virtue, I just lose it sometimes. Thankyou all for your understanding and, moreover, for the many reasonable suggestions to make macports even better. Take care, Darren -------------- next part -------------- An HTML attachment was scrubbed... URL: From dweber at macports.org Sun Mar 22 11:46:30 2009 From: dweber at macports.org (Darren Weber) Date: Sun, 22 Mar 2009 11:46:30 -0700 Subject: stable vs. unstable ports? Message-ID: I've noticed problems during port upgrades. What is the general consensus on having a TAG for each port to indicate it's "success" status within the system? Is it possible to have a meta-port monitor that automatically tracks the status of each package install and reports that status back to a central repository to continuously flag the status of a port install. A simple dichotomy of stable and unstable might suffice (Debian uses stable, unstable, and testing). Perhaps the monitoring system could provide the data required to justify these port status levels. I imagine the system could be something like a) meta-port launches each install using port and monitors the success or failure of that process, then returns a value to a central repository. b) the central repository has some algorithm to determine a port status (stable, unstable, etc.) and it notifies a port maintainer with a daily, weekly digest or summary of the situation. c) the monitoring system and reporting should "switch-off" somehow when the port becomes stable for a while, but it may be reactivated by a failure. That is, the success status of an install is always monitored, but reporting to central repository etc. is not required on any successful install for a stable port. Perhaps the meta-port is simply a module (procedure, function) within port or a wrapper for port? It seems Porticus must be doing something like this already. Take care, Darren -------------- next part -------------- An HTML attachment was scrubbed... URL: From dweber at macports.org Sun Mar 22 12:47:01 2009 From: dweber at macports.org (Darren Weber) Date: Sun, 22 Mar 2009 12:47:01 -0700 Subject: compile farm? Message-ID: Is it possible to use the sourceforge compile farm to provide binary distros for macports? Perhaps cdash or something like it could be used? FYI: http://www.cdash.org/ Take care, Darren PS, I assume GNU savanna is not available for anything that depends on OSX (but does it also exclude BSD - darwin?). http://savannah.gnu.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From dweber at macports.org Sun Mar 22 12:48:41 2009 From: dweber at macports.org (Darren Weber) Date: Sun, 22 Mar 2009 12:48:41 -0700 Subject: compile farm? In-Reply-To: References: Message-ID: On Sun, Mar 22, 2009 at 12:47 PM, Darren Weber wrote: > > Is it possible to use the sourceforge compile farm to provide binary > distros for macports? > > Perhaps cdash or something like it could be used? FYI: > http://www.cdash.org/ > > Take care, Darren > > PS, I assume GNU savanna is not available for anything that depends on OSX > (but does it also exclude BSD - darwin?). > http://savannah.gnu.org/ > > PPS, http://savannah.nongnu.org/ http://www.gnu.org/help/evaluation.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From dluke at geeklair.net Sun Mar 22 13:16:35 2009 From: dluke at geeklair.net (Daniel J. Luke) Date: Sun, 22 Mar 2009 16:16:35 -0400 Subject: port install efficiency issue In-Reply-To: <49C63E5A.5090006@macports.org> References: <37F63397-3AC9-495B-B573-E1FA5D2853D3@macports.org> <20090322073436.GB8488@ninagal.withay.com> <95ED8DF7-4414-45CE-8B77-E48B9C150950@macports.org> <49C63E5A.5090006@macports.org> Message-ID: <8495AD38-B5FC-4977-B6B8-5FEF7AEB3F0D@geeklair.net> On Mar 22, 2009, at 9:34 AM, Rainer M?ller wrote: > Ryan Schmidt wrote: >>> I think port not only pays attention to epoch/version/revision but >>> also the >>> timestamp of Portfile; when Portfile is newer than the install, >>> even when >>> the versioning says it's already installed, it'll run again. >> >> I would not have expected that. >> >> If a rebuild is needed, the maintainer needs to increase the >> revision, version, or epoch. > > I reported this problem earlier: > http://lists.macosforge.org/pipermail/macports-dev/2008-February/004563.html > > If nobody can think of a valid use for this check we should just > drop it. It is somewhat useful when one is developing a new port (since you don't have to remember to clean before you rebuild after changing the Portfile), and there's the -o flag one can use to change the behavior. I don't have a problem with removing the feature, though. -- Daniel J. Luke +========================================================+ | *---------------- dluke at geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 194 bytes Desc: This is a digitally signed message part URL: From ben at cogs.com Sun Mar 22 13:20:10 2009 From: ben at cogs.com (Ben Greenfield) Date: Sun, 22 Mar 2009 16:20:10 -0400 Subject: port install efficiency issue In-Reply-To: <8495AD38-B5FC-4977-B6B8-5FEF7AEB3F0D@geeklair.net> References: <37F63397-3AC9-495B-B573-E1FA5D2853D3@macports.org> <20090322073436.GB8488@ninagal.withay.com> <95ED8DF7-4414-45CE-8B77-E48B9C150950@macports.org> <49C63E5A.5090006@macports.org> <8495AD38-B5FC-4977-B6B8-5FEF7AEB3F0D@geeklair.net> Message-ID: <1E42602C-4F8E-4A4D-AA63-61F703598513@cogs.com> On Mar 22, 2009, at 4:16 PM, Daniel J. Luke wrote: > On Mar 22, 2009, at 9:34 AM, Rainer M?ller wrote: >> Ryan Schmidt wrote: >>>> I think port not only pays attention to epoch/version/revision but >>>> also the >>>> timestamp of Portfile; when Portfile is newer than the install, >>>> even when >>>> the versioning says it's already installed, it'll run again. >>> >>> I would not have expected that. >>> >>> If a rebuild is needed, the maintainer needs to increase the >>> revision, version, or epoch. >> >> I reported this problem earlier: >> http://lists.macosforge.org/pipermail/macports-dev/2008-February/004563.html >> >> If nobody can think of a valid use for this check we should just >> drop it. > > > It is somewhat useful when one is developing a new port (since you > don't have to remember to clean before you rebuild after changing > the Portfile), and there's the -o flag one can use to change the > behavior. > > I don't have a problem with removing the feature, though. How about reverse the logic default is not to do it and a switch to do it? bdg > -- > Daniel J. Luke > +========================================================+ > | *---------------- dluke at geeklair.net ----------------* | > | *-------------- http://www.geeklair.net -------------* | > +========================================================+ > | Opinions expressed are mine and do not necessarily | > | reflect the opinions of my employer. | > +========================================================+ > > > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From dluke at geeklair.net Sun Mar 22 13:21:20 2009 From: dluke at geeklair.net (Daniel J. Luke) Date: Sun, 22 Mar 2009 16:21:20 -0400 Subject: stable vs. unstable ports? In-Reply-To: References: Message-ID: <0C2DB026-75F1-49C6-B32F-661AFE7F11E9@geeklair.net> On Mar 22, 2009, at 2:46 PM, Darren Weber wrote: > What is the general consensus on having a TAG for each port to > indicate it's "success" status within the system? I like this idea (and have mentioned something similar before, other people also seem receptive). > Is it possible to have a meta-port monitor that automatically tracks > the status of each package install and reports that status back to a > central repository to continuously flag the status of a port > install. A simple dichotomy of stable and unstable might suffice > (Debian uses stable, unstable, and testing). Perhaps the monitoring > system could provide the data required to justify these port status > levels. This kind of things is certainly possible, it just requires someone to be willing to take the time to do it. I encourage anyone who is interested in this sort of thing to start playing with the macports source and see what you can come up with. Feel free to discuss on the -dev list (and irc) with people who are more familiar with the base source. The key thing to realize is that MacPorts is all done by volunteers, and the best way to get some functionality you want is to go ahead and implement it yourself. -- Daniel J. Luke +========================================================+ | *---------------- dluke at geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 194 bytes Desc: This is a digitally signed message part URL: From blb at macports.org Sun Mar 22 13:27:12 2009 From: blb at macports.org (Bryan Blackburn) Date: Sun, 22 Mar 2009 14:27:12 -0600 Subject: port install efficiency issue In-Reply-To: References: <49C6437A.5040807@macports.org> <2C269F10-9498-4759-8668-4603FBAB6524@comcast.net> Message-ID: <20090322202712.GC812@ninagal.withay.com> On Sun, Mar 22, 2009 at 11:19:35AM -0700, Darren Weber said: [...] > > On balance, I'm both impressed and disappointed with the complexity of the > macports system to date. For example, dependency resolution needs a lot of > work during upgrades, What do you mean, performance-wise? If so, that's been vastly improved on trunk, see > binary distributions are a great idea in the making > (perhaps forever in the making), Yes, binaries is a definitely-wanted feature, but there are issues ranging from dealing with variants (should binaries for each possible variant combination be provided, some grouping just for binary support?), to the question of where do these get built? Some have suggested the same people who update the port itself, but are all of our machines as clean for such uses (eg, some ports may link against bits which are not declared as dependencies). Then there's the question of actual implementation... > and the whole issue of dependency on > variants is a massive conference debate. Seeing as how variant dependencies is one of the oldest tickets we have (#126), it's obviously wanted & needed, but will require some definite work throughout base; so again, an implementation issue, and a big one in this case. [...] > Perhaps one way to reduce the confusion is to > create branches in the port tree for each major OSX release and platform > (PowerPC, intel, iphone; what's next?). Having multiple branches for the ports themselves has been brought up before, but is unworkable in today's MacPorts because we have so few people to begin with. We have a bit more than 5600 ports and half of those are unmaintained, so doubling the number of Portfiles to maintain would just be more burdensome. Also, for breaking them out per OS release/platform, how many of the people maintaining those 2300 ports has access to both Intel and PowerPC on at least 10.4 and 10.5? A build server/farm would help, but who's going to host it? I don't believe that's one of the services MacOSForge provides. Bryan [...] > > Take care, Darren From raimue at macports.org Sun Mar 22 14:02:04 2009 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Sun, 22 Mar 2009 22:02:04 +0100 Subject: port install efficiency issue In-Reply-To: <8495AD38-B5FC-4977-B6B8-5FEF7AEB3F0D@geeklair.net> References: <37F63397-3AC9-495B-B573-E1FA5D2853D3@macports.org> <20090322073436.GB8488@ninagal.withay.com> <95ED8DF7-4414-45CE-8B77-E48B9C150950@macports.org> <49C63E5A.5090006@macports.org> <8495AD38-B5FC-4977-B6B8-5FEF7AEB3F0D@geeklair.net> Message-ID: <49C6A74C.7040702@macports.org> Daniel J. Luke wrote: >> If nobody can think of a valid use for this check we should just >> drop it. > > It is somewhat useful when one is developing a new port (since you > don't have to remember to clean before you rebuild after changing the > Portfile), and there's the -o flag one can use to change the behavior. This is not what -o does. port -o is to ignore the fact that the Portfile is newer than the state file (usually in work/.macports.foo.state). This happens when you had a failing build, do a sync which hopefully gets a fixed Portfile and then run the install again. In this case, port will recognize that the Portfile was changed since the earlier attempt and automatically cleans and starts over. port -o overrides this check and continues despite the state file being older than the Portfile. But what we discuss here, is the comparison of the Portfile modification time with the time of installation. This affects all phases currently, so you cannot run 'port extract foo' or anything if you already have port foo installed. You would have to use force. But if the Portfile is newer than the currently installed version, then it will continue, but error out in the install phase because a port with exact same name/version/revision/epoch/variants is already installed. Rainer From raimue at macports.org Sun Mar 22 14:17:16 2009 From: raimue at macports.org (=?UTF-8?B?UmFpbmVyIE3DvGxsZXI=?=) Date: Sun, 22 Mar 2009 22:17:16 +0100 Subject: compile farm? In-Reply-To: References: Message-ID: <49C6AADC.2080604@macports.org> Darren Weber wrote: > > Is it possible to use the sourceforge compile farm to provide binary > distros for macports? The sourceforge compile farm does not exist any more for at least two years now. Rainer From talklists at newgeo.com Sun Mar 22 16:01:09 2009 From: talklists at newgeo.com (Scott Haneda) Date: Sun, 22 Mar 2009 16:01:09 -0700 Subject: port install efficiency issue In-Reply-To: <20090322202712.GC812@ninagal.withay.com> References: <49C6437A.5040807@macports.org> <2C269F10-9498-4759-8668-4603FBAB6524@comcast.net> <20090322202712.GC812@ninagal.withay.com> Message-ID: <3FFC1539-E7C9-4CEC-AF38-DD2DE12D7F44@newgeo.com> Can we talk more about this? I have the ability to host such a build farm. Now, I could not host one machine, of every architecture, of every OS, I just do not have the room in colocation. I do have quite a bit of room if we go 1U though. So 2 1U machines, a PPC and a Intel, and I would imagine, that PPC machine could go away a lot sooner than we all think. Mac Mini's could take it further, since they are so small, 8 of them can fit on a shelf and occupy no more than a few U's of space. The damn power bricks are more an issue than anything else. There have to be PPC Mini's out there to be had. As long as the various OS versions could be virtualized, so we could have 10.3, 10.4, 10.5, 10.6 and forward virtualized on each machine, it would not at all be hard to come up with a authentication routine to allow builds to happen on whatever virtual interface you want. I have the Ip space to spare, so each virtual machine could have it's own connection space, or we could do some simple dhcp pooling. Static IP's are something I was alloted a /24 of, and do not see giving up 20 or so of them being an issue. Am I looking at this wrong, or would this be helpful? Is this too much reliance on an outside party for core ports features? I have had access to this data center for 9+ years or so, I do not plan on giving up that access at any time soon. The bandwidth requirements are minimal, it would go unnoticed. On Mar 22, 2009, at 1:27 PM, Bryan Blackburn wrote: > A build server/farm would help, but who's going to host it? I don't > believe > that's one of the services MacOSForge provides. -- Scott * If you contact me off list replace talklists@ with scott@ * From jmr at macports.org Sun Mar 22 17:18:36 2009 From: jmr at macports.org (Joshua Root) Date: Mon, 23 Mar 2009 11:18:36 +1100 Subject: stable vs. unstable ports? In-Reply-To: References: Message-ID: <49C6D55C.7050709@macports.org> Darren Weber wrote: > > I've noticed problems during port upgrades. > > What is the general consensus on having a TAG for each port to indicate > it's "success" status within the system? > > Is it possible to have a meta-port monitor that automatically tracks the > status of each package install and reports that status back to a central > repository to continuously flag the status of a port install. A simple > dichotomy of stable and unstable might suffice (Debian uses stable, > unstable, and testing). Perhaps the monitoring system could provide the > data required to justify these port status levels. IIRC, last time something like this was proposed, the consensus was that "phoning home" is evil and MacPorts shouldn't do it. (The focus then was more on collecting stats on how often each port is used.) Personally I don't see what the problem is as long as it's opt-in. Of course, if we had a build farm producing binaries (see discussion currently ongoing), this information could also be produced by it incidentally to its main function. - Josh From jmr at macports.org Sun Mar 22 17:21:42 2009 From: jmr at macports.org (Joshua Root) Date: Mon, 23 Mar 2009 11:21:42 +1100 Subject: port install efficiency issue In-Reply-To: <8495AD38-B5FC-4977-B6B8-5FEF7AEB3F0D@geeklair.net> References: <37F63397-3AC9-495B-B573-E1FA5D2853D3@macports.org> <20090322073436.GB8488@ninagal.withay.com> <95ED8DF7-4414-45CE-8B77-E48B9C150950@macports.org> <49C63E5A.5090006@macports.org> <8495AD38-B5FC-4977-B6B8-5FEF7AEB3F0D@geeklair.net> Message-ID: <49C6D616.5090302@macports.org> Daniel J. Luke wrote: > On Mar 22, 2009, at 9:34 AM, Rainer M?ller wrote: >> Ryan Schmidt wrote: >>>> I think port not only pays attention to epoch/version/revision but >>>> also the >>>> timestamp of Portfile; when Portfile is newer than the install, >>>> even when >>>> the versioning says it's already installed, it'll run again. >>> >>> I would not have expected that. >>> >>> If a rebuild is needed, the maintainer needs to increase the >>> revision, version, or epoch. >> >> I reported this problem earlier: >> http://lists.macosforge.org/pipermail/macports-dev/2008-February/004563.html >> >> >> If nobody can think of a valid use for this check we should just drop it. > > > It is somewhat useful when one is developing a new port (since you don't > have to remember to clean before you rebuild after changing the > Portfile), and there's the -o flag one can use to change the behavior. > > I don't have a problem with removing the feature, though. We don't have to remove the feature entirely, just turn it off for action_install when the current version(+epoch/revision/variants) of the port is already installed (as opposed to being mid-build). - Josh From jmr at macports.org Sun Mar 22 17:54:25 2009 From: jmr at macports.org (Joshua Root) Date: Mon, 23 Mar 2009 11:54:25 +1100 Subject: port install efficiency issue In-Reply-To: <3FFC1539-E7C9-4CEC-AF38-DD2DE12D7F44@newgeo.com> References: <49C6437A.5040807@macports.org> <2C269F10-9498-4759-8668-4603FBAB6524@comcast.net> <20090322202712.GC812@ninagal.withay.com> <3FFC1539-E7C9-4CEC-AF38-DD2DE12D7F44@newgeo.com> Message-ID: <49C6DDC1.6000405@macports.org> Scott Haneda wrote: > Can we talk more about this? I have the ability to host such a build > farm. Now, I could not host one machine, of every architecture, of > every OS, I just do not have the room in colocation. > > I do have quite a bit of room if we go 1U though. So 2 1U machines, a > PPC and a Intel, and I would imagine, that PPC machine could go away a > lot sooner than we all think. Mac Mini's could take it further, since > they are so small, 8 of them can fit on a shelf and occupy no more than > a few U's of space. The damn power bricks are more an issue than > anything else. There have to be PPC Mini's out there to be had. > > As long as the various OS versions could be virtualized, so we could > have 10.3, 10.4, 10.5, 10.6 and forward virtualized on each machine, it > would not at all be hard to come up with a authentication routine to > allow builds to happen on whatever virtual interface you want. > > I have the Ip space to spare, so each virtual machine could have it's > own connection space, or we could do some simple dhcp pooling. Static > IP's are something I was alloted a /24 of, and do not see giving up 20 > or so of them being an issue. > > Am I looking at this wrong, or would this be helpful? Is this too much > reliance on an outside party for core ports features? I have had access > to this data center for 9+ years or so, I do not plan on giving up that > access at any time soon. The bandwidth requirements are minimal, it > would go unnoticed. Thanks for the offer. I think it's safe to say, though, that finding the hardware for a build farm will be a relatively minor issue. The main thing that is needed is the software. Server-side, to build all the ports in some kind of intelligent order and copy the archives to somewhere from which they can be downloaded by the client, with error reporting; and to keep doing this as needed when new versions and new ports are added. Client-side, to check for the presence of an archive with the desired version/variants on the server, and to download and unarchive it instead of building from source when possible. - Josh From paul.sijpkes at gmail.com Sun Mar 22 18:02:53 2009 From: paul.sijpkes at gmail.com (Paul Sijpkes) Date: Mon, 23 Mar 2009 12:02:53 +1100 Subject: Cannot access rsync.macports.org In-Reply-To: <05A6BEC1-4905-437C-B59D-ADEF8B1778F8@gmail.com> References: <05A6BEC1-4905-437C-B59D-ADEF8B1778F8@gmail.com> Message-ID: <722C2F95-7FD4-4359-AC2C-78841838BB67@gmail.com> Hi all, I just installed MacPorts 1.7.0 and my machine cannot access the rsync URL rsync.macports.org when I use the port -d selfupdate command. Strangely enough, the url that ping looks up (alpha.osforge.org) works in a browser, so this indicates Port 80 is open. Is it possible that whichever port that RSYNC uses is blocked by my ISP? I've never had anything else blocked by them, so this would be odd... I've checked my firewall setting and tried pinging the above addresses, but I have no access. Before I contact my ISP, I'd just like to make sure that the server still exists and also find out which port that selfupdate uses with rsync. Thanks for any help on this matter, Paul From jmr at macports.org Sun Mar 22 18:13:22 2009 From: jmr at macports.org (Joshua Root) Date: Mon, 23 Mar 2009 12:13:22 +1100 Subject: Cannot access rsync.macports.org In-Reply-To: <722C2F95-7FD4-4359-AC2C-78841838BB67@gmail.com> References: <05A6BEC1-4905-437C-B59D-ADEF8B1778F8@gmail.com> <722C2F95-7FD4-4359-AC2C-78841838BB67@gmail.com> Message-ID: <49C6E232.806@macports.org> Paul Sijpkes wrote: > Hi all, > > I just installed MacPorts 1.7.0 and my machine cannot access the rsync URL > rsync.macports.org when I use the port -d selfupdate command. > > Strangely enough, the url that ping looks up (alpha.osforge.org) works > in a browser, > so this indicates Port 80 is open. Is it possible that whichever port > that RSYNC uses is > blocked by my ISP? I've never had anything else blocked by them, so > this would be odd... > > I've checked my firewall setting and tried pinging the above addresses, > but I have no access. > Before I contact my ISP, I'd just like to make sure that the server > still exists and also find out > which port that selfupdate uses with rsync. > > Thanks for any help on this matter, > Paul It should definitely be working. Rsync uses TCP port 873, check if you can telnet to that port on rsync.macports.org. If it is being blocked, there are some alternatives: - Josh From ryandesign at macports.org Sun Mar 22 18:15:13 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 22 Mar 2009 20:15:13 -0500 Subject: Python, Tcl, Tix ... In-Reply-To: References: <96081377-E75A-427D-A9CD-02D8A5CD32A7@macports.org> Message-ID: I am hoping the maintainer of the tcl and tk ports can explain the odd behavior I am seeing. On Mar 22, 2009, at 09:15, R. Pito Salas wrote: > Ryan > > I saw your post on the ticket. Does it mean that I am SOL or are > you looking at it still? > > Thanks, > > Pito > > On Mar 21, 2009, at 6:43 PM, Ryan Schmidt wrote: > >> >> On Mar 21, 2009, at 14:38, R. Pito Salas wrote: >> >>> I am trying to get an application running which is in Python, and >>> in turn invokes Tcl to use Tix. >> >> [snip] >> >>> The most logical thing would be to install Tix with MacPorts, so >>> that, in theory all will be tied together, but I don't think >>> there's a MacPorts Tix Port, is there? >> >> One has been submitted, but not committed: >> >> http://trac.macports.org/ticket/17191 >> >> Looking at it now, I see the port has several problems. I will try >> to fix them. Please check the ticket in a little bit. >> >> > From paul.sijpkes at gmail.com Sun Mar 22 18:38:17 2009 From: paul.sijpkes at gmail.com (Paul Sijpkes) Date: Mon, 23 Mar 2009 12:38:17 +1100 Subject: Cannot access rsync.macports.org In-Reply-To: References: <05A6BEC1-4905-437C-B59D-ADEF8B1778F8@gmail.com> <722C2F95-7FD4-4359-AC2C-78841838BB67@gmail.com> <49C6E232.806@macports.org> Message-ID: <498DEBDB-4376-4247-8F2A-4B50D8FEDBB3@gmail.com> Just a minute... it says connection refused, not that it was not found... This is my selfupdate output... any ideas anyone? sudo port -dv selfupdate Password: DEBUG: Synchronizing ports tree(s) Synchronizing local ports tree from rsync://rsync.macports.org/release/ ports/ DEBUG: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/ release/ports/ /opt/local/var/macports/sources/rsync.macports.org/ release/ports rsync: failed to connect to rsync.macports.org: Connection refused (61) rsync error: error in socket IO (code 10) at /SourceCache/rsync/ rsync-35.2/rsync/clientserver.c(105) [receiver=2.6.9] Error: Synchronization of the local ports tree failed doing rsync DEBUG: Couldn't sync the ports tree: Synchronization of 1 source(s) failed while executing "macports::selfupdate [array get global_options]" Error: /opt/local/bin/port: port selfupdate failed: Couldn't sync the ports tree: Synchronization of 1 source(s) failed On 23/03/2009, at 12:34 PM, Paul Sijpkes wrote: > Thanks for your help Joshua, > > Tried telneting, but still no luck... must be an ISP issue. > Am I missing something? > > telnet rsync.macports.org 873 > > Trying 17.254.17.246... > telnet: connect to address 17.254.17.246: Connection refused > telnet: Unable to connect to remote host > > cheers, > Paul > > On 23/03/2009, at 12:13 PM, Joshua Root wrote: > >> Paul Sijpkes wrote: >>> Hi all, >>> >>> I just installed MacPorts 1.7.0 and my machine cannot access the >>> rsync URL >>> rsync.macports.org when I use the port -d selfupdate command. >>> >>> Strangely enough, the url that ping looks up (alpha.osforge.org) >>> works >>> in a browser, >>> so this indicates Port 80 is open. Is it possible that whichever >>> port >>> that RSYNC uses is >>> blocked by my ISP? I've never had anything else blocked by them, so >>> this would be odd... >>> >>> I've checked my firewall setting and tried pinging the above >>> addresses, >>> but I have no access. >>> Before I contact my ISP, I'd just like to make sure that the server >>> still exists and also find out >>> which port that selfupdate uses with rsync. >>> >>> Thanks for any help on this matter, >>> Paul >> >> It should definitely be working. Rsync uses TCP port 873, check if >> you >> can telnet to that port on rsync.macports.org. >> >> If it is being blocked, there are some alternatives: >> >> >> >> - Josh > From jmr at macports.org Sun Mar 22 18:48:37 2009 From: jmr at macports.org (Joshua Root) Date: Mon, 23 Mar 2009 12:48:37 +1100 Subject: Cannot access rsync.macports.org In-Reply-To: References: <05A6BEC1-4905-437C-B59D-ADEF8B1778F8@gmail.com> <722C2F95-7FD4-4359-AC2C-78841838BB67@gmail.com> <49C6E232.806@macports.org> Message-ID: <49C6EA75.5050507@macports.org> Paul Sijpkes wrote: > Thanks for your help Joshua, > > Tried telneting, but still no luck... must be an ISP issue. > Am I missing something? > > telnet rsync.macports.org 873 > > Trying 17.254.17.246... > telnet: connect to address 17.254.17.246: Connection refused > telnet: Unable to connect to remote host If it's not being blocked by something on your network, then yes, your ISP would be the prime suspect. If you weren't able to access macosforge in a browser I'd ask if you were running PeerGuardian. - Josh From paul.sijpkes at gmail.com Sun Mar 22 18:51:06 2009 From: paul.sijpkes at gmail.com (Paul Sijpkes) Date: Mon, 23 Mar 2009 12:51:06 +1100 Subject: Cannot access rsync.macports.org In-Reply-To: <498DEBDB-4376-4247-8F2A-4B50D8FEDBB3@gmail.com> References: <05A6BEC1-4905-437C-B59D-ADEF8B1778F8@gmail.com> <722C2F95-7FD4-4359-AC2C-78841838BB67@gmail.com> <49C6E232.806@macports.org> <498DEBDB-4376-4247-8F2A-4B50D8FEDBB3@gmail.com> Message-ID: Okay, there was ticket opened on this about 18 months ago, number #12684. Says that if you are running PeerGuardian then it blocks incoming connections from that socket. I've killed peerguardian, but it's still happening... Is there any other process that could do this? On 23/03/2009, at 12:38 PM, Paul Sijpkes wrote: > Just a minute... > > it says connection refused, not that it was not found... > > This is my selfupdate output... any ideas anyone? > > sudo port -dv selfupdate > Password: > DEBUG: Synchronizing ports tree(s) > Synchronizing local ports tree from rsync://rsync.macports.org/ > release/ports/ > DEBUG: /usr/bin/rsync -rtzv --delete-after rsync:// > rsync.macports.org/release/ports/ /opt/local/var/macports/sources/ > rsync.macports.org/release/ports > rsync: failed to connect to rsync.macports.org: Connection refused > (61) > rsync error: error in socket IO (code 10) at /SourceCache/rsync/ > rsync-35.2/rsync/clientserver.c(105) [receiver=2.6.9] > Error: Synchronization of the local ports tree failed doing rsync > DEBUG: Couldn't sync the ports tree: Synchronization of 1 source(s) > failed > while executing > "macports::selfupdate [array get global_options]" > Error: /opt/local/bin/port: port selfupdate failed: Couldn't sync > the ports tree: Synchronization of 1 source(s) failed > > > On 23/03/2009, at 12:34 PM, Paul Sijpkes wrote: > >> Thanks for your help Joshua, >> >> Tried telneting, but still no luck... must be an ISP issue. >> Am I missing something? >> >> telnet rsync.macports.org 873 >> >> Trying 17.254.17.246... >> telnet: connect to address 17.254.17.246: Connection refused >> telnet: Unable to connect to remote host >> >> cheers, >> Paul >> >> On 23/03/2009, at 12:13 PM, Joshua Root wrote: >> >>> Paul Sijpkes wrote: >>>> Hi all, >>>> >>>> I just installed MacPorts 1.7.0 and my machine cannot access the >>>> rsync URL >>>> rsync.macports.org when I use the port -d selfupdate command. >>>> >>>> Strangely enough, the url that ping looks up (alpha.osforge.org) >>>> works >>>> in a browser, >>>> so this indicates Port 80 is open. Is it possible that whichever >>>> port >>>> that RSYNC uses is >>>> blocked by my ISP? I've never had anything else blocked by them, >>>> so >>>> this would be odd... >>>> >>>> I've checked my firewall setting and tried pinging the above >>>> addresses, >>>> but I have no access. >>>> Before I contact my ISP, I'd just like to make sure that the server >>>> still exists and also find out >>>> which port that selfupdate uses with rsync. >>>> >>>> Thanks for any help on this matter, >>>> Paul >>> >>> It should definitely be working. Rsync uses TCP port 873, check if >>> you >>> can telnet to that port on rsync.macports.org. >>> >>> If it is being blocked, there are some alternatives: >>> >>> >>> >>> - Josh >> > From jmr at macports.org Sun Mar 22 18:54:55 2009 From: jmr at macports.org (Joshua Root) Date: Mon, 23 Mar 2009 12:54:55 +1100 Subject: Cannot access rsync.macports.org In-Reply-To: References: <05A6BEC1-4905-437C-B59D-ADEF8B1778F8@gmail.com> <722C2F95-7FD4-4359-AC2C-78841838BB67@gmail.com> <49C6E232.806@macports.org> <498DEBDB-4376-4247-8F2A-4B50D8FEDBB3@gmail.com> Message-ID: <49C6EBEF.60409@macports.org> Paul Sijpkes wrote: > Okay, there was ticket opened on this about 18 months ago, number #12684. > Says that if you are running PeerGuardian then it blocks incoming > connections from that socket. > > I've killed peerguardian, but it's still happening... > Is there any other process that could do this? IIRC, you have unload the PG kext, which often trips people up. - Josh From paul.sijpkes at gmail.com Sun Mar 22 18:59:37 2009 From: paul.sijpkes at gmail.com (Paul Sijpkes) Date: Mon, 23 Mar 2009 12:59:37 +1100 Subject: Cannot access rsync.macports.org In-Reply-To: <49C6EBEF.60409@macports.org> References: <05A6BEC1-4905-437C-B59D-ADEF8B1778F8@gmail.com> <722C2F95-7FD4-4359-AC2C-78841838BB67@gmail.com> <49C6E232.806@macports.org> <498DEBDB-4376-4247-8F2A-4B50D8FEDBB3@gmail.com> <49C6EBEF.60409@macports.org> Message-ID: <9C054739-9B6C-421C-8F08-A616047A210C@gmail.com> How do I do that? Sorry I'm very new to Macs, moved from Linux. What's the process called? On 23/03/2009, at 12:54 PM, Joshua Root wrote: > Paul Sijpkes wrote: >> Okay, there was ticket opened on this about 18 months ago, number >> #12684. >> Says that if you are running PeerGuardian then it blocks incoming >> connections from that socket. >> >> I've killed peerguardian, but it's still happening... >> Is there any other process that could do this? > > IIRC, you have unload the PG kext, which often trips people up. > > - Josh From paul.sijpkes at gmail.com Sun Mar 22 19:36:57 2009 From: paul.sijpkes at gmail.com (Paul Sijpkes) Date: Mon, 23 Mar 2009 13:36:57 +1100 Subject: Cannot access rsync.macports.org In-Reply-To: <982256E9-B7E2-4C46-9BD1-5FF1E16B3061@gmail.com> References: <05A6BEC1-4905-437C-B59D-ADEF8B1778F8@gmail.com> <722C2F95-7FD4-4359-AC2C-78841838BB67@gmail.com> <49C6E232.806@macports.org> <498DEBDB-4376-4247-8F2A-4B50D8FEDBB3@gmail.com> <49C6EBEF.60409@macports.org> <9C054739-9B6C-421C-8F08-A616047A210C@gmail.com> <982256E9-B7E2-4C46-9BD1-5FF1E16B3061@gmail.com> Message-ID: <7D37DA51-2718-4164-8315-F24B7C696138@gmail.com> I've solved the problem... sudo kextunload -b xxx.qnation.PeerGuardian unloads PG. Maybe this problem should be included in the FAQs? Thanks for the help Joshua! On 23/03/2009, at 1:06 PM, Paul Sijpkes wrote: > Okay, I've killed all PG processes, but it's still happening. I'm > assuming your talking about a Kernel extension or something, right? > How do I unload this from the kernel? > > On 23/03/2009, at 12:59 PM, Paul Sijpkes wrote: > >> How do I do that? Sorry I'm very new to Macs, moved from Linux. >> What's the process called? >> >> On 23/03/2009, at 12:54 PM, Joshua Root wrote: >> >>> Paul Sijpkes wrote: >>>> Okay, there was ticket opened on this about 18 months ago, >>>> number #12684. >>>> Says that if you are running PeerGuardian then it blocks incoming >>>> connections from that socket. >>>> >>>> I've killed peerguardian, but it's still happening... >>>> Is there any other process that could do this? >>> >>> IIRC, you have unload the PG kext, which often trips people up. >>> >>> - Josh >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Sun Mar 22 20:02:26 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sun, 22 Mar 2009 22:02:26 -0500 Subject: Cannot access rsync.macports.org In-Reply-To: <7D37DA51-2718-4164-8315-F24B7C696138@gmail.com> References: <05A6BEC1-4905-437C-B59D-ADEF8B1778F8@gmail.com> <722C2F95-7FD4-4359-AC2C-78841838BB67@gmail.com> <49C6E232.806@macports.org> <498DEBDB-4376-4247-8F2A-4B50D8FEDBB3@gmail.com> <49C6EBEF.60409@macports.org> <9C054739-9B6C-421C-8F08-A616047A210C@gmail.com> <982256E9-B7E2-4C46-9BD1-5FF1E16B3061@gmail.com> <7D37DA51-2718-4164-8315-F24B7C696138@gmail.com> Message-ID: On Mar 22, 2009, at 21:36, Paul Sijpkes wrote: > I've solved the problem... > > sudo kextunload -b xxx.qnation.PeerGuardian > > unloads PG. > > Maybe this problem should be included in the FAQs? It is in the FAQ: http://trac.macports.org/wiki/ FAQ#WhatdoIdoifportselfupdatedoesntworkortheRsyncserverrefusesconnection s Please feel free to expand the FAQ entry if necessary. Someone who has experienced the issue and knows what was necessary to fix it is best equipped to make changes to the entry to assist others. From talklists at newgeo.com Sun Mar 22 21:46:20 2009 From: talklists at newgeo.com (Scott Haneda) Date: Sun, 22 Mar 2009 21:46:20 -0700 Subject: Cannot access rsync.macports.org In-Reply-To: <722C2F95-7FD4-4359-AC2C-78841838BB67@gmail.com> References: <05A6BEC1-4905-437C-B59D-ADEF8B1778F8@gmail.com> <722C2F95-7FD4-4359-AC2C-78841838BB67@gmail.com> Message-ID: <42D75678-55AF-45AB-A294-3E7F876ECBA7@newgeo.com> Find out the port and telnet to it. If you can, its an issue with ports or your config. If you can not, it is an issue with your network or settings. -- Scott Iphone says hello. On Mar 22, 2009, at 6:02 PM, Paul Sijpkes wrote: > Hi all, > > I just installed MacPorts 1.7.0 and my machine cannot access the > rsync URL > rsync.macports.org when I use the port -d selfupdate command. > > Strangely enough, the url that ping looks up (alpha.osforge.org) > works in a browser, > so this indicates Port 80 is open. Is it possible that whichever > port that RSYNC uses is > blocked by my ISP? I've never had anything else blocked by them, so > this would be odd... > > I've checked my firewall setting and tried pinging the above > addresses, but I have no access. > Before I contact my ISP, I'd just like to make sure that the server > still exists and also find out > which port that selfupdate uses with rsync. > > Thanks for any help on this matter, > Paul > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From dweber at macports.org Sun Mar 22 22:54:14 2009 From: dweber at macports.org (Darren Weber) Date: Sun, 22 Mar 2009 22:54:14 -0700 Subject: port install efficiency issue In-Reply-To: <49C6DDC1.6000405@macports.org> References: <49C6437A.5040807@macports.org> <2C269F10-9498-4759-8668-4603FBAB6524@comcast.net> <20090322202712.GC812@ninagal.withay.com> <3FFC1539-E7C9-4CEC-AF38-DD2DE12D7F44@newgeo.com> <49C6DDC1.6000405@macports.org> Message-ID: Is it possible to create a distributed build system that uses Xgrid, to allow all macport users the option of adding their machine to a distributed macports build system? In effect, every time anybody on this grid has to build a package from source, some kind of meta-package monitor can detect whether the build and install was successful and then make an inquiry of a central managment system as to whether or not this build should be added to the mirrors for binary distributions. If this inquiry was made before the build and a binary is available somewhere, the system simply downloads the binary (perhaps a torrent system). If the binary is not available, the build proceeds. If it's successful, the outcome of the build is added to the binary downloads available (ie, uploaded and distributed to mirrors to become an effective part of a torrent download system). Also, perhaps the Xgrid system can be used to create a distributed build system, regardless of what packages a user installs, but make sure that it uses idle systems (a lot like the scheduled builds of older days). For example: http://cmgm.stanford.edu/~cparnot/xgrid-stanford/ http://www.apple.com/downloads/dashboard/status/xgridstanford.html On Sun, Mar 22, 2009 at 5:54 PM, Joshua Root wrote: > Scott Haneda wrote: > > Can we talk more about this? I have the ability to host such a build > > farm. Now, I could not host one machine, of every architecture, of > > every OS, I just do not have the room in colocation. > > > > I do have quite a bit of room if we go 1U though. So 2 1U machines, a > > PPC and a Intel, and I would imagine, that PPC machine could go away a > > lot sooner than we all think. Mac Mini's could take it further, since > > they are so small, 8 of them can fit on a shelf and occupy no more than > > a few U's of space. The damn power bricks are more an issue than > > anything else. There have to be PPC Mini's out there to be had. > > > > As long as the various OS versions could be virtualized, so we could > > have 10.3, 10.4, 10.5, 10.6 and forward virtualized on each machine, it > > would not at all be hard to come up with a authentication routine to > > allow builds to happen on whatever virtual interface you want. > > > > I have the Ip space to spare, so each virtual machine could have it's > > own connection space, or we could do some simple dhcp pooling. Static > > IP's are something I was alloted a /24 of, and do not see giving up 20 > > or so of them being an issue. > > > > Am I looking at this wrong, or would this be helpful? Is this too much > > reliance on an outside party for core ports features? I have had access > > to this data center for 9+ years or so, I do not plan on giving up that > > access at any time soon. The bandwidth requirements are minimal, it > > would go unnoticed. > > Thanks for the offer. I think it's safe to say, though, that finding the > hardware for a build farm will be a relatively minor issue. > > The main thing that is needed is the software. Server-side, to build all > the ports in some kind of intelligent order and copy the archives to > somewhere from which they can be downloaded by the client, with error > reporting; and to keep doing this as needed when new versions and new > ports are added. > > Client-side, to check for the presence of an archive with the desired > version/variants on the server, and to download and unarchive it instead > of building from source when possible. > > - Josh > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dweber at macports.org Sun Mar 22 23:06:11 2009 From: dweber at macports.org (Darren Weber) Date: Sun, 22 Mar 2009 23:06:11 -0700 Subject: stable vs. unstable ports? In-Reply-To: <49C6D55C.7050709@macports.org> References: <49C6D55C.7050709@macports.org> Message-ID: I like the idea of an opt-in Xgrid system, whereby users could opt-in to install an Xgrid client that provides a macports build system, binary distributions, and meta-ports monitor. Of course, some folks might interpret it as too much big-brother, but really it's just so common now to have integrated network clusters with two-way traffic. The opt-in and security settings on the facility may need integrity checking (code review - so specific commit rights and few maintainers with security access) and community monitoring to ensure security. Just about every major desktop system around has some kind of automated process monitoring and opt-in bug reporting (windows, mac OSX, gnome, etc.). I guess that Xgrid provides a nice platform for a distributed build system. I have no idea where to start with macports base. If I had time to learn it, I would try. Even so, I would hate to screw around with it without knowing what I'm doing. Is there any documentation on how to get started with hacking macports base - any kind of sandbox to play around with? Anyone know how to work with Xgrid? It's something on my todo list, but I've not read anything about it yet. Take care, Darren On Sun, Mar 22, 2009 at 5:18 PM, Joshua Root wrote: > Darren Weber wrote: > > > > I've noticed problems during port upgrades. > > > > What is the general consensus on having a TAG for each port to indicate > > it's "success" status within the system? > > > > Is it possible to have a meta-port monitor that automatically tracks the > > status of each package install and reports that status back to a central > > repository to continuously flag the status of a port install. A simple > > dichotomy of stable and unstable might suffice (Debian uses stable, > > unstable, and testing). Perhaps the monitoring system could provide the > > data required to justify these port status levels. > > IIRC, last time something like this was proposed, the consensus was that > "phoning home" is evil and MacPorts shouldn't do it. (The focus then was > more on collecting stats on how often each port is used.) Personally I > don't see what the problem is as long as it's opt-in. > > Of course, if we had a build farm producing binaries (see discussion > currently ongoing), this information could also be produced by it > incidentally to its main function. > > - Josh > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dweber at macports.org Sun Mar 22 23:11:17 2009 From: dweber at macports.org (Darren Weber) Date: Sun, 22 Mar 2009 23:11:17 -0700 Subject: compile farm? In-Reply-To: <49C6AADC.2080604@macports.org> References: <49C6AADC.2080604@macports.org> Message-ID: An Xgrid system? On Sun, Mar 22, 2009 at 2:17 PM, Rainer M?ller wrote: > Darren Weber wrote: > > > > Is it possible to use the sourceforge compile farm to provide binary > > distros for macports? > > The sourceforge compile farm does not exist any more for at least two > years now. > > Rainer > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryandesign at macports.org Mon Mar 23 00:33:27 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 23 Mar 2009 02:33:27 -0500 Subject: compile farm? In-Reply-To: References: <49C6AADC.2080604@macports.org> Message-ID: <747E5C62-6A3A-4555-B748-A79C099D8F91@macports.org> On Mar 23, 2009, at 01:11, Darren Weber wrote: > On Sun, Mar 22, 2009 at 2:17 PM, Rainer M?ller wrote: > >> Darren Weber wrote: >> >> > Is it possible to use the sourceforge compile farm to provide >> binary >> > distros for macports? >> >> The sourceforge compile farm does not exist any more for at least two >> years now. > > An Xgrid system? As stated in "Re: port install efficiency issue", finding computers to serve as a build farm should not be a problem. I believe our Apple representatives have even offered such resources already. What we need to discuss is how the build farm would work. Someone (apologies; I forget who) already worked on a script to build a port in a clean environment. I think what still is needed is to then package that up and send it to a download server. Then we need code in the MacPorts base code to check for and if available download those binaries instead of building from source. From ryandesign at macports.org Mon Mar 23 00:38:12 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 23 Mar 2009 02:38:12 -0500 Subject: stable vs. unstable ports? In-Reply-To: References: <49C6D55C.7050709@macports.org> Message-ID: <64FEDC27-0878-4A20-8281-1BEA112D43D0@macports.org> On Mar 23, 2009, at 01:06, Darren Weber wrote: > I like the idea of an opt-in Xgrid system, whereby users could opt- > in to install an Xgrid client that provides a macports build > system, binary distributions, and meta-ports monitor. Of course, > some folks might interpret it as too much big-brother, but really > it's just so common now to have integrated network clusters with > two-way traffic. The opt-in and security settings on the facility > may need integrity checking (code review - so specific commit > rights and few maintainers with security access) and community > monitoring to ensure security. Just about every major desktop > system around has some kind of automated process monitoring and opt- > in bug reporting (windows, mac OSX, gnome, etc.). I guess that > Xgrid provides a nice platform for a distributed build system. > > I have no idea where to start with macports base. If I had time to > learn it, I would try. Even so, I would hate to screw around with > it without knowing what I'm doing. Is there any documentation on > how to get started with hacking macports base - any kind of sandbox > to play around with? > > Anyone know how to work with Xgrid? It's something on my todo > list, but I've not read anything about it yet. Before we can allow arbitrary users to submit their builds to a central server, we would need to ensure that a build that occurs on one user's system is *identical* to the build on any other user's computer. This cannot currently be assured because MacPorts does not build in a chroot, and without this, it is possible for a port to link with libraries that happen to be on the user's system that it ought not link with -- be they libraries from other ports on which the port in question does not declare a dependency, or libraries in / usr/local, to which the compiler always looks. Therefore, a build farm that we control is a better option. Which, as explained in other threads, cannot happen until the software to do the automated builds in the clean environment is written. From ryandesign at macports.org Mon Mar 23 00:47:08 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Mon, 23 Mar 2009 02:47:08 -0500 Subject: port install efficiency issue In-Reply-To: References: <49C6437A.5040807@macports.org> <2C269F10-9498-4759-8668-4603FBAB6524@comcast.net> Message-ID: On Mar 22, 2009, at 13:19, Darren Weber wrote: > On balance, I'm both impressed and disappointed with the complexity > of the macports system to date. For example, dependency resolution > needs a lot of work during upgrades, binary distributions are a > great idea in the making (perhaps forever in the making), and the > whole issue of dependency on variants is a massive conference > debate. I've certainly come across these issues and tried to > submit reasonable trac suggestions for enhancements, etc. on a > couple of ports. My main issue seems to be in getting a few ports > with a lot of dependencies to cooperate, esp. with regard to > variants (eg, Qt, Postgresql, MySQL, VTK, etc.). I do think that > package maintainers should think very carefully about their default > variants and try to provide as many options as possible - that > seems to be the way with Debian packages. Mac OS X is not Debian. The Mac way is to provide not as many options as possible, but as few options as possible. Meet the needs of most of the users with the default setup, and provide a few options for everyone else. As a consumer, I do not enjoy having to select amongst 37 different types of toothpaste at the grocery store. More choices is not always better. http://www.cafeaulait.org/images/remotes.png From trog24 at comcast.net Mon Mar 23 01:08:50 2009 From: trog24 at comcast.net (Frank J. R. Hanstick) Date: Mon, 23 Mar 2009 01:08:50 -0700 Subject: port install efficiency issue In-Reply-To: References: <49C6437A.5040807@macports.org> <2C269F10-9498-4759-8668-4603FBAB6524@comcast.net> Message-ID: On Mar 23, 2009, at 12:47 AM, Ryan Schmidt wrote: > > On Mar 22, 2009, at 13:19, Darren Weber wrote: > >> On balance, I'm both impressed and disappointed with the >> complexity of the macports system to date. For example, >> dependency resolution needs a lot of work during upgrades, binary >> distributions are a great idea in the making (perhaps forever in >> the making), and the whole issue of dependency on variants is a >> massive conference debate. I've certainly come across these >> issues and tried to submit reasonable trac suggestions for >> enhancements, etc. on a couple of ports. My main issue seems to >> be in getting a few ports with a lot of dependencies to cooperate, >> esp. with regard to variants (eg, Qt, Postgresql, MySQL, VTK, >> etc.). I do think that package maintainers should think very >> carefully about their default variants and try to provide as many >> options as possible - that seems to be the way with Debian packages. > > Mac OS X is not Debian. The Mac way is to provide not as many > options as possible, but as few options as possible. Meet the needs > of most of the users with the default setup, and provide a few > options for everyone else. > > As a consumer, I do not enjoy having to select amongst 37 different > types of toothpaste at the grocery store. More choices is not > always better. > > http://www.cafeaulait.org/images/remotes.png > Hello, The Mac way is to provide plug and play which includes software as well as hardware. Frank J. R. Hanstick trog24 at comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From raimue at macports.org Mon Mar 23 03:48:55 2009 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Mon, 23 Mar 2009 11:48:55 +0100 Subject: Python, Tcl, Tix ... In-Reply-To: References: <96081377-E75A-427D-A9CD-02D8A5CD32A7@macports.org> Message-ID: <49C76917.9090406@macports.org> Ryan Schmidt wrote: > I am hoping the maintainer of the tcl and tk ports can explain the > odd behavior I am seeing. Checking the Makefile after configure, there are problems with include paths in TCL_SRC_DIR, TK_SRC_DIR and INCLUDES (which uses TCL_INCLUDES and TK_INCLUDES). TCL_INCLUDES and TK_INCLUDES point to the build directories. But we cannot just put ${prefix}/include/tcl or ${prefix}/include/tk in here. The real problem is that our Tk installation is missing files which are for example shipped with the build from Apple. In particular where I discovered the first build error, Tix looks for tkInt.h which is missing. Apple ships it at: /System/Library/Frameworks/Tk.framework/Versions/8.4/Headers/tk-private/tkInt.h After 'port extract tk', it can be found at: $(port work tk)/tk8.5.6/generic/tkInt.h This port needs a similar approach as the tk port itself does. It extracts the Tcl source and has additional preprocessor flags to search there for include files: configure.cppflags "-I${workpath}/tcl${version}/generic" Or we need to copy these private header files to the usual include location. Maybe it would be good to ask upstream on the Tcl mailing list for advice on this topic. Rainer From jmr at macports.org Mon Mar 23 06:16:43 2009 From: jmr at macports.org (Joshua Root) Date: Tue, 24 Mar 2009 00:16:43 +1100 Subject: stable vs. unstable ports? In-Reply-To: <64FEDC27-0878-4A20-8281-1BEA112D43D0@macports.org> References: <49C6D55C.7050709@macports.org> <64FEDC27-0878-4A20-8281-1BEA112D43D0@macports.org> Message-ID: <49C78BBB.8080008@macports.org> Ryan Schmidt wrote: > > On Mar 23, 2009, at 01:06, Darren Weber wrote: > >> I like the idea of an opt-in Xgrid system, whereby users could opt-in >> to install an Xgrid client that provides a macports build system, >> binary distributions, and meta-ports monitor. Of course, some folks >> might interpret it as too much big-brother, but really it's just so >> common now to have integrated network clusters with two-way traffic. >> The opt-in and security settings on the facility may need integrity >> checking (code review - so specific commit rights and few maintainers >> with security access) and community monitoring to ensure security. >> Just about every major desktop system around has some kind of >> automated process monitoring and opt-in bug reporting (windows, mac >> OSX, gnome, etc.). I guess that Xgrid provides a nice platform for a >> distributed build system. > > Before we can allow arbitrary users to submit their builds to a central > server, we would need to ensure that a build that occurs on one user's > system is *identical* to the build on any other user's computer. This > cannot currently be assured because MacPorts does not build in a chroot, > and without this, it is possible for a port to link with libraries that > happen to be on the user's system that it ought not link with -- be they > libraries from other ports on which the port in question does not > declare a dependency, or libraries in /usr/local, to which the compiler > always looks. > > Therefore, a build farm that we control is a better option. Which, as > explained in other threads, cannot happen until the software to do the > automated builds in the clean environment is written. Quite aside from bugs in MP, we have no way of knowing whether downright malicious changes have been made in user-submitted binaries. TBH, I'm already a little uncomfortable about the ports tree being mirrored, since unlike distfiles there is no system in place to verify the integrity of those files. Portfiles can at least be verified by inspection, but binaries cannot. So I don't think we can accept binaries from users no matter how bug-free base becomes. This doesn't preclude users from sharing their own collections of binaries, but using them would have to be a matter of trust between the user and the provider. - Josh From cerieljacobs at gmail.com Mon Mar 23 09:22:55 2009 From: cerieljacobs at gmail.com (Ceriel Jacobs) Date: Mon, 23 Mar 2009 17:22:55 +0100 Subject: Cannot access rsync.macports.org Message-ID: If you run LittleSnitch create a rule for rsync (/usr/bin/rsync) that allows connections to server hostname rsync.macports.org, port 873, protocol 6 (TCP). Make sure the rule is enabled. From brad at pixilla.com Mon Mar 23 09:37:31 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Mon, 23 Mar 2009 09:37:31 -0700 Subject: port install efficiency issue In-Reply-To: References: <49C6437A.5040807@macports.org> <2C269F10-9498-4759-8668-4603FBAB6524@comcast.net> Message-ID: <8AD2E5DF-7CDE-4C18-86B1-AA151384096F@pixilla.com> On Mar 23, 2009, at 1:08 AM, Frank J. R. Hanstick wrote: > > On Mar 23, 2009, at 12:47 AM, Ryan Schmidt wrote: > >> >> On Mar 22, 2009, at 13:19, Darren Weber wrote: >> >>> On balance, I'm both impressed and disappointed with the >>> complexity of the macports system to date. For example, >>> dependency resolution needs a lot of work during upgrades, binary >>> distributions are a great idea in the making (perhaps forever in >>> the making), and the whole issue of dependency on variants is a >>> massive conference debate. I've certainly come across these >>> issues and tried to submit reasonable trac suggestions for >>> enhancements, etc. on a couple of ports. My main issue seems to >>> be in getting a few ports with a lot of dependencies to cooperate, >>> esp. with regard to variants (eg, Qt, Postgresql, MySQL, VTK, >>> etc.). I do think that package maintainers should think very >>> carefully about their default variants and try to provide as many >>> options as possible - that seems to be the way with Debian packages. >> >> Mac OS X is not Debian. The Mac way is to provide not as many >> options as possible, but as few options as possible. Meet the needs >> of most of the users with the default setup, and provide a few >> options for everyone else. A wonderful tradeoff. Macports also makes it VERY easy to create a local port when the port doesn't meet your needs. >> As a consumer, I do not enjoy having to select amongst 37 different >> types of toothpaste at the grocery store. More choices is not >> always better. I like 3 :) >> http://www.cafeaulait.org/images/remotes.png >> > Hello, > The Mac way is to provide plug and play which includes software as > well as hardware. > Frank J. R. Hanstick The Mac way is to hide the complexity. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dweber at macports.org Mon Mar 23 10:44:59 2009 From: dweber at macports.org (Darren Weber) Date: Mon, 23 Mar 2009 10:44:59 -0700 Subject: compile farm? In-Reply-To: <747E5C62-6A3A-4555-B748-A79C099D8F91@macports.org> References: <49C6AADC.2080604@macports.org> <747E5C62-6A3A-4555-B748-A79C099D8F91@macports.org> Message-ID: On Mon, Mar 23, 2009 at 12:33 AM, Ryan Schmidt wrote: > On Mar 23, 2009, at 01:11, Darren Weber wrote: > > On Sun, Mar 22, 2009 at 2:17 PM, Rainer M?ller wrote: >> >> Darren Weber wrote: >>> >>> > Is it possible to use the sourceforge compile farm to provide binary >>> > distros for macports? >>> >>> The sourceforge compile farm does not exist any more for at least two >>> years now. >>> >> >> An Xgrid system? >> > > As stated in "Re: port install efficiency issue", finding computers to > serve as a build farm should not be a problem. I believe our Apple > representatives have even offered such resources already. What we need to > discuss is how the build farm would work. Someone (apologies; I forget who) > already worked on a script to build a port in a clean environment. I think > what still is needed is to then package that up and send it to a download > server. Then we need code in the MacPorts base code to check for and if > available download those binaries instead of building from source. > > This suggestion may be too complicated, but it's a thought. Suppose it is possible to create a "virtual machine" or some kind of encapsulated "clean environment" (perhaps like a java sdk or something), which can contain any of the environments for OSX (10.x), or at least a standardized subset that is required by default for macports builds. Suppose such an environment could be run from within any OSX system as a virtual machine. Suppose such a "virtual environment" could be distributed on an Xgrid system, it could provide a distributed build system for macports. OK, back to reality... -------------- next part -------------- An HTML attachment was scrubbed... URL: From dweber at macports.org Mon Mar 23 11:12:39 2009 From: dweber at macports.org (Darren Weber) Date: Mon, 23 Mar 2009 11:12:39 -0700 Subject: port install efficiency issue In-Reply-To: References: <49C6437A.5040807@macports.org> <2C269F10-9498-4759-8668-4603FBAB6524@comcast.net> Message-ID: On Mon, Mar 23, 2009 at 12:47 AM, Ryan Schmidt wrote: > > On Mar 22, 2009, at 13:19, Darren Weber wrote: > > On balance, I'm both impressed and disappointed with the complexity of the >> macports system to date. For example, dependency resolution needs a lot of >> work during upgrades, binary distributions are a great idea in the making >> (perhaps forever in the making), and the whole issue of dependency on >> variants is a massive conference debate. I've certainly come across these >> issues and tried to submit reasonable trac suggestions for enhancements, >> etc. on a couple of ports. My main issue seems to be in getting a few ports >> with a lot of dependencies to cooperate, esp. with regard to variants (eg, >> Qt, Postgresql, MySQL, VTK, etc.). I do think that package maintainers >> should think very carefully about their default variants and try to provide >> as many options as possible - that seems to be the way with Debian packages. >> > > Mac OS X is not Debian. The Mac way is to provide not as many options as > possible, but as few options as possible. Meet the needs of most of the > users with the default setup, and provide a few options for everyone else. > > As a consumer, I do not enjoy having to select amongst 37 different types > of toothpaste at the grocery store. More choices is not always better. > > http://www.cafeaulait.org/images/remotes.png > > Well, most of the free software in macports is not programmed for OSX. It's mostly c and c++ programs that are designed for BSD or GNU/Linux (and other free operating systems). I think it is wise to learn from the lessons of those operating systems and distributions (eg, BSD, Debian, etc.). Although I too appreciate Apple design principles and I do enjoy learning more about the OSX platform, I do think that the majority of packages in macports were designed decades before Apple jumped onto BSD, so those different design fundamentals have been tried and tested and I think macports does and should respect that. Hence, when I look at a Portfile, I also take a little time to check out darwinports and Debian packages to learn something about how these software are built and distributed. Let's not forget that Apple is now a big player in major packages used in the free software system. Apple contribute to GCC and I think they now own CUPS (http://www.cups.org/). I think congratulations to Apple (NeXTStep) for making a wise move to a solid platform and moving forward with the open-source community (OpenStep, etc.). OSX is very interesting combination of free software and licenced layers on top. For the most part, we interact with the licenced layers without seeing the foundations, but please never forget that those foundations have all the design features that support everything on OSX. I assume many of those same foundations are a part of just about every free operating system that has a *nix flavour to it. Take care, Darren PS, As for plug and play, my experience with Debian (incl. Ubuntu) is just that; plug and play (for the most part). The entire system is designed, built, and *tested* from the ground up, and it's all free software. Package dependency and conflict resolution is usually right-on and the binary distros install fast. The system even cleans up older packages that are no longer required. I assume all of this is why fink opted to bring that distribution system onto OSX. If your curious and you've never read it, please do take a look at the basics of Debian package management: http://www.debian.org/doc/FAQ/ch-pkg_basics.en.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From afb at macports.org Mon Mar 23 11:18:13 2009 From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=) Date: Mon, 23 Mar 2009 19:18:13 +0100 Subject: compile farm? In-Reply-To: References: <49C6AADC.2080604@macports.org> <747E5C62-6A3A-4555-B748-A79C099D8F91@macports.org> Message-ID: Darren Weber wrote: > This suggestion may be too complicated, but it's a thought. > Suppose it is possible to create a "virtual machine" or some kind > of encapsulated "clean environment" (perhaps like a java sdk or > something), which can contain any of the environments for OSX > (10.x), or at least a standardized subset that is required by > default for macports builds. Suppose such an environment could be > run from within any OSX system as a virtual machine. Suppose such a > "virtual environment" could be distributed on an Xgrid system, it > could provide a distributed build system for macports. This is called a "chroot", and is what MPAB uses to build. See http://trac.macports.org/wiki/MPAB for all the details. > OK, back to reality... Has been for a long time. --anders From jmr at macports.org Mon Mar 23 11:58:00 2009 From: jmr at macports.org (Joshua Root) Date: Tue, 24 Mar 2009 05:58:00 +1100 Subject: port install efficiency issue In-Reply-To: References: <49C6437A.5040807@macports.org> <2C269F10-9498-4759-8668-4603FBAB6524@comcast.net> Message-ID: <49C7DBB8.4090803@macports.org> Darren Weber wrote: > when I look at a Portfile, I also take a little time to check out > darwinports and Debian packages to learn something about how these > software are built and distributed. I'm confused - is this a slip of the keyboard? DarwinPorts no longer exists, the name changed to MacPorts a few years ago. - Josh From dweber at macports.org Mon Mar 23 12:05:06 2009 From: dweber at macports.org (Darren Weber) Date: Mon, 23 Mar 2009 12:05:06 -0700 Subject: compile farm? In-Reply-To: References: <49C6AADC.2080604@macports.org> <747E5C62-6A3A-4555-B748-A79C099D8F91@macports.org> Message-ID: On Mon, Mar 23, 2009 at 11:18 AM, Anders F Bj?rklund wrote: > Darren Weber wrote: > > This suggestion may be too complicated, but it's a thought. Suppose it is >> possible to create a "virtual machine" or some kind of encapsulated "clean >> environment" (perhaps like a java sdk or something), which can contain any >> of the environments for OSX (10.x), or at least a standardized subset that >> is required by default for macports builds. Suppose such an environment >> could be run from within any OSX system as a virtual machine. Suppose such a >> "virtual environment" could be distributed on an Xgrid system, it could >> provide a distributed build system for macports. >> > > This is called a "chroot", and is what MPAB uses to build. > > See http://trac.macports.org/wiki/MPAB for all the details. > > OK, back to reality... >> > > Has been for a long time. > > --anders > > Hey, of course it exists! Why recreate the wheel? Yes, we are "Standing of the shoulders of giants." I have it running on my system now, to learn more about it. I have an OSX 10.5.6 Server on a mac pro (2x quad core zeons, 24 Gb RAM). First thing I note is that the ReadMe.txt contains instructions for an svn export. Two thoughts about that: (a) it can automated as part of the script, (b) it uses trunk, but that could be any branch of the svn (eg, stable, unstable, testing, etc. and I would equate trunk with "testing"). I haven't looked into mpab itself, yet. Can it detect the current platform and make reasonable changes to the chroot for 10.x variants? When I run it, should I pipe the output to a log file? Do you think it is possible to adapt this for Xgrid compilation? Is it possible to have (a) the chroot images distributed, and (b) to have each of the port builds farmed out to different nodes on the grid. I assume that dependency issues prevent (b), so parallel builds of individual packages are not possible - is that right? Nevertheless, it should be possible to farm out the entire autobuild to nodes on a grid for idle-time compilations. Take care, Darren -------------- next part -------------- An HTML attachment was scrubbed... URL: From dweber at macports.org Mon Mar 23 12:15:38 2009 From: dweber at macports.org (Darren Weber) Date: Mon, 23 Mar 2009 12:15:38 -0700 Subject: port install efficiency issue In-Reply-To: <49C7DBB8.4090803@macports.org> References: <49C6437A.5040807@macports.org> <2C269F10-9498-4759-8668-4603FBAB6524@comcast.net> <49C7DBB8.4090803@macports.org> Message-ID: On Mon, Mar 23, 2009 at 11:58 AM, Joshua Root wrote: > Darren Weber wrote: > > when I look at a Portfile, I also take a little time to check out > > darwinports and Debian packages to learn something about how these > > software are built and distributed. > > I'm confused - is this a slip of the keyboard? DarwinPorts no longer > exists, the name changed to MacPorts a few years ago. > > - Josh > Sorry I should be referring to: http://www.freebsd.org/ports/ For example, http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/boaconstructor/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmr at macports.org Mon Mar 23 12:52:13 2009 From: jmr at macports.org (Joshua Root) Date: Tue, 24 Mar 2009 06:52:13 +1100 Subject: port install efficiency issue In-Reply-To: References: <49C6437A.5040807@macports.org> <2C269F10-9498-4759-8668-4603FBAB6524@comcast.net> <49C7DBB8.4090803@macports.org> Message-ID: <49C7E86D.1080902@macports.org> Darren Weber wrote: > > > On Mon, Mar 23, 2009 at 11:58 AM, Joshua Root > wrote: > > Darren Weber wrote: > > when I look at a Portfile, I also take a little time to check out > > darwinports and Debian packages to learn something about how these > > software are built and distributed. > > I'm confused - is this a slip of the keyboard? DarwinPorts no longer > exists, the name changed to MacPorts a few years ago. > > - Josh > > > > Not exactly, I still find examples of darwinports online, eg: > http://apache dot darwinports dot com/ > > Please enlighten me about this stuff. I thought darwinports were the > BSD variety, from which macports are copied or derived and adapted. I > sometimes get the impression these files are older than macports, yet I > do find them a helpful reference sometimes. - Josh From drf at blackchairdvd.com Mon Mar 23 13:00:39 2009 From: drf at blackchairdvd.com (drf) Date: Mon, 23 Mar 2009 20:00:39 +0000 Subject: php5 & "port test php5" Message-ID: <49C7EA67.9010101@blackchairdvd.com> Hi, My setup: Mac Mini, 10.4.11, Xcode 2.5, GCC 4, MacPorts 1.7 Everything compiles fine, there are some complaints about signedness from the compiler, but it all looks ok. But when I run the PHP test suite, over 70 tests fail, including ones I wouldn't really expect, like on the function easterdate(). I can not find any hints anywhere on what might be happening, so I'm wondering if these tests really are that important. Should a completely default, standard, stock install of php5 with MacPorts pass all the PHP self tests fine? The thing is, when I set up everything myself (not using MacPorts to compile php5) the same set of tests failed - the config of php5 did reference various macport installed libraries, etc. I am now at the point where I am wondering if I ought to toss all of MacPorts and try to install everything myself that is needed to compile php5. So any advice, pointers on where to look, or hints on 64 bit vs 32 would be greatly appreciated TIA doug From blb at macports.org Mon Mar 23 13:11:34 2009 From: blb at macports.org (Bryan Blackburn) Date: Mon, 23 Mar 2009 14:11:34 -0600 Subject: Python, Tcl, Tix ... In-Reply-To: <49C76917.9090406@macports.org> References: <96081377-E75A-427D-A9CD-02D8A5CD32A7@macports.org> <49C76917.9090406@macports.org> Message-ID: <20090323201134.GE564@ninagal.withay.com> On Mon, Mar 23, 2009 at 11:48:55AM +0100, Rainer M?ller said: [...] > The real problem is that our Tk installation is missing files which are > for example shipped with the build from Apple. In particular where I > discovered the first build error, Tix looks for tkInt.h which is missing. > > Apple ships it at: > /System/Library/Frameworks/Tk.framework/Versions/8.4/Headers/tk-private/tkInt.h > > After 'port extract tk', it can be found at: > $(port work tk)/tk8.5.6/generic/tkInt.h > > This port needs a similar approach as the tk port itself does. It > extracts the Tcl source and has additional preprocessor flags to search > there for include files: > configure.cppflags "-I${workpath}/tcl${version}/generic" > > Or we need to copy these private header files to the usual include > location. Maybe it would be good to ask upstream on the Tcl mailing list > for advice on this topic. Note that the same goes for the Tcl private headers, which is ticket #17189: Bryan > > Rainer From brad at pixilla.com Mon Mar 23 13:34:46 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Mon, 23 Mar 2009 13:34:46 -0700 Subject: php5 & "port test php5" In-Reply-To: <49C7EA67.9010101@blackchairdvd.com> References: <49C7EA67.9010101@blackchairdvd.com> Message-ID: On Mar 23, 2009, at 1:00 PM, drf wrote: > Hi, > > My setup: Mac Mini, 10.4.11, Xcode 2.5, GCC 4, MacPorts 1.7 > > Everything compiles fine, there are some complaints about signedness > from the compiler, but it all looks ok. But when I run the PHP test > suite, over 70 tests fail, including ones I wouldn't really expect, > like on the function easterdate(). I can not find any hints > anywhere on what might be happening, so I'm wondering if these tests > really are that important. Should a completely default, standard, > stock install of php5 with MacPorts pass all the PHP self tests fine? What are you commands are you executing and what are the results? I don't see a php function named easterdate. There is easter_date which appears to work fine on my php5 install. port installed [...] php5 @5.2.8_1+apache2+imap+macosx+mysql5+pear+pspell+readline+sqlite +tidy (active) > The thing is, when I set up everything myself (not using MacPorts to > compile php5) the same set of tests failed - the config of php5 did > reference various macport installed libraries, etc. I am now at the > point where I am wondering if I ought to toss all of MacPorts and > try to install everything myself that is needed to compile php5. > > So any advice, pointers on where to look, or hints on 64 bit vs 32 > would be greatly appreciated Please provide more information on your environment like macports version, php5 version, php5 line from port installed, the command you are using to test php5 and the result of those tests. If the result is to verbose summarize. //Brad From brad at pixilla.com Mon Mar 23 13:42:05 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Mon, 23 Mar 2009 13:42:05 -0700 Subject: php5 & "port test php5" In-Reply-To: References: <49C7EA67.9010101@blackchairdvd.com> Message-ID: On Mar 23, 2009, at 1:34 PM, Bradley Giesbrecht wrote: > > On Mar 23, 2009, at 1:00 PM, drf wrote: > >> Hi, >> >> My setup: Mac Mini, 10.4.11, Xcode 2.5, GCC 4, MacPorts 1.7 >> >> Everything compiles fine, there are some complaints about >> signedness from the compiler, but it all looks ok. But when I run >> the PHP test suite, over 70 tests fail, including ones I wouldn't >> really expect, like on the function easterdate(). I can not find >> any hints anywhere on what might be happening, so I'm wondering if >> these tests really are that important. Should a completely default, >> standard, stock install of php5 with MacPorts pass all the PHP self >> tests fine? > > What are you commands are you executing and what are the results? > > I don't see a php function named easterdate. There is easter_date > which appears to work fine on my php5 install. > > port installed > [...] > php5 @5.2.8_1+apache2+imap+macosx+mysql5+pear+pspell+readline+sqlite > +tidy (active) > > >> The thing is, when I set up everything myself (not using MacPorts >> to compile php5) the same set of tests failed - the config of php5 >> did reference various macport installed libraries, etc. I am now >> at the point where I am wondering if I ought to toss all of >> MacPorts and try to install everything myself that is needed to >> compile php5. >> >> So any advice, pointers on where to look, or hints on 64 bit vs 32 >> would be greatly appreciated > > Please provide more information on your environment like macports > version, php5 version, php5 line from port installed, the command > you are using to test php5 and the result of those tests. If the > result is to verbose summarize. I see you included everything I asked for. My brain mis-fired. //Brad From brad at pixilla.com Mon Mar 23 14:22:05 2009 From: brad at pixilla.com (Bradley Giesbrecht) Date: Mon, 23 Mar 2009 14:22:05 -0700 Subject: php5 & "port test php5" In-Reply-To: <49C7EA67.9010101@blackchairdvd.com> References: <49C7EA67.9010101@blackchairdvd.com> Message-ID: On Mar 23, 2009, at 1:00 PM, drf wrote: > Hi, > > My setup: Mac Mini, 10.4.11, Xcode 2.5, GCC 4, MacPorts 1.7 > > Everything compiles fine, there are some complaints about signedness > from the compiler, but it all looks ok. But when I run the PHP test > suite, over 70 tests fail, including ones I wouldn't really expect, > like on the function easterdate(). I can not find any hints > anywhere on what might be happening, so I'm wondering if these tests > really are that important. Should a completely default, standard, > stock install of php5 with MacPorts pass all the PHP self tests fine? > > The thing is, when I set up everything myself (not using MacPorts to > compile php5) the same set of tests failed - the config of php5 did > reference various macport installed libraries, etc. I am now at the > point where I am wondering if I ought to toss all of MacPorts and > try to install everything myself that is needed to compile php5. > > So any advice, pointers on where to look, or hints on 64 bit vs 32 > would be greatly appreciated The system I tested "port test php5" already had php5 installed and port doesn't seem to want to output anything. However, I didn't rebuild php5 it on that system and then: # cd `port dir php5`/work/php-5.2.8/ # make test and virtually everything is passing or being skipped. I don't know what to make of these results but I'll post them for you to look at. ===================================================================== TEST RESULT SUMMARY --------------------------------------------------------------------- Exts skipped : 37 Exts tested : 42 --------------------------------------------------------------------- Number of tests : 6567 5541 Tests borked : 1 ( 0.0%) -------- Tests skipped : 1025 ( 15.6%) -------- Tests warned : 3 ( 0.0%) ( 0.1%) Tests failed : 48 ( 0.7%) ( 0.9%) Expected fail : 4 ( 0.1%) ( 0.1%) Tests passed : 5486 ( 83.5%) ( 99.0%) --------------------------------------------------------------------- Time taken : 664 seconds ===================================================================== I have been using macports php5 for a couple weeks now coming from gentoo and I haven't had any problems to speak of. //Brad From drf at blackchairdvd.com Mon Mar 23 15:01:17 2009 From: drf at blackchairdvd.com (drf) Date: Mon, 23 Mar 2009 22:01:17 +0000 Subject: php5 & "port test php5" In-Reply-To: References: <49C7EA67.9010101@blackchairdvd.com> Message-ID: <49C806AD.7000803@blackchairdvd.com> An HTML attachment was scrubbed... URL: From felix.schaefer at tu-dortmund.de Tue Mar 24 01:18:24 2009 From: felix.schaefer at tu-dortmund.de (=?ISO-8859-1?Q?Felix_Sch=E4fer?=) Date: Tue, 24 Mar 2009 09:18:24 +0100 Subject: rails not finding itself? Message-ID: <7ED56EC2-F5DD-40A8-AF94-4FC05EBB8114@tu-dortmund.de> Hello, I have some trouble getting rails to work: It used to work, but now it fails with the following error: """ sahaquiel:~ felix$ rails -v /opt/local/lib/ruby/vendor_ruby/1.8/rubygems.rb:636:in `report_activate_error': Could not find RubyGem rails (>= 0) (Gem::LoadError) from /opt/local/lib/ruby/vendor_ruby/1.8/rubygems.rb:141:in `activate' from /opt/local/lib/ruby/vendor_ruby/1.8/rubygems.rb:49:in `gem' from /opt/local/bin/rails:18 """ I installed everything with 'port install rb-rails', and port is uptodate. Here are a few details on the system: """ sahaquiel:~ felix$ uname -a Darwin sahaquiel.lan 9.6.0 Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008; root:xnu-1228.9.59~1/RELEASE_I386 i386 sahaquiel:~ felix$ sw_vers ProductName: Mac OS X ProductVersion: 10.5.6 BuildVersion: 9G55 sahaquiel:~ felix$ echo $PATH /opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/ local/bin:/usr/X11/bin sahaquiel:~ felix$ ruby -v ruby 1.8.7 (2008-08-11 patchlevel 72) [i686-darwin9] sahaquiel:~ felix$ ruby -e 'puts $:' /opt/local/lib/ruby/site_ruby/1.8 /opt/local/lib/ruby/site_ruby/1.8/i686-darwin9 /opt/local/lib/ruby/site_ruby /opt/local/lib/ruby/vendor_ruby/1.8 /opt/local/lib/ruby/vendor_ruby/1.8/i686-darwin9 /opt/local/lib/ruby/vendor_ruby /opt/local/lib/ruby/1.8 /opt/local/lib/ruby/1.8/i686-darwin9 . sahaquiel:~ felix$ gem env RubyGems Environment: - RUBYGEMS VERSION: 1.3.1 - RUBY VERSION: 1.8.7 (2008-08-11 patchlevel 72) [i686-darwin9] - INSTALLATION DIRECTORY: /opt/local/lib/ruby/gems/1.8 - RUBY EXECUTABLE: /opt/local/bin/ruby - EXECUTABLE DIRECTORY: /opt/local/bin - RUBYGEMS PLATFORMS: - ruby - x86-darwin-9 - GEM PATHS: - /opt/local/lib/ruby/gems/1.8 - /Users/felix/.gem/ruby/1.8 - GEM CONFIGURATION: - :update_sources => true - :verbose => true - :benchmark => false - :backtrace => false - :bulk_threshold => 1000 - REMOTE SOURCES: - http://gems.rubyforge.org/ """ I'm quite new to ruby and rails, so I have no clue where rubygems would look for installed gems, but I assumed that they should find each other if all installed with port. Thanks for the help, Felix From ryandesign at macports.org Tue Mar 24 01:38:07 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue, 24 Mar 2009 03:38:07 -0500 Subject: Python, Tcl, Tix ... In-Reply-To: <49C76917.9090406@macports.org> References: <96081377-E75A-427D-A9CD-02D8A5CD32A7@macports.org> <49C76917.9090406@macports.org> Message-ID: <5898400F-E70D-43A2-988F-8883D2CC86EB@macports.org> On Mar 23, 2009, at 05:48, Rainer M?ller wrote: > Ryan Schmidt wrote: >> I am hoping the maintainer of the tcl and tk ports can explain the >> odd behavior I am seeing. > > Checking the Makefile after configure, there are problems with include > paths in TCL_SRC_DIR, TK_SRC_DIR and INCLUDES (which uses TCL_INCLUDES > and TK_INCLUDES). > > TCL_INCLUDES and TK_INCLUDES point to the build directories. But we > cannot just put ${prefix}/include/tcl or ${prefix}/include/tk in here. > > The real problem is that our Tk installation is missing files which > are > for example shipped with the build from Apple. In particular where I > discovered the first build error, Tix looks for tkInt.h which is > missing. > > Apple ships it at: > /System/Library/Frameworks/Tk.framework/Versions/8.4/Headers/tk- > private/tkInt.h > > After 'port extract tk', it can be found at: > $(port work tk)/tk8.5.6/generic/tkInt.h > > This port needs a similar approach as the tk port itself does. It > extracts the Tcl source and has additional preprocessor flags to > search > there for include files: > configure.cppflags "-I${workpath}/tcl${version}/generic" > > Or we need to copy these private header files to the usual include > location. Maybe it would be good to ask upstream on the Tcl mailing > list > for advice on this topic. There are several ports that want to download and unpack the Tcl source as part of their build process. It seems wasteful and unnecessary to me. And it never happens that all of those ports get updated to the current version of Tcl. Currently, we have amsn, otcl and tclcl using the source of tcl 8.4.9; expect, itcl and itk using the source of tcl 8.4.14; and of course tk using the source of tcl 8.5.6. I would be in favor of the tcl and tk ports installing everything that's required for other software to use Tcl and Tk. Markus, can you do this, or ask on the Tcl mailing list if they have other suggestions? From cssdev at mac.com Tue Mar 24 02:29:25 2009 From: cssdev at mac.com (cssdev at mac.com) Date: Tue, 24 Mar 2009 05:29:25 -0400 Subject: Incorrect libjpeg.dylib after installing ImageMagick In-Reply-To: <9D1705FA-9298-46A9-B967-7CCC70029516@macports.org> References: <52498.65.113.40.1.1237572545.squirrel@calmail.berkeley.edu> <3BF90774-22DD-401B-8FE7-7864CB698D7A@atmo.arizona.edu> <9D1705FA-9298-46A9-B967-7CCC70029516@macports.org> Message-ID: On Mar 20, 2009, at 8:00 PM, Ryan Schmidt wrote: > On Mar 20, 2009, at 13:20, Yolande Serra wrote: > >> Not sure this will help, but if you defined a DYLD_LIBRARY_PATH in >> your .bashrc or .profile get rid of it. >> >> The libraries that macs point to are found assuming this variable >> is not defined. Somewhere buried in the system it has a path to >> its own libs. You mess this up when you define dynamic library >> paths. > > I agree with Yolande: it sounds like you have DYLD_LIBRARY_PATH set, > and you should not. I'll note that there are cases requiring this environment variable. If this is one of those, then you can probably use DYLD_FALLBACK_LIBRARY_PATH instead. See http://developer.apple.com/documentation/DeveloperTools/Conceptual/DynamicLibraries/100-Articles/DynamicLibraryUsageGuidelines.html for more information about load libraries. Chris From cssdev at mac.com Tue Mar 24 02:33:22 2009 From: cssdev at mac.com (cssdev at mac.com) Date: Tue, 24 Mar 2009 05:33:22 -0400 Subject: Problem installing vtk In-Reply-To: <49C38BD3.4070309@gmail.com> References: <49C38BD3.4070309@gmail.com> Message-ID: On Mar 20, 2009, at 8:28 AM, David Trem wrote: > May somebody help ? > I have a problem installing vtk on MacBook OS X 10.5.6, using > macports 1.700 (fresh install). > See console output below. > > [...] > > /opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync > .macports.org_release_ports_graphics_vtk/work/VTK/Rendering/ > vtkCocoaGLView.h:11: error: using typedef-name > 'NSOpenGLPixelFormatAttribute' after 'enum' > /System/Library/Frameworks/AppKit.framework/Headers/NSOpenGL.h:90: > error: 'NSOpenGLPixelFormatAttribute' has a previous declaration here > make[2]: *** [Rendering/CMakeFiles/vtkRendering.dir/ > vtkCocoaRenderWindowInteractor.o] Error 1 > make[1]: *** [Rendering/CMakeFiles/vtkRendering.dir/all] Error 2 > make: *** [all] Error 2 I'll take look ... I think I might have only built the x11 variant. I might have missed another required Leopard fix for the Cocoa windowing. Chris From trog24 at comcast.net Tue Mar 24 08:50:05 2009 From: trog24 at comcast.net (Frank J. R. Hanstick) Date: Tue, 24 Mar 2009 08:50:05 -0700 Subject: dbus startup at system startup. Message-ID: Hello, At system startup, I get the following error messages sent to system.log: Mar 24 08:40:11 localhost launchd: org.macports.dbus: respawning too quickly! throttling Mar 24 08:40:11 localhost launchd: org.macports.dbus: 9 more failures without living at least 60 seconds will cause job removal Mar 24 08:40:11 localhost launchd: org.macports.dbus: will restart in 10 seconds Mar 24 08:40:21 Franks-PPC-G4 launchd: org.macports.dbus: respawning too quickly! throttling Mar 24 08:40:21 Franks-PPC-G4 launchd: org.macports.dbus: 8 more failures without living at least 60 seconds will cause job removal Mar 24 08:40:21 Franks-PPC-G4 launchd: org.macports.dbus: will restart in 10 seconds Mar 24 08:40:31 Franks-PPC-G4 launchd: org.macports.dbus: respawning too quickly! throttling Mar 24 08:40:31 Franks-PPC-G4 launchd: org.macports.dbus: 7 more failures without living at least 60 seconds will cause job removal Mar 24 08:40:31 Franks-PPC-G4 launchd: org.macports.dbus: will restart in 10 seconds Mar 24 08:40:41 Franks-PPC-G4 launchd: org.macports.dbus: respawning too quickly! throttling Mar 24 08:40:41 Franks-PPC-G4 launchd: org.macports.dbus: 6 more failures without living at least 60 seconds will cause job removal Mar 24 08:40:41 Franks-PPC-G4 launchd: org.macports.dbus: will restart in 10 seconds Mar 24 08:40:51 Franks-PPC-G4 launchd: org.macports.dbus: respawning too quickly! throttling Mar 24 08:40:51 Franks-PPC-G4 launchd: org.macports.dbus: 5 more failures without living at least 60 seconds will cause job removal Mar 24 08:40:51 Franks-PPC-G4 launchd: org.macports.dbus: will restart in 10 seconds Mar 24 08:41:01 Franks-PPC-G4 launchd: org.macports.dbus: respawning too quickly! throttling Mar 24 08:41:01 Franks-PPC-G4 launchd: org.macports.dbus: 4 more failures without living at least 60 seconds will cause job removal Mar 24 08:41:01 Franks-PPC-G4 launchd: org.macports.dbus: will restart in 10 seconds Mar 24 08:41:11 Franks-PPC-G4 launchd: org.macports.dbus: respawning too quickly! throttling Mar 24 08:41:11 Franks-PPC-G4 launchd: org.macports.dbus: 3 more failures without living at least 60 seconds will cause job removal Mar 24 08:41:11 Franks-PPC-G4 launchd: org.macports.dbus: will restart in 10 seconds Mar 24 08:41:22 Franks-PPC-G4 launchd: org.macports.dbus: respawning too quickly! throttling Mar 24 08:41:22 Franks-PPC-G4 launchd: org.macports.dbus: 2 more failures without living at least 60 seconds will cause job removal Mar 24 08:41:22 Franks-PPC-G4 launchd: org.macports.dbus: will restart in 10 seconds Mar 24 08:41:32 Franks-PPC-G4 launchd: org.macports.dbus: respawning too quickly! throttling Mar 24 08:41:32 Franks-PPC-G4 launchd: org.macports.dbus: 1 more failure without living at least 60 seconds will cause job removal Mar 24 08:41:32 Franks-PPC-G4 launchd: org.macports.dbus: will restart in 10 seconds Mar 24 08:41:42 Franks-PPC-G4 launchd: org.macports.dbus: respawning too quickly! throttling Mar 24 08:41:42 Franks-PPC-G4 launchd: org.macports.dbus: too many failures in succession I installed dbus via sudo port install dbus and entered: launchctl load /Library/LaunchAgents/org.freedesktop.dbus-session.plist as directed; yet, I still get these error messages at system startup time. How do I get them to stop? Frank J. R. Hanstick trog24 at comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From admin2 at enabled.com Tue Mar 24 11:59:55 2009 From: admin2 at enabled.com (Noah) Date: Tue, 24 Mar 2009 11:59:55 -0700 Subject: Could not run GTK+ test program Message-ID: <49C92DAB.4070804@enabled.com> How can I fix this error so wireshark can build. Looks like it is a problem with the GTK+ being found. sh-3.2# port install wireshark Portfile changed since last build; discarding previous state. ---> Fetching wireshark ---> Attempting to fetch wireshark-1.0.6.tar.bz2 from http://www.wireshark.org/download/src/ ---> Verifying checksum(s) for wireshark ---> Extracting wireshark ---> Configuring wireshark ^[ODError: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_wireshark/work/wireshark-1.0.6" && ./configure --prefix=/opt/local --enable-gtk2 --with-net-snmp=no --with-ucd-snmp=no --disable-usr-local --without-adns --without-pcre --disable-ipv6 --with-pcap=/opt/local --with-ssl=/opt/local --with-zlib=/opt/local --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info --without-portaudio --disable-warnings-as-errors " returned error 1 Command output: checking for dpkg-buildpackage... no checking for xcodebuild... yes checking for hdiutil... yes checking for bless... yes checking whether we can add -Wall -W to CFLAGS... yes checking whether we can add -Wdeclaration-after-statement to CFLAGS... yes checking whether we can add -Wendif-labels to CFLAGS... yes checking whether we can add -Wpointer-arith to CFLAGS... yes checking whether we can add -Wno-pointer-sign to CFLAGS... yes checking whether we can add -Warray-bounds to CFLAGS... no checking whether we should treat compiler warnings as errors... no checking for platform-specific compiler flags... Apple GCC - added -no-cpp-precomp checking for platform-specific linker flags... Apple linker - added -Wl,-single_module and -Wl,-search_paths_first checking whether we can build with Core Foundation, Launch Services, and Core Services... yes checking whether to use /usr/local for headers and libraries... no checking for GNU sed as first sed in PATH... no checking if profile builds must be generated... no checking for pkg-config... /opt/local/bin/pkg-config checking for GTK+ - version >= 2.0.0... no *** Could not run GTK+ test program, checking why... *** The test program compiled, but did not run. This usually means *** that the run-time linker is not finding GTK+ or finding the wrong *** version of GTK+. If it is not finding GTK+, you'll need to set your *** LD_LIBRARY_PATH environment variable, or edit /etc/ld.so.conf to point *** to the installed location Also, make sure you have run ldconfig if that *** is required on your system *** *** If you have an old version installed, it is best to remove it, although *** you may also be able to get things to work by modifying LD_LIBRARY_PATH configure: error: GTK+ isn't available, so Wireshark can't be compiled Error: Status 1 encountered during processing. From trog24 at comcast.net Tue Mar 24 12:22:17 2009 From: trog24 at comcast.net (Frank J. R. Hanstick) Date: Tue, 24 Mar 2009 12:22:17 -0700 Subject: dbus startup at system startup. In-Reply-To: References: Message-ID: <6459588C-F443-4894-ADF1-0D6EF854F1E1@comcast.net> Hello, I figured out the problem. Somehow, the plist associated with org.macports got inserted into LaunchDaemons. I removed it and the dbus messages stopped appearing. Great when I can solve my own problems once in a while. Frank On Mar 24, 2009, at 8:50 AM, Frank J. R. Hanstick wrote: > Hello, > At system startup, I get the following error messages sent to > system.log: > > Mar 24 08:40:11 localhost launchd: org.macports.dbus: respawning > too quickly! throttling > Mar 24 08:40:11 localhost launchd: org.macports.dbus: 9 more > failures without living at least 60 seconds will cause job removal > Mar 24 08:40:11 localhost launchd: org.macports.dbus: will restart > in 10 seconds > Mar 24 08:40:21 Franks-PPC-G4 launchd: org.macports.dbus: > respawning too quickly! throttling > Mar 24 08:40:21 Franks-PPC-G4 launchd: org.macports.dbus: 8 more > failures without living at least 60 seconds will cause job removal > Mar 24 08:40:21 Franks-PPC-G4 launchd: org.macports.dbus: will > restart in 10 seconds > Mar 24 08:40:31 Franks-PPC-G4 launchd: org.macports.dbus: > respawning too quickly! throttling > Mar 24 08:40:31 Franks-PPC-G4 launchd: org.macports.dbus: 7 more > failures without living at least 60 seconds will cause job removal > Mar 24 08:40:31 Franks-PPC-G4 launchd: org.macports.dbus: will > restart in 10 seconds > Mar 24 08:40:41 Franks-PPC-G4 launchd: org.macports.dbus: > respawning too quickly! throttling > Mar 24 08:40:41 Franks-PPC-G4 launchd: org.macports.dbus: 6 more > failures without living at least 60 seconds will cause job removal > Mar 24 08:40:41 Franks-PPC-G4 launchd: org.macports.dbus: will > restart in 10 seconds > Mar 24 08:40:51 Franks-PPC-G4 launchd: org.macports.dbus: > respawning too quickly! throttling > Mar 24 08:40:51 Franks-PPC-G4 launchd: org.macports.dbus: 5 more > failures without living at least 60 seconds will cause job removal > Mar 24 08:40:51 Franks-PPC-G4 launchd: org.macports.dbus: will > restart in 10 seconds > Mar 24 08:41:01 Franks-PPC-G4 launchd: org.macports.dbus: > respawning too quickly! throttling > Mar 24 08:41:01 Franks-PPC-G4 launchd: org.macports.dbus: 4 more > failures without living at least 60 seconds will cause job removal > Mar 24 08:41:01 Franks-PPC-G4 launchd: org.macports.dbus: will > restart in 10 seconds > Mar 24 08:41:11 Franks-PPC-G4 launchd: org.macports.dbus: > respawning too quickly! throttling > Mar 24 08:41:11 Franks-PPC-G4 launchd: org.macports.dbus: 3 more > failures without living at least 60 seconds will cause job removal > Mar 24 08:41:11 Franks-PPC-G4 launchd: org.macports.dbus: will > restart in 10 seconds > Mar 24 08:41:22 Franks-PPC-G4 launchd: org.macports.dbus: > respawning too quickly! throttling > Mar 24 08:41:22 Franks-PPC-G4 launchd: org.macports.dbus: 2 more > failures without living at least 60 seconds will cause job removal > Mar 24 08:41:22 Franks-PPC-G4 launchd: org.macports.dbus: will > restart in 10 seconds > Mar 24 08:41:32 Franks-PPC-G4 launchd: org.macports.dbus: > respawning too quickly! throttling > Mar 24 08:41:32 Franks-PPC-G4 launchd: org.macports.dbus: 1 more > failure without living at least 60 seconds will cause job removal > Mar 24 08:41:32 Franks-PPC-G4 launchd: org.macports.dbus: will > restart in 10 seconds > Mar 24 08:41:42 Franks-PPC-G4 launchd: org.macports.dbus: > respawning too quickly! throttling > Mar 24 08:41:42 Franks-PPC-G4 launchd: org.macports.dbus: too many > failures in succession > > I installed dbus via sudo port install dbus and entered: > > launchctl load /Library/LaunchAgents/org.freedesktop.dbus- > session.plist > > as directed; yet, I still get these error messages at system > startup time. How do I get them to stop? > > Frank J. R. Hanstick > trog24 at comcast.net > > > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users Frank J. R. Hanstick trog24 at comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrei at tchijov.com Tue Mar 24 17:01:14 2009 From: andrei at tchijov.com (Andrei Tchijov) Date: Tue, 24 Mar 2009 20:01:14 -0400 Subject: Problems with pango Message-ID: I am trying to install "+quartz" flavor of gimp. Unfortunately, while trying to install poppler +quartz, I have run into following problem [local/bin] > uninstall pango ---> Deactivating pango @1.24.0_0+macosx+quartz ---> Uninstalling pango @1.24.0_0+macosx+quartz [local/bin] > install pango +no_x11 ---> Fetching pango ---> Verifying checksum(s) for pango ---> Extracting pango ---> Applying patches to pango ---> Configuring pango ---> Building pango ---> Staging pango into destroot ---> Installing pango @1.24.0_0+macosx+quartz ---> Activating pango @1.24.0_0+macosx+quartz ---> Cleaning pango [local/bin] > install poppler +quartz ---> Fetching gtk2 Error: Please uninstall or deactivate the pango port and reinstall it by running `port install pango +no_x11`. Error: Target org.macports.fetch returned: pango must be installed with the no_x11 variant enabled. Error: The following dependencies failed to build: gtk2 openjpeg poppler-data Error: Status 1 encountered during processing. [local/bin] > installed pango The following ports are currently installed: pango @1.24.0_0+macosx+quartz (active) [local/bin] > selfupdate MacPorts base version 1.700 installed Downloaded MacPorts base version 1.700 The MacPorts installation is not outdated so it was not updated [local/bin] > install gtk2 +quartz +no_x11 ---> Fetching gtk2 Error: Please uninstall or deactivate the pango port and reinstall it by running `port install pango +no_x11`. Error: Target org.macports.fetch returned: pango must be installed with the no_x11 variant enabled. Error: Status 1 encountered during processing. Please advice, Andrei From trog24 at comcast.net Tue Mar 24 17:05:59 2009 From: trog24 at comcast.net (Frank J. R. Hanstick) Date: Tue, 24 Mar 2009 17:05:59 -0700 Subject: Building xorg-libX11 Message-ID: Hello, I got this error: ---> Building xorg-libX11 DEBUG: Executing org.macports.build (xorg-libX11) DEBUG: port allows a parallel build DEBUG: Environment: MACOSX_DEPLOYMENT_TARGET='10.4' DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xor g-libX11/work/libX11-1.2" && make all' Making all in include make[1]: Nothing to be done for `all'. Making all in modules Making all in im Making all in ximcp make[3]: Nothing to be done for `all'. make[3]: Nothing to be done for `all-am'. Making all in lc Making all in Utf8 make[3]: Nothing to be done for `all'. Making all in def make[3]: Nothing to be done for `all'. Making all in gen make[3]: Nothing to be done for `all'. Making all in xlocale make[3]: Nothing to be done for `all'. make[3]: Nothing to be done for `all-am'. Making all in om Making all in generic make[3]: Nothing to be done for `all'. make[3]: Nothing to be done for `all-am'. make[2]: Nothing to be done for `all-am'. Making all in src cd util && make make[2]: Nothing to be done for `all'. make all-recursive Making all in util make[3]: Nothing to be done for `all'. Making all in xcms make[3]: Nothing to be done for `all'. Making all in xlibi18n make[3]: Nothing to be done for `all'. Making all in xkb make[3]: Nothing to be done for `all'. cd util && make make[4]: Nothing to be done for `all'. /bin/sh ../libtool --tag=CC --mode=link /usr/bin/gcc-4.0 -I../ include -I../include/X11 -I../include -I../include/X11 -I../src/xcms - I../src/xkb -I../src/xlibi18n -Wall -Wpointer-arith -Wstrict- prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested- externs -fno-strict-aliasing -Wbad-function-cast -Wall -Wpointer- arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing- declarations -Wnested-externs -fno-strict-aliasing -D_BSD_SOURCE - DHAS_FCHOWN -DHAS_STICKY_DIR_BIT -I/opt/local/include -I/opt/local/ include -I/opt/local/include -I/opt/local/include -I/opt/local/ include -DHASXDMAUTH -D_BSD_SOURCE -DX11_t -DTRANS_CLIENT -O2 - version-number 6:2:0 -no-undefined -L/opt/local/lib -o libX11.la - rpath /opt/local/lib AllCells.lo AllowEv.lo AllPlanes.lo AutoRep.lo Backgnd.lo BdrWidth.lo Bell.lo Border.lo ChAccCon.lo ChActPGb.lo ChClMode.lo ChCmap.lo ChGC.lo ChKeyCon.lo ChkIfEv.lo ChkMaskEv.lo ChkTypEv.lo ChkTypWEv.lo ChkWinEv.lo ChPntCon.lo ChProp.lo ChSaveSet.lo ChWAttrs.lo ChWindow.lo CirWin.lo CirWinDn.lo CirWinUp.lo ClDisplay.lo ClearArea.lo Clear.lo ConfWind.lo Context.lo ConvSel.lo CopyArea.lo CopyCmap.lo CopyGC.lo CopyPlane.lo CrBFData.lo CrCmap.lo CrCursor.lo CrGC.lo CrGlCur.lo CrPFBData.lo CrPixmap.lo CrWindow.lo Cursor.lo DefCursor.lo DelProp.lo Depths.lo DestSubs.lo DestWind.lo DisName.lo DrArc.lo DrArcs.lo DrLine.lo DrLines.lo DrPoint.lo DrPoints.lo DrRect.lo DrRects.lo DrSegs.lo ErrDes.lo ErrHndlr.lo evtomask.lo EvToWire.lo FetchName.lo FillArc.lo FillArcs.lo FillPoly.lo FillRct.lo FillRcts.lo FilterEv.lo Flush.lo Font.lo FontInfo.lo FontNames.lo FreeCmap.lo FreeCols.lo FreeCurs.lo FreeEData.lo FreeGC.lo FreePix.lo FSSaver.lo FSWrap.lo GCMisc.lo Geom.lo GetAtomNm.lo GetColor.lo GetDflt.lo GetFPath.lo GetFProp.lo GetGCVals.lo GetGeom.lo GetHColor.lo GetHints.lo GetIFocus.lo GetImage.lo GetKCnt.lo GetMoEv.lo GetNrmHint.lo GetPCnt.lo GetPntMap.lo GetProp.lo GetRGBCMap.lo GetSOwner.lo GetSSaver.lo GetStCmap.lo GetTxtProp.lo GetWAttrs.lo GetWMCMapW.lo GetWMProto.lo globals.lo GrButton.lo GrKeybd.lo GrKey.lo GrPointer.lo GrServer.lo Host.lo Iconify.lo IfEvent.lo imConv.lo ImText16.lo ImText.lo ImUtil.lo InitExt.lo InsCmap.lo IntAtom.lo KeyBind.lo KeysymStr.lo KillCl.lo LiHosts.lo LiICmaps.lo LiProps.lo ListExt.lo LoadFont.lo LockDis.lo locking.lo LookupCol.lo LowerWin.lo Macros.lo MapRaised.lo MapSubs.lo MapWindow.lo MaskEvent.lo Misc.lo ModMap.lo MoveWin.lo NextEvent.lo OCWrap.lo OMWrap.lo OpenDis.lo ParseCmd.lo ParseCol.lo ParseGeom.lo PeekEvent.lo PeekIfEv.lo Pending.lo PixFormats.lo PmapBgnd.lo PmapBord.lo PolyReg.lo PolyTxt16.lo PolyTxt.lo PropAlloc.lo PutBEvent.lo PutImage.lo Quarks.lo QuBest.lo QuColor.lo QuColors.lo QuCurShp.lo QuExt.lo QuKeybd.lo QuPntr.lo QuStipShp.lo QuTextE16.lo QuTextExt.lo QuTileShp.lo QuTree.lo RaiseWin.lo RdBitF.lo RecolorC.lo ReconfWin.lo ReconfWM.lo Region.lo RegstFlt.lo RepWindow.lo RestackWs.lo RotProp.lo ScrResStr.lo SelInput.lo SendEvent.lo SetBack.lo SetClMask.lo SetClOrig.lo SetCRects.lo SetDashes.lo SetFont.lo SetFore.lo SetFPath.lo SetFunc.lo SetHints.lo SetIFocus.lo SetLocale.lo SetLStyle.lo SetNrmHint.lo SetPMask.lo SetPntMap.lo SetRGBCMap.lo SetSOwner.lo SetSSaver.lo SetState.lo SetStCmap.lo SetStip.lo SetTile.lo SetTSOrig.lo SetTxtProp.lo SetWMCMapW.lo SetWMProto.lo StBytes.lo StColor.lo StColors.lo StName.lo StNColor.lo StrKeysym.lo StrToText.lo Sync.lo Synchro.lo Text16.lo Text.lo TextExt16.lo TextExt.lo TextToStr.lo TrCoords.lo UndefCurs.lo UngrabBut.lo UngrabKbd.lo UngrabKey.lo UngrabPtr.lo UngrabSvr.lo UninsCmap.lo UnldFont.lo UnmapSubs.lo UnmapWin.lo VisUtil.lo WarpPtr.lo Window.lo WinEvent.lo Withdraw.lo WMGeom.lo WMProps.lo WrBitF.lo XlibAsync.lo XlibInt.lo Xrm.lo ConnDis.lo x11_trans.lo xlibi18n/libi18n.la xcms/libxcms.la xkb/libxkb.la -L/opt/ local/lib -lXau -L/opt/local/lib -lXdmcp rm -fr .libs/libX11.lax rm -fr .libs/libX11.lax mkdir .libs/libX11.lax rm -fr .libs/libX11.lax/libi18n.a mkdir .libs/libX11.lax/libi18n.a Extracting /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xor g-libX11/work/libX11-1.2/src/xlibi18n/.libs/libi18n.a (cd .libs/libX11.lax/libi18n.a && ar x /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xor g-libX11/work/libX11-1.2/src/xlibi18n/.libs/libi18n.a) rm -fr .libs/libX11.lax/libxcms.a mkdir .libs/libX11.lax/libxcms.a Extracting /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xor g-libX11/work/libX11-1.2/src/xcms/.libs/libxcms.a (cd .libs/libX11.lax/libxcms.a && ar x /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xor g-libX11/work/libX11-1.2/src/xcms/.libs/libxcms.a) rm -fr .libs/libX11.lax/libxkb.a mkdir .libs/libX11.lax/libxkb.a Extracting /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xor g-libX11/work/libX11-1.2/src/xkb/.libs/libxkb.a (cd .libs/libX11.lax/libxkb.a && ar x /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xor g-libX11/work/libX11-1.2/src/xkb/.libs/libxkb.a) /usr/bin/gcc-4.0 -dynamiclib -o .libs/libX11.6.2.0.dylib .libs/ AllCells.o .libs/AllowEv.o .libs/AllPlanes.o .libs/AutoRep.o .libs/ Backgnd.o .libs/BdrWidth.o .libs/Bell.o .libs/Border.o .libs/ ChAccCon.o .libs/ChActPGb.o .libs/ChClMode.o .libs/ChCmap.o .libs/ ChGC.o .libs/ChKeyCon.o .libs/ChkIfEv.o .libs/ChkMaskEv.o .libs/ ChkTypEv.o .libs/ChkTypWEv.o .libs/ChkWinEv.o .libs/ChPntCon.o .libs/ ChProp.o .libs/ChSaveSet.o .libs/ChWAttrs.o .libs/ChWindow.o .libs/ CirWin.o .libs/CirWinDn.o .libs/CirWinUp.o .libs/ClDisplay.o .libs/ ClearArea.o .libs/Clear.o .libs/ConfWind.o .libs/Context.o .libs/ ConvSel.o .libs/CopyArea.o .libs/CopyCmap.o .libs/CopyGC.o .libs/ CopyPlane.o .libs/CrBFData.o .libs/CrCmap.o .libs/CrCursor.o .libs/ CrGC.o .libs/CrGlCur.o .libs/CrPFBData.o .libs/CrPixmap.o .libs/ CrWindow.o .libs/Cursor.o .libs/DefCursor.o .libs/DelProp.o .libs/ Depths.o .libs/DestSubs.o .libs/DestWind.o .libs/DisName.o .libs/ DrArc.o .libs/DrArcs.o .libs/DrLine.o .libs/DrLines.o .libs/ DrPoint.o .libs/DrPoints.o .libs/DrRect.o .libs/DrRects.o .libs/ DrSegs.o .libs/ErrDes.o .libs/ErrHndlr.o .libs/evtomask.o .libs/ EvToWire.o .libs/FetchName.o .libs/FillArc.o .libs/FillArcs.o .libs/ FillPoly.o .libs/FillRct.o .libs/FillRcts.o .libs/FilterEv.o .libs/ Flush.o .libs/Font.o .libs/FontInfo.o .libs/FontNames.o .libs/ FreeCmap.o .libs/FreeCols.o .libs/FreeCurs.o .libs/FreeEData.o .libs/ FreeGC.o .libs/FreePix.o .libs/FSSaver.o .libs/FSWrap.o .libs/ GCMisc.o .libs/Geom.o .libs/GetAtomNm.o .libs/GetColor.o .libs/ GetDflt.o .libs/GetFPath.o .libs/GetFProp.o .libs/GetGCVals.o .libs/ GetGeom.o .libs/GetHColor.o .libs/GetHints.o .libs/GetIFocus.o .libs/ GetImage.o .libs/GetKCnt.o .libs/GetMoEv.o .libs/GetNrmHint.o .libs/ GetPCnt.o .libs/GetPntMap.o .libs/GetProp.o .libs/GetRGBCMap.o .libs/ GetSOwner.o .libs/GetSSaver.o .libs/GetStCmap.o .libs/ GetTxtProp.o .libs/GetWAttrs.o .libs/GetWMCMapW.o .libs/ GetWMProto.o .libs/globals.o .libs/GrButton.o .libs/GrKeybd.o .libs/ GrKey.o .libs/GrPointer.o .libs/GrServer.o .libs/Host.o .libs/ Iconify.o .libs/IfEvent.o .libs/imConv.o .libs/ImText16.o .libs/ ImText.o .libs/ImUtil.o .libs/InitExt.o .libs/InsCmap.o .libs/ IntAtom.o .libs/KeyBind.o .libs/KeysymStr.o .libs/KillCl.o .libs/ LiHosts.o .libs/LiICmaps.o .libs/LiProps.o .libs/ListExt.o .libs/ LoadFont.o .libs/LockDis.o .libs/locking.o .libs/LookupCol.o .libs/ LowerWin.o .libs/Macros.o .libs/MapRaised.o .libs/MapSubs.o .libs/ MapWindow.o .libs/MaskEvent.o .libs/Misc.o .libs/ModMap.o .libs/ MoveWin.o .libs/NextEvent.o .libs/OCWrap.o .libs/OMWrap.o .libs/ OpenDis.o .libs/ParseCmd.o .libs/ParseCol.o .libs/ParseGeom.o .libs/ PeekEvent.o .libs/PeekIfEv.o .libs/Pending.o .libs/PixFormats.o .libs/ PmapBgnd.o .libs/PmapBord.o .libs/PolyReg.o .libs/PolyTxt16.o .libs/ PolyTxt.o .libs/PropAlloc.o .libs/PutBEvent.o .libs/PutImage.o .libs/ Quarks.o .libs/QuBest.o .libs/QuColor.o .libs/QuColors.o .libs/ QuCurShp.o .libs/QuExt.o .libs/QuKeybd.o .libs/QuPntr.o .libs/ QuStipShp.o .libs/QuTextE16.o .libs/QuTextExt.o .libs/ QuTileShp.o .libs/QuTree.o .libs/RaiseWin.o .libs/RdBitF.o .libs/ RecolorC.o .libs/ReconfWin.o .libs/ReconfWM.o .libs/Region.o .libs/ RegstFlt.o .libs/RepWindow.o .libs/RestackWs.o .libs/RotProp.o .libs/ ScrResStr.o .libs/SelInput.o .libs/SendEvent.o .libs/SetBack.o .libs/ SetClMask.o .libs/SetClOrig.o .libs/SetCRects.o .libs/ SetDashes.o .libs/SetFont.o .libs/SetFore.o .libs/SetFPath.o .libs/ SetFunc.o .libs/SetHints.o .libs/SetIFocus.o .libs/SetLocale.o .libs/ SetLStyle.o .libs/SetNrmHint.o .libs/SetPMask.o .libs/ SetPntMap.o .libs/SetRGBCMap.o .libs/SetSOwner.o .libs/ SetSSaver.o .libs/SetState.o .libs/SetStCmap.o .libs/SetStip.o .libs/ SetTile.o .libs/SetTSOrig.o .libs/SetTxtProp.o .libs/ SetWMCMapW.o .libs/SetWMProto.o .libs/StBytes.o .libs/StColor.o .libs/ StColors.o .libs/StName.o .libs/StNColor.o .libs/StrKeysym.o .libs/ StrToText.o .libs/Sync.o .libs/Synchro.o .libs/Text16.o .libs/ Text.o .libs/TextExt16.o .libs/TextExt.o .libs/TextToStr.o .libs/ TrCoords.o .libs/UndefCurs.o .libs/UngrabBut.o .libs/ UngrabKbd.o .libs/UngrabKey.o .libs/UngrabPtr.o .libs/ UngrabSvr.o .libs/UninsCmap.o .libs/UnldFont.o .libs/ UnmapSubs.o .libs/UnmapWin.o .libs/VisUtil.o .libs/WarpPtr.o .libs/ Window.o .libs/WinEvent.o .libs/Withdraw.o .libs/WMGeom.o .libs/ WMProps.o .libs/WrBitF.o .libs/XlibAsync.o .libs/XlibInt.o .libs/ Xrm.o .libs/ConnDis.o .libs/x11_trans.o .libs/libX11.lax/libi18n.a/ ICWrap.o .libs/libX11.lax/libi18n.a/imCallbk.o .libs/libX11.lax/ libi18n.a/imDefFlt.o .libs/libX11.lax/libi18n.a/imDefIc.o .libs/ libX11.lax/libi18n.a/imDefIm.o .libs/libX11.lax/libi18n.a/ imDefLkup.o .libs/libX11.lax/libi18n.a/imDispch.o .libs/libX11.lax/ libi18n.a/imEvToWire.o .libs/libX11.lax/libi18n.a/imExten.o .libs/ libX11.lax/libi18n.a/imImSw.o .libs/libX11.lax/libi18n.a/ imInsClbk.o .libs/libX11.lax/libi18n.a/imInt.o .libs/libX11.lax/ libi18n.a/imKStoUCS.o .libs/libX11.lax/libi18n.a/imLcFlt.o .libs/ libX11.lax/libi18n.a/imLcGIc.o .libs/libX11.lax/libi18n.a/ imLcIc.o .libs/libX11.lax/libi18n.a/imLcIm.o .libs/libX11.lax/ libi18n.a/imLcLkup.o .libs/libX11.lax/libi18n.a/imLcPrs.o .libs/ libX11.lax/libi18n.a/imLcSIc.o .libs/libX11.lax/libi18n.a/ imRm.o .libs/libX11.lax/libi18n.a/imRmAttr.o .libs/libX11.lax/ libi18n.a/imThaiFlt.o .libs/libX11.lax/libi18n.a/imThaiIc.o .libs/ libX11.lax/libi18n.a/imThaiIm.o .libs/libX11.lax/libi18n.a/ imTrans.o .libs/libX11.lax/libi18n.a/imTransR.o .libs/libX11.lax/ libi18n.a/imTrX.o .libs/libX11.lax/libi18n.a/IMWrap.o .libs/ libX11.lax/libi18n.a/lcCharSet.o .libs/libX11.lax/libi18n.a/ lcConv.o .libs/libX11.lax/libi18n.a/lcCT.o .libs/libX11.lax/libi18n.a/ lcDB.o .libs/libX11.lax/libi18n.a/lcDefConv.o .libs/libX11.lax/ libi18n.a/lcDynamic.o .libs/libX11.lax/libi18n.a/lcEuc.o .libs/ libX11.lax/libi18n.a/lcFile.o .libs/libX11.lax/libi18n.a/ lcGenConv.o .libs/libX11.lax/libi18n.a/lcGeneric.o .libs/libX11.lax/ libi18n.a/lcInit.o .libs/libX11.lax/libi18n.a/lcJis.o .libs/ libX11.lax/libi18n.a/lcPrTxt.o .libs/libX11.lax/libi18n.a/ lcPublic.o .libs/libX11.lax/libi18n.a/lcPubWrap.o .libs/libX11.lax/ libi18n.a/lcRM.o .libs/libX11.lax/libi18n.a/lcSjis.o .libs/libX11.lax/ libi18n.a/lcStd.o .libs/libX11.lax/libi18n.a/lcTxtPr.o .libs/ libX11.lax/libi18n.a/lcUTF8.o .libs/libX11.lax/libi18n.a/ lcUtil.o .libs/libX11.lax/libi18n.a/lcWrap.o .libs/libX11.lax/ libi18n.a/mbWMProps.o .libs/libX11.lax/libi18n.a/mbWrap.o .libs/ libX11.lax/libi18n.a/omDefault.o .libs/libX11.lax/libi18n.a/ omGeneric.o .libs/libX11.lax/libi18n.a/omImText.o .libs/libX11.lax/ libi18n.a/omText.o .libs/libX11.lax/libi18n.a/omTextEsc.o .libs/ libX11.lax/libi18n.a/omTextExt.o .libs/libX11.lax/libi18n.a/ omTextPer.o .libs/libX11.lax/libi18n.a/omXChar.o .libs/libX11.lax/ libi18n.a/utf8WMProps.o .libs/libX11.lax/libi18n.a/utf8Wrap.o .libs/ libX11.lax/libi18n.a/wcWrap.o .libs/libX11.lax/libi18n.a/ XDefaultIMIF.o .libs/libX11.lax/libi18n.a/XDefaultOMIF.o .libs/ libX11.lax/libi18n.a/xim_trans.o .libs/libX11.lax/libxcms.a/ AddDIC.o .libs/libX11.lax/libxcms.a/AddSF.o .libs/libX11.lax/ libxcms.a/CCC.o .libs/libX11.lax/libxcms.a/cmsAllCol.o .libs/ libX11.lax/libxcms.a/cmsAllNCol.o .libs/libX11.lax/libxcms.a/ cmsCmap.o .libs/libX11.lax/libxcms.a/cmsColNm.o .libs/libX11.lax/ libxcms.a/cmsGlobls.o .libs/libX11.lax/libxcms.a/cmsInt.o .libs/ libX11.lax/libxcms.a/cmsLkCol.o .libs/libX11.lax/libxcms.a/ cmsMath.o .libs/libX11.lax/libxcms.a/cmsProp.o .libs/libX11.lax/ libxcms.a/cmsTrig.o .libs/libX11.lax/libxcms.a/CvCols.o .libs/ libX11.lax/libxcms.a/CvColW.o .libs/libX11.lax/libxcms.a/HVC.o .libs/ libX11.lax/libxcms.a/HVCGcC.o .libs/libX11.lax/libxcms.a/ HVCGcV.o .libs/libX11.lax/libxcms.a/HVCGcVC.o .libs/libX11.lax/ libxcms.a/HVCMnV.o .libs/libX11.lax/libxcms.a/HVCMxC.o .libs/ libX11.lax/libxcms.a/HVCMxV.o .libs/libX11.lax/libxcms.a/ HVCMxVC.o .libs/libX11.lax/libxcms.a/HVCMxVs.o .libs/libX11.lax/ libxcms.a/HVCWpAj.o .libs/libX11.lax/libxcms.a/IdOfPr.o .libs/ libX11.lax/libxcms.a/Lab.o .libs/libX11.lax/libxcms.a/LabGcC.o .libs/ libX11.lax/libxcms.a/LabGcL.o .libs/libX11.lax/libxcms.a/ LabGcLC.o .libs/libX11.lax/libxcms.a/LabMnL.o .libs/libX11.lax/ libxcms.a/LabMxC.o .libs/libX11.lax/libxcms.a/LabMxL.o .libs/ libX11.lax/libxcms.a/LabMxLC.o .libs/libX11.lax/libxcms.a/ LabWpAj.o .libs/libX11.lax/libxcms.a/LRGB.o .libs/libX11.lax/ libxcms.a/Luv.o .libs/libX11.lax/libxcms.a/LuvGcC.o .libs/libX11.lax/ libxcms.a/LuvGcL.o .libs/libX11.lax/libxcms.a/LuvGcLC.o .libs/ libX11.lax/libxcms.a/LuvMnL.o .libs/libX11.lax/libxcms.a/ LuvMxC.o .libs/libX11.lax/libxcms.a/LuvMxL.o .libs/libX11.lax/ libxcms.a/LuvMxLC.o .libs/libX11.lax/libxcms.a/LuvWpAj.o .libs/ libX11.lax/libxcms.a/OfCCC.o .libs/libX11.lax/libxcms.a/ PrOfId.o .libs/libX11.lax/libxcms.a/QBlack.o .libs/libX11.lax/ libxcms.a/QBlue.o .libs/libX11.lax/libxcms.a/QGreen.o .libs/ libX11.lax/libxcms.a/QRed.o .libs/libX11.lax/libxcms.a/QuCol.o .libs/ libX11.lax/libxcms.a/QuCols.o .libs/libX11.lax/libxcms.a/ QWhite.o .libs/libX11.lax/libxcms.a/SetCCC.o .libs/libX11.lax/ libxcms.a/SetGetCols.o .libs/libX11.lax/libxcms.a/StCol.o .libs/ libX11.lax/libxcms.a/StCols.o .libs/libX11.lax/libxcms.a/ UNDEFINED.o .libs/libX11.lax/libxcms.a/uvY.o .libs/libX11.lax/ libxcms.a/XRGB.o .libs/libX11.lax/libxcms.a/xyY.o .libs/libX11.lax/ libxcms.a/XYZ.o .libs/libX11.lax/libxkb.a/XKB.o .libs/libX11.lax/ libxkb.a/XKBAlloc.o .libs/libX11.lax/libxkb.a/XKBBell.o .libs/ libX11.lax/libxkb.a/XKBBind.o .libs/libX11.lax/libxkb.a/ XKBCompat.o .libs/libX11.lax/libxkb.a/XKBCtrls.o .libs/libX11.lax/ libxkb.a/XKBCvt.o .libs/libX11.lax/libxkb.a/XKBExtDev.o .libs/ libX11.lax/libxkb.a/XKBGAlloc.o .libs/libX11.lax/libxkb.a/ XKBGeom.o .libs/libX11.lax/libxkb.a/XKBGetByName.o .libs/libX11.lax/ libxkb.a/XKBGetMap.o .libs/libX11.lax/libxkb.a/XKBleds.o .libs/ libX11.lax/libxkb.a/XKBList.o .libs/libX11.lax/libxkb.a/ XKBMAlloc.o .libs/libX11.lax/libxkb.a/XKBMisc.o .libs/libX11.lax/ libxkb.a/XKBNames.o .libs/libX11.lax/libxkb.a/XKBRdBuf.o .libs/ libX11.lax/libxkb.a/XKBSetGeom.o .libs/libX11.lax/libxkb.a/ XKBSetMap.o .libs/libX11.lax/libxkb.a/XKBUse.o -L/opt/local/lib / opt/local/lib/libXau.dylib /opt/local/lib/libXdmcp.dylib - install_name /opt/local/lib/libX11.6.dylib -compatibility_version 9 - current_version 9.0 -Wl,-single_module ld: Undefined symbols: __XlcUtf8Loader /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/libtool: internal link edit command failed make[3]: *** [libX11.la] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all] Error 2 make: *** [all-recursive] Error 1 Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xor g-libX11/work/libX11-1.2" && make all " returned error 2 Command output: Making all in xlibi18n make[3]: Nothing to be done for `all'. Making all in xkb make[3]: Nothing to be done for `all'. cd util && make make[4]: Nothing to be done for `all'. /bin/sh ../libtool --tag=CC --mode=link /usr/bin/gcc-4.0 -I../ include -I../include/X11 -I../include -I../include/X11 -I../src/xcms - I../src/xkb -I../src/xlibi18n -Wall -Wpointer-arith -Wstrict- prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested- externs -fno-strict-aliasing -Wbad-function-cast -Wall -Wpointer- arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing- declarations -Wnested-externs -fno-strict-aliasing -D_BSD_SOURCE - DHAS_FCHOWN -DHAS_STICKY_DIR_BIT -I/opt/local/include -I/opt/local/ include -I/opt/local/include -I/opt/local/include -I/opt/local/ include -DHASXDMAUTH -D_BSD_SOURCE -DX11_t -DTRANS_CLIENT -O2 - version-number 6:2:0 -no-undefined -L/opt/local/lib -o libX11.la - rpath /opt/local/lib AllCells.lo AllowEv.lo AllPlanes.lo AutoRep.lo Backgnd.lo BdrWidth.lo Bell.lo Border.lo ChAccCon.lo ChActPGb.lo ChClMode.lo ChCmap.lo ChGC.lo ChKeyCon.lo ChkIfEv.lo ChkMaskEv.lo ChkTypEv.lo ChkTypWEv.lo ChkWinEv.lo ChPntCon.lo ChProp.lo ChSaveSet.lo ChWAttrs.lo ChWindow.lo CirWin.lo CirWinDn.lo CirWinUp.lo ClDisplay.lo ClearArea.lo Clear.lo ConfWind.lo Context.lo ConvSel.lo CopyArea.lo CopyCmap.lo CopyGC.lo CopyPlane.lo CrBFData.lo CrCmap.lo CrCursor.lo CrGC.lo CrGlCur.lo CrPFBData.lo CrPixmap.lo CrWindow.lo Cursor.lo DefCursor.lo DelProp.lo Depths.lo DestSubs.lo DestWind.lo DisName.lo DrArc.lo DrArcs.lo DrLine.lo DrLines.lo DrPoint.lo DrPoints.lo DrRect.lo DrRects.lo DrSegs.lo ErrDes.lo ErrHndlr.lo evtomask.lo EvToWire.lo FetchName.lo FillArc.lo FillArcs.lo FillPoly.lo FillRct.lo FillRcts.lo FilterEv.lo Flush.lo Font.lo FontInfo.lo FontNames.lo FreeCmap.lo FreeCols.lo FreeCurs.lo FreeEData.lo FreeGC.lo FreePix.lo FSSaver.lo FSWrap.lo GCMisc.lo Geom.lo GetAtomNm.lo GetColor.lo GetDflt.lo GetFPath.lo GetFProp.lo GetGCVals.lo GetGeom.lo GetHColor.lo GetHints.lo GetIFocus.lo GetImage.lo GetKCnt.lo GetMoEv.lo GetNrmHint.lo GetPCnt.lo GetPntMap.lo GetProp.lo GetRGBCMap.lo GetSOwner.lo GetSSaver.lo GetStCmap.lo GetTxtProp.lo GetWAttrs.lo GetWMCMapW.lo GetWMProto.lo globals.lo GrButton.lo GrKeybd.lo GrKey.lo GrPointer.lo GrServer.lo Host.lo Iconify.lo IfEvent.lo imConv.lo ImText16.lo ImText.lo ImUtil.lo InitExt.lo InsCmap.lo IntAtom.lo KeyBind.lo KeysymStr.lo KillCl.lo LiHosts.lo LiICmaps.lo LiProps.lo ListExt.lo LoadFont.lo LockDis.lo locking.lo LookupCol.lo LowerWin.lo Macros.lo MapRaised.lo MapSubs.lo MapWindow.lo MaskEvent.lo Misc.lo ModMap.lo MoveWin.lo NextEvent.lo OCWrap.lo OMWrap.lo OpenDis.lo ParseCmd.lo ParseCol.lo ParseGeom.lo PeekEvent.lo PeekIfEv.lo Pending.lo PixFormats.lo PmapBgnd.lo PmapBord.lo PolyReg.lo PolyTxt16.lo PolyTxt.lo PropAlloc.lo PutBEvent.lo PutImage.lo Quarks.lo QuBest.lo QuColor.lo QuColors.lo QuCurShp.lo QuExt.lo QuKeybd.lo QuPntr.lo QuStipShp.lo QuTextE16.lo QuTextExt.lo QuTileShp.lo QuTree.lo RaiseWin.lo RdBitF.lo RecolorC.lo ReconfWin.lo ReconfWM.lo Region.lo RegstFlt.lo RepWindow.lo RestackWs.lo RotProp.lo ScrResStr.lo SelInput.lo SendEvent.lo SetBack.lo SetClMask.lo SetClOrig.lo SetCRects.lo SetDashes.lo SetFont.lo SetFore.lo SetFPath.lo SetFunc.lo SetHints.lo SetIFocus.lo SetLocale.lo SetLStyle.lo SetNrmHint.lo SetPMask.lo SetPntMap.lo SetRGBCMap.lo SetSOwner.lo SetSSaver.lo SetState.lo SetStCmap.lo SetStip.lo SetTile.lo SetTSOrig.lo SetTxtProp.lo SetWMCMapW.lo SetWMProto.lo StBytes.lo StColor.lo StColors.lo StName.lo StNColor.lo StrKeysym.lo StrToText.lo Sync.lo Synchro.lo Text16.lo Text.lo TextExt16.lo TextExt.lo TextToStr.lo TrCoords.lo UndefCurs.lo UngrabBut.lo UngrabKbd.lo UngrabKey.lo UngrabPtr.lo UngrabSvr.lo UninsCmap.lo UnldFont.lo UnmapSubs.lo UnmapWin.lo VisUtil.lo WarpPtr.lo Window.lo WinEvent.lo Withdraw.lo WMGeom.lo WMProps.lo WrBitF.lo XlibAsync.lo XlibInt.lo Xrm.lo ConnDis.lo x11_trans.lo xlibi18n/libi18n.la xcms/libxcms.la xkb/libxkb.la -L/opt/ local/lib -lXau -L/opt/local/lib -lXdmcp rm -fr .libs/libX11.lax rm -fr .libs/libX11.lax mkdir .libs/libX11.lax rm -fr .libs/libX11.lax/libi18n.a mkdir .libs/libX11.lax/libi18n.a Extracting /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xor g-libX11/work/libX11-1.2/src/xlibi18n/.libs/libi18n.a (cd .libs/libX11.lax/libi18n.a && ar x /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xor g-libX11/work/libX11-1.2/src/xlibi18n/.libs/libi18n.a) rm -fr .libs/libX11.lax/libxcms.a mkdir .libs/libX11.lax/libxcms.a Extracting /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xor g-libX11/work/libX11-1.2/src/xcms/.libs/libxcms.a (cd .libs/libX11.lax/libxcms.a && ar x /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xor g-libX11/work/libX11-1.2/src/xcms/.libs/libxcms.a) rm -fr .libs/libX11.lax/libxkb.a mkdir .libs/libX11.lax/libxkb.a Extracting /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xor g-libX11/work/libX11-1.2/src/xkb/.libs/libxkb.a (cd .libs/libX11.lax/libxkb.a && ar x /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_xor g-libX11/work/libX11-1.2/src/xkb/.libs/libxkb.a) /usr/bin/gcc-4.0 -dynamiclib -o .libs/libX11.6.2.0.dylib .libs/ AllCells.o .libs/AllowEv.o .libs/AllPlanes.o .libs/AutoRep.o .libs/ Backgnd.o .libs/BdrWidth.o .libs/Bell.o .libs/Border.o .libs/ ChAccCon.o .libs/ChActPGb.o .libs/ChClMode.o .libs/ChCmap.o .libs/ ChGC.o .libs/ChKeyCon.o .libs/ChkIfEv.o .libs/ChkMaskEv.o .libs/ ChkTypEv.o .libs/ChkTypWEv.o .libs/ChkWinEv.o .libs/ChPntCon.o .libs/ ChProp.o .libs/ChSaveSet.o .libs/ChWAttrs.o .libs/ChWindow.o .libs/ CirWin.o .libs/CirWinDn.o .libs/CirWinUp.o .libs/ClDisplay.o .libs/ ClearArea.o .libs/Clear.o .libs/ConfWind.o .libs/Context.o .libs/ ConvSel.o .libs/CopyArea.o .libs/CopyCmap.o .libs/CopyGC.o .libs/ CopyPlane.o .libs/CrBFData.o .libs/CrCmap.o .libs/CrCursor.o .libs/ CrGC.o .libs/CrGlCur.o .libs/CrPFBData.o .libs/CrPixmap.o .libs/ CrWindow.o .libs/Cursor.o .libs/DefCursor.o .libs/DelProp.o .libs/ Depths.o .libs/DestSubs.o .libs/DestWind.o .libs/DisName.o .libs/ DrArc.o .libs/DrArcs.o .libs/DrLine.o .libs/DrLines.o .libs/ DrPoint.o .libs/DrPoints.o .libs/DrRect.o .libs/DrRects.o .libs/ DrSegs.o .libs/ErrDes.o .libs/ErrHndlr.o .libs/evtomask.o .libs/ EvToWire.o .libs/FetchName.o .libs/FillArc.o .libs/FillArcs.o .libs/ FillPoly.o .libs/FillRct.o .libs/FillRcts.o .libs/FilterEv.o .libs/ Flush.o .libs/Font.o .libs/FontInfo.o .libs/FontNames.o .libs/ FreeCmap.o .libs/FreeCols.o .libs/FreeCurs.o .libs/FreeEData.o .libs/ FreeGC.o .libs/FreePix.o .libs/FSSaver.o .libs/FSWrap.o .libs/ GCMisc.o .libs/Geom.o .libs/GetAtomNm.o .libs/GetColor.o .libs/ GetDflt.o .libs/GetFPath.o .libs/GetFProp.o .libs/GetGCVals.o .libs/ GetGeom.o .libs/GetHColor.o .libs/GetHints.o .libs/GetIFocus.o .libs/ GetImage.o .libs/GetKCnt.o .libs/GetMoEv.o .libs/GetNrmHint.o .libs/ GetPCnt.o .libs/GetPntMap.o .libs/GetProp.o .libs/GetRGBCMap.o .libs/ GetSOwner.o .libs/GetSSaver.o .libs/GetStCmap.o .libs/ GetTxtProp.o .libs/GetWAttrs.o .libs/GetWMCMapW.o .libs/ GetWMProto.o .libs/globals.o .libs/GrButton.o .libs/GrKeybd.o .libs/ GrKey.o .libs/GrPointer.o .libs/GrServer.o .libs/Host.o .libs/ Iconify.o .libs/IfEvent.o .libs/imConv.o .libs/ImText16.o .libs/ ImText.o .libs/ImUtil.o .libs/InitExt.o .libs/InsCmap.o .libs/ IntAtom.o .libs/KeyBind.o .libs/KeysymStr.o .libs/KillCl.o .libs/ LiHosts.o .libs/LiICmaps.o .libs/LiProps.o .libs/ListExt.o .libs/ LoadFont.o .libs/LockDis.o .libs/locking.o .libs/LookupCol.o .libs/ LowerWin.o .libs/Macros.o .libs/MapRaised.o .libs/MapSubs.o .libs/ MapWindow.o .libs/MaskEvent.o .libs/Misc.o .libs/ModMap.o .libs/ MoveWin.o .libs/NextEvent.o .libs/OCWrap.o .libs/OMWrap.o .libs/ OpenDis.o .libs/ParseCmd.o .libs/ParseCol.o .libs/ParseGeom.o .libs/ PeekEvent.o .libs/PeekIfEv.o .libs/Pending.o .libs/PixFormats.o .libs/ PmapBgnd.o .libs/PmapBord.o .libs/PolyReg.o .libs/PolyTxt16.o .libs/ PolyTxt.o .libs/PropAlloc.o .libs/PutBEvent.o .libs/PutImage.o .libs/ Quarks.o .libs/QuBest.o .libs/QuColor.o .libs/QuColors.o .libs/ QuCurShp.o .libs/QuExt.o .libs/QuKeybd.o .libs/QuPntr.o .libs/ QuStipShp.o .libs/QuTextE16.o .libs/QuTextExt.o .libs/ QuTileShp.o .libs/QuTree.o .libs/RaiseWin.o .libs/RdBitF.o .libs/ RecolorC.o .libs/ReconfWin.o .libs/ReconfWM.o .libs/Region.o .libs/ RegstFlt.o .libs/RepWindow.o .libs/RestackWs.o .libs/RotProp.o .libs/ ScrResStr.o .libs/SelInput.o .libs/SendEvent.o .libs/SetBack.o .libs/ SetClMask.o .libs/SetClOrig.o .libs/SetCRects.o .libs/ SetDashes.o .libs/SetFont.o .libs/SetFore.o .libs/SetFPath.o .libs/ SetFunc.o .libs/SetHints.o .libs/SetIFocus.o .libs/SetLocale.o .libs/ SetLStyle.o .libs/SetNrmHint.o .libs/SetPMask.o .libs/ SetPntMap.o .libs/SetRGBCMap.o .libs/SetSOwner.o .libs/ SetSSaver.o .libs/SetState.o .libs/SetStCmap.o .libs/SetStip.o .libs/ SetTile.o .libs/SetTSOrig.o .libs/SetTxtProp.o .libs/ SetWMCMapW.o .libs/SetWMProto.o .libs/StBytes.o .libs/StColor.o .libs/ StColors.o .libs/StName.o .libs/StNColor.o .libs/StrKeysym.o .libs/ StrToText.o .libs/Sync.o .libs/Synchro.o .libs/Text16.o .libs/ Text.o .libs/TextExt16.o .libs/TextExt.o .libs/TextToStr.o .libs/ TrCoords.o .libs/UndefCurs.o .libs/UngrabBut.o .libs/ UngrabKbd.o .libs/UngrabKey.o .libs/UngrabPtr.o .libs/ UngrabSvr.o .libs/UninsCmap.o .libs/UnldFont.o .libs/ UnmapSubs.o .libs/UnmapWin.o .libs/VisUtil.o .libs/WarpPtr.o .libs/ Window.o .libs/WinEvent.o .libs/Withdraw.o .libs/WMGeom.o .libs/ WMProps.o .libs/WrBitF.o .libs/XlibAsync.o .libs/XlibInt.o .libs/ Xrm.o .libs/ConnDis.o .libs/x11_trans.o .libs/libX11.lax/libi18n.a/ ICWrap.o .libs/libX11.lax/libi18n.a/imCallbk.o .libs/libX11.lax/ libi18n.a/imDefFlt.o .libs/libX11.lax/libi18n.a/imDefIc.o .libs/ libX11.lax/libi18n.a/imDefIm.o .libs/libX11.lax/libi18n.a/ imDefLkup.o .libs/libX11.lax/libi18n.a/imDispch.o .libs/libX11.lax/ libi18n.a/imEvToWire.o .libs/libX11.lax/libi18n.a/imExten.o .libs/ libX11.lax/libi18n.a/imImSw.o .libs/libX11.lax/libi18n.a/ imInsClbk.o .libs/libX11.lax/libi18n.a/imInt.o .libs/libX11.lax/ libi18n.a/imKStoUCS.o .libs/libX11.lax/libi18n.a/imLcFlt.o .libs/ libX11.lax/libi18n.a/imLcGIc.o .libs/libX11.lax/libi18n.a/ imLcIc.o .libs/libX11.lax/libi18n.a/imLcIm.o .libs/libX11.lax/ libi18n.a/imLcLkup.o .libs/libX11.lax/libi18n.a/imLcPrs.o .libs/ libX11.lax/libi18n.a/imLcSIc.o .libs/libX11.lax/libi18n.a/ imRm.o .libs/libX11.lax/libi18n.a/imRmAttr.o .libs/libX11.lax/ libi18n.a/imThaiFlt.o .libs/libX11.lax/libi18n.a/imThaiIc.o .libs/ libX11.lax/libi18n.a/imThaiIm.o .libs/libX11.lax/libi18n.a/ imTrans.o .libs/libX11.lax/libi18n.a/imTransR.o .libs/libX11.lax/ libi18n.a/imTrX.o .libs/libX11.lax/libi18n.a/IMWrap.o .libs/ libX11.lax/libi18n.a/lcCharSet.o .libs/libX11.lax/libi18n.a/ lcConv.o .libs/libX11.lax/libi18n.a/lcCT.o .libs/libX11.lax/libi18n.a/ lcDB.o .libs/libX11.lax/libi18n.a/lcDefConv.o .libs/libX11.lax/ libi18n.a/lcDynamic.o .libs/libX11.lax/libi18n.a/lcEuc.o .libs/ libX11.lax/libi18n.a/lcFile.o .libs/libX11.lax/libi18n.a/ lcGenConv.o .libs/libX11.lax/libi18n.a/lcGeneric.o .libs/libX11.lax/ libi18n.a/lcInit.o .libs/libX11.lax/libi18n.a/lcJis.o .libs/ libX11.lax/libi18n.a/lcPrTxt.o .libs/libX11.lax/libi18n.a/ lcPublic.o .libs/libX11.lax/libi18n.a/lcPubWrap.o .libs/libX11.lax/ libi18n.a/lcRM.o .libs/libX11.lax/libi18n.a/lcSjis.o .libs/libX11.lax/ libi18n.a/lcStd.o .libs/libX11.lax/libi18n.a/lcTxtPr.o .libs/ libX11.lax/libi18n.a/lcUTF8.o .libs/libX11.lax/libi18n.a/ lcUtil.o .libs/libX11.lax/libi18n.a/lcWrap.o .libs/libX11.lax/ libi18n.a/mbWMProps.o .libs/libX11.lax/libi18n.a/mbWrap.o .libs/ libX11.lax/libi18n.a/omDefault.o .libs/libX11.lax/libi18n.a/ omGeneric.o .libs/libX11.lax/libi18n.a/omImText.o .libs/libX11.lax/ libi18n.a/omText.o .libs/libX11.lax/libi18n.a/omTextEsc.o .libs/ libX11.lax/libi18n.a/omTextExt.o .libs/libX11.lax/libi18n.a/ omTextPer.o .libs/libX11.lax/libi18n.a/omXChar.o .libs/libX11.lax/ libi18n.a/utf8WMProps.o .libs/libX11.lax/libi18n.a/utf8Wrap.o .libs/ libX11.lax/libi18n.a/wcWrap.o .libs/libX11.lax/libi18n.a/ XDefaultIMIF.o .libs/libX11.lax/libi18n.a/XDefaultOMIF.o .libs/ libX11.lax/libi18n.a/xim_trans.o .libs/libX11.lax/libxcms.a/ AddDIC.o .libs/libX11.lax/libxcms.a/AddSF.o .libs/libX11.lax/ libxcms.a/CCC.o .libs/libX11.lax/libxcms.a/cmsAllCol.o .libs/ libX11.lax/libxcms.a/cmsAllNCol.o .libs/libX11.lax/libxcms.a/ cmsCmap.o .libs/libX11.lax/libxcms.a/cmsColNm.o .libs/libX11.lax/ libxcms.a/cmsGlobls.o .libs/libX11.lax/libxcms.a/cmsInt.o .libs/ libX11.lax/libxcms.a/cmsLkCol.o .libs/libX11.lax/libxcms.a/ cmsMath.o .libs/libX11.lax/libxcms.a/cmsProp.o .libs/libX11.lax/ libxcms.a/cmsTrig.o .libs/libX11.lax/libxcms.a/CvCols.o .libs/ libX11.lax/libxcms.a/CvColW.o .libs/libX11.lax/libxcms.a/HVC.o .libs/ libX11.lax/libxcms.a/HVCGcC.o .libs/libX11.lax/libxcms.a/ HVCGcV.o .libs/libX11.lax/libxcms.a/HVCGcVC.o .libs/libX11.lax/ libxcms.a/HVCMnV.o .libs/libX11.lax/libxcms.a/HVCMxC.o .libs/ libX11.lax/libxcms.a/HVCMxV.o .libs/libX11.lax/libxcms.a/ HVCMxVC.o .libs/libX11.lax/libxcms.a/HVCMxVs.o .libs/libX11.lax/ libxcms.a/HVCWpAj.o .libs/libX11.lax/libxcms.a/IdOfPr.o .libs/ libX11.lax/libxcms.a/Lab.o .libs/libX11.lax/libxcms.a/LabGcC.o .libs/ libX11.lax/libxcms.a/LabGcL.o .libs/libX11.lax/libxcms.a/ LabGcLC.o .libs/libX11.lax/libxcms.a/LabMnL.o .libs/libX11.lax/ libxcms.a/LabMxC.o .libs/libX11.lax/libxcms.a/LabMxL.o .libs/ libX11.lax/libxcms.a/LabMxLC.o .libs/libX11.lax/libxcms.a/ LabWpAj.o .libs/libX11.lax/libxcms.a/LRGB.o .libs/libX11.lax/ libxcms.a/Luv.o .libs/libX11.lax/libxcms.a/LuvGcC.o .libs/libX11.lax/ libxcms.a/LuvGcL.o .libs/libX11.lax/libxcms.a/LuvGcLC.o .libs/ libX11.lax/libxcms.a/LuvMnL.o .libs/libX11.lax/libxcms.a/ LuvMxC.o .libs/libX11.lax/libxcms.a/LuvMxL.o .libs/libX11.lax/ libxcms.a/LuvMxLC.o .libs/libX11.lax/libxcms.a/LuvWpAj.o .libs/ libX11.lax/libxcms.a/OfCCC.o .libs/libX11.lax/libxcms.a/ PrOfId.o .libs/libX11.lax/libxcms.a/QBlack.o .libs/libX11.lax/ libxcms.a/QBlue.o .libs/libX11.lax/libxcms.a/QGreen.o .libs/ libX11.lax/libxcms.a/QRed.o .libs/libX11.lax/libxcms.a/QuCol.o .libs/ libX11.lax/libxcms.a/QuCols.o .libs/libX11.lax/libxcms.a/ QWhite.o .libs/libX11.lax/libxcms.a/SetCCC.o .libs/libX11.lax/ libxcms.a/SetGetCols.o .libs/libX11.lax/libxcms.a/StCol.o .libs/ libX11.lax/libxcms.a/StCols.o .libs/libX11.lax/libxcms.a/ UNDEFINED.o .libs/libX11.lax/libxcms.a/uvY.o .libs/libX11.lax/ libxcms.a/XRGB.o .libs/libX11.lax/libxcms.a/xyY.o .libs/libX11.lax/ libxcms.a/XYZ.o .libs/libX11.lax/libxkb.a/XKB.o .libs/libX11.lax/ libxkb.a/XKBAlloc.o .libs/libX11.lax/libxkb.a/XKBBell.o .libs/ libX11.lax/libxkb.a/XKBBind.o .libs/libX11.lax/libxkb.a/ XKBCompat.o .libs/libX11.lax/libxkb.a/XKBCtrls.o .libs/libX11.lax/ libxkb.a/XKBCvt.o .libs/libX11.lax/libxkb.a/XKBExtDev.o .libs/ libX11.lax/libxkb.a/XKBGAlloc.o .libs/libX11.lax/libxkb.a/ XKBGeom.o .libs/libX11.lax/libxkb.a/XKBGetByName.o .libs/libX11.lax/ libxkb.a/XKBGetMap.o .libs/libX11.lax/libxkb.a/XKBleds.o .libs/ libX11.lax/libxkb.a/XKBList.o .libs/libX11.lax/libxkb.a/ XKBMAlloc.o .libs/libX11.lax/libxkb.a/XKBMisc.o .libs/libX11.lax/ libxkb.a/XKBNames.o .libs/libX11.lax/libxkb.a/XKBRdBuf.o .libs/ libX11.lax/libxkb.a/XKBSetGeom.o .libs/libX11.lax/libxkb.a/ XKBSetMap.o .libs/libX11.lax/libxkb.a/XKBUse.o -L/opt/local/lib / opt/local/lib/libXau.dylib /opt/local/lib/libXdmcp.dylib - install_name /opt/local/lib/libX11.6.dylib -compatibility_version 9 - current_version 9.0 -Wl,-single_module ld: Undefined symbols: __XlcUtf8Loader /usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/libtool: internal link edit command failed make[3]: *** [libX11.la] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all] Error 2 make: *** [all-recursive] Error 1 Warning: the following items did not execute (for xorg-libX11): org.macports.destroot org.macports.build DEBUG: invalid command name "::ui_init" while executing "::ui_init $priority $prefix $channels $message" ("uplevel" body line 2) invoked from within "uplevel 1 $body" Error: Unable to upgrade port: 1 following the: sudo port -d upgrade installed command. The interesting thing is that MacPorts began repeating the attempts to build xorg-libX11 in a loop to where I had to use a control C to terminate the process. I tried sending an attachment containing the repeated sequencing; but, the file exceeded the 150K limit. If someone would like a copy of the file, please okay the transfer or provide another address that accepts a 300K file. Frank J. R. Hanstick trog24 at comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From raimue at macports.org Tue Mar 24 17:11:19 2009 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Wed, 25 Mar 2009 01:11:19 +0100 Subject: Problems with pango In-Reply-To: References: Message-ID: <49C976A7.2080306@macports.org> Andrei Tchijov wrote: > [local/bin] > install gtk2 +quartz +no_x11 > ---> Fetching gtk2 > Error: Please uninstall or deactivate the pango port and reinstall it > by running `port install pango +no_x11`. > Error: Target org.macports.fetch returned: pango must be installed > with the no_x11 variant enabled. > Error: Status 1 encountered during processing. You already have pango installed, but for gtk2 +no_x11 you also need pango +no_x11. Isn't the error message quite clear on that? sudo port deactivate pango sudo port install pango +no_x11 You might need to rebuild any port that depends on pango afterwards, I am not sure. If everything went successful, you can uninstall the inactive pango version. Rainer From andrei at tchijov.com Tue Mar 24 17:20:45 2009 From: andrei at tchijov.com (Andrei Tchijov) Date: Tue, 24 Mar 2009 20:20:45 -0400 Subject: Problems with pango In-Reply-To: <49C976A7.2080306@macports.org> References: <49C976A7.2080306@macports.org> Message-ID: <72659822-9B39-4B6B-B85F-3D10660E833A@tchijov.com> Message is quite clear, unfortunately performing these steps does not cure the problem. If you look into command trace in my original e- mail, you will see that 1) I did execute prescribed steps without any success, 2) I do not have X11 version of pango anywhere. Personally I think there is some sort of confusion about "+quartz" and "+no_x11". When you install pango with "+no_x11", you end-up with "+quartz". Below are output from variants and installed [local/bin] > variants pango pango has the variants: macosx: Platform variant, do not select manually quartz: Add Quartz graphics interface no_x11: Disable support for X11 universal: Build for multiple architectures [local/bin] > installed pango The following ports are currently installed: pango @1.24.0_0+macosx+quartz (active) [local/bin] > Looks like "variants" does understand that "no_x11" is there, but port name "pango @1.24.0_0+macosx+quartz" does not contain "+no_x11" for some reason. On Mar 24, 2009, at 20:11 , Rainer M?ller wrote: > Andrei Tchijov wrote: >> [local/bin] > install gtk2 +quartz +no_x11 >> ---> Fetching gtk2 >> Error: Please uninstall or deactivate the pango port and reinstall it >> by running `port install pango +no_x11`. >> Error: Target org.macports.fetch returned: pango must be installed >> with the no_x11 variant enabled. >> Error: Status 1 encountered during processing. > > You already have pango installed, but for gtk2 +no_x11 you also need > pango +no_x11. Isn't the error message quite clear on that? > > sudo port deactivate pango > sudo port install pango +no_x11 > > You might need to rebuild any port that depends on pango afterwards, I > am not sure. If everything went successful, you can uninstall the > inactive pango version. > > Rainer From andrei at tchijov.com Tue Mar 24 17:28:26 2009 From: andrei at tchijov.com (Andrei Tchijov) Date: Tue, 24 Mar 2009 20:28:26 -0400 Subject: Problems with pango In-Reply-To: <49C976A7.2080306@macports.org> References: <49C976A7.2080306@macports.org> Message-ID: <79C1EC85-881F-477B-8A2F-61A8BCD8A31F@tchijov.com> Even stranger ... is there difference between invoking commands from "port interactive mode" and via command line? I have tried to do "deactivate"/"install" sequence from command line (I used to do it in "interactive mode") and result is different. First of all, it did not allow me to do "install pango +no_x11" due to the fact that cairo was installed with "+quartz", but it did allow me to do "install pango +no_x11 +quartz". Now I can continue with my install. Sorry to bother you. Andrei On Mar 24, 2009, at 20:11 , Rainer M?ller wrote: > Andrei Tchijov wrote: >> [local/bin] > install gtk2 +quartz +no_x11 >> ---> Fetching gtk2 >> Error: Please uninstall or deactivate the pango port and reinstall it >> by running `port install pango +no_x11`. >> Error: Target org.macports.fetch returned: pango must be installed >> with the no_x11 variant enabled. >> Error: Status 1 encountered during processing. > > You already have pango installed, but for gtk2 +no_x11 you also need > pango +no_x11. Isn't the error message quite clear on that? > > sudo port deactivate pango > sudo port install pango +no_x11 > > You might need to rebuild any port that depends on pango afterwards, I > am not sure. If everything went successful, you can uninstall the > inactive pango version. > > Rainer From shreevatsa.public at gmail.com Tue Mar 24 20:25:40 2009 From: shreevatsa.public at gmail.com (Shreevatsa R) Date: Tue, 24 Mar 2009 23:25:40 -0400 Subject: stable vs. unstable ports? In-Reply-To: References: Message-ID: <7675454e0903242025m65f886cbya2274d855eda4d43@mail.gmail.com> [Changing the topic from build systems and replying just to the original question] 2009/3/22 Darren Weber : > > I've noticed problems during port upgrades. > > What is the general consensus on having a TAG for each port to indicate it's > "success" status within the system? There is already a low-tech way of doing this: see if any bugs have been reported against the given port. :) Chances are that if others have had problems with upgrades, they would have (hopefully) filed a ticket against the port. Checking this is very easy to do thanks to Rainer M?ller's recently implemented Trac report, e.g. use http://trac.macports.org/report/16?PORT=python25 to see if there are any recent bugs with the python25 port that you care about. > Is it possible to have a meta-port monitor that automatically tracks the > status of each package install and reports that status back to a central > repository to continuously flag the status of a port install.? A simple > dichotomy of stable and unstable might suffice (Debian uses stable, > unstable, and testing).? Perhaps the monitoring system could provide the > data required to justify these port status levels. Note that what Debian does is something quite a bit more: they have entirely different *sets* of ports marked stable, testing, unstable and users choose to install all their packages from the same set ("tree"). This is fine for Debian to do because they have enough people, but it would not be a good idea for MacPorts: having to maintain multiple sets of inter-compatible ports leads to too much fragmentation and the situation might end up similar to that with Fink: the stable ports work very well but are too outdated for most purposes, the unstable ports are really unstable and *still* quite a bit older than in MacPorts. Having only one current version of each port, which everyone gets and reports bugs against etc. is one of MacPorts's strengths. From andrei at tchijov.com Tue Mar 24 20:48:45 2009 From: andrei at tchijov.com (Andrei Tchijov) Date: Tue, 24 Mar 2009 23:48:45 -0400 Subject: Problems with pango In-Reply-To: <49C976A7.2080306@macports.org> References: <49C976A7.2080306@macports.org> Message-ID: <25EAA888-C267-42E8-85CA-104878A28AD2@tchijov.com> I finally was able to build X11-less version of gimp. The only problem [local/bin] > install gimp +quartz ---> Building ufraw Error: Target org.macports.build returned: shell command " cd "/opt/ local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_graphics_ufraw/work/ufraw-0.15" && make all " returned error 2 Command output: make all-recursive Making all in po make[2]: Nothing to be done for `all'. Making all in icons make[2]: Nothing to be done for `all'. /usr/bin/g++-4.0 -O2 -L/opt/local/lib -o ufraw ufraw.o libufraw.a - R/opt/local/lib -Wl,-framework -Wl,CoreFoundation -L/opt/local/lib - lexiv2 -lintl -lc -liconv -lz -lexpat -L/opt/local/lib -lglib-2.0 - lintl -liconv -L/opt/local/lib -llcms -L/opt/local/lib -lpng12 - lz -L/opt/local/lib -lgtkimageview -lgtk-quartz-2.0 -lgdk-quartz-2.0 -latk-1.0 -lgio-2.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lcairo - lpangoft2-1.0 -lpango-1.0 -lm -lpixman-1 -lfontconfig -lexpat - lfreetype -lpng12 -lz -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lintl - liconv -ltiff -ljpeg -lbz2 -lz -lintl Undefined symbols: "_CMCloseProfile", referenced from: _uf_get_display_profile in libufraw.a(uf_gtk.o) "_CMFlattenProfile", referenced from: _uf_get_display_profile in libufraw.a(uf_gtk.o) "_CMGetProfileByAVID", referenced from: _uf_get_display_profile in libufraw.a(uf_gtk.o) ld: symbol(s) not found collect2: ld returned 1 exit status make[2]: *** [ufraw] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Error: The following dependencies failed to build: ufraw xsane sane- backends libusb Error: Status 1 encountered during processing. [local/bin] > Am I correct that this has something to do with scanner support? Gimp is running more or less fine. I guess I will have to stay away fro scanner. Andrei On Mar 24, 2009, at 20:11 , Rainer M?ller wrote: > Andrei Tchijov wrote: >> [local/bin] > install gtk2 +quartz +no_x11 >> ---> Fetching gtk2 >> Error: Please uninstall or deactivate the pango port and reinstall it >> by running `port install pango +no_x11`. >> Error: Target org.macports.fetch returned: pango must be installed >> with the no_x11 variant enabled. >> Error: Status 1 encountered during processing. > > You already have pango installed, but for gtk2 +no_x11 you also need > pango +no_x11. Isn't the error message quite clear on that? > > sudo port deactivate pango > sudo port install pango +no_x11 > > You might need to rebuild any port that depends on pango afterwards, I > am not sure. If everything went successful, you can uninstall the > inactive pango version. > > Rainer From dave.evans55 at googlemail.com Wed Mar 25 03:30:44 2009 From: dave.evans55 at googlemail.com (David Evans) Date: Wed, 25 Mar 2009 10:30:44 +0000 Subject: some kde ports, phonon, and qt4-mac Message-ID: <49CA07D4.1070001@googlemail.com> Previously I said: >While upgrading phonon I get this message: > >-- Found Qt-Version 4.4.3 (using /opt/local/libexec/qt4-mac/bin/qmake) >-- Found Threads: TRUE >-- Found Automoc4: /opt/local/bin/automoc4 >CMake Error at CMakeLists.txt:134 (message): > Qt compiled without support for -fvisibility=hidden. This will break > plugins and linking of some applications. Please fix your Qt installation. > >I get the same message with these ports: > >kdebase4 kdelibs4 kdepimlibs4 phonon >I've recompiled qt4-mac and still get the same message. I believe I have now found the cause of this. I think it is because of ccache. I've disabled ccache in /opt/local/etc/macports/macports.conf and recompiled qt4-mac (both the old version and the one that appeared a couple of days ago. Now I no longer get the above message about -fvisibility=hidden. Rebuilding qt4-mac with ccache makes the message reappear. See also bug 18912 which says more or less the same thing. From gregreedee at gmail.com Wed Mar 25 04:37:59 2009 From: gregreedee at gmail.com (Gregory Dodwell) Date: Wed, 25 Mar 2009 22:37:59 +1100 Subject: Gnucash crashes on launch: no, I don't have mesa Message-ID: <789f92700903250437l1205ec7do251ea17b9b703021@mail.gmail.com> OSX 10.5.6 "Leopard" on Intel iMac Xquartz 2.3.2 Latest MacPorts: version 1.700 trying to run after installation today: Here's me: /opt/local/bin/gnucash-bin In reply a partially drawn splash for a couple of seconds then: gnc.bin-Message: main: binreloc relocation support was disabled at configure time. Xlib: extension "RANDR" missing on display "/tmp/launch-IUF4Zq/:0". Abort trap Any clues? -------------- next part -------------- An HTML attachment was scrubbed... URL: From gigantaur at optusnet.com.au Wed Mar 25 04:55:08 2009 From: gigantaur at optusnet.com.au (Chris) Date: Wed, 25 Mar 2009 22:55:08 +1100 Subject: perl Makefile.PL for XMLTV causes Bus Error Message-ID: <49CA1B9C.1070006@optusnet.com.au> Gday all, I am new to the list - apols if I'm misisng something obvious. I am getting a Bus Error when trying perl Makefile.PL as the first step for installing XMLTV (after sucessfully installing the pre-reqs). Macports 1.70, Leopard 10.5.6 (Intel) with Security Update 2009-001! After many attempts I've tried a clean Leopard install (on my Intel mac) - the default version of xcode (that came with leopard) as well as xcode3.12. I've tried ports Perl 5.8(9) and 5.10 as well as source for xmltv-0.5.49 xmltv-0.5.50 xmltv-0.5.51 xmltv-0.5.52 xmltv-0.5.53 xmltv-0.5.54 xmltv-0.5.55 from sourceforge I was able to succesfully compile and install xmltv_prereq-8 and I can compile xmltv with the native vendor/apple shipped Perl. Has anyone got any ideas ? I tried searching for hints on how to debug a bus error but there is not much I can find I started down this path (macports/perl/xmltv) as I got badly bitten by Security Update 2009-001 breaking Apple shipped Perl See http://discussions.apple.com/thread.jspa?messageID=9022650#9022650 thanks in advance, Chris From olaf at foellinger.de Wed Mar 25 11:09:44 2009 From: olaf at foellinger.de (Olaf Foellinger) Date: Wed, 25 Mar 2009 19:09:44 +0100 Subject: Gnucash crashes on launch: no, I don't have mesa In-Reply-To: <789f92700903250437l1205ec7do251ea17b9b703021@mail.gmail.com> References: <789f92700903250437l1205ec7do251ea17b9b703021@mail.gmail.com> Message-ID: <20090325180944.GA1167@foellinger.de> Hi, * Gregory Dodwell [25.03.09 12:38]wrote: > OSX 10.5.6 "Leopard" on Intel iMac > Xquartz 2.3.2 > Latest MacPorts: version 1.700 > trying to run after installation today: > Here's me: /opt/local/bin/gnucash-bin > In reply a partially drawn splash for a couple of seconds then: > gnc.bin-Message: main: binreloc relocation support was disabled at > configure time. > Xlib: extension "RANDR" missing on display "/tmp/launch-IUF4Zq/:0". > Abort trap > Any clues? maybe you can try the script /opt/local/bin/gnucash? Gru? Olaf From ms at mac-specialist.com Wed Mar 25 11:23:26 2009 From: ms at mac-specialist.com (Bill Hernandez) Date: Wed, 25 Mar 2009 13:23:26 -0500 Subject: runpsync triggers error - Can't locate MacOSX/File.pm Message-ID: <58617346-470A-47B3-B0D4-E964BDFCC7EB@mac-specialist.com> I've been seeing some errors during startup in the system log for sometime now, so the other day I decided to do an archive/install of the operating system. I still have the same system log errors during startup, but everything seems to be working well. I've been using runpsync for a long time and all of the sudden it is not working as shown below: [2009.25.03](11:15AM) -> [roscoe] ~ $ sudo /usr/local/bin/runpsync 0 - d 0 '/' '/Volumes/Backup_24' Password: Backup begun Wed Mar 25 11:16:18 2009 Can't locate MacOSX/File.pm in @INC (@INC contains: /System/Library/Perl/5.8.8/darwin-thread-multi-2level /System/Library/Perl/5.8.8 /Library/Perl/5.8.8/darwin-thread-multi-2level /Library/Perl/5.8.8 /Library/Perl /Network/Library/Perl/5.8.8/darwin-thread-multi-2level /Network/Library/Perl/5.8.8 /Network/Library/Perl /System/Library/Perl/Extras/5.8.8/darwin-thread-multi-2level /System/Library/Perl/Extras/5.8.8 /Library/Perl/5.8.6 /Library/Perl/5.8.1 .) at /usr/local/bin/psync line 14. BEGIN failed--compilation aborted at /usr/local/bin/psync line 14. Backup completed: Wed Mar 25 11:16:19 2009[2009.25.03](11:16AM) -> [roscoe] ~ $ WHEN I do a search for 'File.pm', I seem to find a bunch of them. Not quite sure what has happened ? FILES FOUND : /opt/local/lib/perl5/5.8.9/darwin-2level/IO/File.pm /opt/local/lib/perl5/5.8.9/Digest/file.pm /opt/local/lib/perl5/5.8.9/Tie/File.pm /opt/local/var/macports/software/perl5.8/5.8.8_3+darwin_9/opt/local/ lib/perl5/5.8.8/darwin-2level/IO/File.pm /opt/local/var/macports/software/perl5.8/5.8.8_3+darwin_9/opt/local/ lib/perl5/5.8.8/Digest/file.pm /opt/local/var/macports/software/perl5.8/5.8.8_3+darwin_9/opt/local/ lib/perl5/5.8.8/Tie/File.pm /opt/local/var/macports/software/perl5.8/5.8.9_2/opt/local/lib/ perl5/5.8.9/darwin-2level/IO/File.pm /opt/local/var/macports/software/perl5.8/5.8.9_2/opt/local/lib/ perl5/5.8.9/Digest/file.pm /opt/local/var/macports/software/perl5.8/5.8.9_2/opt/local/lib/ perl5/5.8.9/Tie/File.pm /System/Library/Perl/5.8.8/darwin-thread-multi-2level/IO/File.pm /System/Library/Perl/5.8.8/Digest/file.pm /System/Library/Perl/5.8.8/Tie/File.pm /System/Library/Perl/Extras/5.8.8/Archive/Tar/File.pm /System/Library/Perl/Extras/5.8.8/darwin-thread-multi-2level/DBD/File.pm /System/Library/Perl/Extras/5.8.8/LWP/Protocol/file.pm /System/Library/Perl/Extras/5.8.8/Path/Class/File.pm /System/Library/Perl/Extras/5.8.8/Regexp/Common/URI/file.pm /System/Library/Perl/Extras/5.8.8/URI/file.pm Any ideas ? Bill Hernandez Plano, Texas From raimue at macports.org Wed Mar 25 12:50:38 2009 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Wed, 25 Mar 2009 20:50:38 +0100 Subject: runpsync triggers error - Can't locate MacOSX/File.pm In-Reply-To: <58617346-470A-47B3-B0D4-E964BDFCC7EB@mac-specialist.com> References: <58617346-470A-47B3-B0D4-E964BDFCC7EB@mac-specialist.com> Message-ID: <49CA8B0E.6050004@macports.org> Bill Hernandez wrote: > [2009.25.03](11:15AM) -> [roscoe] ~ $ sudo /usr/local/bin/runpsync 0 - > d 0 '/' '/Volumes/Backup_24' > Password: > > Backup begun Wed Mar 25 11:16:18 2009 > > Can't locate MacOSX/File.pm in @INC (@INC contains: > > /System/Library/Perl/5.8.8/darwin-thread-multi-2level > /System/Library/Perl/5.8.8 > /Library/Perl/5.8.8/darwin-thread-multi-2level > /Library/Perl/5.8.8 > /Library/Perl > /Network/Library/Perl/5.8.8/darwin-thread-multi-2level > /Network/Library/Perl/5.8.8 > /Network/Library/Perl > /System/Library/Perl/Extras/5.8.8/darwin-thread-multi-2level > /System/Library/Perl/Extras/5.8.8 > /Library/Perl/5.8.6 > /Library/Perl/5.8.1 .) at /usr/local/bin/psync line 14. > > BEGIN failed--compilation aborted at /usr/local/bin/psync line 14. > Backup completed: Wed Mar 25 11:16:19 2009[2009.25.03](11:16AM) -> > [roscoe] ~ $ Looks like your psync is using /usr/bin/perl instead of /opt/local/bin/perl. > WHEN I do a search for 'File.pm', I seem to find a bunch of them. Not > quite sure what has happened ? $ port provides /opt/local/lib/perl5/vendor_perl/5.8.8/darwin-thread-multi-2level/MacOSX/File.pm /opt/local/lib/perl5/vendor_perl/5.8.8/darwin-thread-multi-2level/MacOSX/File.pm is provided by: p5-macosx-file You probably don't have p5-macosx-file installed? Rainer From ms at mac-specialist.com Wed Mar 25 15:16:00 2009 From: ms at mac-specialist.com (Bill Hernandez) Date: Wed, 25 Mar 2009 17:16:00 -0500 Subject: runpsync triggers error - Can't locate MacOSX/File.pm In-Reply-To: <58617346-470A-47B3-B0D4-E964BDFCC7EB@mac-specialist.com> References: <58617346-470A-47B3-B0D4-E964BDFCC7EB@mac-specialist.com> Message-ID: I just found these. http://developers.slashdot.org/article.pl?sid=09/02/18/1435227 http://www.theregister.co.uk/2009/02/16/apple_update_perl_breakage/ http://bulknews.typepad.com/blog/2009/02/mac-os-x-security-update-2009001-breaks-perl-cpan.html On Mar 25, 2009, at 1:23 PM, Bill Hernandez wrote: > I've been seeing some errors during startup in the system log for > sometime now, so the other day I decided to do an archive/install of > the operating system. > > I still have the same system log errors during startup, but > everything seems to be working well. > > I've been using runpsync for a long time and all of the sudden it is > not working as shown below: > > [2009.25.03](11:15AM) -> [roscoe] ~ $ sudo /usr/local/bin/runpsync 0 > -d 0 '/' '/Volumes/Backup_24' > Password: > From raimue at macports.org Wed Mar 25 15:33:13 2009 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Wed, 25 Mar 2009 23:33:13 +0100 Subject: runpsync triggers error - Can't locate MacOSX/File.pm In-Reply-To: <880A28DB-47FB-469A-8025-E34EA6761769@mac-specialist.com> References: <58617346-470A-47B3-B0D4-E964BDFCC7EB@mac-specialist.com> <49CA8B0E.6050004@macports.org> <9ABFD30E-CBFA-4E75-AA49-61867E96D1BB@mac-specialist.com> <49CA9DAC.3030009@macports.org> <880A28DB-47FB-469A-8025-E34EA6761769@mac-specialist.com> Message-ID: <49CAB129.6090708@macports.org> Bill Hernandez wrote: > I normally do everything associated with MacPorts via the Terminal, > but the other day I updated all the ports installed using > PortAuthority, and it installed perl > > I changed : > > FROM : #!/usr/bin/perl > TO : #!/opt/local/bin/perl > > In both /usr/bin/runpsync, and /usr/bin/psync I assume you meant /usr/local/bin here? > in psync I also changed : > > FROM : # eval 'exec /usr/bin/perl -S $0 ${1+"$@"}' > TO : eval '/opt/local/bin/perl -S $0 ${1+"$@"}' Looks good. > [2009.25.03](04:30PM) -> [roscoe] ~ $ sudo /usr/local/bin/runpsync 0 - > d 0 '/' '/Volumes/Backup_5' > Password: > Backup begun Wed Mar 25 16:31:16 2009 > Can't locate DB_File.pm in @INC (@INC contains: > /opt/local/lib/perl5/5.8.9/darwin-2level > /opt/local/lib/perl5/5.8.9 > /opt/local/lib/perl5/site_perl/5.8.9/darwin-2level > /opt/local/lib/perl5/site_perl/5.8.9 > /opt/local/lib/perl5/site_perl > /opt/local/lib/perl5/vendor_perl/5.8.9/darwin-2level > /opt/local/lib/perl5/vendor_perl/5.8.9 > /opt/local/lib/perl5/vendor_perl/5.8.8 > /opt/local/lib/perl5/vendor_perl/5.8.8/darwin-2level > /opt/local/lib/perl5/vendor_perl .) at > /usr/local/bin/psync line 13. > > BEGIN failed--compilation aborted at /usr/local/bin/psync line 13. > Backup completed: Wed Mar 25 16:31:16 2009[2009.25.03](04:31PM) -> > [roscoe] ~ $ Looks like http://trac.macports.org/ticket/18111 You need perl5.8 +db to get DB_File.pm. To add the variant to perl5.8 which you already have installed, run: sudo port -fn upgrade perl5.8 +db > I just found : > > http://developers.slashdot.org/article.pl?sid=09/02/18/1435227 > > http://www.theregister.co.uk/2009/02/16/apple_update_perl_breakage/ As you are using Perl from MacPorts, bugs in the system version do not affect you in this case. Rainer From ms at mac-specialist.com Wed Mar 25 17:38:26 2009 From: ms at mac-specialist.com (Bill Hernandez) Date: Wed, 25 Mar 2009 19:38:26 -0500 Subject: runpsync triggers error - Can't locate MacOSX/File.pm [solved] In-Reply-To: References: <58617346-470A-47B3-B0D4-E964BDFCC7EB@mac-specialist.com> Message-ID: Thanks to Rainer M?ller for helping me get perl, psync and runsync fixed. I included the steps so it will hopefully help others. On Mar 25, 2009, at 5:16 PM, Bill Hernandez wrote: > I just found these. > > http://developers.slashdot.org/article.pl?sid=09/02/18/1435227 > > http://www.theregister.co.uk/2009/02/16/apple_update_perl_breakage/ > > http://bulknews.typepad.com/blog/2009/02/mac-os-x-security-update-2009001-breaks-perl-cpan.html > > > > > On Mar 25, 2009, at 1:23 PM, Bill Hernandez wrote: > >> I've been seeing some errors during startup in the system log for >> sometime now, so the other day I decided to do an archive/install >> of the operating system. >> >> I still have the same system log errors during startup, but >> everything seems to be working well. >> >> I've been using runpsync for a long time and all of the sudden it >> is not working as shown below: >> >> [2009.25.03](11:15AM) -> [roscoe] ~ $ sudo /usr/local/bin/runpsync >> 0 -d 0 '/' '/Volumes/Backup_24' >> Password Looks like your psync is using /usr/bin/perl instead of /opt/local/bin/perl. > WHEN I do a search for 'File.pm', I seem to find a bunch of them. Not > quite sure what has happened ? $ port provides /opt/local/lib/perl5/vendor_perl/5.8.8/darwin-thread-multi-2level/ MacOSX/File.pm /opt/local/lib/perl5/vendor_perl/5.8.8/darwin-thread-multi-2level/ MacOSX/File.pm is provided by: p5-macosx-file You probably don't have p5-macosx-file installed? Rainer Bill Hernandez wrote: > Any other suggestions ? You need to run psync using /opt/local/bin/perl, it seems to be using /usr/bin/perl currently. The system provided perl will not use modules installed by MacPorts. Rainer Bill Hernandez wrote: > I normally do everything associated with MacPorts via the Terminal, > but the other day I updated all the ports installed using > PortAuthority, and it installed perl > > I changed : > > FROM : #!/usr/bin/perl > TO : #!/opt/local/bin/perl > > In both /usr/bin/runpsync, and /usr/bin/psync I assume you meant /usr/local/bin here? > in psync I also changed : > > FROM : # eval 'exec /usr/bin/perl -S $0 ${1+"$@"}' > TO : eval '/opt/local/bin/perl -S $0 ${1+"$@"}' Looks good. > [2009.25.03](04:30PM) -> [roscoe] ~ $ sudo /usr/local/bin/runpsync 0 - > d 0 '/' '/Volumes/Backup_5' > Password: > Backup begun Wed Mar 25 16:31:16 2009 > Can't locate DB_File.pm in @INC (@INC contains: > /opt/local/lib/perl5/5.8.9/darwin-2level > /opt/local/lib/perl5/5.8.9 > /opt/local/lib/perl5/site_perl/5.8.9/darwin-2level > /opt/local/lib/perl5/site_perl/5.8.9 > /opt/local/lib/perl5/site_perl > /opt/local/lib/perl5/vendor_perl/5.8.9/darwin-2level > /opt/local/lib/perl5/vendor_perl/5.8.9 > /opt/local/lib/perl5/vendor_perl/5.8.8 > /opt/local/lib/perl5/vendor_perl/5.8.8/darwin-2level > /opt/local/lib/perl5/vendor_perl .) at > /usr/local/bin/psync line 13. > > BEGIN failed--compilation aborted at /usr/local/bin/psync line 13. > Backup completed: Wed Mar 25 16:31:16 2009[2009.25.03](04:31PM) -> > [roscoe] ~ $ Looks like http://trac.macports.org/ticket/18111 You need perl5.8 +db to get DB_File.pm. To add the variant to perl5.8 which you already have installed, run: sudo port -fn upgrade perl5.8 +db > I just found : > > http://developers.slashdot.org/article.pl?sid=09/02/18/1435227 > > http://www.theregister.co.uk/2009/02/16/apple_update_perl_breakage/ As you are using Perl from MacPorts, bugs in the system version do not affect you in this case. Rainer On Mar 25, 2009, at 5:33 PM, Rainer M?ller wrote: > You need perl5.8 +db to get DB_File.pm. To add the variant to perl5.8 > which you already have installed, run: > sudo port -fn upgrade perl5.8 +db Rainer, Thanks a million... My backup is working great... Best Regards, Bill Hernandez Plano, Texas From darrell.usenet6 at telus.net Wed Mar 25 17:42:44 2009 From: darrell.usenet6 at telus.net (Darrell Greenwood) Date: Wed, 25 Mar 2009 17:42:44 -0700 Subject: ntop Crashes Consistently on Mac OSX 10.5.6 after CryptoKey update Message-ID: <250320091742442645%darrell.usenet6@telus.net> I find that ntop crashes consistently after SetCryptoKey occurs. iBook G4, 10.5.6, MacPorts 1.7, ntop 3.3.8. Log excerpts below. Any troubleshooting hints? Cheers, Darrell Mar 24 13:46:25 aabs kernel[0]: SetCryptoKey R: len 16, idx 2 Mar 24 13:52:06 aabs ReportCrash[48690]: Formulating crash report for process ntop[47893] Mar 24 19:50:08 aabs kernel[0]: SetCryptoKey R: len 16, idx 1 Mar 24 19:51:10 aabs ReportCrash[1966]: Formulating crash report for process ntop[551] Mar 25 11:53:43 aabs kernel[0]: SetCryptoKey R: len 16, idx 1 Mar 25 11:54:11 aabs ReportCrash[24192]: Formulating crash report for process ntop[23033] Mar 25 14:11:12 aabs kernel[0]: SetCryptoKey R: len 16, idx 2 Mar 25 14:12:02 aabs ReportCrash[2396]: Formulating crash report for process ntop[1190] Mar 25 15:11:12 aabs kernel[0]: SetCryptoKey R: len 16, idx 1 Mar 25 15:12:03 aabs ReportCrash[4056]: Formulating crash report for process ntop[3912] Mar 25 16:11:12 aabs kernel[0]: SetCryptoKey R: len 16, idx 2 Mar 25 16:12:03 aabs ReportCrash[5626]: Formulating crash report for process ntop[4383] Mar 25 17:11:12 aabs kernel[0]: SetCryptoKey R: len 16, idx 1 Mar 25 17:12:03 aabs ReportCrash[7298]: Formulating crash report for process ntop[5809] -- From dweber at macports.org Wed Mar 25 19:11:33 2009 From: dweber at macports.org (Darren Weber) Date: Wed, 25 Mar 2009 19:11:33 -0700 Subject: stable vs. unstable ports? In-Reply-To: <7675454e0903242025m65f886cbya2274d855eda4d43@mail.gmail.com> References: <7675454e0903242025m65f886cbya2274d855eda4d43@mail.gmail.com> Message-ID: I've been working with macports under the mis-apprehension that it would operate along the lines of freeBSD (and some frustration may arise mostly from that lack of understanding). I decided that it's time for me to do some long-overdue homework. I've been working mostly with linux (and developed a preference for Debian-Ubuntu), so I need to get educated about BSD, as macports seems to follow that model (to some extent). In case it's of interest to others, I found a few interesting links online (I apologize if similar macports docs are available, I must check into that also): http://www.freebsd.org/ http://www.freebsd.org/doc/en_US.ISO8859-1/books/dev-model/book.html http://www.freebsd.org/doc/en_US.ISO8859-1/articles/releng/article.html http://www.freebsd.org/doc/en/books/handbook/using-sysinstall.html http://www.freebsd.org/doc/en/books/handbook/index.html Handbook downloads in multiple formats: ftp://ftp.freebsd.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/handbook/ http://www.lemis.com/grog/Documentation/CFBSD/ BSD jails (chroot) http://en.wikipedia.org/wiki/Chroot http://www.freebsd.org/doc/en/books/handbook/jails.html http://www.freebsd.org/doc/en/books/handbook/virtualization.html *NIX history http://www.freebsd.org/cgi/cvsweb.cgi/src/share/misc/bsd-family-tree?rev=1.115.2.3;content-type=text%2Fplain freebsd vs openbsd (vs netbsd) http://forums.whirlpool.net.au/forum-replies-archive.cfm/488714.html http://www.linuxquestions.org/questions/bsd-17/important-read-this-before-posting-177142/ http://www.serverwatch.com/tutorials/article.php/10825_3393051_1 BSD vs Linux http://www.over-yonder.net/~fullermd/rants/bsd4linux/bsd4linux1.php Bill Joy I find it curious that Bill Joy created chroot to build BSD and then went on to found Sun and probably contributed a lot to java design - perhaps the whole idea of a chroot to build BSD might have been just the right inspiration for the java vm and sdk. http://en.wikipedia.org/wiki/Bill_Joy http://www.theregister.co.uk/2003/09/11/bill_joys_greatest_gift/ On Tue, Mar 24, 2009 at 8:25 PM, Shreevatsa R wrote: > [Changing the topic from build systems and replying just to the > original question] > > 2009/3/22 Darren Weber : > > > > I've noticed problems during port upgrades. > > > > What is the general consensus on having a TAG for each port to indicate > it's > > "success" status within the system? > > There is already a low-tech way of doing this: see if any bugs have > been reported against the given port. :) > Chances are that if others have had problems with upgrades, they would > have (hopefully) filed a ticket against the port. > Checking this is very easy to do thanks to Rainer M?ller's recently > implemented Trac report, e.g. use > http://trac.macports.org/report/16?PORT=python25 > to see if there are any recent bugs with the python25 port that you care > about. > > > Is it possible to have a meta-port monitor that automatically tracks the > > status of each package install and reports that status back to a central > > repository to continuously flag the status of a port install. A simple > > dichotomy of stable and unstable might suffice (Debian uses stable, > > unstable, and testing). Perhaps the monitoring system could provide the > > data required to justify these port status levels. > > Note that what Debian does is something quite a bit more: they have > entirely different *sets* of ports marked stable, testing, unstable > and users choose to install all their packages from the same set > ("tree"). This is fine for Debian to do because they have enough > people, but it would not be a good idea for MacPorts: having to > maintain multiple sets of inter-compatible ports leads to too much > fragmentation and the situation might end up similar to that with > Fink: the stable ports work very well but are too outdated for most > purposes, the unstable ports are really unstable and *still* quite a > bit older than in MacPorts. Having only one current version of each > port, which everyone gets and reports bugs against etc. is one of > MacPorts's strengths. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From afb at macports.org Thu Mar 26 01:00:00 2009 From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=) Date: Thu, 26 Mar 2009 09:00:00 +0100 Subject: stable vs. unstable ports? In-Reply-To: References: <7675454e0903242025m65f886cbya2274d855eda4d43@mail.gmail.com> Message-ID: Darren Weber wrote: > I've been working with macports under the mis-apprehension that it > would operate along the lines of freeBSD (and some frustration may > arise mostly from that lack of understanding). I decided that it's > time for me to do some long-overdue homework. I've been working > mostly with linux (and developed a preference for Debian-Ubuntu), > so I need to get educated about BSD, as macports seems to follow > that model (to some extent). Not only MacPorts, but also Mac OS X is closer to FreeBSD than to Linux. On the other hand, many of the tools in use (such as bash or make) are from GNU, so it's something of a mix between BSD and GNU... For the really adventurous, it's even possible to install MacPorts on FreeBSD and on GNU/Linux. There are packages available for FreeBSD, Fedora and Ubuntu. Not many ports, but "base" should still run. --anders From dweber at macports.org Thu Mar 26 11:29:04 2009 From: dweber at macports.org (Darren Weber) Date: Thu, 26 Mar 2009 11:29:04 -0700 Subject: stable vs. unstable ports? In-Reply-To: <7675454e0903242025m65f886cbya2274d855eda4d43@mail.gmail.com> References: <7675454e0903242025m65f886cbya2274d855eda4d43@mail.gmail.com> Message-ID: Recently, I was running something like update-all and there were some issues with the netCDF library. It was upgraded by the maintainer, who manually updated a dependency on HDF5 within their dev environment, who then put out a request to the HDF5 maintainer to update that package, but this could not happen because of other dependencies on HDF5. This situation persisted for quite some time. As a consequence, the netCDF package was broken during the upgrade process. (Please forgive me if any or all of these recollections are just plain wrong, but something like this happened and it's just the main idea that's important). Despite all the reasons why this might or might not be a good process model, I don't like it for daily work. For the purpose of my daily work, I do want a stable environment, I don't need to be on the cutting edge (or is that a bleeding edge). There are times when I want to get closer to the cutting edge - that's when I grab and modify the Portfile in my local repository and tinker with it (and any dependency issues, etc.). I do like the way this is possible in macports. However, for the vast majority of packages, I just want them to work, I want them to be stable and I want them to be nice to each other, to work in harmony. I would love an automated tagging system that can monitor the success or failure of port builds and trace this status through the dependency tree to automatically identify the conjunction of all stable ports. It should provide a report of that information to the maintainers of each package, indicating the status of builds (broken down by variants and including a relevant dependency list for each build-type that fails - not EVERY build, just the category of build that fails). All this currently happens in trac and it requires a lot of effort to monitor and manage it. Perhaps some of that effort could be spent on programming a meta-port monitor and status report system. In effect, macports already has multiplicity of ports for each package, mainly because there are separate ports for each major-minor release of a package (like postgresql-83, etc.) and so do many other port or package management systems. It's not uncommon for a large package management system to deal with the contingencies of multiple versions for a package, including installation of multiple versions at the same time (due to user preferences or due to package dependency). At some point, in some way, it is inevitable that a package management system must have some kind of stable - unstable tag on it's packages (ports), whether it is automatic or manual (ie, developer decisions). At present, it appears this is all manual in macports and there is no way for a user to use a simple category selector in the port program, but perhaps your suggestion for python is a move toward some level of automation. Thanks, Darren On Tue, Mar 24, 2009 at 8:25 PM, Shreevatsa R wrote: > [Changing the topic from build systems and replying just to the > original question] > > 2009/3/22 Darren Weber : > > > > I've noticed problems during port upgrades. > > > > What is the general consensus on having a TAG for each port to indicate > it's > > "success" status within the system? > > There is already a low-tech way of doing this: see if any bugs have > been reported against the given port. :) > Chances are that if others have had problems with upgrades, they would > have (hopefully) filed a ticket against the port. > Checking this is very easy to do thanks to Rainer M?ller's recently > implemented Trac report, e.g. use > http://trac.macports.org/report/16?PORT=python25 > to see if there are any recent bugs with the python25 port that you care > about. > > > Is it possible to have a meta-port monitor that automatically tracks the > > status of each package install and reports that status back to a central > > repository to continuously flag the status of a port install. A simple > > dichotomy of stable and unstable might suffice (Debian uses stable, > > unstable, and testing). Perhaps the monitoring system could provide the > > data required to justify these port status levels. > > Note that what Debian does is something quite a bit more: they have > entirely different *sets* of ports marked stable, testing, unstable > and users choose to install all their packages from the same set > ("tree"). This is fine for Debian to do because they have enough > people, but it would not be a good idea for MacPorts: having to > maintain multiple sets of inter-compatible ports leads to too much > fragmentation and the situation might end up similar to that with > Fink: the stable ports work very well but are too outdated for most > purposes, the unstable ports are really unstable and *still* quite a > bit older than in MacPorts. Having only one current version of each > port, which everyone gets and reports bugs against etc. is one of > MacPorts's strengths. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From groups.2009a at grandfenwick.net Thu Mar 26 13:54:04 2009 From: groups.2009a at grandfenwick.net (Dave Howell) Date: Thu, 26 Mar 2009 13:54:04 -0700 Subject: Install from Binary Archives (was Re: port install efficiency issue) In-Reply-To: References: <49C6437A.5040807@macports.org> <2C269F10-9498-4759-8668-4603FBAB6524@comcast.net> <20090322202712.GC812@ninagal.withay.com> <3FFC1539-E7C9-4CEC-AF38-DD2DE12D7F44@newgeo.com> <49C6DDC1.6000405@macports.org> Message-ID: On Mar 22, 2009, at 22:54 , Darren Weber wrote: > > I In effect, every time anybody on this grid has to build a package > from source, some kind of meta-package monitor can detect whether > the build and install was successful and then make an inquiry of a > central managment system as to whether or not this build should be > added to the mirrors for binary distributions. If this inquiry was > made before the build and a binary is available somewhere, the > system simply downloads the binary (perhaps a torrent system). If > the binary is not available, the build proceeds. Maybe I'm not following it correctly, but it sounds very complicated. What about this: I do a "ports install widget", ports looks for a binary, doesn't find one that matches (in this case, the default options and current version), so it goes about building it. When it's done, it says "upload compiled binary to binary archives?" I say "Y", and up it goes. Now it's available for the next user who comes along. When I first install MacPorts, I could select at that time to en/ disable the "upload binaries" option. This scheme inherently selects for more popular configurations. If nobody ever happens to ask for a particular setup, it'll never take up space in the archive. There is probably some effort on somebody's part required to help figure out when a particular binary is actually a match or not. Widget 3.2 compiled on Intel 2.0GHz Core 2 Duo under OSX 10.5.2 with gcc 4.0 from XCode 3.0 Widget 3.2 compiled on Intel 2.0GHz Core 2 Duo under OSX 10.5.2 with gcc 4.0 from XCode 3.1.2 Widget 3.2 compiled on Intel 2.0GHz Core 2 Duo under OSX 10.5.4 with gcc 4.0 from XCode 3.1.2 Same or different? I personally don't think I know enough to be able to answer that question, but I know enough to believe that the answer is not necessarily the same for different ports, depending on what they link to? I certainly love the sound of "port install fuudingus" saying There is a binary for this port available. Compiled under OSX 10.5.4 with gcc 4.0 from XCode 3.1.2 Warning! Your installation of XCode is 3.0 Would you like to install from the binary file (Y/N)? From daniels.douglas at gmail.com Thu Mar 26 14:00:00 2009 From: daniels.douglas at gmail.com (Doug Daniels) Date: Thu, 26 Mar 2009 16:00:00 -0500 Subject: Cannot install protocols for pkill and pgrep Message-ID: I'm attempting to install the protocols library from port on Mac OS X 10.5.6. I see it listed on the macports website: http://trac.macports.org/browser/trunk/dports/sysutils/proctools/Portfile I updated my port: sudo port selfupdate Then I try to do a sudo port list | grep protocols and I don't see it listed at all. I run: / >sudo port install protocols Password: Error: Port protocols not found Do I need to modify my sources.conf or something to get the Protocols library? -------------- next part -------------- An HTML attachment was scrubbed... URL: From groups.2009a at grandfenwick.net Thu Mar 26 14:09:09 2009 From: groups.2009a at grandfenwick.net (Dave Howell) Date: Thu, 26 Mar 2009 14:09:09 -0700 Subject: stable vs. unstable ports? In-Reply-To: <64FEDC27-0878-4A20-8281-1BEA112D43D0@macports.org> References: <49C6D55C.7050709@macports.org> <64FEDC27-0878-4A20-8281-1BEA112D43D0@macports.org> Message-ID: <2AAF5972-7AC8-4D87-9471-2F29938DB22F@grandfenwick.net> On Mar 23, 2009, at 0:38 , Ryan Schmidt wrote: > > Before we can allow arbitrary users to submit their builds to a > central server, we would need to ensure that a build that occurs on > one user's system is *identical* to the build on any other user's > computer. This cannot currently be assured because MacPorts does not > build in a chroot, and without this, it is possible for a port to > link with libraries that happen to be on the user's system that it > ought not link with -- be they libraries from other ports on which > the port in question does not declare a dependency, or libraries in / > usr/local, to which the compiler always looks. Would two "identical builds" be byte-identical? If so, then a binary doesn't become available until *two* (or three or whatever) identical binaries are uploaded. And/or, there's some command line library tool (I'm on vacation and my reference books are home) that I can run to get a listing of what libraries are called by a particular binary, isn't there? Wouldn't that help screen wacky-linked binaries? The deliberate uploading of contaminated binaries, however, is a whole different kettle of worms. :/ From LenoreHorner at sbcglobal.net Thu Mar 26 14:50:22 2009 From: LenoreHorner at sbcglobal.net (Lenore Horner) Date: Thu, 26 Mar 2009 16:50:22 -0500 Subject: Cannot install protocols for pkill and pgrep In-Reply-To: References: Message-ID: On Mar 26, 2009, at 16:00 , Doug Daniels wrote: > I'm attempting to install the protocols library from port on Mac OS > X 10.5.6. > > I see it listed on the macports website: > http://trac.macports.org/browser/trunk/dports/sysutils/proctools/Portfile > > I updated my port: > sudo port selfupdate > > Then I try to do a sudo port list | grep protocols and I don't see > it listed at all. > > I run: > / >sudo port install protocols > Password: > Error: Port protocols not found spelling error? proctools but you typed protocols > > Do I need to modify my sources.conf or something to get the > Protocols library? > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From gregreedee at gmail.com Thu Mar 26 14:57:48 2009 From: gregreedee at gmail.com (Gregory Dodwell) Date: Fri, 27 Mar 2009 08:57:48 +1100 Subject: re Gnucash crashes on launch Message-ID: <789f92700903261457u627d29dfu6e5288c09c5729ea@mail.gmail.com> Date: Wed, 25 Mar 2009 19:09:44 +0100 From: Olaf Foellinger Subject: Re: Gnucash crashes on launch: no, I don't have mesa To: macports-users at lists.macosforge.org Message-ID: <20090325180944.GA1167 at foellinger.de> Content-Type: text/plain; charset=iso-8859-1 Hi, * Gregory Dodwell [25.03.09 12:38]wrote: >> OSX 10.5.6 "Leopard" on Intel iMac >> Xquartz 2.3.2 >> Latest MacPorts: version 1.700 >> trying to run after installation today: >> Here's me: /opt/local/bin/gnucash-bin >> In reply a partially drawn splash for a couple of seconds then: >> gnc.bin-Message: main: binreloc relocation support was disabled at >> configure time. >> Xlib: extension "RANDR" missing on display "/tmp/launch-IUF4Zq/:0". >> Abort trap > > Any clues? > maybe you can try the script /opt/local/bin/gnucash? > Gru? Olaf I tried that script, and also tried backgrounding it for good measure --no luck-- here's the result: bash-3.2$ /opt/local/bin/gnucash dyld: Symbol not found: _gll_noop Referenced from: /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL Expected in: /opt/local/lib/libGL.dylib Trace/BPT trap bash-3.2$ /opt/local/bin/gnucash & [1] 88155 bash-3.2$ dyld: Symbol not found: _gll_noop Referenced from: /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL Expected in: /opt/local/lib/libGL.dylib [1]+ Trace/BPT trap /opt/local/bin/gnucash bash-3.2$ -------------- next part -------------- An HTML attachment was scrubbed... URL: From cedayiv at gmail.com Thu Mar 26 15:10:53 2009 From: cedayiv at gmail.com (Charles Day) Date: Thu, 26 Mar 2009 15:10:53 -0700 Subject: re Gnucash crashes on launch In-Reply-To: <789f92700903261457u627d29dfu6e5288c09c5729ea@mail.gmail.com> References: <789f92700903261457u627d29dfu6e5288c09c5729ea@mail.gmail.com> Message-ID: <1d6843d80903261510o72bb3a27m34b7b542825b8d31@mail.gmail.com> 2009/3/26 Gregory Dodwell > Date: Wed, 25 Mar 2009 19:09:44 +0100 > From: Olaf Foellinger > Subject: Re: Gnucash crashes on launch: no, I don't have mesa > To: macports-users at lists.macosforge.org > Message-ID: <20090325180944.GA1167 at foellinger.de> > Content-Type: text/plain; charset=iso-8859-1 > > Hi, > > * Gregory Dodwell [25.03.09 12:38]wrote: > > >> OSX 10.5.6 "Leopard" on Intel iMac > >> Xquartz 2.3.2 > >> Latest MacPorts: version 1.700 > >> trying to run after installation today: > >> Here's me: /opt/local/bin/gnucash-bin > >> In reply a partially drawn splash for a couple of seconds then: > >> gnc.bin-Message: main: binreloc relocation support was disabled at > >> configure time. > >> Xlib: extension "RANDR" missing on display "/tmp/launch-IUF4Zq/:0". > >> Abort trap > > > Any clues? > > > maybe you can try the script /opt/local/bin/gnucash? > > > > Gru? Olaf > > I tried that script, and also tried backgrounding it for good measure --no > luck-- here's the result: > There is a discussion about this being related to mesa. See: http://www.nabble.com/Symbol-not-found:-_gll_noop-td22241078.html > > bash-3.2$ /opt/local/bin/gnucash > dyld: Symbol not found: _gll_noop > Referenced from: > /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL > Expected in: /opt/local/lib/libGL.dylib > > Trace/BPT trap > bash-3.2$ /opt/local/bin/gnucash & > [1] 88155 > bash-3.2$ dyld: Symbol not found: _gll_noop > Referenced from: > /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL > Expected in: /opt/local/lib/libGL.dylib > > > [1]+ Trace/BPT trap /opt/local/bin/gnucash > bash-3.2$ > > > > > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From raimue at macports.org Thu Mar 26 15:19:59 2009 From: raimue at macports.org (=?ISO-8859-1?Q?Rainer_M=FCller?=) Date: Thu, 26 Mar 2009 23:19:59 +0100 Subject: Install from Binary Archives (was Re: port install efficiency issue) In-Reply-To: References: <49C6437A.5040807@macports.org> <2C269F10-9498-4759-8668-4603FBAB6524@comcast.net> <20090322202712.GC812@ninagal.withay.com> <3FFC1539-E7C9-4CEC-AF38-DD2DE12D7F44@newgeo.com> <49C6DDC1.6000405@macports.org> Message-ID: <49CBFF8F.7080907@macports.org> Dave Howell wrote: > What about this: I do a "ports install widget", ports looks for a > binary, doesn't find one that matches (in this case, the default > options and current version), so it goes about building it. When it's > done, it says "upload compiled binary to binary archives?" I say "Y", > and up it goes. Now it's available for the next user who comes along. Sure, we would just distribute arbitrary binaries to end-users... NOT! Ever thought about security? What if I upload some rootkit instead of the real software and everyone installs it? No, this will not work. Rainer From trog24 at comcast.net Thu Mar 26 15:46:04 2009 From: trog24 at comcast.net (Frank J. R. Hanstick) Date: Thu, 26 Mar 2009 15:46:04 -0700 Subject: Activation error Message-ID: <8DA7D10B-0FA4-4AE2-98AA-AE0D7943B027@comcast.net> Hello, I got the following activation error: ---> Activating xorg-libX11 @1.2_0 Error: Activating xorg-libX11 @1.2_0 failed: Image error: /opt/local/ include/X11/cursorfont.h already exists and does not belong to a registered port. Unable to activate port xorg-libX11. when trying the following command: sudo port upgrade xorg-libX11 Any ideas anyone? Frank J. R. Hanstick trog24 at comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From dweber at macports.org Thu Mar 26 15:51:32 2009 From: dweber at macports.org (Darren Weber) Date: Thu, 26 Mar 2009 15:51:32 -0700 Subject: stable vs. unstable ports? In-Reply-To: <2AAF5972-7AC8-4D87-9471-2F29938DB22F@grandfenwick.net> References: <49C6D55C.7050709@macports.org> <64FEDC27-0878-4A20-8281-1BEA112D43D0@macports.org> <2AAF5972-7AC8-4D87-9471-2F29938DB22F@grandfenwick.net> Message-ID: On Thu, Mar 26, 2009 at 2:09 PM, Dave Howell wrote: > > On Mar 23, 2009, at 0:38 , Ryan Schmidt wrote: > > >> Before we can allow arbitrary users to submit their builds to a central >> server, we would need to ensure that a build that occurs on one user's >> system is *identical* to the build on any other user's computer. This cannot >> currently be assured because MacPorts does not build in a chroot, and >> without this, it is possible for a port to link with libraries that happen >> to be on the user's system that it ought not link with -- be they libraries >> from other ports on which the port in question does not declare a >> dependency, or libraries in /usr/local, to which the compiler always looks. >> > > Would two "identical builds" be byte-identical? If so, then a binary > doesn't become available until *two* (or three or whatever) identical > binaries are uploaded. > > And/or, there's some command line library tool (I'm on vacation and my > reference books are home) that I can run to get a listing of what libraries > are called by a particular binary, isn't there? Wouldn't that help screen > wacky-linked binaries? > > The deliberate uploading of contaminated binaries, however, is a whole > different kettle of worms. :/ > > I've been running mpab for a few days now, ie: http://trac.macports.org/wiki/MPAB This is a chroot approach. Obviously, as it is, anyone could tinker with it to include a rootkit or whatever. Nevertheless, I wonder if it's possible to create a binary app of this, which is authenticated during installation (at least), and we ensure that it must do some handshaking to get hold of the "official" and "secure" port tree somehow (probably an encrypted handshake, encrypted file archive for download, etc.) and then it goes about it's business on a user machine and only does an upload (if any) when there is some kind of further authentication that the port build is correct (binary md5 etc. for at least 2-5 builds on the exact same configuration). Even if it does no uploads, it could create useful information about the stability or integrity (you name it) of the entire build process. It would be really neat to have an Xgrid controller (or many) be able to run a job that can parse out port dependencies and have some kind of parallelism in the build. Best, Darren PS, `man otool` can tell you just about anything you need to know about the binary file, eg otool -l /opt/local/bin/gls otool -L /opt/local/bin/gls -------------- next part -------------- An HTML attachment was scrubbed... URL: From dweber at macports.org Thu Mar 26 15:52:10 2009 From: dweber at macports.org (Darren Weber) Date: Thu, 26 Mar 2009 15:52:10 -0700 Subject: Install from Binary Archives (was Re: port install efficiency issue) In-Reply-To: <49CBFF8F.7080907@macports.org> References: <49C6437A.5040807@macports.org> <2C269F10-9498-4759-8668-4603FBAB6524@comcast.net> <20090322202712.GC812@ninagal.withay.com> <3FFC1539-E7C9-4CEC-AF38-DD2DE12D7F44@newgeo.com> <49C6DDC1.6000405@macports.org> <49CBFF8F.7080907@macports.org> Message-ID: On Thu, Mar 26, 2009 at 3:19 PM, Rainer M?ller wrote: > Dave Howell wrote: > > What about this: I do a "ports install widget", ports looks for a > > binary, doesn't find one that matches (in this case, the default > > options and current version), so it goes about building it. When it's > > done, it says "upload compiled binary to binary archives?" I say "Y", > > and up it goes. Now it's available for the next user who comes along. > > Sure, we would just distribute arbitrary binaries to end-users... NOT! > Ever thought about security? What if I upload some rootkit instead of > the real software and everyone installs it? No, this will not work. > > Rainer > I've been running mpab for a few days now, ie: http://trac.macports.org/wiki/MPAB This is a chroot approach. Obviously, as it is, anyone could tinker with it to include a rootkit or whatever. Nevertheless, I wonder if it's possible to create a binary app of this, which is authenticated during installation (at least), and we ensure that it must do some handshaking to get hold of the "official" and "secure" port tree somehow (probably an encrypted handshake, encrypted file archive for download, etc.) and then it goes about it's business on a user machine and only does an upload (if any) when there is some kind of further authentication that the port build is correct (binary md5 etc. for at least 2-5 builds on the exact same configuration). Even if it does no uploads, it could create useful information about the stability or integrity (you name it) of the entire build process. It would be really neat to have an Xgrid controller (or many) be able to run a job that can parse out port dependencies and have some kind of parallelism in the build. Best, Darren PS, `man otool` can tell you just about anything you need to know about the binary file, eg otool -l /opt/local/bin/gls otool -L /opt/local/bin/gls -------------- next part -------------- An HTML attachment was scrubbed... URL: From frstan at bellsouth.net Thu Mar 26 16:33:47 2009 From: frstan at bellsouth.net (William Davis) Date: Thu, 26 Mar 2009 19:33:47 -0400 Subject: Activation error In-Reply-To: <8DA7D10B-0FA4-4AE2-98AA-AE0D7943B027@comcast.net> References: <8DA7D10B-0FA4-4AE2-98AA-AE0D7943B027@comcast.net> Message-ID: <80ACCBAF-4EBD-4720-8BA9-30D0BB0BE643@bellsouth.net> Usually that is a left over file from a failed install. In this case just do sudo port -f upgrade xorg-libX11 [or do -fu if you don't want to keep the old version] WSD On Mar 26, 2009, at 6:46 PM, Frank J. R. Hanstick wrote: > Hello, > I got the following activation error: > > ---> Activating xorg-libX11 @1.2_0 > Error: Activating xorg-libX11 @1.2_0 failed: Image error: /opt/local/ > include/X11/cursorfont.h already exists and does not belong to a > registered port. Unable to activate port xorg-libX11. > > when trying the following command: > > sudo port upgrade xorg-libX11 > > Any ideas anyone? > Frank J. R. Hanstick > trog24 at comcast.net > > > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users William Davis frstanATbellsouthDOTnet Mac OS X.5.6 Darwin 9.5.0 XQuartz 2.3.3_rc2 (xorg-server 1.4.2-apple37) Mac Mini Intel Duo @ 1.86 GHz Mundus vult decepi, ego non -------------- next part -------------- An HTML attachment was scrubbed... URL: From jmr at macports.org Thu Mar 26 16:58:15 2009 From: jmr at macports.org (Joshua Root) Date: Fri, 27 Mar 2009 10:58:15 +1100 Subject: Activation error In-Reply-To: <80ACCBAF-4EBD-4720-8BA9-30D0BB0BE643@bellsouth.net> References: <8DA7D10B-0FA4-4AE2-98AA-AE0D7943B027@comcast.net> <80ACCBAF-4EBD-4720-8BA9-30D0BB0BE643@bellsouth.net> Message-ID: <49CC1697.2090201@macports.org> William Davis wrote: > Usually that is a left over file from a failed install. In this case just do > sudo port -f upgrade xorg-libX11 [or do -fu if you don't want to keep > the old version] Don't do that. Upgrade normally applies to all dependencies as well, so you would be rebuilding all of them because of the -f. (You can use -n to avoid processing dependencies.) In fact, -f upgrade is not called for in this situation at all, but rather -f activate. - Josh From raimue at macports.org Thu Mar 26 17:05:46 2009 From: raimue at macports.org (=?UTF-8?B?UmFpbmVyIE3DvGxsZXI=?=) Date: Fri, 27 Mar 2009 01:05:46 +0100 Subject: Google Summer of Code 2009 - Money for students working on MacPorts! Message-ID: <49CC185A.9060806@macports.org> Hi, Summer of Code is a annual program hold by Google to attract new developers for the open source world. You work on a open source project over the summer and earn $4500 USD. It is a great opportunity for college students to get a real, on the ground programming experience, work on an exciting open source project with mentoring from its developers. MacPorts has great tasks on the ideas page that could use attention, and still has slots for volunteers. Get in contact with us and apply if you are interested! Please also spread the word if you are a MacPorts user and a friend of yours would be qualified. This is a great opportunity not just for the students, but to foster and extend the MacPorts project. See this wiki page for more information: http://trac.macports.org/wiki/SummerOfCode Application is still open until April 3, 19:00 UTC. For more details, just contact the list, me or any of the mentors. Rainer From frstan at bellsouth.net Thu Mar 26 18:00:39 2009 From: frstan at bellsouth.net (William Davis) Date: Thu, 26 Mar 2009 21:00:39 -0400 Subject: Activation error In-Reply-To: <49CC1697.2090201@macports.org> References: <8DA7D10B-0FA4-4AE2-98AA-AE0D7943B027@comcast.net> <80ACCBAF-4EBD-4720-8BA9-30D0BB0BE643@bellsouth.net> <49CC1697.2090201@macports.org> Message-ID: <0B7F8CBA-861A-4A86-B3EA-29D2595F1DDB@bellsouth.net> right you are! WSD On Mar 26, 2009, at 7:58 PM, Joshua Root wrote: > William Davis wrote: >> Usually that is a left over file from a failed install. In this >> case just do >> sudo port -f upgrade xorg-libX11 [or do -fu if you don't want to >> keep >> the old version] > > Don't do that. Upgrade normally applies to all dependencies as well, > so > you would be rebuilding all of them because of the -f. (You can use -n > to avoid processing dependencies.) > > In fact, -f upgrade is not called for in this situation at all, but > rather -f activate. > > - Josh William Davis frstanATbellsouthDOTnet Mac OS X.5.6 Darwin 9.5.0 XQuartz 2.3.3_rc2 (xorg-server 1.4.2-apple37) Mac Mini Intel Duo @ 1.86 GHz Mundus vult decepi, ego non From ryandesign at macports.org Thu Mar 26 19:56:34 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 26 Mar 2009 21:56:34 -0500 Subject: dbus startup at system startup. In-Reply-To: <6459588C-F443-4894-ADF1-0D6EF854F1E1@comcast.net> References: <6459588C-F443-4894-ADF1-0D6EF854F1E1@comcast.net> Message-ID: <37794214-F58E-47D9-A054-1B57C0609273@macports.org> On Mar 24, 2009, at 14:22, Frank J. R. Hanstick wrote: > On Mar 24, 2009, at 8:50 AM, Frank J. R. Hanstick wrote: > >> At system startup, I get the following error messages sent to >> system.log: >> >> Mar 24 08:40:11 localhost launchd: org.macports.dbus: respawning >> too quickly! throttling >> Mar 24 08:40:11 localhost launchd: org.macports.dbus: 9 more >> failures without living at least 60 seconds will cause job removal >> Mar 24 08:40:11 localhost launchd: org.macports.dbus: will restart >> in 10 seconds [snip] >> I installed dbus via sudo port install dbus and entered: >> >> launchctl load /Library/LaunchAgents/org.freedesktop.dbus- >> session.plist >> >> as directed; yet, I still get these error messages at system >> startup time. How do I get them to stop? > > I figured out the problem. Somehow, the plist associated with > org.macports got inserted into LaunchDaemons. I removed it and the > dbus messages stopped appearing. Great when I can solve my own > problems once in a while. The dbus port is supposed to install the file org.macports.dbus.plist into /Library/LaunchDaemons, and the file org.freedesktop.dbus- session.plist into /Library/LaunchAgents. At least, it does so on my system. I have never attempted to start them though. From ryandesign at macports.org Thu Mar 26 20:04:28 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 26 Mar 2009 22:04:28 -0500 Subject: php5 & "port test php5" In-Reply-To: <49C7EA67.9010101@blackchairdvd.com> References: <49C7EA67.9010101@blackchairdvd.com> Message-ID: <09C9BF97-46AB-4D2D-90D6-980B688C1411@macports.org> On Mar 23, 2009, at 15:00, drf wrote: > My setup: Mac Mini, 10.4.11, Xcode 2.5, GCC 4, MacPorts 1.7 > > Everything compiles fine, there are some complaints about > signedness from the compiler, but it all looks ok. But when I run > the PHP test suite, over 70 tests fail, including ones I wouldn't > really expect, like on the function easterdate(). I can not find > any hints anywhere on what might be happening, so I'm wondering if > these tests really are that important. Should a completely default, > standard, stock install of php5 with MacPorts pass all the PHP self > tests fine? > > The thing is, when I set up everything myself (not using MacPorts > to compile php5) the same set of tests failed - the config of php5 > did reference various macport installed libraries, etc. I am now > at the point where I am wondering if I ought to toss all of > MacPorts and try to install everything myself that is needed to > compile php5. > > So any advice, pointers on where to look, or hints on 64 bit vs 32 > would be greatly appreciated Hi. I'm the maintainer of php5 in MacPorts. On the few occasions when I have tried "port test php5", it did not pass everything either. Please feel free to enter into a dialog about this with the developers of PHP. I have not had the energy to do so myself. They're often quite rude in responding to bug reports and I haven't felt like being abused lately. I recommend you use MacPorts for all your software installation needs, including PHP. You could build it all yourself, but it would be a lot of work figuring out things that we have already figured out in MacPorts. If the software available in MacPorts doesn't fully meet your needs, please bring it to our attention so that we can improve the ports until they do meet your needs. I have not attempted to compile php5 as a universal binary or 64-bit. I would not be surprised if it did not work. If you try it and it works, or if you can figure out how to make it work, please let us know. From ryandesign at macports.org Thu Mar 26 20:23:58 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu, 26 Mar 2009 22:23:58 -0500 Subject: stable vs. unstable ports? In-Reply-To: References: <49C6D55C.7050709@macports.org> <64FEDC27-0878-4A20-8281-1BEA112D43D0@macports.org> <2AAF5972-7AC8-4D87-9471-2F29938DB22F@grandfenwick.net> Message-ID: <2AE7AB32-F26E-4F4D-AD76-41D7CEE805DC@macports.org> On Mar 26, 2009, at 17:51, Darren Weber wrote: > On Thu, Mar 26, 2009 at 2:09 PM, Dave Howell wrote: > >> On Mar 23, 2009, at 0:38 , Ryan Schmidt wrote: >> >>> Before we can allow arbitrary users to submit their builds to a >>> central server, we would need to ensure that a build that occurs >>> on one user's system is *identical* to the build on any other >>> user's computer. This cannot currently be assured because >>> MacPorts does not build in a chroot, and without this, it is >>> possible for a port to link with libraries that happen to be on >>> the user's system that it ought not link with -- be they >>> libraries from other ports on which the port in question does not >>> declare a dependency, or libraries in /usr/local, to which the >>> compiler always looks. >> >> Would two "identical builds" be byte-identical? If so, then a >> binary doesn't become available until *two* (or three or whatever) >> identical binaries are uploaded. >> >> And/or, there's some command line library tool (I'm on vacation >> and my reference books are home) that I can run to get a listing >> of what libraries are called by a particular binary, isn't there? >> Wouldn't that help screen wacky-linked binaries? >> >> The deliberate uploading of contaminated binaries, however, is a >> whole different kettle of worms. :/ > > I've been running mpab for a few days now, ie: > http://trac.macports.org/wiki/MPAB > > This is a chroot approach. Obviously, as it is, anyone could > tinker with it to include a rootkit or whatever. Nevertheless, I > wonder if it's possible to create a binary app of this, which is > authenticated during installation (at least), and we ensure that it > must do some handshaking to get hold of the "official" and "secure" > port tree somehow (probably an encrypted handshake, encrypted file > archive for download, etc.) and then it goes about it's business on > a user machine and only does an upload (if any) when there is some > kind of further authentication that the port build is correct > (binary md5 etc. for at least 2-5 builds on the exact same > configuration). Even if it does no uploads, it could create useful > information about the stability or integrity (you name it) of the > entire build process. It would be really neat to have an Xgrid > controller (or many) be able to run a job that can parse out port > dependencies and have some kind of parallelism in the build. Libraries and compressed files (which include manpages) tend to differ everytime they're built, even if they're functionally the same. So you can't just run an md5 checksum over everything and expect it to be the same after repeated builds. I hadn't thought of securing a distributed build system from malicious users until Joshua's message, but now I agree that from a security standpoint we cannot allow user-uploaded binaries at all. Dave's proposed safeguard of requiring n users to upload functionally identical files isn't going to help; if a malicious user can upload a bad binary from 1 computer, they can borrow n friends' computers and create n throwaway email addresses and upload the binary how ever many times we've specified. There are botnets out there with thousands of computers that can be commandeered by hackers to do whatever. So let's kill the idea of user-submitted binaries now. We want dedicated build servers under the control of the MacPorts project. So let's flesh out MPAB into something that can be run on such build servers. Then we can look at acquiring the servers. From trog24 at comcast.net Thu Mar 26 23:33:09 2009 From: trog24 at comcast.net (Frank J. R. Hanstick) Date: Thu, 26 Mar 2009 23:33:09 -0700 Subject: Activation error In-Reply-To: <49CC1697.2090201@macports.org> References: <8DA7D10B-0FA4-4AE2-98AA-AE0D7943B027@comcast.net> <80ACCBAF-4EBD-4720-8BA9-30D0BB0BE643@bellsouth.net> <49CC1697.2090201@macports.org> Message-ID: <740A7ADA-312B-4F52-83CF-BE1B6534E44E@comcast.net> Hello, The -f took care of the problem. Thank you. Frank On Mar 26, 2009, at 4:58 PM, Joshua Root wrote: > William Davis wrote: >> Usually that is a left over file from a failed install. In this >> case just do >> sudo port -f upgrade xorg-libX11 [or do -fu if you don't want to >> keep >> the old version] > > Don't do that. Upgrade normally applies to all dependencies as > well, so > you would be rebuilding all of them because of the -f. (You can use -n > to avoid processing dependencies.) > > In fact, -f upgrade is not called for in this situation at all, but > rather -f activate. > > - Josh Frank J. R. Hanstick trog24 at comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From jpg at gmx.com Fri Mar 27 02:37:03 2009 From: jpg at gmx.com (Jamie Griffin) Date: Fri, 27 Mar 2009 09:37:03 +0000 Subject: fvwm2 build problem Message-ID: <20090327093703.GA66909@Macbook.local> Hi I having some trouble getting fvwm2 to install and need some help if possible. I'm using Leopard 10.5.6 (Intel) with xcode 3.1.2. Some of the dependencies won't build and i don't know why. Any help appreciated. Jamie. This is the error i'm getting: --------------------------------------------------------------------- Error: Target org.macports.destroot returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_gnome-libs/work/gnome-libs-1.4.2" && make install DESTDIR=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_gnome-libs/work/destroot " returned error 2 Command output: -- Installing ./html/libart-core-construction-apis.html /bin/ksh[1]: ../../: cannot execute [Is a directory] -- Installing ./html/libart-extended-construction-apis.html /bin/ksh[1]: ../../: cannot execute [Is a directory] -- Installing ./html/libart-memory-management.html /bin/ksh[1]: ../../: cannot execute [Is a directory] -- Installing ./html/libart-svp-rendering.html /bin/ksh[1]: ../../: cannot execute [Is a directory] -- Installing ./html/libart-svps.html /bin/ksh[1]: ../../: cannot execute [Is a directory] -- Installing ./html/libart-transformation-operations.html /bin/ksh[1]: ../../: cannot execute [Is a directory] -- Installing ./html/libart.html /bin/ksh[1]: ../../: cannot execute [Is a directory] -- Installing ./html/problems-memory.html /bin/ksh[1]: ../../: cannot execute [Is a directory] -- Installing ./html/problems.html /bin/ksh[1]: ../../: cannot execute [Is a directory] -- Installing ./html/sample-display.html /bin/ksh[1]: ../../: cannot execute [Is a directory] -- Installing ./html/sample.html /bin/ksh[1]: ../../: cannot execute [Is a directory] -- Installing ./html/x35.html /bin/ksh[1]: ../../: cannot execute [Is a directory] -- Installing ./html/index.sgml /bin/ksh: line 1: ../../: cannot execute [Is a directory] make[3]: *** [install-data-local] Error 126 make[2]: *** [install-am] Error 2 make[1]: *** [install-recursive] Error 1 make: *** [install-recursive] Error 1 Error: The following dependencies failed to build: gnome-libs xorg-libXinerama xorg-xineramaproto xpm Error: Status 1 encountered during processing. -------------------------------------------------------------------- -- GNUPG Key-ID: 0x842DD368 GNUPG Key-Fingerprint: F850 A09C F877 FBC4 A63C FDDC 7484 4EEF 842D D368 AIM: jpg at gmx.com -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 194 bytes Desc: not available URL: From drf at blackchairdvd.com Fri Mar 27 03:35:55 2009 From: drf at blackchairdvd.com (drf) Date: Fri, 27 Mar 2009 10:35:55 +0000 Subject: php5 & "port test php5" In-Reply-To: <09C9BF97-46AB-4D2D-90D6-980B688C1411@macports.org> References: <49C7EA67.9010101@blackchairdvd.com> <09C9BF97-46AB-4D2D-90D6-980B688C1411@macports.org> Message-ID: <49CCAC0B.9010100@blackchairdvd.com> Ryan Schmidt wrote: > > On Mar 23, 2009, at 15:00, drf wrote: > >> My setup: Mac Mini, 10.4.11, Xcode 2.5, GCC 4, MacPorts 1.7 >> >> Everything compiles fine, there are some complaints about signedness >> from the compiler, but it all looks ok. But when I run the PHP test >> suite, over 70 tests fail, including ones I wouldn't really expect, >> like on the function easterdate(). I can not find any hints anywhere >> on what might be happening, so I'm wondering if these tests really >> are that important. Should a completely default, standard, stock >> install of php5 with MacPorts pass all the PHP self tests fine? >> >> The thing is, when I set up everything myself (not using MacPorts to >> compile php5) the same set of tests failed - the config of php5 did >> reference various macport installed libraries, etc. I am now at the >> point where I am wondering if I ought to toss all of MacPorts and try >> to install everything myself that is needed to compile php5. >> >> So any advice, pointers on where to look, or hints on 64 bit vs 32 >> would be greatly appreciated > > Hi. I'm the maintainer of php5 in MacPorts. > > On the few occasions when I have tried "port test php5", it did not > pass everything either. Please feel free to enter into a dialog about > this with the developers of PHP. I have not had the energy to do so > myself. They're often quite rude in responding to bug reports and I > haven't felt like being abused lately. I checked out some of the test reports and the Expected Output was hardly what the code would output as far as I could tell / program in PHP.... So I'm not too worried. > I recommend you use MacPorts for all your software installation needs, > including PHP. You could build it all yourself, but it would be a lot > of work figuring out things that we have already figured out in > MacPorts. If the software available in MacPorts doesn't fully meet > your needs, please bring it to our attention so that we can improve > the ports until they do meet your needs. I wanted to include a few extensions, and dropped one from the supported list IIRC. I also wanted to compile against an install of Percona's MySQL - I could not find anything in the ports list of MacPorts related to Percona. Like I said, my install of PHP failed the same set of tests the MacPorts compile of PHP did, so it's not something specific to MacPorts I presume. What to modify and how things worked in MacPorts was pretty obvious, so it all went smoothly; I have PHP set up using MacPorts. Thanks for all your work and everyone else on MacPorts! > > I have not attempted to compile php5 as a universal binary or 64-bit. > I would not be surprised if it did not work. If you try it and it > works, or if you can figure out how to make it work, please let us know. But if the test suite doesn't work, how does one really know...? :) doug From ryandesign at macports.org Fri Mar 27 04:04:21 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 27 Mar 2009 06:04:21 -0500 Subject: php5 & "port test php5" In-Reply-To: <49CCAC0B.9010100@blackchairdvd.com> References: <49C7EA67.9010101@blackchairdvd.com> <09C9BF97-46AB-4D2D-90D6-980B688C1411@macports.org> <49CCAC0B.9010100@blackchairdvd.com> Message-ID: <1E55E619-4332-4F0F-82F9-18DFE42AD627@macports.org> On Mar 27, 2009, at 05:35, drf wrote: > I wanted to include a few extensions, and dropped one from the > supported list IIRC. I also wanted to compile against an install > of Percona's MySQL - I could not find anything in the ports list of > MacPorts related to Percona. Like I said, my install of PHP failed > the same set of tests the MacPorts compile of PHP did, so it's not > something specific to MacPorts I presume. This is the first I've heard of Percona's MySQL before. It seems they have written patches to improve MySQL in various performance-related ways? Perhaps we could integrate some or all of their patches into the mysql5 port. If you desire this, please file tickets with more details. >> I have not attempted to compile php5 as a universal binary or 64- >> bit. I would not be surprised if it did not work. If you try it >> and it works, or if you can figure out how to make it work, please >> let us know. > > But if the test suite doesn't work, how does one really know...? :) I meant: if you can get php5 to even compile universal, for any combination of universal architectures, that would be good to know (and if you cannot, that would be good to know too). I'm not even sure all of php5's dependencies can be compiled universal. I simply have not yet tried. I just ran the tests for 5.3.0RC1 (am in the process of updating the php5-devel port to that version); here's the summary: Number of tests : 9537 7891 Tests skipped : 1646 ( 17.3%) -------- Tests warned : 3 ( 0.0%) ( 0.0%) Tests failed : 31 ( 0.3%) ( 0.4%) Expected fail : 5 ( 0.1%) ( 0.1%) Tests passed : 7852 ( 82.3%) ( 99.5%) --------------------------------------------------------------------- Time taken : 1428 seconds When you run the tests, it offers to send a report to the PHP developers automatically. Hopefully they're reading these reports and making improvements. From ryandesign at macports.org Fri Mar 27 04:46:35 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Fri, 27 Mar 2009 06:46:35 -0500 Subject: fvwm2 build problem In-Reply-To: <20090327093703.GA66909@Macbook.local> References: <20090327093703.GA66909@Macbook.local> Message-ID: On Mar 27, 2009, at 04:37, Jamie Griffin wrote: > I having some trouble getting fvwm2 to install and need some help if > possible. > > I'm using Leopard 10.5.6 (Intel) with xcode 3.1.2. > > Some of the dependencies won't build and i don't know why. Any help > appreciated. Jamie. > > This is the error i'm getting: > > --------------------------------------------------------------------- > > Error: Target org.macports.destroot returned: shell command " cd > "/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome > _gnome-libs/work/gnome-libs-1.4.2" > && make install > DESTDIR=/opt/local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome > _gnome-libs/work/destroot > " returned error 2 > Command output: -- Installing ./html/libart-core-construction- > apis.html > /bin/ksh[1]: ../../: cannot execute [Is a directory] > -- Installing ./html/libart-extended-construction-apis.html > /bin/ksh[1]: ../../: cannot execute [Is a directory] > -- Installing ./html/libart-memory-management.html > /bin/ksh[1]: ../../: cannot execute [Is a directory] > -- Installing ./html/libart-svp-rendering.html > /bin/ksh[1]: ../../: cannot execute [Is a directory] > -- Installing ./html/libart-svps.html > /bin/ksh[1]: ../../: cannot execute [Is a directory] > -- Installing ./html/libart-transformation-operations.html > /bin/ksh[1]: ../../: cannot execute [Is a directory] > -- Installing ./html/libart.html > /bin/ksh[1]: ../../: cannot execute [Is a directory] > -- Installing ./html/problems-memory.html > /bin/ksh[1]: ../../: cannot execute [Is a directory] > -- Installing ./html/problems.html > /bin/ksh[1]: ../../: cannot execute [Is a directory] > -- Installing ./html/sample-display.html > /bin/ksh[1]: ../../: cannot execute [Is a directory] > -- Installing ./html/sample.html > /bin/ksh[1]: ../../: cannot execute [Is a directory] > -- Installing ./html/x35.html > /bin/ksh[1]: ../../: cannot execute [Is a directory] > -- Installing ./html/index.sgml > /bin/ksh: line 1: ../../: cannot execute [Is a directory] > make[3]: *** [install-data-local] Error 126 > make[2]: *** [install-am] Error 2 > make[1]: *** [install-recursive] Error 1 > make: *** [install-recursive] Error 1 > > Error: The following dependencies failed to build: gnome-libs > xorg-libXinerama xorg-xineramaproto xpm > Error: Status 1 encountered during processing. http://trac.macports.org/ticket/14363 Try: sudo port selfupdate sudo port clean gnome-libs Does the problem still occur after that? From talklists at newgeo.com Fri Mar 27 05:06:23 2009 From: talklists at newgeo.com (Scott Haneda) Date: Fri, 27 Mar 2009 05:06:23 -0700 Subject: php5 & "port test php5" In-Reply-To: <1E55E619-4332-4F0F-82F9-18DFE42AD627@macports.org> References: <49C7EA67.9010101@blackchairdvd.com> <09C9BF97-46AB-4D2D-90D6-980B688C1411@macports.org> <49CCAC0B.9010100@blackchairdvd.com> <1E55E619-4332-4F0F-82F9-18DFE42AD627@macports.org> Message-ID: <0CA50938-556E-4330-8352-800A77D58F80@newgeo.com> On Mar 27, 2009, at 4:04 AM, Ryan Schmidt wrote: > I meant: if you can get php5 to even compile universal, for any > combination of universal architectures, that would be good to know > (and if you cannot, that would be good to know too). I'm not even > sure all of php5's dependencies can be compiled universal. I simply > have not yet tried Some of them can, I would go as far as to say, most of them still can not. This is very much the exact reason why Mark Lyniage does not have time to make his php installer anymore. In some regards, it was not possible without a lot of work to get the depends working. The last I looked into this was a few months ago, I suspect it is still pretty accurate today. -- Scott * If you contact me off list replace talklists@ with scott@ * From dweber at macports.org Fri Mar 27 11:24:45 2009 From: dweber at macports.org (Darren Weber) Date: Fri, 27 Mar 2009 11:24:45 -0700 Subject: stable vs. unstable ports? In-Reply-To: <2AE7AB32-F26E-4F4D-AD76-41D7CEE805DC@macports.org> References: <49C6D55C.7050709@macports.org> <64FEDC27-0878-4A20-8281-1BEA112D43D0@macports.org> <2AAF5972-7AC8-4D87-9471-2F29938DB22F@grandfenwick.net> <2AE7AB32-F26E-4F4D-AD76-41D7CEE805DC@macports.org> Message-ID: FYI, running mpab (without any mods) on a mac Pro system: Model Name: Mac Pro Model Identifier: MacPro3,1 Processor Name: Quad-Core Intel Xeon Processor Speed: 2.8 GHz Number Of Processors: 2 Total Number Of Cores: 8 L2 Cache (per processor): 12 MB Memory: 24 GB Bus Speed: 1.6 GHz It's been running since 11 am, Monday 23rd March, 2009. It's now: Fri Mar 27 11:22:21 PDT 2009 The auto-build is currently at: Building slib-guile (1645 of 5648)... I don't know how to interrogate the success or failure rates. Best, Darren On Thu, Mar 26, 2009 at 8:23 PM, Ryan Schmidt wrote: > On Mar 26, 2009, at 17:51, Darren Weber wrote: > > > On Thu, Mar 26, 2009 at 2:09 PM, Dave Howell wrote: >> >> On Mar 23, 2009, at 0:38 , Ryan Schmidt wrote: >>> >>> Before we can allow arbitrary users to submit their builds to a central >>>> server, we would need to ensure that a build that occurs on one user's >>>> system is *identical* to the build on any other user's computer. This cannot >>>> currently be assured because MacPorts does not build in a chroot, and >>>> without this, it is possible for a port to link with libraries that happen >>>> to be on the user's system that it ought not link with -- be they libraries >>>> from other ports on which the port in question does not declare a >>>> dependency, or libraries in /usr/local, to which the compiler always looks. >>>> >>> >>> Would two "identical builds" be byte-identical? If so, then a binary >>> doesn't become available until *two* (or three or whatever) identical >>> binaries are uploaded. >>> >>> And/or, there's some command line library tool (I'm on vacation and my >>> reference books are home) that I can run to get a listing of what libraries >>> are called by a particular binary, isn't there? Wouldn't that help screen >>> wacky-linked binaries? >>> >>> The deliberate uploading of contaminated binaries, however, is a whole >>> different kettle of worms. :/ >>> >> >> I've been running mpab for a few days now, ie: >> http://trac.macports.org/wiki/MPAB >> >> This is a chroot approach. Obviously, as it is, anyone could tinker with >> it to include a rootkit or whatever. Nevertheless, I wonder if it's >> possible to create a binary app of this, which is authenticated during >> installation (at least), and we ensure that it must do some handshaking to >> get hold of the "official" and "secure" port tree somehow (probably an >> encrypted handshake, encrypted file archive for download, etc.) and then it >> goes about it's business on a user machine and only does an upload (if any) >> when there is some kind of further authentication that the port build is >> correct (binary md5 etc. for at least 2-5 builds on the exact same >> configuration). Even if it does no uploads, it could create useful >> information about the stability or integrity (you name it) of the entire >> build process. It would be really neat to have an Xgrid controller (or >> many) be able to run a job that can parse out port dependencies and have >> some kind of parallelism in the build. >> > > > Libraries and compressed files (which include manpages) tend to differ > everytime they're built, even if they're functionally the same. So you can't > just run an md5 checksum over everything and expect it to be the same after > repeated builds. > > I hadn't thought of securing a distributed build system from malicious > users until Joshua's message, but now I agree that from a security > standpoint we cannot allow user-uploaded binaries at all. Dave's proposed > safeguard of requiring n users to upload functionally identical files isn't > going to help; if a malicious user can upload a bad binary from 1 computer, > they can borrow n friends' computers and create n throwaway email addresses > and upload the binary how ever many times we've specified. There are botnets > out there with thousands of computers that can be commandeered by hackers to > do whatever. > > So let's kill the idea of user-submitted binaries now. We want dedicated > build servers under the control of the MacPorts project. So let's flesh out > MPAB into something that can be run on such build servers. Then we can look > at acquiring the servers. > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From blb at macports.org Fri Mar 27 13:44:02 2009 From: blb at macports.org (Bryan Blackburn) Date: Fri, 27 Mar 2009 14:44:02 -0600 Subject: stable vs. unstable ports? In-Reply-To: References: <49C6D55C.7050709@macports.org> <64FEDC27-0878-4A20-8281-1BEA112D43D0@macports.org> <2AAF5972-7AC8-4D87-9471-2F29938DB22F@grandfenwick.net> <2AE7AB32-F26E-4F4D-AD76-41D7CEE805DC@macports.org> Message-ID: <20090327204402.GF815@ninagal.withay.com> On Fri, Mar 27, 2009 at 11:24:45AM -0700, Darren Weber said: > FYI, running mpab (without any mods) on a mac Pro system: > > Model Name: Mac Pro > Model Identifier: MacPro3,1 > Processor Name: Quad-Core Intel Xeon > Processor Speed: 2.8 GHz > Number Of Processors: 2 > Total Number Of Cores: 8 > L2 Cache (per processor): 12 MB > Memory: 24 GB > Bus Speed: 1.6 GHz > > It's been running since 11 am, Monday 23rd March, 2009. It's now: > Fri Mar 27 11:22:21 PDT 2009 > > The auto-build is currently at: > Building slib-guile (1645 of 5648)... > > I don't know how to interrogate the success or failure rates. Check in /path/to/chroot/var/tmp/portresults; you should see subdirectories success and fail which include debug output for each port built. Bryan > > Best, Darren > [...] From jpg at gmx.com Fri Mar 27 13:57:12 2009 From: jpg at gmx.com (Jamie Griffin) Date: Fri, 27 Mar 2009 21:57:12 +0100 Subject: fvwm2 build problem Message-ID: <20090327205712.231760@gmx.com> -------------- next part -------------- An HTML attachment was scrubbed... URL: From travisgriggs at gmail.com Fri Mar 27 14:18:33 2009 From: travisgriggs at gmail.com (Travis Griggs) Date: Fri, 27 Mar 2009 14:18:33 -0700 Subject: Cairo default configuration Message-ID: Ryan Schmidt (the maintainer of the Cairo port) asked me to lobby the list for feedback on an issue I recently ran aground of. Cairo can be built with multiple backends. Once upon a time, the default configuration caused only the xlib backend to be built. You had to take extra steps to get the quartz backend built. And then that changed, and BOTH backends were turned on by default. Ryan recently changed it back to the old way, so that quartz requires extra configuration to work. I've lobbied him to revert it (I should take a moment to thank him for providing the port in the first place, thank you very much Ryan) so that quartz is on by default. In fact I might go so far as to say xlib does not need to be turned on unless told to be, but that's because for MY uses, I just need quartz. -- Travis Griggs Objologist I patented thinking... and I still can't find anyone infringing. From ikbenjosvantongeren at gmail.com Fri Mar 27 14:37:34 2009 From: ikbenjosvantongeren at gmail.com (Jos van Tongeren) Date: Fri, 27 Mar 2009 22:37:34 +0100 Subject: Post to the list Message-ID: <250ee9790903271437v65759409x3aa9e0bf43866572@mail.gmail.com> Please post me to the list, thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrei at tchijov.com Fri Mar 27 15:10:18 2009 From: andrei at tchijov.com (Andrei Tchijov) Date: Fri, 27 Mar 2009 18:10:18 -0400 Subject: Cairo default configuration In-Reply-To: References: Message-ID: <628AD201-2A37-4AE2-83DF-2578EB078CD0@tchijov.com> Actually it is not "cut and dry". Just few days ago I was trying to build "quartz" versions of Gimp and Dia (I thing Gimp is using Cairo and I assume Dia use it too). With Gimp result was more or less OK. There are some quirks but it is usable. Dia on other hand is useless. I was able to build application, but it has drawing issues which renders it completely unacceptable. At the same time, X11 based version of both programs work just fine. So if making quartz default option will force maintainers to fix all existing problems, then I am all for it. But it is almost guarantied to increase number of no-so-happy macport users (at least temporary) in the process. Andrei On Mar 27, 2009, at 17:18 , Travis Griggs wrote: > Ryan Schmidt (the maintainer of the Cairo port) asked me to lobby > the list for feedback on an issue I recently ran aground of. Cairo > can be built with multiple backends. Once upon a time, the default > configuration caused only the xlib backend to be built. You had to > take extra steps to get the quartz backend built. And then that > changed, and BOTH backends were turned on by default. Ryan recently > changed it back to the old way, so that quartz requires extra > configuration to work. I've lobbied him to revert it (I should take > a moment to thank him for providing the port in the first place, > thank you very much Ryan) so that quartz is on by default. In fact I > might go so far as to say xlib does not need to be turned on unless > told to be, but that's because for MY uses, I just need quartz. > > -- > Travis Griggs > Objologist > I patented thinking... and I still can't find anyone infringing. > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From LenoreHorner at sbcglobal.net Fri Mar 27 16:09:04 2009 From: LenoreHorner at sbcglobal.net (Lenore Horner) Date: Fri, 27 Mar 2009 18:09:04 -0500 Subject: Cairo default configuration In-Reply-To: References: Message-ID: <65E11C44-6AC2-41CE-A37B-D57C9E575AB1@sbcglobal.net> I've set my build parameters for quartz so I could built a quartz gnucash (which is working pretty well, by the way). Lenore On Mar 27, 2009, at 16:18 , Travis Griggs wrote: > Ryan Schmidt (the maintainer of the Cairo port) asked me to lobby > the list for feedback on an issue I recently ran aground of. Cairo > can be built with multiple backends. Once upon a time, the default > configuration caused only the xlib backend to be built. You had to > take extra steps to get the quartz backend built. And then that > changed, and BOTH backends were turned on by default. Ryan recently > changed it back to the old way, so that quartz requires extra > configuration to work. I've lobbied him to revert it (I should take > a moment to thank him for providing the port in the first place, > thank you very much Ryan) so that quartz is on by default. In fact I > might go so far as to say xlib does not need to be turned on unless > told to be, but that's because for MY uses, I just need quartz. > > -- > Travis Griggs > Objologist > I patented thinking... and I still can't find anyone infringing. > > _______________________________________________ > macports-users mailing list > macports-users at lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From shreevatsa.public at gmail.com Fri Mar 27 20:53:35 2009 From: shreevatsa.public at gmail.com (Shreevatsa R) Date: Fri, 27 Mar 2009 23:53:35 -0400 Subject: Cairo default configuration In-Reply-To: References: Message-ID: <7675454e0903272053m59236bd4nff15376b76e6dd6d@mail.gmail.com> On Fri, Mar 27, 2009 at 5:18 PM, Travis Griggs wrote: > default. Ryan recently changed it back to the old way, so that quartz > requires extra configuration to work. I've lobbied him to revert it (I What is the advantage of this, or what is the disadvantage of having quartz work by default? FWIW, I do use the quartz variant, so I would prefer having it work. From travisgriggs at gmail.com Fri Mar 27 21:19:53 2009 From: travisgriggs at gmail.com (Travis Griggs) Date: Fri, 27 Mar 2009 21:19:53 -0700 Subject: Cairo default configuration In-Reply-To: <7675454e0903272053m59236bd4nff15376b76e6dd6d@mail.gmail.com> References: <7675454e0903272053m59236bd4nff15376b76e6dd6d@mail.gmail.com> Message-ID: <2D5E233A-9D46-4670-BD03-9A8EBC3CB5EB@gmail.com> On Mar 27, 2009, at 8:53 PM, Shreevatsa R wrote: > On Fri, Mar 27, 2009 at 5:18 PM, Travis Griggs > wrote: >> default. Ryan recently changed it back to the old way, so that quartz >> requires extra configuration to work. I've lobbied him to revert it >> (I > > What is the advantage of this, or what is the disadvantage of having > quartz work by default? > > FWIW, I do use the quartz variant, so I would prefer having it work. I maintain the VisualWorks Smalltalk binding to Cairo, on multiple platforms, including OSX. Many in our community, want to play with Cairo using Smalltalk. So, I've been telling them to just use Macports to get the libraries on their machine, it's the easiest turnkey way to get it. Having to edit variants.conf files, or know that they should always add +quartz to every cairo related port command, makes that less of a "turnkey" solution. I've been scratching my head for a week or so now, while I'm seeing an increased amount of "hey, why doesn't this work anymore" traffic. -- Travis Griggs tgriggs at cincom.com "The dissenter is every human being at those moments of his life when he resigns momentarily from the herd and thinks for himself." - Archibald MacLeish, poet and librarian From ryandesign at macports.org Sat Mar 28 03:28:06 2009 From: ryandesign at macports.org (Ryan Schmidt) Date: Sat, 28 Mar 2009 05:28:06 -0500 Subject: Post to the list In-Reply-To: <250ee9790903271437v65759409x3aa9e0bf43866572@mail.gmail.com> References: <250ee9790903271437v65759409x3aa9e0bf43866572@mail.gmail.com> Message-ID: <79F8E9C4-A7D6-45A6-875C-7DE3FB3B03DB@macports.org> On Mar 27, 2009, at 16:37, Jos van Tongeren wrote: > Please post me to the list, If you mean that you would like to subscribe to the mailing list, then you can do so yourself by visiting this web site: http://lists.macosforge.org/mailman/listinfo.cgi/macports-users From frstan at bellsouth.net Sat Mar 28 09:51:45 2009 From: frstan at bellsouth.net (William Davis) Date: Sat, 28 Mar 2009 12:51:45 -0400 Subject: kdelibs4 upgrade error -- files exists Message-ID: <7145E558-10F8-4CC4-95D5-2E0FD0F8527C@bellsouth.net> The kdelibs4 upgrade fails for me with a "files exists" error while it is trying to install one of its dependencies qt4-kde: xinstall: /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_aqua_qt4-kde/work/qt-mac-opensource- src-4.4.3/GPL_EXCEPTION.TXT -> /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_re Error: Target org.macports.destroot returned: ln: /opt/local/var/ macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_aqua_qt4-kde/work/destroot/opt/local/bin/ lrelease: File exists Warning: the following items did not execute (for qt4-kde): org.macports.activate org.macports.destroot org.macports.install Error: The following dependencies failed to build: qt4-kde DEBUG: Registry error: qt4-kde not registered as installed & active. invoked from within "registry_active ${portname}" invoked from within "$workername eval registry_active \${portname}" Error: Unable to upgrade port: 1 macintosh:~ frstan$ This is likely because I have : macintosh:~ frstan$ port installed *qt4* The following ports are currently installed: qt4-mac @4.5.0_1 (active) qt4-x11 @4.4.3_2 (active) macintosh:~ frstan$ what do you advise? William Davis frstanATbellsouthDOTnet Mac OS X.5.6 Darwin 9.5.0 XQuartz 2.3.3_rc2 (xorg-server 1.4.2-apple37) Mac Mini Intel Duo @ 1.86 GHz Mundus vult decepi, ego non From mcalhoun at macports.org Sat Mar 28 10:34:06 2009 From: mcalhoun at macports.org (Marcus Calhoun-Lopez) Date: Sat, 28 Mar 2009 17:34:06 +0000 (UTC) Subject: kdelibs4 upgrade error -- files exists References: <7145E558-10F8-4CC4-95D5-2E0FD0F8527C@bellsouth.net> Message-ID: William Davis bellsouth.net> writes: > > The kdelibs4 upgrade fails for me with a "files exists" error while it > is trying to install one of its dependencies qt4-kde: > > This is likely because I have : > > macintosh:~ frstan$ port installed *qt4* > The following ports are currently installed: > qt4-mac @4.5.0_1 (active) > qt4-x11 @4.4.3_2 (active) > macintosh:~ frstan$ I do not think this is a conflict between qt4-mac and qt4-kde. For one thing, it happens during the destroot phase and not during activation. The last time I saw an error like this, it was because an install had started, been stopped, and then restarted. In this scenario: lrelease was created, the install was stopped, and then an attempt was made to create lrelease again (an error). If this is the case, then port clean qt4-kde port install qt4-kde should solve the problem. -Marcus From ms at mac-specialist.com Sat Mar 28 12:07:09 2009 From: ms at mac-specialist.com (Bill Hernandez) Date: Sat, 28 Mar 2009 14:07:09 -0500 Subject: Error Installing : subversion +bash_completion +mac_os_x_server_mod_dav_svn Message-ID: I tried to accessing subversion on a machine running OS X SERVER 10.4.x (latest 10.4 version) and ran into a couple of errors related to something called 'neon'. ( 1 ) I had installed 'CornerStone svn client' yesterday tried on my workstation. ( 2 ) Setup a repository on my local machine, which worked fine. ( 3 ) Modified the apache2 virtual host conf file to allow WebDav over SSL on port 8443 ( 3 ) Tried to create the repository using the client, using : 'https://www.example.com:8443/svn/repository' as the path, but kept running into an error, so today I looked at the server and did a $which svn, and to my surprise found there wasn't any. On the Leopard machine that I am using, just for grins, I also tried : [2009.28.03](01:40PM) -> [roscoe] ~ $ which svn /usr/bin/svn and sure enough, it finally became clear why I couldn't access the server using the client. Cornerstone worked fine with a repository on my local machine, but not on the server. I didn't realize OS X Server 10.4 didn't have subversion installed, silly me. Anyway, MacPorts to the rescue, I tried installing subversion using : $ sudo port install -v subversion +bash_completion +mac_os_x_server_mod_dav_svn below, but ran into a couple of errors during the install. Any ideas ? Bill Hernandez Plano, Texas [2009.28.03](01:08PM) -> [roscoe] ~ $ sudo port selfupdate Password: [2009.28.03](01:08PM) -> [roscoe] ~ $ port installed apache2 The following ports are currently installed: apache2 @2.2.10_0 (active) MacPorts base version 1.700 installed Downloaded MacPorts base version 1.700 The MacPorts installation is not outdated so it was not updated [2009.28.03](01:08PM) -> [roscoe] ~ $ port info subversion subversion @1.6.0, Revision 1 (devel) Variants: bash_completion, darwin_7, disable_keychain, mac_os_x_server_mod_dav_svn, mod_dav_svn, no_bdb, no_neon, tools, unicode_path Subversion is a version control system designed to be as similar to cvs(1) as possible, while fixing many outstanding problems with cvs(1). Homepage: http://subversion.tigris.org/ Library Dependencies: expat, neon, apr, apr-util, db46, sqlite3, gettext, libiconv, serf, cyrus-sasl2 Platforms: darwin Maintainers: dluke at geeklair.net [2009.28.03](01:09PM) -> [roscoe] ~ $ sudo port install -v subversion +bash_completion+mac_os_x_server_mod_dav_svn ---> Fetching bash-completion ---> Attempting to fetch bash-completion-20060301.tar.bz2 from http://distfiles.macports.org/bash-completion ---> Verifying checksum(s) for bash-completion ---> Extracting bash-completion ---> Configuring bash-completion ---> Building bash-completion ---> Staging bash-completion into destroot ---> Installing bash-completion @20060301_1 To use bash_completion, add the following lines at the end of your .bash_profile: if [ -f /opt/local/etc/bash_completion ]; then . /opt/local/etc/bash_completion fi ---> Activating bash-completion @20060301_1 ---> Cleaning bash-completion ---> Fetching neon ---> Attempting to fetch neon-0.28.3.tar.gz from http://distfiles.macports.org/neon ---> Verifying checksum(s) for neon ---> Extracting neon ---> Configuring neon ---> Building neon ---> Staging neon into destroot ---> Installing neon @0.28.3_1 ---> Activating neon @0.28.3_1 ---> Cleaning neon ---> Fetching serf ---> Attempting to fetch serf-0.3.0.tar.bz2 from http://serf.googlecode.com/files/ ---> Verifying checksum(s) for serf ---> Extracting serf ---> Configuring serf ---> Building serf ---> Staging serf into destroot ---> Installing serf @0.3.0_0 ---> Activating serf @0.3.0_0 ---> Cleaning serf ---> Fetching subversion ---> Attempting to fetch subversion-1.6.0.tar.bz2 from http://subversion.tigris.org/downloads/ ---> Verifying checksum(s) for subversion ---> Extracting subversion ---> Applying patches to subversion ---> Configuring subversion ERROR: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_devel_subversion/work/subversion-1.6.0" && ./configure --prefix=/opt/local --with-berkeley-db=yes --with-neon=/ opt/local --with-apr=/opt/local/bin/apr-1-config --with-apr-util=/opt/ local/bin/apu-1-config --mandir=\${prefix}/share/man --disable-neon- version-check --with-serf=/opt/local --with-sasl=/opt/local --with- apxs=/opt/apache2/bin/apxs --disable-mod-activation " returned error 1 Command output: configure: Apache Portable Runtime Utility (APRUTIL) library configuration checking for APR-util... yes checking APR-UTIL version... 1.3.4 checking for pkg-config... /opt/local/bin/pkg-config configure: checking neon library checking neon library version... 0.28.3 checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes configure: serf library configuration checking serf.h usability... yes checking serf.h presence... yes checking for serf.h... yes checking for serf_context_create in -lserf-0... yes configure: looking for apr_memcache as part of apr-util checking apr_memcache.h usability... yes checking apr_memcache.h presence... yes checking for apr_memcache.h... yes checking for apr_memcache_create in -laprutil-1... yes checking for Apache module support via DSO through APXS... found at / opt/apache2/bin/apxs checking httpd version... recent enough checking whether Apache version is compatible with APR version... NO configure: error: Apache version incompatible with APR version ERROR: Status 1 encountered during processing. [2009.28.03](01:15PM) -> [roscoe] ~ $ From christopher.rob.jones at cern.ch Sat Mar 28 14:38:37 2009 From: christopher.rob.jones at cern.ch (Chris Jones) Date: Sat, 28 Mar 2009 21:38:37 +0000 Subject: kdelibs4 upgrade error -- files exists In-Reply-To: References: <7145E558-10F8-4CC4-95D5-2E0FD0F8527C@bellsouth.net> Message-ID: <7851B3E2-0216-44A4-999D-F68F97992466@cern.ch> > Hi, > to create lrelease again (an error). > > If this is the case, then > port clean qt4-kde > port install qt4-kde > should solve the problem. I experienced the same problem (I had to stop the build the first time I tried to install since I need to shutdown my machine). A clean helps, but U still get an error during the destroot staging ? > Chris-Jones-Macbook-Pro ~ > sudo port clean qt4-kde > ---> Cleaning qt4-kde > Chris-Jones-Macbook-Pro ~ > sudo port install qt4-kde > ---> Fetching qt4-kde > ---> Verifying checksum(s) for qt4-kde > ---> Extracting qt4-kde > ---> Applying patches to qt4-kde > ---> Configuring qt4-kde > ---> Building qt4-kde > ---> Staging qt4-kde into destroot > Error: Target org.macports.destroot returned: xinstall: Cannot > stat: /opt/local/var/macports/sources/rsync.macports.org/release/ > ports/aqua/qt4-kde/files/qt4-kde, No such file or directory > Error: Status 1 encountered during processing. Any ideas ? cheers Chris > > From dweber at macports.org Sat Mar 28 15:20:27 2009 From: dweber at macports.org (Darren Weber) Date: Sat, 28 Mar 2009 15:20:27 -0700 Subject: dbus and launchd spinning out of control Message-ID: I've only just noticed my Utilities -> Console log and it contains streams of the following messages: 3/28/09 3:11:03 PM org.macports.dbus[20573] Failed to start message bus: The pid file "/opt/local/var/run/dbus/pid" exists, if the message bus is not running, remove this file 3/28/09 3:11:03 PM com.apple.launchd[1] (org.macports.dbus) Throttling respawn: Will start in 10 seconds 3/28/09 3:11:03 PM com.apple.launchd[1] (org.macports.dbus) Throttling respawn: Will start in 10 seconds 3/28/09 3:11:13 PM org.macports.dbus[20575] Failed to start message bus: The pid file "/opt/local/var/run/dbus/pid" exists, if the message bus is not running, remove this file 3/28/09 3:11:13 PM com.apple.launchd[1] (org.macports.dbus) Throttling respawn: Will start in 10 seconds 3/28/09 3:11:13 PM com.apple.launchd[1] (org.macports.dbus) Throttling respawn: Will start in 10 seconds 3/28/09 3:11:23 PM org.macports.dbus[20579] Failed to start message bus: The pid file "/opt/local/var/run/dbus/pid" exists, if the message bus is not running, remove this file 3/28/09 3:11:23 PM com.apple.launchd[1] (org.macports.dbus) Throttling respawn: Will start in 10 seconds 3/28/09 3:11:23 PM com.apple.launchd[1] (org.macports.dbus) Throttling respawn: Will start in 10 seconds 3/28/09 3:11:33 PM org.macports.dbus[20583] Failed to start message bus: The pid file "/opt/local/var/run/dbus/pid" exists, if the message bus is not running, remove this file 3/28/09 3:11:33 PM com.apple.launchd[1] (org.macports.dbus) Throttling respawn: Will start in 10 seconds So every 10 sec, launchd is trying to get dbus up and running, but it fails because an old pid file is hanging around. Can this be resolved automatically? When I check the file, I get: [ dweber at XXXX ~ ]$ ls -l /opt/local/var/run/dbus/pid -rw-r--r-- 1 root messagebus 4 2008-09-19 21:05 /opt/local/var/run/dbus/pid Given the date of this pid file (Sep 2008), I can only assume that this entire process has been repeated every 10 seconds for months, whenever my laptop system is running. I've now removed the old pid file and the launchd job has finally come to rest. I'm not a frequent checker of system logs, I just use the system and I guess most people are also unlikely to check the system logs (console). I'm curious about why this situation arose and, moreover, why it was not automatically resolved (it clearly required my intervention to remove the old pid file). Take care, Darren -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcalhoun at macports.org Sat Mar 28 15:29:35 2009 From: mcalhoun at macports.org (Marcus Calhoun-Lopez) Date: Sat, 28 Mar 2009 22:29:35 +0000 (UTC) Subject: kdelibs4 upgrade error -- files exists References: <7145E558-10F8-4CC4-95D5-2E0FD0F8527C@bellsouth.net> <7851B3E2-0216-44A4-999D-F68F97992466@cern.ch> Message-ID: Chris Jones cern.ch> writes: > I experienced the same problem (I had to stop the build the first time > I tried to install since I need to shutdown my machine). A clean > helps, but U still get an error during the destroot staging ? > > > Chris-Jones-Macbook-Pro ~ > sudo port clean qt4-kde > > ---> Cleaning qt4-kde ... > > Error: Target org.macports.destroot returned: xinstall: Cannot > > stat: /opt/local/var/macports/sources/rsync.macports.org/release/ > > ports/aqua/qt4-kde/files/qt4-kde, No such file or directory > > Error: Status 1 encountered during processing. A different error message is progress of sorts. When qt4-mac was copied to qt4-kde, then one of the files was not renamed as it should have been. This has been fixed in r48782. As soon as the changes show up on the rsync server, port selfupdate should allow you to install. Thanks for catching my oversight. -Marcus From jpg at gmx.com Sat Mar 28 15:35:51 2009 From: jpg at gmx.com (Jamie Griffin) Date: Sat, 28 Mar 2009 23:35:51 +0100 Subject: Another window manager failed to build: gnustep Message-ID: <20090328223734.231780@gmx.com> -------------- next part -------------- An HTML attachment was scrubbed... URL: From dweber at macports.org Sat Mar 28 15:38:40 2009 From: dweber at macports.org (Darren Weber) Date: Sat, 28 Mar 2009 15:38:40 -0700 Subject: dbus and launchd spinning out of control In-Reply-To: References: Message-ID: I'm not sure if there is a specific ticket on this already, but maybe this one comes close: http://trac.macports.org/ticket/18462 On my system, I have the following LaunchDeamon and LaunchAgent: [ dweber at XXX ~ ]$ cat /Library/LaunchDaemons/org.macports.dbus.plist Debug Label org.macports.dbus OnDemand ProgramArguments /opt/local/bin/daemondo --label=dbus --start-cmd /opt/local/bin/dbus-daemon --system --nofork ; --pid=exec RunAtLoad [ dweber at XXX ~ ]$ cat /Library/LaunchAgents/org.freedesktop.dbus-session.plist Label org.freedesktop.dbus-session ServiceIPC OnDemand ProgramArguments /opt/local/bin/dbus-daemon --nofork --session Sockets unix_domain_listener SecureSocketWithKey DBUS_LAUNCHD_SESSION_BUS_SOCKET On Sat, Mar 28, 2009 at 3:20 PM, Darren Weber wrote: > > I've only just noticed my Utilities -> Console log and it contains streams > of the following messages: > > 3/28/09 3:11:03 PM org.macports.dbus[20573] Failed to start message bus: > The pid file "/opt/local/var/run/dbus/pid" exists, if the message bus is not > running, remove this file > 3/28/09 3:11:03 PM com.apple.launchd[1] (org.macports.dbus) Throttling > respawn: Will start in 10 seconds > 3/28/09 3:11:03 PM com.apple.launchd[1] (org.macports.dbus) Throttling > respawn: Will start in 10 seconds > 3/28/09 3:11:13 PM org.macports.dbus[20575] Failed to start message bus: > The pid file "/opt/local/var/run/dbus/pid" exists, if the message bus is not > running, remove this file > 3/28/09 3:11:13 PM com.apple.launchd[1] (org.macports.dbus) Throttling > respawn: Will start in 10 seconds > 3/28/09 3:11:13 PM com.apple.launchd[1] (org.macports.dbus) Throttling > respawn: Will start in 10 seconds > 3/28/09 3:11:23 PM org.macports.dbus[20579] Failed to start message bus: > The pid file "/opt/local/var/run/dbus/pid" exists, if the message bus is not > running, remove this file > 3/28/09 3:11:23 PM com.apple.launchd[1] (org.macports.dbus) Throttling > respawn: Will start in 10 seconds > 3/28/09 3:11:23 PM com.apple.launchd[1] (org.macports.dbus) Throttling > respawn: Will start in 10 seconds > 3/28/09 3:11:33 PM org.macports.dbus[20583] Failed to start message bus: > The pid file "/opt/local/var/run/dbus/pid" exists, if the message bus is not > running, remove this file > 3/28/09 3:11:33 PM com.apple.launchd[1] (org.macports.dbus) Throttling > respawn: Will start in 10 seconds > > > So every 10 sec, launchd is trying to get dbus up and running, but it fails > because an old pid file is hanging around. Can this be resolved > automatically? When I check the file, I get: > > [ dweber at XXXX ~ ]$ ls -l /opt/local/var/run/dbus/pid > -rw-r--r-- 1 root messagebus 4 2008-09-19 21:05 /opt/local/var/run/dbus/pid > > > Given the date of this pid file (Sep 2008), I can only assume that this > entire process has been repeated every 10 seconds for months, whenever my > laptop system is running. I've now removed the old pid file and the launchd > job has finally come to rest. > > I'm not a frequent checker of system logs, I just use the system and I > guess most people are also unlikely to check the system logs (console). I'm > curious about why this situation arose and, moreover, why it was not > automatically resolved (it clearly required my intervention to remove the > old pid file). > > Take care, Darren > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mcalhoun at macports.org Sat Mar 28 15:44:16 2009 From: mcalhoun at macports.org (Marcus Calhoun-Lopez) Date: Sat, 28 Mar 2009 22:44:16 +0000 (UTC) Subject: dbus and launchd spinning out of control References: Message-ID: Darren Weber macports.org> writes: >Can this be resolved automatically?? >/opt/local/var/run/dbus/pidGiven the date of this pid file (Sep 2008), >I can only assume that this entire >process has been repeated every 10 seconds for months, >whenever my laptop system is running.? I've now >removed the old pid file and the launchd job has finally come to rest. This is related to ticket #15081 (http://trac.macports.org/ticket/15081). Your machine at some point probably suffered a forced reboot. Since dbus does not need the nice features of MacPorts startup (start, stop, restart, etc.), I am currently trying to bypass it in favor of a simpler solution. This should solve your problem. As soon as I make more progress, I will post the relevant information in #15081. -Marcus From jason.macdonald1 at gmail.com Sat Mar 28 16:45:19 2009 From: jason.macdonald1 at gmail.com (Jason MacDonald) Date: Sat, 28 Mar 2009 20:45:19 -0300 Subject: XMGrace Error Message-ID: <38e57f500903281645o2ea748e8tcc3ff38e93254e5a@mail.gmail.com> Hi I installed the grace port but get this error when I try to run the program. xmgrace Warning: Widget must be a VendorShell. Error: attempt to add non-widget child "dsm" to parent "xmgrace" which supports only widgets ProductName: Mac OS X ProductVersion: 10.5.6 BuildVersion: 9G55 Darwin jason-macdonalds-macbook.local 9.6.0 Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008; root:xnu-1228.9.59~1/RELEASE_I386 i386 also on the same system having issues with gnuplot ---> Verifying checksum(s) for db46 Error: Checksum (md5) mismatch for patch.4.6.21.3 Error: Target org.macports.checksum returned: Unable to verify file checksums Error: The following dependencies failed to build: gd2 xorg-libs xorg-libxcb xorg-xcb-proto python26 db46 gdbm openssl readline sqlite3 tk tcl xorg-libxkbfile xorg-libxkbui xorg-xcb-util Error: Status 1 encountered during processing. any help greatly appreciated. Thanks -- Jason MacDonald -------------- next part -------------- An HTML attachment was scrubbed... URL: