DBD::mysql question
Hi. I’m trying to install p5.12-dbd-mysql but it starts to download MySQL 5 with a view, I should imagine, to install that first. Seeing as I’ve rolled my own MySQL what’s the syntax to port install p5.12-dbd-mysql without MySQL? Is it sudo port install p5.12-dbd-mysql -mysql5? Any help appreciated, Cheers, Phil. -- Please consider the environment before reading this email... ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: DBD::mysql question
On Oct 29, 2011, at 05:50, Phil Dobbin wrote: Seeing as I’ve rolled my own MySQL what’s the syntax to port install p5.12-dbd-mysql without MySQL? Is it sudo port install p5.12-dbd-mysql -mysql5? As far as I know, DBD::MySQL requires the MySQL libraries, and MacPorts won't use the MySQL you compiled yourself. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: DBD::mysql question
On Oct 29, 2011, at 5:50 AM, Phil Dobbin wrote: Hi. I’m trying to install p5.12-dbd-mysql but it starts to download MySQL 5 with a view, I should imagine, to install that first. Seeing as I’ve rolled my own MySQL what’s the syntax to port install p5.12-dbd-mysql without MySQL? Is it sudo port install p5.12-dbd-mysql -mysql5? I could be wrong, but I think if a port depends on another port (as described in its portfile), you are kinda out of luck --- the dependency will get installed. That is why I have a couple of three different perls now on my computer, and a few other superfluous software packages. Instead, for the most part, when it comes to perl modules, just install them using cpan or cpanminus (I prefer cpanminus). As long as your macport preferred perl is the default perl in the path, your requested module will get installed correctly. -- Puneet Kishor ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Lots and lots of system time
Please pardon me if this is off topic, but it is about a phenomenon I only see when macports is compiling software: So I'd like to hear if other macports users are seeing the same: Namely, that the majority of CPU time while compiling is system time, not user time. Right now, for example, I am compiling gimp2, and top says CPU usage: 10.34% user, 86.20% sys, 3.44% idle It did not use to be this way. Unfortunately, several things got upgraded about the same time, so I am not certain which one to blame: The OS to Lion, and XCode and macports itself. Does anyone else see this? Can you come up with a possible explanation off the top of your head? I thought it might be possible to play around with dtrace to find out what system calls are sucking up all the time, but my dtrace-foo is rather limited. The system is a 13 inch MacBook Pro with SSD, not a HD. I have full-disk encryption enabled, but I am pretty sure this started before I turned it on. - Harald ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: DBD::mysql question
On 29/10/11 at 14:03, ryandes...@macports.org (Ryan Schmidt) wrote: On Oct 29, 2011, at 05:50, Phil Dobbin wrote: Seeing as I’ve rolled my own MySQL what’s the syntax to port install p5.12-dbd-mysql without MySQL? Is it sudo port install p5.12-dbd-mysql -mysql5? As far as I know, DBD::MySQL requires the MySQL libraries, and MacPorts won't use the MySQL you compiled yourself. I just wondered because DBI installed fine from MacPorts. But looking back at the copy of my install of DBD::mysql I had to explicity add flags for perl to find the MySQL libs includes at compile time (this with perl 5.14 DBD::mysql in usr/local/) so maybe not... Cheers, Phil. -- Please consider the environment before reading this email... ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Lots and lots of system time
Hi, I noticed that too and I think this started with xcode 4.0. Dom Am 29.10.2011 um 16:54 schrieb Harald Hanche-Olsen han...@math.ntnu.no: Please pardon me if this is off topic, but it is about a phenomenon I only see when macports is compiling software: So I'd like to hear if other macports users are seeing the same: Namely, that the majority of CPU time while compiling is system time, not user time. Right now, for example, I am compiling gimp2, and top says CPU usage: 10.34% user, 86.20% sys, 3.44% idle It did not use to be this way. Unfortunately, several things got upgraded about the same time, so I am not certain which one to blame: The OS to Lion, and XCode and macports itself. Does anyone else see this? Can you come up with a possible explanation off the top of your head? I thought it might be possible to play around with dtrace to find out what system calls are sucking up all the time, but my dtrace-foo is rather limited. The system is a 13 inch MacBook Pro with SSD, not a HD. I have full-disk encryption enabled, but I am pretty sure this started before I turned it on. - Harald ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: DBD::mysql question
On 29/10/11 at 14:11, punk.k...@gmail.com (Mr. Puneet Kishor) wrote: [snip] Instead, for the most part, when it comes to perl modules, just install them using cpan or cpanminus (I prefer cpanminus). As long as your macport preferred perl is the default perl in the path, your requested module will get installed correctly. Hi, Puneet. I think I’ll have to stick with version of DBD::mysql I installed in /usr/local/ as I don’t really want to link to MySQL libs includes that are not in /opt/local/ Cheers, Phil. -- Please consider the environment before reading this email... ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Lots and lots of system time
On Oct 29, 2011, at 10:54 AM, Harald Hanche-Olsen wrote: Please pardon me if this is off topic, but it is about a phenomenon I only see when macports is compiling software: So I'd like to hear if other macports users are seeing the same: Namely, that the majority of CPU time while compiling is system time, not user time. Right now, for example, I am compiling gimp2, and top says CPU usage: 10.34% user, 86.20% sys, 3.44% idle It did not use to be this way. Unfortunately, several things got upgraded about the same time, so I am not certain which one to blame: The OS to Lion, and XCode and macports itself. Does anyone else see this? Can you come up with a possible explanation off the top of your head? I thought it might be possible to play around with dtrace to find out what system calls are sucking up all the time, but my dtrace-foo is rather limited. The system is a 13 inch MacBook Pro with SSD, not a HD. I have full-disk encryption enabled, but I am pretty sure this started before I turned it on. I have not noticed this particular situation, however based on experiences with OSF from years ago, I know that what is considered System time vs User time is in reality quite different than what most expect it to be… and easily changed. Since you indicate that you have an SSD, my immediate assumption goes to What does an SSD look like to the OS? I do not know the code, but I would guess that an SSD is NOT using the same code path which a disk uses, but rather that which memory uses. Or put another way, all of the structures which process I/O for a rotating disk have timings in them which are not relevant to an SSD, and which in fact would impede its performance. So I would assume that the SSD reads/writes are based on memory read/writes and are therefore read as part of System Time. Quite frankly, I would suspect that Apple's developers never even looked at the issue. For my 40+ yeas in the business ALL accounting is an add-on after thought. It is never designed in from the beginning, and the tools to process what little data is available are basically unchanged since Dennis Richie, et.al first wrote Unix. It is a sad state of affairs, but sadly true. T.T.F.N. William H. Magill # iMac11,3 Core i7 [2.936GHz - 4 GB 1333] OS X 10.7.2 # iMac6,1 Core 2 Duo [2.16GHz - 3 GB 667] OS X 10.6.8 # MacBook Pro4.1 Core 2 Duo [2.5GHz - 4GB 667] OS X 10.6.8 # Mac mini Core Duo [1.66 Ghz - 2 GB 667] OS X 10.6.8 # Flat-panel iMac (2.1) [800MHz - Super Drive - 768 Meg] OS X 10.4.11 # PWS433a [Alpha 21164 Rev 7.2 (EV56)- 64 Meg] Tru64 5.1a # XP1000 [Alpha 21264-3 (EV6) - 256 meg] FreeBSD 5.3 # XP1000 [Alpha 21264-A (EV6-7) - 256 meg] FreeBSD 5.3 mag...@mcgillsociety.org mag...@me.com whmag...@gmail.com ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: DBD::mysql question
On Oct 29, 2011, at 10:08, Phil Dobbin wrote: On 29/10/11 at 14:03, ryandes...@macports.org (Ryan Schmidt) wrote: On Oct 29, 2011, at 05:50, Phil Dobbin wrote: Seeing as I’ve rolled my own MySQL what’s the syntax to port install p5.12-dbd-mysql without MySQL? Is it sudo port install p5.12-dbd-mysql -mysql5? As far as I know, DBD::MySQL requires the MySQL libraries, and MacPorts won't use the MySQL you compiled yourself. I just wondered because DBI installed fine from MacPorts. But looking back at the copy of my install of DBD::mysql I had to explicity add flags for perl to find the MySQL libs includes at compile time (this with perl 5.14 DBD::mysql in usr/local/) so maybe not... DBI is the DataBase-Independent module; it doesn't depend on any database engine; DBD are the DataBase-Dependent modules; each of them depend on the libraries for their respective database engines. You write your abstract database-independent perl code to talk to DBI, which then talks to the appropriate DBD module to actually talk to the specific database you're using. Two questions for you... 1. Why did you compile your MySQL server yourself? Why not use the MacPorts mysql5-server port? 2. Even if you want to continue using your own hand-compiled MySQL server, that's not a problem. p5-dbd-mysql should happily talk to it. In order to do so, it will need its own copies of the MySQL libraries, as installed by the mysql5 port. So just let MacPorts install the mysql5 port for you, even if you don't plan to use it as your server. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: DBD::mysql question
On 29/10/11 at 01:22, ryandes...@macports.org (Ryan Schmidt) wrote: Two questions for you... 1. Why did you compile your MySQL server yourself? Why not use the MacPorts mysql5-server port? I’d originally downloaded installed the MySQL binary but that proved problematical as I’d used the 32-bit version the perl I’d installed in /usr/local/ (not wanting to mess with the system perl) was 64-bit therefore they wouldn’t play nice. At the time I hadn’t looked at MacPorts (wish I had) mainly because in years gone by I’d used Fink didn’t particularly enjoy the experience (YMMV). So I compiled MySQL 64-bit from source. However, when it came to apache2 I read up on MacPorts decided to try it. 2. Even if you want to continue using your own hand-compiled MySQL server, that's not a problem. p5-dbd-mysql should happily talk to it. In order to do so, it will need its own copies of the MySQL libraries, as installed by the mysql5 port. So just let MacPorts install the mysql5 port for you, even if you don't plan to use it as your server. I think that would be the ideal answer as I now have versions of apache2, PHP, PEAR perl from MacPorts I’m finding MacPorts a pleasure to use. Thanks for all the help, Ryan everybody else, Cheers, Phil. -- Please consider the environment before reading this email... ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: DBD::mysql question
On Oct 29, 2011, at 08:11, Mr. Puneet Kishor wrote: I could be wrong, but I think if a port depends on another port (as described in its portfile), you are kinda out of luck --- the dependency will get installed. That is why I have a couple of three different perls now on my computer, and a few other superfluous software packages. If MacPorts installed the ports for you, in response to a port you asked to have installed, then they're not superfluous. Having multiple perls installed is annoying, I agree. Most ports that use perl shouldn't care which perl you use. 5.12 is the version we're defaulting to now so that would probably be a safe version to use. Instead, for the most part, when it comes to perl modules, just install them using cpan or cpanminus (I prefer cpanminus). As long as your macport preferred perl is the default perl in the path, your requested module will get installed correctly. If you use MacPorts, you shouldn't use CPAN to install modules; they'll conflict with MacPorts ports of those modules. If ports don't exist for the modules you need, request them, or even create them yourself and submit them; the cpan2port script makes it pretty easy to create ports for perl modules. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Lots and lots of system time
On Oct 29, 2011, at 09:54, Harald Hanche-Olsen wrote: the majority of CPU time while compiling is system time, not user time. Right now, for example, I am compiling gimp2, and top says CPU usage: 10.34% user, 86.20% sys, 3.44% idle The system is a 13 inch MacBook Pro with SSD, not a HD. I have full-disk encryption enabled, but I am pretty sure this started before I turned it on. I have not used Lion or its new full-disk encryption feature but that seems to me like a likely candidate for something that would take system time to do. If you have another disk available without full disk encryption (an external hard drive or thumb drive maybe), you could compile a MacPorts installation on that drive and install some ports with it and see if it behaves differently. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
