Re: port-arm/48193: On NetBSD/evbearmv6hf-el for Raspberry Pi, MACHINE_ARCH returns earm, but *hf* is expected in /usr/share/mk/bsd.own.mk .

[Izumi Tsutsui <tsutsui%ceres.dti.ne.jp@localhost>]

The following reply was made to PR port-arm/48193; it has been noted by GNATS.

From: Izumi Tsutsui <tsutsui%ceres.dti.ne.jp@localhost>
To: matt%3am-software.com@localhost
Cc: gnats-bugs%NetBSD.org@localhost, tsutsui%ceres.dti.ne.jp@localhost
Subject: Re: port-arm/48193: On NetBSD/evbearmv6hf-el for Raspberry Pi, 
MACHINE_ARCH
         returns earm, but *hf* is expected in /usr/share/mk/bsd.own.mk .
Date: Mon, 16 Sep 2013 18:25:44 +0900

 > Uh, no.  It solves the PR.
 
 No. It just worked around the problem, and then causes another problems.
 
 You should first define what MACHINE_ARCH and sysctl.hw.machine_arch mean,
 before touching sources. Kernel architectures? Userland binary ABI?
 
 >  It even solves the problem of untarring a different
 > implementation in a chroot and then getting the right MACHINE_ARCH for that 
 > tree.
 
 If hf and sf can be switched dynamically, it will cause confusion
 to have static MACHINE_ARCH in <arm/param.h> and dynamic one
 returned by sysctl.
 
 > It can be backed out if and when someone comes up with a better solution.
 
 Probably you should read the commit guidelines again. You didn't
 have a prior discussion, and you didn't even test your changes.
 If core members don't have to have reviews even for exported API changes,
 I have no further comments though.
 
 ---
 Izumi Tsutsui