Date: Wed, 04 Jun 2014 23:49:15 +1000 From: Kubilay Kocak <koobs@FreeBSD.org> To: Sevan / Venture37 <venture37@gmail.com> Cc: "freebsd-dtrace@freebsd.org" <freebsd-dtrace@freebsd.org> Subject: Re: DTrace probes for python 2.7.7 Message-ID: <538F23DB.2040003@FreeBSD.org> In-Reply-To: <CA%2BU3Mf6NYYpOHr_C81qg%2B4%2Bz_caxA-ErtCLkJdqp41NFPDzXpg@mail.gmail.com> References: <CA%2BU3Mf7_t3GuRMS0YicRb03ti56LHg_DD=iC=%2BD_wEj2SPNwyg@mail.gmail.com> <538EF858.9000305@FreeBSD.org> <CA%2BU3Mf6NYYpOHr_C81qg%2B4%2Bz_caxA-ErtCLkJdqp41NFPDzXpg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/06/2014 10:37 PM, Sevan / Venture37 wrote: > On 4 June 2014 11:43, Kubilay Kocak <koobs@freebsd.org> wrote: >> Both of my official FreeBSD Python buildbots support dtrace, and I've >> been doing my best to support jcea@ over the past year or so: >> >> http://buildbot.python.org/all/buildslaves/koobs-freebsd9 >> http://buildbot.python.org/all/buildslaves/koobs-freebsd10 >> >> I'd like to see us be one of the first to support it (in ports), so let >> me know if there's anything I can do :) > > Hi Koobs, > I'd check the output of your builds it doesn't appear to be building > with dtrace enabled > configure: WARNING: unrecognized options: --with-dtrace > You need to rerun autoconf after patching > > The 2.7.6 patches merged with lang/python27 as expected, but the build > fails due to issues with the paths added in as part of the patch which > I'm currently looking into now. > > > > Sevan > The buildmaster sets the configure argument for all builds unconditionally (for when dtrace support does land in tip) but jcea has only tested using the custom builder so far Have you been in touch with Jesús yet? This is the relevant issue ID: http://bugs.python.org/issue13405
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?538F23DB.2040003>