From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 18:41:42 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D68C1065674 for ; Fri, 21 Jan 2011 18:41:42 +0000 (UTC) (envelope-from alexkozlov0@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id D3EFB8FC21 for ; Fri, 21 Jan 2011 18:41:41 +0000 (UTC) Received: by fxm16 with SMTP id 16so2178989fxm.13 for ; Fri, 21 Jan 2011 10:41:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:date:from:to:subject:message-id :mime-version:content-type:content-disposition; bh=SmGfwF317kSsxNdJgfJZnZYPSz+I3WECLVzuXdtmefA=; b=w1UuQT0J8cCuHOBR5mNGmbwY9XtdUYJyAn3hhcBrcSBXeuXVm3nAP/lUintykjeXnc N8vNA5DVgXc2Hkk1XUHaQdz1ybFae3mkIouJy6KNx6lRcLmQHh+JkrCPVyNYQkIo1bVW p+o3O7jsy1Qf2mejEpn0Kfh0e7hgUk+Z+sfLA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:date:from:to:subject:message-id:mime-version:content-type :content-disposition; b=lRkEAf1rUsjKcTAdDbPHeQGPlJ13A09mMlkSKemePI4kbbYhE7Wg5TVlDTFUIqzMIp wYu+yelEvxTV6n/cOjfp20pbyYaU6VR7zDccL/sdbAwmFibTfoOAo6RL2iCZhVFlrHvJ 2M1ofvXcglT30MTVFjmYMMFfQWxLb2b8tZaMo= Received: by 10.223.73.202 with SMTP id r10mr952560faj.133.1295633527449; Fri, 21 Jan 2011 10:12:07 -0800 (PST) Received: from ravenloft.kiev.ua (ravenloft.kiev.ua [94.244.131.95]) by mx.google.com with ESMTPS id c11sm3716459fav.2.2011.01.21.10.12.04 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 21 Jan 2011 10:12:05 -0800 (PST) Sender: Alex Kozlov Date: Fri, 21 Jan 2011 20:11:32 +0200 From: Alex Kozlov To: Alexander Shikoff , current@FreeBSD.org, spam@rm-rf.kiev.ua Message-ID: <20110121181132.GA16527@ravenloft.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Cc: Subject: Re: "broken pipe" error during building of port X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2011 18:41:42 -0000 On Fri, Jan 21, 2011 at 07:24:48PM +0200, Alexander Shikoff wrote: > Yesterday I got latest sources of -CURRENT and upgraded my installation. > Now when I build any port "broken pipe" error message appear: > > /usr/ports/mail/mutt-devel>make > ===> Vulnerability check disabled, database not found > ===> License check disabled, port has not defined LICENSE > ===> Found saved configuration for mutt-devel-1.5.21 > ===> Extracting for mutt-devel-1.5.21 > => SHA256 Checksum OK for mutt/mutt-1.5.21.tar.gz. > => SHA256 Checksum OK for mutt/patch-1.5.21.rr.compressed.gz. > => SHA256 Checksum OK for mutt/patch-1.5.21.vvv.initials.gz. > => SHA256 Checksum OK for mutt/patch-1.5.21.vvv.quote.gz. > ===> Patching for mutt-devel-1.5.21 > ===> Applying distribution patches for mutt-devel-1.5.21 > ===> Applying FreeBSD patches for mutt-devel-1.5.21 > I can't seem to find a patch in there anywhere. > ===> mutt-devel-1.5.21 depends on file: /usr/local/bin/automake-1.11 - found > ===> mutt-devel-1.5.21 depends on file: /usr/local/bin/autoconf-2.68 - found > ===> mutt-devel-1.5.21 depends on shared library: iconv.3grep: writing output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > grep: writing output: Broken pipe > [...] > > Also error sometimes appears after executing "man something": > > /home/minotaur>man muttrc > zcat: error writing to output: Broken pipe > zcat: /usr/local/man/man5/muttrc.5.gz: uncompress failed > > I found thread from stable@ mailing list > http://www.mail-archive.com/freebsd-stable@freebsd.org/msg111266.html > with same error on 8.1-RC2. The solution there is to get 'sh' sources > from previous release. I'm not sure whether it will help in my case. Nope, old sh is only masked the issue. Problem was in sudo signal(SIGPIPE) handling: http://www.mail-archive.com/freebsd-stable@freebsd.org/msg111494.html > Any way to solve the issue? Thanks in advance! -- Adios