From nobody Tue Aug 30 17:19:55 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 4MHDZj1Yb0z4ZwZt for ; Tue, 30 Aug 2022 17:19:57 +0000 (UTC) (envelope-from jsm@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 4MHDZj10nhz3CbY; Tue, 30 Aug 2022 17:19:57 +0000 (UTC) (envelope-from jsm@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1661879997; 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=sBwRTNvTgJNuij5CavVnXRkMy891pjgVjkmu0AX+t6M=; b=ZmZfkvdEJII5M8ft3Ll8FRgWcYWegbX1iiNODg+7QI1Xexfl5+/dWGx2TaYnxUrqPSaDZp jvOzT2Wv7cYBc+Y0YP2mcHvF2TgUBwBn8Q80zn7zdPRb2W7ytIZergylHzPfIq2Uw1yrFS RtsNI6C3p+/8Q+tArq297pp620c1DS8eTHYh0WyN/WSB8M5wYvcDIh74ZmWFdxj0pn0y8a ds7dRB17mBFXReouTATvbOa3mksGRbWcTqpCpHY/g8LZPlbTQjHXlhkUPoLcwEePxgiuNc AIivpZoWwsct6QC50+MrvofvTZ2uEJqYVNE0n03+QdYJ929LlKTYE6d3sL2+rg== Received: from [192.168.1.5] (mail.northatlanticmusicsupplies.com [212.237.182.202]) (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: jsm) by smtp.freebsd.org (Postfix) with ESMTPSA id 4MHDZh3yTtz1P4y; Tue, 30 Aug 2022 17:19:56 +0000 (UTC) (envelope-from jsm@FreeBSD.org) Message-ID: <63bd8a64-33a7-64b7-8014-6ac936c56668@FreeBSD.org> Date: Tue, 30 Aug 2022 19:19:55 +0200 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 (X11; FreeBSD amd64; rv:91.0) Gecko/20100101 Thunderbird/91.13.0 Subject: Re: archivers/arj fails to build on jail Content-Language: en-US From: Jesper Schmitz Mouridsen To: Renato Botelho , 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> <503d2719-4942-3d2e-b6c8-7fcd91f4fe4a@FreeBSD.org> In-Reply-To: <503d2719-4942-3d2e-b6c8-7fcd91f4fe4a@FreeBSD.org> 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=1661879997; 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=sBwRTNvTgJNuij5CavVnXRkMy891pjgVjkmu0AX+t6M=; b=kR/NLf98XKP4W/QglQjBVr/MJimGnUpPz0WdC7DV7JJ3T+8DMVYcTfeWVAzMfamCDrgEuK xIjOTFI2X9O8xaXzruKmq51HqSuee2/agbTDcNvrsHp2s8NxLRbYwQGpQXQqQK3d9EwcTl AoHZbe/17ry5d/vpW5g0WaejRW9ZTZVf5l1lK5m96jla6E7yQnD8u/a3kqbeOzq+cCODOv fpiRbBXQRm9AM9QKYof5mqa0zMejsL0HzIRs0SsBgxAW5QD3MvNOYu2Fnyiw2JxeRT3UmP RNfXV6YHEEf9mPHBdYlOgoCFrJal58YQkU4QGB1VoIlewE0XFSPmF6XdDdH9UQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1661879997; a=rsa-sha256; cv=none; b=IYgUN8ROtUqiJlRUHQOcJPehdm2zCQhEjyAPleO/cXXyQ0t6rm+wuZpk3jcJENPetBRrTk lRJoKW0RBGic1J6tRn4WxjZxvpmT2em9EOm5urx1vXs2V9MHeAd9aE+IjiLTvEWkmiYXK4 sQTluwdXsNWEG1mYuNYzrJ+2dLaNCFRXhpt0Vh9d4YFMdPj5aN6E0Bb8KriO469G3llD0X IRrcjWbxLLh7O24MYaKUuumk7O5Uw1LGiLK1PuNMGaT2Wl4goINc47Xx4Vv05GX6J/TnnN mjSYoWhtzuu6Zs+MD3zuePnEO4q3uA4iWlMbFxjHodg3CWdVT0wuhcSUV3Q8Mw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N On 30.08.2022 18.45, Jesper Schmitz Mouridsen wrote: > > On 30.08.2022 18.03, Renato Botelho wrote: >> 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. >> > if you inspect the output of realpath /usr/bin/cc i think we are close > to a cause.. it includes /basejail in my setup.. if you copy cc out of > basejail e.g /usr/local/bin and make CC=/usr/local/bin it also works.. > > perhaps some linking  of msgbind fails because of "wrong" realpath... That even manifests without a jail so moving /usr/bin to /something/usr/bin and having /usr/bin as a śyḿlink to /something/usr/bin breaks the port