Date: Sun, 10 Apr 2016 17:03:41 -0700 From: Mehmet Erol Sanliturk <m.e.sanliturk@gmail.com> To: "William A. Mahaffey III" <wam@hiwaay.net> Cc: "FreeBSD ports list !!!!" <freebsd-ports@freebsd.org> Subject: Re: 'porting' AMD compiler suite Message-ID: <CAOgwaMtE0710DoB00grPi6D_NMqToxL8rGDqm76QKMS_mD%2BeWA@mail.gmail.com> In-Reply-To: <570AE735.2060606@hiwaay.net> References: <570ACDB6.1020703@hiwaay.net> <20160410230338.GB24900@server.rulingia.com> <570AE735.2060606@hiwaay.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Apr 10, 2016 at 4:50 PM, William A. Mahaffey III <wam@hiwaay.net> wrote: > On 04/10/16 18:09, Peter Jeremy wrote: > >> On 2016-Apr-10 17:09:04 -0453, "William A. Mahaffey III" <wam@hiwaay.net> >> wrote: >> >>> configure process completed OK, but created a Makefile w/ what seems to >>> be a bunch of linuxisms in conditionals to allow compilation for >>> different architectures, see attached orig-Makefile. >>> >> Have you tried using gmake, rather than the base make? >> >> > > OK, I tried gmake & got the attached, lotta '#include malloc.h' all over > the place, I'll have to handle that file-by-file :-/ .... > > -- > > William A. Mahaffey III > > ---------------------------------------------------------------------- > > "The M1 Garand is without doubt the finest implement of war > ever devised by man." > -- Gen. George S. Patton Jr. > > > _______________________________________________ > > Important problem here is the following : In make files , there are other references to "make" commands , means , even you started from gmake , at the next make invocation , it will invoke the FreeBSD make . Therefore , you need to use a jail and replace the FreeBSD make with gmake , or , by traversing all of the make files , replace "make" invocations by "gmake" . Mehmet Erol Sanliturk
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOgwaMtE0710DoB00grPi6D_NMqToxL8rGDqm76QKMS_mD%2BeWA>