From nobody Tue Aug 30 16:03:48 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4MHBtv04vhz4Zn81 for ; Tue, 30 Aug 2022 16:03:51 +0000 (UTC) (envelope-from garga@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4MHBtt6cVcz41vn; Tue, 30 Aug 2022 16:03:50 +0000 (UTC) (envelope-from garga@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1661875430; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=AhKUnQvxJE2PWCixaLPL3RKdZ1kKAekzjLOcQMZw/Ww=; b=sB+yLRKSME+wJMmok+WIAtZIhZMjZW8jYKs0VKsvPe5TreH7tEwLu8Tw2FCRX3I4saev41 xUE2b9TnmEbYr3zU0KsMTq3ykOmINmQQB4jyfJLeHm7m8ZZoDz7kn8OAcbBv6Xikm2N7gI FW3lJfW6Pj5NKBXJRqhUA7aVPQl93qjuuN5/sfelDXUH0zEcZxQuP+ghcnhmO5Qb0bQIJM XUSRVStjBW9VtP5zjJBzKKgY4+cP2cVsefKSbXSRMLX2vvCuR2dNo0BI3OQTxWR39mBqZe Sk+xNzc8CmRJcW2y0CI47wSu+NVaFpzJsk3dZMqjBSYNpmaJNP/laWuWCbaJIA== Received: from [172.21.4.170] (dynamic-177-53-82-16.telecominternet.net.br [177.53.82.16]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) (Authenticated sender: garga) by smtp.freebsd.org (Postfix) with ESMTPSA id 4MHBtt1pPfz1NYl; Tue, 30 Aug 2022 16:03:50 +0000 (UTC) (envelope-from garga@FreeBSD.org) Message-ID: Date: Tue, 30 Aug 2022 13:03:48 -0300 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.2.0 Subject: Re: archivers/arj fails to build on jail Content-Language: en-US From: Renato Botelho To: Jesper Schmitz Mouridsen , Current FreeBSD Cc: erdgeist@erdgeist.org References: <9636d41e-bf21-8130-ff15-e5dcbaaa4fe8@FreeBSD.org> <430844d1-ae2f-90d2-eec7-646c848e084f@FreeBSD.org> <74388082-ea84-564c-44ee-f1a568b75d5b@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1661875430; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=AhKUnQvxJE2PWCixaLPL3RKdZ1kKAekzjLOcQMZw/Ww=; b=hbQPPvNHeviiaSfRWSw/le/ndAmqdZmVT0/MGrs/8nGAOsuN36mOBwc5343IGAHYCbYDW/ r96dLuUirLyrIk4wk+72HnFVX2Zu0adM8F5DSGk7poFQgyL27kx4KSVpXxjdt7Z2D3vYcC ORJTqUOwwX+TyIyT0HiXwJAwyV8M7klYYEy1EDAjHBqC/T9HZ04lPpRShoGqUzUMbK/L33 NWVo5NhwrIRfwRXceFSM/UFQcRQ+nKCS+lrI9wmTMPsIqa3BQ2pn3t0hMxy5Jo3srzPA/B Wo8nKa8WQXxQBd4RAZaUUYtOJc9r8mWzRW63+6OXV6cgxzV4z3nV5bQali58MQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1661875430; a=rsa-sha256; cv=none; b=UuQE9+BZSzxN1t1H5qqc475aDbCUXyHDGgXcoGgNKbVKx86sha0Bb1iiGnhYlsOGemaz8M 9E67A3+eNwlUkcpSzL8qL4SWEKTfgaRkJvTpK3KmPCoJ+Dq8gOGuy4ssTEEZ6tE6Qa2hsV VJRpoZMMCCV3jLeFz7B3q9ba49Zk+cVIuA9FdqnMK2AHwcqTEHJb7oqOe6yJ8v5Ii6EQht QGouRGNXtzQlVTJ4D8xV2C2wDC9QUrMOT1q14woxRqXrpn9GrYkGRbT1YFHj5etc9kYQR9 OQSyJTs1CCKcwd8HLlNJbgBKdHMjUDXgt9Z4NQAO20SP7OwcmiR10pqWwlzkIw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N On 30/08/22 12:39, Renato Botelho wrote: > On 30/08/22 11:35, Jesper Schmitz Mouridsen wrote: >> >> On 30.08.2022 13.17, Renato Botelho wrote: >>> On 29/08/22 20:32, Jesper Schmitz Mouridsen wrote: >>>> >>>> >>>> On 29.08.2022 17.29, Renato Botelho wrote: >>>>> There is a PR [1] opened for years reporting arj fails to build on >>>>> a jail.  Recently I reproduced it on a system running CURRENT. >>>>> >>>>> I just launched a jail and tried to build it, and got the error as >>>>> described: >>>> Did you use ezjail? >>>> >>>> I tried to replicate and I think the error is triggered by >>>> the nullfs usage of ezjail. I copied the settings of ezjail without >>>> nullfs usage (using the basejail as path adding etc from the failing >>>> jail to it and removing the fstab from jail.conf) and arj did get a >>>> working msgbind. >>> >>> Yes, I also use ezjail.  I'm cc'ing ezjail's maintainer to see if we >>> can get some advice. >>> >>> Thanks! >>> >> Hi again. >> >> >> I narrowed this down to  symlinks ,wiithin the jail, to the nullfs >> mountpoint. >> >> Replacing symlinks to the basejail mount point with dirs and setting >> this in the fstab of the jail >> >> and msgbind is a valid executable >> >> /usr/jails/basejail/bin /usr/jails/test1/bin nullfs ro 0 0 >> /usr/jails/basejail/boot /usr/jails/test1/boot nullfs ro 0 0 >> /usr/jails/basejail/lib /usr/jails/test1/lib nullfs ro 0 0 >> /usr/jails/basejail/libexec /usr/jails/test1/libexec nullfs ro 0 0 >> /usr/jails/basejail/rescue /usr/jails/test1/rescue nullfs ro 0 0 >> /usr/jails/basejail/sbin /usr/jails/test1/sbin nullfs ro 0 0 >> /usr/jails/basejail/usr/bin /usr/jails/test1/usr/bin nullfs ro 0 0 >> /usr/jails/basejail/usr/lib /usr/jails/test1/usr/lib nullfs ro 0 0 >> /usr/jails/basejail/usr/include /usr/jails/test1/usr/include nullfs ro >> 0 0 >> /usr/jails/basejail/usr/lib32 /usr/jails/test1/usr/lib32 nullfs ro 0 0 >> /usr/jails/basejail/usr/ports /usr/jails/test1/usr/ports nullfs ro 0 0 >> /usr/jails/basejail/usr/libdata /usr/jails/test1/usr/libdata nullfs ro >> 0 0 >> /usr/jails/basejail/usr/sbin /usr/jails/test1/usr/sbin nullfs ro 0 0 >> /usr/jails/basejail/usr/share /usr/jails/test1/usr/share nullfs ro 0 0 >> /usr/jails/basejail/usr/libexec /usr/jails/test1/usr/libexec nullfs ro >> 0 0 >> /usr/jails/basejail/usr/src /usr/jails/test1/usr/src nullfs ro 0 0 >> >> It should be further narrowed down but nullfs alone is not the issue. > > Interesting.  And just to add a note here, I copied msgbind from jail to > host and tried to execute it to confirm binary was really bad and I got > the same Abort trap message. > And one more interesting information is it builds fine with gcc. I just added USE_GCC=yes to the port and it worked. -- Renato Botelho