From owner-freebsd-ports@freebsd.org Thu Apr 14 19:19:45 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9B9B8ADABE6 for ; Thu, 14 Apr 2016 19:19:45 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5EECC18F0 for ; Thu, 14 Apr 2016 19:19:44 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from kabini1.local (user-24-214-48-39.knology.net [24.214.48.39]) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id u3EJJgF1032709 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Thu, 14 Apr 2016 14:19:43 -0500 Subject: Re: 'porting' AMD compiler suite References: <570ACDB6.1020703@hiwaay.net> <20160410230338.GB24900@server.rulingia.com> <570AE735.2060606@hiwaay.net> <570BAC56.5060008@hiwaay.net> <570D5A0B.3010703@hiwaay.net> <20160413015933.GA13695@neutralgood.org> <570DEF42.30100@hiwaay.net> <570F02EF.4000103@hiwaay.net> <570F3D37.5060405@FreeBSD.org> Cc: freebsd-ports@freebsd.org From: "William A. Mahaffey III" Message-ID: <570FED4D.1060603@hiwaay.net> Date: Thu, 14 Apr 2016 14:25:11 -0453.75 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 In-Reply-To: <570F3D37.5060405@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Apr 2016 19:19:45 -0000 On 04/14/16 01:54, Andriy Gapon wrote: > On 14/04/2016 05:38, William A. Mahaffey III wrote: >> All seems OK w/ the system headers (I know, shocking !!!!), the required files >> defining a '__uintptr_t' are in fact unconditionally included, so it must be >> something else (bad defines somewhere, or ....). I am still chasing .... > Apologies, but are you serious?.. > > $ fgrep -r __uintptr_t /usr/include/ > ... > /usr/include/x86/_types.h:typedef __uint64_t __uintptr_t; > /usr/include/x86/_types.h:typedef __uint32_t __uintptr_t; > ... > > This is on an amd64 head system. > Yeah, but the includes are several layers down, took me a bit to figure them out. Did I mention that I am *NOT* a kernel hacker ? Most of this system-type stuff is greek to me, organizationally (which is obviously on me, nobody else). I am still getting compile errors, looks like config.h has a bad line in it, which '#define's uintptr_t as 'unsigned long', which would give a compile error when used in a typedef line. I am going to just comment the offending lines out of the config.h file & see if I get farther. If so (or not, actually), I'll post back for either closure or hints. -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr.