Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hi Peter,

On Sat, Apr 30, 2011 at 8:31 PM, Peter Teeson <peter.teeson@bell.net> wrote:

You were kind enough to encourage me previously to track down a bug.
Since then I have installed the Mac dependencies, git, and the sources.
Now I am trying to get to the point of doing a build but have hit a wall
because ./autogen failed.
I've googled "Can't locate Archive/Zip.pm in ..." and there are several
hits.

You got a dirty environments with stuff from macports/fink or manual
installation of stuff.

Also I sent a descriptive post to the list, but so far no one has
responded with guidance.

Don't remember such a mail, but might be I missed it because of other stuff.

checking for required Perl modules... Can't locate Archive/Zip.pm in @INC
(@INC contains: /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
/opt/local/lib/perl5/5.8.9/darwin-2level /opt/local/lib/perl5/5.8.9 .) at -e
line 1.

See - neither Mac OS X nor Xcode install stuff in /opt/local - so
whatever third-party stuff you did install it is messing with the
environment stuff.

Examine your login-startup files (~/.bashrc or ~/.profile and similar)
and get rid of any macports or fink or darwinports stuff.

ciao
Christian

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.