From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10792 invoked by alias); 22 Jan 2015 08:49:29 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 34340 Received: (qmail 11996 invoked from network); 22 Jan 2015 08:49:26 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=xPQBIdA8rnHMoXOKWCtxUQs8M2vV2OB0ueFHicQJuDQ=; b=WK1KBgh/+bK5/6J9aSeRIitSBuz3pbPVXel/MP76oPtJMYxlIXmvkWJYPfmYKmdppK vdrLVwDzNSY9J6HTOOi2Sj98/ZFQF1tGhNvYWEzfj5VMcecqyGB5+gWHnB29ijbqsFD4 h/tZFI9eGzUrD0ZU05IJnNB+sQ55KtxLnfFJVk22eVy0ES23j26kDnPufE+HnSoWgBDZ A+DuhqtdfqIHwehBmd2YC2Ljb4sGMDeNJjNVXhiG/kbPfynUOMhyNuSuVz0gmKDRiUig qmeZKf4/9oMQ+O8LOVteGYGfu/nYHJyj/wcSbjXgrW8eZCWMkn3SkI4758ppKuSSNljQ a2yw== X-Gm-Message-State: ALoCoQkcUBHAn8bcI/OyKalgi3ZI27GssRgtwT/0zYW5KaMF+QYH5LXp0xMUMLSx8G2oan5j/HEL MIME-Version: 1.0 X-Received: by 10.152.7.180 with SMTP id k20mr371729laa.4.1421916560909; Thu, 22 Jan 2015 00:49:20 -0800 (PST) X-Originating-IP: [80.239.194.50] In-Reply-To: <54C045A8.10102@eastlink.ca> References: <54B9AA99.6080403@eastlink.ca> <150116185732.ZM30791@torch.brasslantern.com> <54B9D726.2020108@eastlink.ca> <20150119102910.18102a0b@pwslap01u.europe.root.pri> <54C045A8.10102@eastlink.ca> Date: Thu, 22 Jan 2015 08:49:20 +0000 Message-ID: Subject: Re: make check problem From: Peter Stephenson To: zsh workers Content-Type: multipart/alternative; boundary=001a11c217d2837a0a050d39bfe2 --001a11c217d2837a0a050d39bfe2 Content-Type: text/plain; charset=UTF-8 On 22 January 2015 at 00:34, Ray Andrews wrote: > I'm getting this 'make check' problem: > > ./V07pcre.ztst: skipped (the zsh/pcre module is not available) > > All three 'pcre_*' functions exist in both: > > /usr/lib/i386-linux-gnu/libpcre.a > /usr/lib/i386-linux-gnu/libpcre.so > > ... so I'm wondering why they are not linked. > > This is under Debian testing. (On webmail, apologies if the format is a bit uncontrollable.) This is quite a common problem if your Linux setup isn't specifically installed for software development. The check needs to be able to perform a compilation, so it has to find the headers as well as the libraries. Those are typically in some additional package. You'll probably find you have a package "pcre" installed and need another one called "pcre-devel" or something similar. pws --001a11c217d2837a0a050d39bfe2--