Re: Build Failed for RISC-V Image Using isar/kas-container

[Uladzimir Bely <ubely@ilbers.de>]

On Tue, 2025-04-22 at 21:14 +0800, Sun, Yi wrote:
> On 17.04.2025 08:58, Uladzimir Bely wrote:
> > 
> > Hello.
> > 
> > This looks like a temporary bug, when `ubuntu-ports` repo is
> > temporary
> > not synchronized with `ubuntu` one. We periodicaly face it and
> > can't do
> > anything with it.
> > 
> > I also this issue now when crossbuilding riscv64 and arm64 ubuntu-
> > noble
> > targets. It was not reproduced week ago.
> > 
> > There are two options to get a successfull build:
> > 
> > 1. Disable cross-compile option - but it is relatively slow.
> > 2. Use some snapshot that is known to work.
> > 
> > For example, this additional configuration (I used one-week-ago
> > snapshot) works for me:
> > 
> > ```
> > Mirror selection
> > - [*] Use the distros snapshot mirror
> >  - (*) Custom date
> >    - (20250410T000000Z) Custom snapshot date
> > ```
> > 
> > I'm attaching kas configuration I can get working build with.
> 
> Hi Uladzimir,
> 
> I'm adding some actual .bb files for my project and have a few
> questions.
> 
> 1, It seems the installation of the linux-libc-dev package is failing
> in the host rootfs.
> Have you happened to run into this issue before?
> 
> ```
> > Broken libc6-dev:amd64 Depends on linux-libc-dev:amd64 < none @un
> > pH >                                        
> >   Considering linux-libc-dev:amd64 1 as a solution to libc6-
> > dev:amd64 24                                      
> >   Considering linux-libc-dev:amd64 1 as a solution to libc6-
> > dev:amd64 24                                      
> > Done                                                               
> >                                            
> > Some packages could not be installed. This may mean that you
> > have                                             
> > requested an impossible situation or if you are using the
> > unstable                                            
> > distribution that some required packages have not yet been
> > created                                            
> > or been moved out of
> > Incoming.                                                          
> >                       
> > The following information may help to resolve the
> > situation:                                                  
> >                                                                    
> >                                            
> > The following packages have unmet
> > dependencies:                                                      
> >          
> >  libc6-dev : Depends: linux-libc-dev but it is not
> > installable                                                
> > E: Unable to correct problems, you have held broken
> > packages.                                                 
> > WARNING: exit code 100 from a shell
> > command.                                                           
> >        
> > DEBUG: Executing shell function
> > rootfs_do_umounts                                                  
> >            
> > DEBUG: Shell function rootfs_do_umounts
> > finished                                                           
> >    
> > DEBUG: Python function do_rootfs_install
> > finished                                                           
> >   
> ERROR: Task (/build/../repo/meta-isar/recipes-devtools/sbuild-
> chroot/sbuild-chroot-host-db2m.bb:do_rootfs_install) failed with exit
> code '1'                                                            
> ```
> 

Yes, it happend at least previous week (not only for riscv64, but also
for e.g. arm64) and using snapshot was a working solution.

You can see this issue in e.g. CrossTest.test_cross in our Gitlab CI
https://gitlab.isar-build.org/ilbers/isar/-/jobs/2159 

Today it seems to be fixed by ubuntu upstream just works with main
ubuntu/ubuntu-ports repos.

> 2, So I tried disabling cross-build working aroud above issue. As you
> mentioned, the performance is quite poor.
> Would you mind explaining a bit more about why that happens? And is
> there anything I can do to improve it?

Sometimes such problems can happen in upstream (ubuntu and debian)
repos. We can't do anything with it except to using snapshots known to
be working/stable.

> 
> 3, Do you have an estimated timeline for the v0.10 release?
> 
> Thanks
>     --Sun, Yi

0.11 is going to be released soon, maybe even by the end of this week
or. After that riscv64/noble patches will be sent to the maillist and
merged soon. For now, you can recheck my 'ubely/riscv64' branch I tend
to keep updated and thus force-pushed sometimes.

-- 
Best regards,
Uladzimir.


-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/bda953bba6e5e37943db310a28b9cabdc6f0ff4a.camel%40ilbers.de.