Date: Fri, 10 Aug 2018 12:40:48 +0800 From: blubee blubeeme <gurenchan@gmail.com> To: freebsd.ed.lists@sumeritec.com Cc: FreeBSD current <freebsd-current@freebsd.org> Subject: Re: #includes and #defined Message-ID: <CALM2mE==pj2%2B0iE5hTkDLAruAU8DFobpdnQDCLMhTV0J04sWqA@mail.gmail.com> In-Reply-To: <20180810082813.3a165d2b.freebsd.ed.lists@sumeritec.com> References: <CALM2mEnRxQKcgmpMhg0yVX0iF9JhFPyJKZ6BOrvT7kQTas9jEA@mail.gmail.com> <20180810082813.3a165d2b.freebsd.ed.lists@sumeritec.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 10, 2018 at 8:28 AM Erich Dollansky < freebsd.ed.lists@sumeritec.com> wrote: > Hi, > > On Fri, 10 Aug 2018 08:01:42 +0800 > blubee blubeeme <gurenchan@gmail.com> wrote: > > > What's the proper way to define and include FreeBSD amd64 in GNU > > Makefiles > > > > Do we define FreeBSD as x86_64 or amd64 also is it __FreeBSD__, > > FreeBSD__, or __FreeBSD > > > > I've seen all of the above looking through different projects. > > clang defines '__FreeBSD__' > > Erich > What about the architecture name is it recommended to use x86_64 or amd64? Best, Owen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALM2mE==pj2%2B0iE5hTkDLAruAU8DFobpdnQDCLMhTV0J04sWqA>