History repeats itself with ARM architectures ...
At one point in time (see your favorite VCS for rpm -- git, cvs, whatever)
rpmrc carried entries for i786/i886/I986.
RPM development (IMHO) became impossible when RPM needed to detect a specific
hardware (and buggy!) hardware flashing on PPC by
RPMTAG_IDENTITY is calculating as digest of part of package header that
does not contain irrelevant to package build tag entries.
Mathematically RPMTAG_IDENTITY value is a result of function of two
variable: a package header and an rpm utility, thus this value can
differ for same package and
mhatle commented on this pull request.
> @@ -80,6 +80,10 @@ optflags: armv6hl -O2 -g -march=armv6 -mfloat-abi=hard
> -mfpu=vfp
optflags: armv7l -O2 -g -march=armv7
optflags: armv7hl -O2 -g -march=armv7-a -mfloat-abi=hard -mfpu=vfpv3-d16
optflags: armv7hnl -O2 -g -march=armv7-a
kwizart commented on this pull request.
> @@ -80,6 +80,10 @@ optflags: armv6hl -O2 -g -march=armv6 -mfloat-abi=hard
> -mfpu=vfp
optflags: armv7l -O2 -g -march=armv7
optflags: armv7hl -O2 -g -march=armv7-a -mfloat-abi=hard -mfpu=vfpv3-d16
optflags: armv7hnl -O2 -g -march=armv7-a
> armv8* is aarch64 machines in 32-bit mode.
What is aarch32 then ? (open question).
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
On 03/29/2018 06:00 PM, Michael Schroeder wrote:
On Wed, Mar 28, 2018 at 04:02:16PM +0300, Panu Matilainen wrote:
The reason for the "unexpected" rich dependency backport is that we failed
to add a new rpmlib() dependency tracker when adding these new dependencies,
and thus rpm 4.13.0* wont
