That's why I suggest use a simple main() and makefile. Then you link them explicitly. Rump is linked statically I believe. It is supposed to support dynamic linkage but I don't think I got it to work that way yet.
Damien Sent from Proton Mail Android -------- Original Message -------- On 21/4/25 10:13 am, Zhaoming Luo <zhming...@163.com> wrote: > On Sun, Apr 20, 2025 at 10:49:41PM +0000, Damien Zammit wrote: > > Hi, > > > > Which rump libraries are you linking to? Its vital to link to the right > ones. Part of the challenge is working out which ones. > > > It's indeed more challenging than I thought. I supposed I can see the > linked rump library using ldd, but it seems it's not the correct way: > ``` > demo@debian:~/hurd$ ldd build/rumpplay/rumpplay > libirqhelp.so.0.3 => /lib/i386-gnu/libirqhelp.so.0.3 (0x011ff000) > libpthread.so.0.3 => /lib/i386-gnu/libpthread.so.0.3 (0x01203000) > libpciaccess.so.0 => /lib/i386-gnu/libpciaccess.so.0 (0x01214000) > libc.so.0.3 => /lib/i386-gnu/libc.so.0.3 (0x01220000) > libmachuser.so.1 => /lib/i386-gnu/libmachuser.so.1 (0x0149a000) > libhurduser.so.0.3 => /lib/i386-gnu/libhurduser.so.0.3 (0x014b1000) > /lib/ld.so => /lib/ld.so.1 (0x00001000) > libz.so.1 => /lib/i386-gnu/libz.so.1 (0x014e2000) > ``` > > So I cannot rely on ldd. How to solve this challenge? > > Zhaoming > >
