Opened 10 years ago
Closed 10 years ago
#44648 closed defect (fixed)
p5.8-perlmagick: fails to build on 10.7
Reported by: | mojca (Mojca Miklavec) | Owned by: | ryandesign (Ryan Carsten Schmidt) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | lion | Cc: | astricker@… |
Port: | p5.8-perlmagick |
Description
make[1]: Entering directory `/opt/local/var/macports/build/_opt_mports_dports_perl_p5-perlmagick/p5.8-perlmagick/work/ImageMagick-6.8.9-1/PerlMagick/default' chmod 644 Magick.bs cp Magick.bs blib/arch/auto/Image/Magick/Magick.bs chmod 644 blib/arch/auto/Image/Magick/Magick.bs AutoSplit: Can't open ../blib/lib/Image/Magick.pm: No such file or directory cp Magick.pm ../blib/lib/Image/Magick.pm make[1]: *** [pm_to_blib] Error 2 make[1]: Leaving directory `/opt/local/var/macports/build/_opt_mports_dports_perl_p5-perlmagick/p5.8-perlmagick/work/ImageMagick-6.8.9-1/PerlMagick/default' make: *** [subdirs] Error 2 make: *** Waiting for unfinished jobs.... cp Magick.pm blib/lib/Image/Magick.pm AutoSplitting blib/lib/Image/Magick.pm (blib/lib/auto/Image/Magick) make: Leaving directory `/opt/local/var/macports/build/_opt_mports_dports_perl_p5-perlmagick/p5.8-perlmagick/work/ImageMagick-6.8.9-1/PerlMagick'
It might make sense to simply remove support for 5.8.
See also comment:12:ticket:43480.
Change History (2)
comment:1 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
comment:2 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Disabled parallel build in r123830. The buildslave said "package found, not building again" so a previous rebuild must have already succeeded. Still, it could be a parallel build failure that is only reached by chance, and since the port doesn't take that long to build, disabling parallel building isn't awful.
Note: See
TracTickets for help on using
tickets.
I am not able to reproduce this issue on Lion with p5.8-perlmagick. It doesn't sound like a Lion- or perl5.8-specific problem to me, but rather like an intermittent parallel build failure.