From nobody Tue Aug 30 16:45:49 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 4MHCqN4PrRz4ZsJB for ; Tue, 30 Aug 2022 16:45:52 +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 4MHCqN3sKlz47LD; Tue, 30 Aug 2022 16:45:52 +0000 (UTC) (envelope-from jsm@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1661877952; 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=Z8ZDPVR3oGq5/CwnUoZSKOIRB8K2rPle9KSoIYQRoRc=; b=RISWCMYYj5lgYjeigiP5uf0tyiKn6kg6aALLsQXctkowCo/OX5GkTjVB3l2XY3OpiktDWr IyUMJekqBf/8PYwORu9KMsPGQmZREw7kv1zLVySKI9+yHbRGDs7hsA+BIEtCXzAoSzs7qk 9o0xSZhaNsaaDkl/RPYX2ZCZD93dbz3UjhFPj/dTkM/u3ir/0dRkY1PpFg+xKYmOXha8X+ SlNrGFxynHp4rqfPBoaywaCji0M2Wv3GYMlAB1SCAmR0XCOFmERNJdBXmKNpnh+RdHfeAw m5pH+tzVjbuaPEwQabiGGmfeEvVdMpJsyLK6mwIaqiLoJ9Cz5g3Y4P+yyQKEQQ== 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) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: jsm) by smtp.freebsd.org (Postfix) with ESMTPSA id 4MHCqM6ph7z1Nwj; Tue, 30 Aug 2022 16:45:51 +0000 (UTC) (envelope-from jsm@FreeBSD.org) Message-ID: <503d2719-4942-3d2e-b6c8-7fcd91f4fe4a@FreeBSD.org> Date: Tue, 30 Aug 2022 18:45:49 +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 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> From: Jesper Schmitz Mouridsen 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=1661877952; 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=Z8ZDPVR3oGq5/CwnUoZSKOIRB8K2rPle9KSoIYQRoRc=; b=rNSDEFrzC5FvoHr/9ZV/a9sPYo/3c3EDTLMwkaVFz/TOVMoW4WHBYEHnFtVOAXpYhFaPBW CyUN1CEJ/QDHKWSRrK8Omp2OjeJsygO5o7ya2UBDIG9tyW3nWAShSMFntHca/wM60RgvTV qrIiExY9Emxkz6KcGZ/V5OmzAmj/x/F+mGhFmSIyPLHfmnCOyV9XN6Pkh6ZfWcqcGtIN8c +JC+vFYE8sTh0cTyND1fPVWxQEmTyp5Mg3jQu+wom/7PhaPKJrVB4AMp0nN9xHciZZz5RC AAYphGMhiU1FbWlnzJMAQuuUsykEZ1cJrsY8S6nN7cz7PEwPq/KyfOG5OOyn7A== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1661877952; a=rsa-sha256; cv=none; b=dMAJ4T4cF6ImWbZ4yzZDSWjAFar0z4kErZnjssJNV7ufBlPn2AHDUW3BHpUaBM+eP02KP9 LpR2hlYkZQmOJBhFL7h0GYoyVcmcchdrJ2SHzhbD5Pe3pzhy0kqyNBGIg8rp+xD2T8M3h0 4knhnXnPJrGuw6/Upgcd1TCERr8hCPLwsNgHEkYxXCItCjoSocaYq+w5HP3b/GGeStU2bW hVIgd9WrxafglAI9h2oFNxKffU2yvD5LkZx1YGJtYsW/OnoZJ4NxCZlTU5OgsPtjlDRV1e iXSybKSbATfyYi365Enh11gI4SaPZVOFv7o/4vRZdBKG+BtW8LxMMoabz7TY8g== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N 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...