From owner-freebsd-ports@FreeBSD.ORG Mon Apr 21 22:07:26 2014 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6BCCD7DB; Mon, 21 Apr 2014 22:07:26 +0000 (UTC) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E3BD71D13; Mon, 21 Apr 2014 22:07:25 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.8/8.14.8) with ESMTP id s3LM7J7l031924; Tue, 22 Apr 2014 01:07:19 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.8.3 kib.kiev.ua s3LM7J7l031924 Received: (from kostik@localhost) by tom.home (8.14.8/8.14.8/Submit) id s3LM7Jki031923; Tue, 22 Apr 2014 01:07:19 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 22 Apr 2014 01:07:19 +0300 From: Konstantin Belousov To: Emanuel Haupt Subject: Re: bash usage of fdescfs [was: Re: amd64/188699: Dev tree] Message-ID: <20140421220718.GU4016@kib.kiev.ua> References: <201404171850.s3HIo1am064874@freefall.freebsd.org> <201404211431.12922.jhb@freebsd.org> <20140421195133.GO4016@kib.kiev.ua> <5355933B.4030804@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="e4annfiqlsPm5rKd" Content-Disposition: inline In-Reply-To: <5355933B.4030804@FreeBSD.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tom.home Cc: ports@freebsd.org, freebsd-amd64@freebsd.org, John Baldwin X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Apr 2014 22:07:26 -0000 --e4annfiqlsPm5rKd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 21, 2014 at 11:52:59PM +0200, Emanuel Haupt wrote: > On 21/04/14 21:51, Konstantin Belousov wrote: > > On Mon, Apr 21, 2014 at 02:31:12PM -0400, John Baldwin wrote: > >> On Thursday, April 17, 2014 2:50:01 pm Konstantin Belousov wrote: > >>> The following reply was made to PR amd64/188699; it has been noted by= GNATS. > >>> > >>> From: Konstantin Belousov > >>> To: John Allman > >>> Cc: freebsd-gnats-submit@FreeBSD.org > >>> Subject: Re: amd64/188699: Dev tree > >>> Date: Thu, 17 Apr 2014 21:44:52 +0300 > >>> > >>> On Wed, Apr 16, 2014 at 05:32:45PM +0000, John Allman wrote: > >>> > This is how to reproduce it: > >>> > > >>> > Fresh install of 10 on AMD 64 > >>> > install bash `pkg install bash` > >>> > Switch to bash `bash` > >>> > push a here document into a loop: `while true ; do echo; done< <(= echo "123")` > >>> > receive an error: "-su: /dev/fd/62: No such file or directory" > >>> > > >>> > I'm sorry I haven't been able to research this any further. I fou= nd how while working on some important matters. As I mentioned the above wo= rks fine in all > >> previous versions of FreeBSD up until 10. > >>> > >How-To-Repeat: > >>> > Fresh install > >>> > pkg install bash > >>> > bash > >>> > while true; do echo foo done< <(echo "123") > >>> > > >>> > -su: /dev/fd/62: No such file or directory > >>> > >>> So do you have fdescfs mounted on /dev/fd on the machine where the > >>> test fails ? It works for me on head, and if unmounted, I get the > >>> same failure message as yours. I very much doubt that it has anyth= ing > >>> to do with a system version. > >> > >> Question I have is why is bash deciding to use /dev/fd/ and require > >> fdescfs? On older releases bash uses named pipes for this instead. > > > > The aclocal.m4 contains the test which verifies the presence and usabil= ity > > of /dev/fd/n for n>=3D3 on the _build_ host. The result of the test > > is used on the installation host afterward. > > > > Such kinds of bugs are endemic in our ports, but apparently upstreams > > are guilty too. >=20 > Is there anything I can do to patch the bash port? I am more than happy= =20 > to implement a fix and contact upstream about the problem. Ideally, upstream should test the presence of fdescfs mount at runtime, instead of the compile time. They already have unused have_devfd variable. The port could add the pkg installation message which would mention the need of the mount, like it is done by openjdk ports currently. --e4annfiqlsPm5rKd Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBAgAGBQJTVZaWAAoJEJDCuSvBvK1BhF4P/0u6jQUA82J+nRAcpq+ghKDJ i5nV/VKBwOP7l2gXiHvpLOrW9KHwZxucnkm3f6uHR+w8495x2hRBLyUQt8IHWFFG tZzmHNTjrdTTWi5+G3zmcTZI+liwAnXsBbydHEEUk9uxg0SmwgNJM5w+9u83zDVQ GewHUzKzLugZypqWMRz63rkwvaeVc0jW2Zy7F7lI+i4rYHPTTng0BFC8kSkY2QxH Z1gS1Dk5mykOUdoh/MAEePxDHcrm4YJVGWu4SmMformOnCzQOUux7gTSDviC9wPk wlp2YgIiHHE7viEavO41NF/XUojj0FW1ybkw++7nBG0aQ9G6MwJH70YiX7fG/xoE KKr2QIbcTRrE9TtQe9zA74REAbk5YGq/FqL4iFKk4BewGlGGpAWaaYa3Rs7L6V6W TCdKuMhv3r/SS3zyppjHYDsSZPkn6YxToHq5orLvofRO8wgmGwwHu3Ob2jk+QOa/ IAwdSu3ubiniaZCYWCwD/kAPRdzGlZVjycKY5PHlaJh7fJjLC5+DQnSluJh17lzD fK2UtcwQP/8TzIbib6MFugmDXzVA4vJQziQ6v7A5YLUg+ppGennyBGrcfkXWmwTk jkcx+d+NiMjthDvcxITaBcV6svgoml+d9JjMr/ZEAqMwZQv2p1QC+4vLAHOd3a3z ycijHkizPqGqa7t6Qvrd =KceN -----END PGP SIGNATURE----- --e4annfiqlsPm5rKd--