'porting' AMD compiler suite

[William A. Mahaffey III]

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.