From owner-freebsd-dtrace@FreeBSD.ORG Wed Jul 16 04:14:49 2014 Return-Path: Delivered-To: freebsd-dtrace@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 035E4540 for ; Wed, 16 Jul 2014 04:14:49 +0000 (UTC) Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::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 C0AD828A7 for ; Wed, 16 Jul 2014 04:14:48 +0000 (UTC) Received: by mail-ie0-f181.google.com with SMTP id rp18so300411iec.26 for ; Tue, 15 Jul 2014 21:14:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=3GyFIu4cUjZIPBs6a+u4e6botOuJXlhszNZY1IAX8bc=; b=m/jIO5882MI+a1r2UsXRb+hiRhuC705HyZzO4WlBQ74pEUUK1WzRxS1PgErInYXjQD L7P1Zbw+3rz9ETOhvnx636koO1FynvTYGKsVGhhG0YA9zoIt2TflJF2IuSTSMY9x4sTf G7aK0Uj5yRdwHXedVzrHYUqojogjL9l1+6iYlaalUxXeGnw8Qwlib0bUVuGeTtWKJeN8 V2j79Zrf4DP9e72NsacbtJEkBwTWE8ZzY7ypRMKpU8EZEWne4m+P65GNaGEdhvwp1jWL efcAdjR8PPTGv2HSWJ+GMbd0Awgi/cKNN0xwIMuqcqJb6JbS1F0mOgq3skR1lUUo6dwh iLEg== X-Received: by 10.42.214.207 with SMTP id hb15mr34780423icb.30.1405484088223; Tue, 15 Jul 2014 21:14:48 -0700 (PDT) Received: from raichu (24-212-142-131.cable.teksavvy.com. [24.212.142.131]) by mx.google.com with ESMTPSA id l5sm3338436ige.6.2014.07.15.21.14.47 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 15 Jul 2014 21:14:47 -0700 (PDT) Sender: Mark Johnston Date: Wed, 16 Jul 2014 00:14:45 -0400 From: Mark Johnston To: Sevan / Venture37 Subject: Re: DTrace probes for python 2.7.7 Message-ID: <20140716041445.GB20065@raichu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) 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: Wed, 16 Jul 2014 04:14:49 -0000 On Mon, Jun 09, 2014 at 07:40:07PM +0100, Sevan / Venture37 wrote: > On 9 June 2014 19:28, Mark Johnston wrote: > > 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 > > Indeed, that was it, with dtraceall module loaded on r266655 VM's, > everything fails with the same error now. > > "dtrace: failed to compile script Include/pydtrace.d: line 26: typedef > redeclared: __uint8_t" I've since discovered that the correct way to solve this problem is by adding "-xnolibs" to the dtrace -G flags.