Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #81470 > unrolled thread

Bug#1040663: linux: Please build linux-libc-dev package for loong64

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1040663: linux: Please build linux-libc-dev package for loong64 Adrian Bunk <bunk@debian.org> - 2024-01-06 20:30 +0100

#81470 — Bug#1040663: linux: Please build linux-libc-dev package for loong64

On Wed, Jul 12, 2023 at 11:07:12AM +0200, Bastian Blank wrote:
> Control: tags -1 confirmed
> 
> Hi
> 
> On Sat, Jul 08, 2023 at 08:41:03PM +0200, John Paul Adrian Glaubitz wrote:
> > Please enable building the linux-libc-dev package for the new Debian architecture loong64.
> > The corresponding kernel architecture is called "loongarch".
> 
> I can't find loong64 in the debian architecture table used on
> ftp-master, so we can't add it yet.

This changed in 6.6.8-1 where you made the linux-libc-dev package 
binary-all. The problem you mention no longer exists in this form,
but not having loong64 headers in the now binary-all package made
many packages FTBFS on loong64.

Please add support for linux-libc-dev-only architectures in 
debian/bin/gencontrol.py.

With a binary-all linux-libc-dev it does still work to have a different 
src:linux in unreleased, but linux-libc-dev does now break every time 
src:linux gets updated since a binary-all package 6.6.10-1 has a higher 
version than linux-libc-dev_6.6.9+loong64 in unreleased.

In practice this means that linux-libc-dev must ship headers at the 
latest when an architecture gets added in ports, far earlier than
building kernel images (which as you said might require other changes
on the ftp-master side).

> Bastian

Thanks
Adrian

[toc] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web