Date: Sat, 14 Mar 2020 17:26:38 -0400 From: Ed Maste <emaste@freebsd.org> To: Dimitry Andric <dim@freebsd.org> Cc: Roman Bogorodskiy <novel@freebsd.org>, waitman@waitman.net, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Build failed compiling ittnotify_static.pico Message-ID: <CAPyFy2A8G=1fejV0m%2B8vh1TNHpF0ca_DERLOnxFOYA15kr7VUw@mail.gmail.com> In-Reply-To: <B9A2A100-FDF6-44D0-B291-0824FF630DD8@FreeBSD.org> References: <20200313205706.GD1053@rancor.immure.com> <8740b5f9fef5ce417ea8968543de2992@waitman.net> <14a5e39b65511d7ab4ffe370717d57e5@waitman.net> <D966E0E8-6208-4353-B9AE-A6F14EBF9D03@FreeBSD.org> <20200314162429.GA47907@kloomba> <B9A2A100-FDF6-44D0-B291-0824FF630DD8@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 14 Mar 2020 at 13:14, Dimitry Andric <dim@freebsd.org> wrote: > > These are for the 32-bit stage. The initial fix I committed in r358907 > worked for the main buildword stage, but apparently not for the 32-bit > stage, which stores its object files in a slightly different directory > (e.g. the obj-lib32 subpath). > > Ed Maste tried to fix that up in r358909, but maybe it does not work in > all situations, for example with custom MAKEOBJDIRPREFIX settings? My change in r358909 will definitely not be effective if you already had a failed build between r358907 and r358909.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2A8G=1fejV0m%2B8vh1TNHpF0ca_DERLOnxFOYA15kr7VUw>