Mailinglist Archive: opensuse-buildservice (132 mails)

< Previous Next >
Re: [opensuse-buildservice] [RFC] Is there any plan to add ILP32 support for aarch64?
  • From: Bamvor Jian Zhang <bamvor.zhangjian@xxxxxxxxxx>
  • Date: Tue, 27 Jan 2015 17:20:02 +0800
  • Message-id: <>
On 2015/1/26 17:57, Jan Engelhardt wrote:

On Monday 2015-01-26 10:30, Bamvor Jian Zhang wrote:

I got 4 commit about aarch64 in obs source code[openbuildservice] with
"git log --grep aarch64":
effc064 [backend] aarch64 workers can also build 32bit arm
e0bd2e5 [api] add aarch64 to xml schema file
b71ecfe [api] add aarch64 architecture
0c08cbe [backend] add aarch64 architecture

But I still not puzzled about how to start.

I also found some Linux32 definitions in obs source code[openbuildservice],
does it
mean the ilp32 is supported on the following architecture?

src/backend/ 'x86_64' => [ 'x86_64', 'i586:linux32',
'i686:linux32' ],
src/backend/ 'sparc64' => [ 'sparc64v', 'sparc64',
'sparcv9v', 'sparcv9', 'sparcv8:linux32', 'sparc:linux32' ],

This table maps `uname -m` to packages that can be built (using :helper).

'x86_64' => [ 'x86_64', 'x32', 'i586:linux32', ...]

Similar for arm.
got it. thanks.

BTW: basically, add ilp32 support means that adding ilp32 support to kernel,
gcc and glibc. And pass CC or CXX with additional -mabi=ilp32 to overwrite
default -mabi=lp64 when building the packages.

This is better done in /usr/lib/rpm/rpmrc:

optflags: x86_64 -O2 -g -m64 -D_FORTIFY_SOURCE=2 ...
optflags: x32 -O2 -g -mx32 -D_FORTIFY_SOURCE=2 ...

which means rpm itself needs to be augmented first.

I am not familiar with rpm internal. I guess you suggest me that add ilp32
support for rpm first?

Just like the x32 patch from H.J. Lu[1]?




To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx

< Previous Next >