Date: Wed, 13 Apr 2016 21:45:13 -0453.75 From: "William A. Mahaffey III" <wam@hiwaay.net> Cc: FreeBSD ports list !!!! <freebsd-ports@freebsd.org> Subject: Re: 'porting' AMD compiler suite Message-ID: <570F02EF.4000103@hiwaay.net> In-Reply-To: <CAOgwaMv6B7kAasKQm=ujfRCxeDF2icMWSs9pEcZ0O7uOuXgAcA@mail.gmail.com> 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> <CAOgwaMv6B7kAasKQm=ujfRCxeDF2icMWSs9pEcZ0O7uOuXgAcA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04/13/16 02:51, Mehmet Erol Sanliturk wrote: > On Wed, Apr 13, 2016 at 12:02 AM, William A. Mahaffey III <wam@hiwaay.net> > wrote: > >> On 04/12/16 21:05, Kevin P. Neal wrote: >> >>> On Tue, Apr 12, 2016 at 03:32:21PM -0453, William A. Mahaffey III wrote: >>> >>>> A bit of poking around yields a 'typedef __uintptr_t uintptr_t;' >>>>> statement as line 78 of /usr/include/sys/_stdint.h, where __uintptr_t >>>>> isn't defined anywhere .... Any clues ? TIA & have a good one. >>>>> >>>>> >>>>> >>>> *C'mon* !!!! Someone throw me a bone :-). Whassup here, this can't be >>>> the 1st time this has happened .... where is __uintptr_t >>>> defined/typedef'ed ? >>>> >>> % find /usr/include/ -type f -print | xargs grep __uintptr_t >>> >>> You'll need to follow the includes backwards until you get to an include >>> that looks like it is meant to be directly included. That particular >>> command >>> is left as an exercise to the reader. >>> >> >> *Boooyah*, thanks. It looks like some GNU-ism, still chasing ;-). Thanks >> again. >> >> -- >> >> William A. Mahaffey III >> >> ---------------------------------------------------------------------- >> >> "The M1 Garand is without doubt the finest implement of war >> ever devised by man." >> -- Gen. George S. Patton Jr. >> >> _______________________________________________ >> >> > > There are differences between FreeBSD and Linux include directory places . > > Assume , it it is possible to build Open64 in Linux , but it is failing in > FreeBSD due to unfound files : > > There is a need to specify include directories ( -I.... ) in make files > correctly for the FreeBSD being equivalent to Linux include directories . > > > For example , some files are specified in Linux as #include <name.h> , > but in FreeBSD as #include <sys/name.h> . > > > Mehmet Erol Sanliturk . > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > 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 .... -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?570F02EF.4000103>