Date: Wed, 8 May 2013 21:58:34 -0700 From: "Simon J. Gerraty" <sjg@juniper.net> To: Warner Losh <imp@bsdimp.com> Cc: Garrett Cooper <yanegomi@gmail.com>, freebsd-toolchain@freebsd.org, "freebsd-arch@FreeBSD.org Arch" <freebsd-arch@freebsd.org> Subject: Re: [RFC] adding a variable to .mk and Makefile.inc1 to point to top of the FreeBSD source tree Message-ID: <20130509045834.2E67058097@chaos.jnpr.net> In-Reply-To: <9CD1CE3E-C17C-4C63-BA03-190531185D7A@bsdimp.com> References: <CAGH67wS21otQr1fBqQ2z=XQjUV30QUjdtyAkzC_Tf1Ts%2BPq%2B8g@mail.gmail.com> <20130507213118.5277F58097@chaos.jnpr.net> <D6BADC3E-CCC4-4D85-8857-FB6BAAFBB820@bsdimp.com> <20130508054121.DCA7258097@chaos.jnpr.net> <9CD1CE3E-C17C-4C63-BA03-190531185D7A@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> Do you mean why not simply use ${MACHINE}.${MACHINE_ARCH} always?
>> Encoding both MACHINE and MACHINE_ARCH always is doable, but I avoid =
>'.'
Actually I only avoid '.' in the captured dirdeps.
So ${MACHINE}.${MACHINE_ARCH} in objdir may be ok - will take a look.
Dealing with ${MACHINE}.${MACHINE_ARCH} is actually easy it just gets
stripped from the captured dirdeps, it is references to other machine
and arch's that need to be captured but cannot be dealt with as neatly.
The vast majority of such cases though are for pseudo machines like
"host" and "common" (for generated files which are machine
independent) where the issue shouldn't arise anyway.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130509045834.2E67058097>