Date: Tue, 30 Aug 2022 16:35:01 +0200 From: Jesper Schmitz Mouridsen <jsm@FreeBSD.org> To: Renato Botelho <garga@FreeBSD.org>, Current FreeBSD <freebsd-current@freebsd.org> Cc: erdgeist@erdgeist.org Subject: Re: archivers/arj fails to build on jail Message-ID: <d6462697-48ad-576d-2138-47841dbfbe92@FreeBSD.org> In-Reply-To: <74388082-ea84-564c-44ee-f1a568b75d5b@FreeBSD.org> References: <9636d41e-bf21-8130-ff15-e5dcbaaa4fe8@FreeBSD.org> <430844d1-ae2f-90d2-eec7-646c848e084f@FreeBSD.org> <74388082-ea84-564c-44ee-f1a568b75d5b@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. >>> >>> gmake[3]: *** [GNUmakefile:258: freebsd12.1/en/rs/msg_crp.h] Abort trap >>> >>> msgbind binary built inside arj, when called, ends like this. I has >>> no clue about what could be the root cause here. I also don't >>> understand why arj builds fine on poudriere, which uses jail as well. >>> >>> If anyone has any idea about what could be causing this, please let >>> me know. >>> >>> [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235636 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d6462697-48ad-576d-2138-47841dbfbe92>