Date: Wed, 3 Mar 2021 10:36:55 +0100 From: Paul Floyd <pjfloyd@wanadoo.fr> To: Ed Maste <emaste@freebsd.org> Cc: "toolchain@freebsd.org" <toolchain@freebsd.org> Subject: Re: clang options for load segments Message-ID: <4e2be84d-3929-6bb5-5bea-0444f29f429f@wanadoo.fr> In-Reply-To: <CAPyFy2BzBVX0Q1tB39CA-fXQj4b44MMVAhWOvi6fRaDPaEzs8g@mail.gmail.com> References: <fb3e3660-a6c0-c8ce-5055-624cde7ce95c@wanadoo.fr> <4D81BCDE-ECBC-49D8-BF17-38E334141FE0@FreeBSD.org> <89794bb8-5e97-36a7-0b6a-fa2eaf76a72a@wanadoo.fr> <CAPyFy2BzBVX0Q1tB39CA-fXQj4b44MMVAhWOvi6fRaDPaEzs8g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Ed PT_LOAD, I'm fully in agreement, I need to fix this in Valgrind. > Thank you so much for this, I will be very happy to finally see > FreeBSD support upstream. Me too! > IMO we should look at removing devel/valgrind and replacing it with > valgrind-devel, given the amount of not-upstream work that exists in > both of them. What I think would be best is that when 3.17 comes out, we move devel/valgrind to be based on that date and move valgrind-devel to 3.18 (if that is the next version). And when it is finally upstreamed, base the ports off the official sourceware git repo. A+ Paul
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4e2be84d-3929-6bb5-5bea-0444f29f429f>