[MacPorts] #26320: ikiwiki gives 'Bus Error' with perl5.8

MacPorts noreply at macports.org
Fri Sep 17 05:38:13 PDT 2010


#26320: ikiwiki gives 'Bus Error' with perl5.8
--------------------------------+-------------------------------------------
  Reporter:  geychaner@…        |       Owner:  tommyd@…           
      Type:  defect             |      Status:  reopened           
  Priority:  Normal             |   Milestone:                     
 Component:  ports              |     Version:  1.9.1              
Resolution:                     |    Keywords:                     
      Port:  ikiwiki            |  
--------------------------------+-------------------------------------------

Comment(by geychaner@…):

 Replying to [comment:16 tommyd@…]:
 > Replying to [comment:15 geychaner@…]:
 > > Would overriding perl5.bin in the portfile fix this problem?
 >
 > [...] overwriting configure.cmd which had the incorrect perl5 binary.
 Then of course the ikiwiki files would land in the correct perl version -
 if the installation itself would go through even! Again, the problem are
 missing packages there.

 Ok, so we have a fix for one of the two problems; modifying the portfile
 will allow ikiwiki to go to the right place.  Take that code I stuck in
 post-patch and stick it in pre-configure, and have it set "configure.bin".
 I still think the "modules not in @INC" problem is really a perl problem,
 not an ikiwiki problem.

 > > I'd do it, but I've already spent more time with it than I
 should...I'm in Chile on a 2MB/s connection, so every uninstall/reinstall
 test cycle takes me hours.
 >
 > Right, while I have a slightly better connection, I am still used to
 trigger all my install tasks with the infamous `-n` option... also because
 I'm still on an early core 2 duo and not on one of these fancy i5 / i7
 machines.

 Got you beat there; mine is an original Core Duo.

 > > I think it should be thrown right back at the perl5 port owners.  It
 really, '''really''' shouldn't be this hard.  Really.
 >
 > Right, that is what I am thinking of as well. I had a similar nightmare
 for a python-based ports where the situation with all the different
 py24-*, py25-* and py26-* ports is even worse. It would all be much, much
 easier if people like me wouldn't fear upgrading so much and we could just
 use binary packages.

 I agree; Python is just as bad.  I have 3 pythons on my system: the Mac OS
 X default, the one Scisoft installed in /Applications/scisoft, and the one
 Plone (or maybe Trac) installed somewhere in /usr/local (but not
 /usr/local/bin).  Which one you get depends on your $PATH, and they each
 have a different module subset installed.

-- 
Ticket URL: <https://trac.macports.org/ticket/26320#comment:17>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list