Bug 1215812

Summary:	cross-ppc64le-gcc no longer built for SLE
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Michal Suchanek <msuchanek>
Component:	Development	Assignee:	E-mail List <screening-team-bugs>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	msuchanek
Version:	Current
Target Milestone:	---
Hardware:	Other
OS:	Other
See Also:	https://bugzilla.suse.com/show_bug.cgi?id=1214460
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Michal Suchanek 2023-09-28 12:51:14 UTC

The devel:gcc project no longer has cross-compilers built for SLE.

We use these cross-compilers to test building the kernel on different platforms.

Comment 1 Richard Biener 2023-09-28 13:18:34 UTC

Yes, we're not keeping both "modes" but now build the "real" cross compilers where possible.  You can use the cross-ppc64le-gcc13-bootstrap packages
though, those still contain the "freestanding" variant and the -bootstrap
packages are always built since they do not depend on the cross glibc.

Does that provide everything necessary?

Comment 2 Michal Suchanek 2023-09-28 13:40:13 UTC

At the very least it does not provide the package name.

I will try using the bootstrap compiler and see if that works.

Comment 3 Michal Suchanek 2023-09-28 14:35:30 UTC

I was able to aggregate the bootstrap compilers on SLE15 bu on SLE12 the cross-gcc does not build because of missing cross-binutils.

Comment 4 Richard Biener 2023-09-29 06:15:12 UTC

But with missing cross-binutils how could you cross-compile kernels there?  This can hardly be a regression then?  ISTR you are (re-)building packages somewhere, so I suggest you (re-)build binutils as fit.

You can also cross-compile for SLE12 from SLE15.

Comment 5 Michal Suchanek 2023-09-29 08:44:37 UTC

They are not missing, they are missing the 'use for build' flag.

And of course, any historical packages remain.

Comment 6 Michal Suchanek 2023-10-02 10:03:14 UTC

(In reply to Richard Biener from comment #4)
> But with missing cross-binutils how could you cross-compile kernels there? 
> This can hardly be a regression then?  ISTR you are (re-)building packages
> somewhere, so I suggest you (re-)build binutils as fit.
> 
> You can also cross-compile for SLE12 from SLE15.

However, that means going into the server room and putting SLE15 boot media into the builders.

I needed to reinstall a machine anyway so I also migrated the builders, with this I don't really need to have cross-compilers on SLE12.

(In reply to Michal Suchanek from comment #5)
> They are not missing, they are missing the 'use for build' flag.
> 
> And of course, any historical packages remain.

Which I suppose would be the fallout of using multibuild instead of package links. With package links the flags can be specified per package, with multibuild they cannot.