RE: ActivePerl on OS X: ppm not working, no DBD::mysql PPM available
"Jan Dubois" <[email protected]> Thu, 4 Oct 2012 12:44:15 -0700
| Newsgroups | gmane.comp.lang.perl.active-perl |
|---|---|
| Organization | ActiveState Software Inc |
| Message-ID | <[email protected]> |
This is a multipart message in MIME format. --===============0414984009== Content-Type: multipart/alternative; boundary="----=_NextPart_000_06C9_01CDA22D.F6435BD0" Content-Language: en-us This is a multipart message in MIME format. ------=_NextPart_000_06C9_01CDA22D.F6435BD0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Michiel, =20 Yes, we will probably switch to 64-bit-only builds on OS X for Perl 5.18 = next year. Switching the 5.16 builds right now will require setting up = yet another PPM repo and build system, and will also not work well with = the PPM Index pages. =20 As for the GUI crash, I heard back from QA that this issue only happens = on OS X 10.8 systems that have been upgraded from an earlier version of = OS X, and not on fresh installs of Mountain Lion. That way it slipped = through the release testing. =20 Cheers, -Jan =20 From: Michiel Beijen [mailto:[email protected]]=20 Sent: Thursday, October 04, 2012 12:23 PM To: Jan Dubois Cc: [email protected] Subject: Re: ActivePerl on OS X: ppm not working, no DBD::mysql PPM = available =20 Hi Jan, On Thu, Oct 4, 2012 at 8:42 PM, Jan Dubois <[email protected]> wrote: I needed this myself before too, but the problem is that ActivePerl is a "fat" binary (contains executable code for both the 32-bit and 64-bit version in the same files). That means any modules must be built the same way, and there is no corresponding MySQL library in the same = format. Maybe we should try to build a module manually just for 64-bit mode, but it will still require some manual effort to get this into the PPM setup. Of course I can not make decisions for ActiveState, but would it not = make sense to build 64-bit only versions? OS X has been 64-bit only = since Lion, which is about a year and a half now. I have no clue, but it = *might* be easier to build 64-bit only than to try to fix the current = 'fat' binaries to use 64-bit only builds in some cases. -- Mike ------=_NextPart_000_06C9_01CDA22D.F6435BD0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" = xmlns:o=3D"urn:schemas-microsoft-com:office:office" = xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" = xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta = http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta = name=3DGenerator content=3D"Microsoft Word 14 (filtered = medium)"><style><!-- /* Font Definitions */ @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman","serif";} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:purple; text-decoration:underline;} span.EmailStyle17 {mso-style-type:personal-reply; font-family:"Calibri","sans-serif"; color:#1F497D;} .MsoChpDefault {mso-style-type:export-only; font-family:"Calibri","sans-serif";} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.WordSection1 {page:WordSection1;} --></style><!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue = vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'>Hi Michiel,<o:p></o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'><o:p> </o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'>Yes, we will probably switch to 64-bit-only builds on OS X for Perl = 5.18 next year. Switching the 5.16 builds right now will require setting = up yet another PPM repo and build system, and will also not work well = with the PPM Index pages.<o:p></o:p></span></p><p = class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'><o:p> </o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'>As for the GUI crash, I heard back from QA that this issue only = happens on OS X 10.8 systems that have been upgraded from an earlier = version of OS X, and not on fresh installs of Mountain Lion. That way it = slipped through the release testing.<o:p></o:p></span></p><p = class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'><o:p> </o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'>Cheers,<o:p></o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'>-Jan<o:p></o:p></span></p><p class=3DMsoNormal><span = style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497= D'><o:p> </o:p></span></p><div = style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in = 4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF = 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span = style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>= </b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> = Michiel Beijen [mailto:[email protected]] <br><b>Sent:</b> = Thursday, October 04, 2012 12:23 PM<br><b>To:</b> Jan = Dubois<br><b>Cc:</b> = [email protected]<br><b>Subject:</b> Re: ActivePerl on = OS X: ppm not working, no DBD::mysql PPM = available<o:p></o:p></span></p></div></div><p = class=3DMsoNormal><o:p> </o:p></p><p class=3DMsoNormal = style=3D'margin-bottom:12.0pt'>Hi Jan,<o:p></o:p></p><div><p = class=3DMsoNormal>On Thu, Oct 4, 2012 at 8:42 PM, Jan Dubois <<a = href=3D"mailto:[email protected]" = target=3D"_blank">[email protected]</a>> wrote:<o:p></o:p></p><p = class=3DMsoNormal>I needed this myself before too, but the problem is = that ActivePerl is<br>a "fat" binary (contains executable code = for both the 32-bit and 64-bit<br>version in the same files). That = means any modules must be built the<br>same way, and there is no = corresponding MySQL library in the same format.<br><br>Maybe we should = try to build a module manually just for 64-bit mode, but<br>it will = still require some manual effort to get this into the PPM = setup.<o:p></o:p></p><div><p class=3DMsoNormal><br>Of course I can not = make decisions for ActiveState, but would it not make sense to build = 64-bit only versions? OS X has been 64-bit only since Lion, which is = about a year and a half now. I have no clue, but it *might* be easier to = build 64-bit only than to try to fix the current 'fat' binaries to use = 64-bit only builds in some = cases.<br>--<br>Mike<o:p></o:p></p></div></div></div></div></body></html> ------=_NextPart_000_06C9_01CDA22D.F6435BD0-- --===============0414984009== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ActivePerl mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs --===============0414984009==--