From owner-freebsd-dtrace@FreeBSD.ORG Mon Jun 9 18:28:34 2014 Return-Path: Delivered-To: freebsd-dtrace@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 09E81524 for ; Mon, 9 Jun 2014 18:28:34 +0000 (UTC) Received: from mail-ve0-x235.google.com (mail-ve0-x235.google.com [IPv6:2607:f8b0:400c:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BB1A223AC for ; Mon, 9 Jun 2014 18:28:33 +0000 (UTC) Received: by mail-ve0-f181.google.com with SMTP id db11so1494634veb.26 for ; Mon, 09 Jun 2014 11:28:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=PU7VJML5CsaycuiwZa4xFuA1wqBY9PUijGTEpHrk3y4=; b=L4qxRS1ad4U4ILAhZ9U3EraThgZ5kv+tz2MOS9eK+fW1JsbcCX3Cam9OLr1HDVP425 b3XGf/7VfLbZVQxLnD1zfZgC9fHncvRgC2aWGyOoGfzjNcCiRCASeJp60x/1VTMxzXg6 yU1lCNuZ5ZB4OX9ilC/Z41oHl4GQfrcHab83RWgztXguxrf7WkAEk1355NGMKqGDdX+o mMRHYyCMBEguAM9NY0aZ7PK7nQ66FaCa19oQm2Je21riCgvnQ4YMw7SJskdQE5AF8nw7 BViokEylb3aa3PZMYBC41hV9SUFI1UqvzOMZD+mu5UZfwNFtJhavsr49x6hCyu1dx/aG QLCw== MIME-Version: 1.0 X-Received: by 10.52.33.241 with SMTP id u17mr1774641vdi.82.1402338512751; Mon, 09 Jun 2014 11:28:32 -0700 (PDT) Sender: markjdb@gmail.com Received: by 10.220.162.68 with HTTP; Mon, 9 Jun 2014 11:28:32 -0700 (PDT) In-Reply-To: References: Date: Mon, 9 Jun 2014 14:28:32 -0400 X-Google-Sender-Auth: gpCkdrklACIVzx_GStSXKLii-qg Message-ID: Subject: Re: DTrace probes for python 2.7.7 From: Mark Johnston To: "Sevan / Venture37" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-dtrace@freebsd.org" X-BeenThere: freebsd-dtrace@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "A discussion list for developers working on DTrace in FreeBSD." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jun 2014 18:28:34 -0000 On Mon, Jun 9, 2014 at 2:16 PM, Sevan / Venture37 wro= te: > On 4 June 2014 20:15, Sevan / Venture37 wrote: >> dtrace: failed to compile script Include/pydtrace.d: line 26: typedef >> redeclared: __uint8_t > > On i386 the build fails differently with r266655 snapshot from 20140525 > > =E2=80=9Cfailed to compile script Include/pydtrace.d: =E2=80=9C/usr/lib/d= trace/ip.d=E2=80=9D > line 2: type redeclared: struct devinfo" > > There is of course an inconsistent. > > The original error regarding the redeclaration of __uint8_t was from a > AMD64 host running r266972. > > Installing the AMD64 r266655 snapshot & retrying the build results in, > > failed to compile script Include/pydtrace.d: > =E2=80=9C/usr/lib/dtrace/unistd.d=E2=80=9D, line 135: syntax error near = =E2=80=9Ccsinfo_t=E2=80=9D > > Can anyone shed some light on what's going on. This is probably because the build is running dtrace -G without the dtrace kernel modules loaded. This shouldn't be a problem, but currently is because dtrace(1) parses the scripts in /usr/lib/dtrace and errors out if dtrace isn't available in the kernel. Things like "#pragma depends_on" don't work, and there seem to be bugs in the error reporting of libdtrace; one ends up with the error messages above. I'd like to fix this by changing dtrace -G to not process scripts in the libdir, but I'm not yet sure what the implications of this are. I will ask on the dtrace-discuss list soon. In the meantime, a somewhat unsatisfactory workaround would be to just kldload dtraceall before starting the build. -Mark