Date: Wed, 20 Jul 2022 17:55:09 +0200 From: Stefan Esser <se@FreeBSD.org> To: Tomoaki AOKI <junchoon@dec.sakura.ne.jp>, Andy Farkas <andyf@andyit.com.au> Cc: freebsd-ports@freebsd.org Subject: Re: svgalib build fail with portmaster Message-ID: <82bc7e15-ba20-d258-2a04-391d611a953f@FreeBSD.org> In-Reply-To: <20220720215504.88a245ea12e95bf46729e646@dec.sakura.ne.jp> References: <36ed0442-bea0-1ec1-874e-c346f550ed5d@andyit.com.au> <20220720215504.88a245ea12e95bf46729e646@dec.sakura.ne.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 20.07.22 um 14:55 schrieb Tomoaki AOKI: [...] > Looking into commit log at cgit [1], the problematic file is already > there at the first commit and unchanged afterwards. So the file should > be there when you installed (or previously updated). See my reply to the OP, this is a port that removes files from the base system when "make all" is used to build it. > Another possiblity would be you changed LOCALBASE when you installed > (or updated) previouly but portmaster doesn't recorded the fact > properly. (i.e., the port was installed under /opt/, but portmaster > looks for /usr/local due to mis-recorded LOCALBASE.) > But this case you SHOULD know and notice what happened clearly. No, portmaster did not play any role, except that it noticed that the files were no longer there to safe into a backup package in case the newly built port had an issue or would not install. Regards, STefan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?82bc7e15-ba20-d258-2a04-391d611a953f>