NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: port-arm/48215: pkg_add fails on recent NetBSD/evbearmv6hf-el current
The following reply was made to PR port-arm/48215; it has been noted by GNATS.
From: Matt Thomas <matt%3am-software.com@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: port-arm-maintainer%netbsd.org@localhost,
gnats-admin%netbsd.org@localhost,
netbsd-bugs%netbsd.org@localhost
Subject: Re: port-arm/48215: pkg_add fails on recent NetBSD/evbearmv6hf-el
current
Date: Tue, 17 Sep 2013 10:36:32 -0700
On Sep 17, 2013, at 10:35 AM, matthew green <mrg%eterna.com.au@localhost>
wrote:
> The following reply was made to PR port-arm/48215; it has been noted =
by GNATS.
>=20
> From: matthew green <mrg%eterna.com.au@localhost>
> To: christos%zoulas.com@localhost (Christos Zoulas)
> Cc: port-arm-maintainer%netbsd.org@localhost,
> gnats-admin%netbsd.org@localhost,
> netbsd-bugs%netbsd.org@localhost, ryoon%NetBSD.org@localhost,
> gnats-bugs%NetBSD.org@localhost
> Subject: re: port-arm/48215: pkg_add fails on recent =
NetBSD/evbearmv6hf-el current
> Date: Wed, 18 Sep 2013 03:30:37 +1000
>=20
>> | since these binaries are always going to report the same value,
>> | i suspect that fixing arm/param.h to report the right value
>> | depending on the compiler options would fix the problem without
>> | having to patch every program that uses them to use sysctl on
>> | netbsd...
>>=20
>> The problem is that some archs with different machine_archs use the
>> same toolchain and can't be told apart.
>=20
> how so? can't the header file define MACHINE/MACHINE_ARCH based
> upon the compiler defines? eg, from sparc64/param.h:
>=20
> #ifdef __arch64__
> #define _MACHINE sparc64
> #define MACHINE "sparc64"
> #define _MACHINE_ARCH sparc64
> #define MACHINE_ARCH "sparc64"
> #define MID_MACHINE MID_SPARC64
> #else
> #define _MACHINE sparc
> #define MACHINE "sparc"
> #define _MACHINE_ARCH sparc
> #define MACHINE_ARCH "sparc"
> #define MID_MACHINE MID_SPARC
> #endif
For evbearm & evbearmv5, there is nothing to distinguish them.
Ditto for evbearmhf & evbearmv5hf.=
Home |
Main Index |
Thread Index |
Old Index