From owner-freebsd-questions@FreeBSD.ORG Mon Jun 11 19:00:13 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 163C016A474 for ; Mon, 11 Jun 2007 19:00:13 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id F1BF813C4BF for ; Mon, 11 Jun 2007 19:00:12 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 0F69A1A4D84 for ; Mon, 11 Jun 2007 11:59:57 -0700 (PDT) Received: from rot13.obsecurity.org (rot13.obsecurity.org [192.168.1.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id 4C06651455 for ; Mon, 11 Jun 2007 15:00:12 -0400 (EDT) Received: by rot13.obsecurity.org (Postfix, from userid 1001) id 2406CBE79; Mon, 11 Jun 2007 15:00:12 -0400 (EDT) Date: Mon, 11 Jun 2007 15:00:12 -0400 From: Kris Kennaway To: freebsd-questions@freebsd.org Message-ID: <20070611190012.GA948@rot13.obsecurity.org> References: <20070607130509.GA4004@gronau-ws> <444plefjfk.fsf@be-well.ilk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <444plefjfk.fsf@be-well.ilk.org> User-Agent: Mutt/1.4.2.3i Subject: Re: some ports want to compile with icc X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2007 19:00:13 -0000 On Mon, Jun 11, 2007 at 02:13:51PM -0400, Lowell Gilbert wrote: > mein name writes: > > > Some ports (e.g. clamav or lighttpd) want to compile with the icc, even if I don't select > > it in my make.conf or somewhere else. I tried to set the gcc as > > default compiler with CC=gcc but this doesn't change anything. If > > I deinstall the icc I get an error while compiling clamav like this: > > > > > > icc: not found > > *** Error code 127 > > > > Stop in /usr/ports/security/clamav/work/clamav-0.90.3/libclamav. > > *** Error code 1 > > > > Stop in /usr/ports/security/clamav/work/clamav-0.90.3. > > *** Error code 1 > > > > Stop in /usr/ports/security/clamav/work/clamav-0.90.3. > > *** Error code 1 > > > > Stop in /usr/ports/security/clamav. > > *** Error code 1 > > > > Stop in /usr/ports/security/clamav. > > ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portinstall.53682.0 env make > > ** Fix the problem and try again. > > ** Listing the failed packages (*:skipped / !:failed) > > ! security/clamav (new compiler error) > > ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed > > > > > > > > Any suggestions? > > It does not do this for me, and I cannot guess what could make it do > so. Perhaps there is more information in the upgrade transcript, > before the error? Are you sure you don't have something set in make.conf? I can confirm that clamav does NOT look for icc if it is not installed on the system. Perhaps it does detect it and try to use it automatically if it is present when 'make configure' runs. You will need to provide the config.log file to the clamav port maintainer for them to look into the problem. Kris