Date: Tue, 30 Aug 2022 08:17:26 -0300 From: Renato Botelho <garga@FreeBSD.org> To: Jesper Schmitz Mouridsen <jsm@FreeBSD.org>, Current FreeBSD <freebsd-current@freebsd.org> Cc: erdgeist@erdgeist.org Subject: Re: archivers/arj fails to build on jail Message-ID: <74388082-ea84-564c-44ee-f1a568b75d5b@FreeBSD.org> In-Reply-To: <430844d1-ae2f-90d2-eec7-646c848e084f@FreeBSD.org> References: <9636d41e-bf21-8130-ff15-e5dcbaaa4fe8@FreeBSD.org> <430844d1-ae2f-90d2-eec7-646c848e084f@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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! >> >> 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 -- Renato Botelho
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?74388082-ea84-564c-44ee-f1a568b75d5b>