On 22/09/2020 16:47, Truong Vu wrote:
You are correct, the "identical architecture" means the same machine
hardware name as shown by the -m option of the uname command.
Thanks for clearing that up. It just seemed something of a blindly
obvious statement; surely nobody would expect an RPM
ate: Tue, 22 Sep 2020 10:18:05 +0100
From: Jonathan Buzzard
To: gpfsug main discussion list
Subject: [gpfsug-discuss] Portability interface
Message-ID: <4b586251-d208-8535-925a-311023af3...@strath.ac.uk>
Content-Type: text/plain; charset=utf-8; format=flowed
I have a question about us
We've used the same built RPMs (generally built on Intel) on Intel and AMD
x86-64 CPUs, and definitely have a mix of ISAs from both vendors, and
haven't run into any problems.
On Tue, Sep 22, 2020 at 10:18:05AM +0100, Jonathan Buzzard wrote:
>
> I have a question about using RPM's for the
We've always taken it to mean ..
RHEL != CentOS
7.1 != 7.2 (though mostly down to the kernel).
ppc64le != x86_64
But never differentiated by microarchitecture. That doesn't mean to say we are
correct in these assumptions __
Simon
On 22/09/2020, 10:17,
I have a question about using RPM's for the portability interface on
different CPU's.
According to /usr/lpp/mmfs/src/README
The generated RPM can ONLY be deployed to the machine with
identical architecture, distribution level, Linux kernel version
and GPFS version.
So does this
