Diego Nieto Cid, le dim. 25 mai 2025 20:40:18 +0100, a ecrit:
> > 
> > Perhaps you are missing the libc.so.0.3 -> libc.so symlink in your build
> > directory? or elf/ld-x86-64.so.1 -> ld.so? or mach/libmachuser.so.1 ->
> > libmachuser.so or hurd/libhurduser.so.0.3 -> libhurduser.so
> > 
> 
> Hmm, it doesn't seem to be the case:
> 
>     demo@debian:~/dev/hurd/upstream/glibc-build$ ls -l *.so* elf/*.so* 
> mach/*.so* hurd/*.so*
>       -rwxrwxr-x 1 demo demo  1398528 May 24 19:34 elf/ld.so
>     * lrwxrwxr-x 1 demo demo        5 May 24 19:34 elf/ld-x86-64.so.1 -> ld.so
>       -rwxrwxr-x 1 demo demo    36928 May 24 19:34 elf/sotruss-lib.so
>       -rwxrwxr-x 1 demo demo  1733416 May 23 23:05 hurd/libhurduser-link.so
>       -rwxrwxr-x 1 demo demo  1741152 May 24 19:34 hurd/libhurduser.so
>     * lrwxrwxr-x 1 demo demo       14 May 24 19:34 hurd/libhurduser.so.0.3 -> 
> libhurduser.so
>       -rwxrwxr-x 1 demo demo 14449640 May 24 19:34 libc.so
>     * lrwxrwxr-x 1 demo demo        7 May 23 23:41 libc.so.0.3 -> libc.so
>       -rwxrwxr-x 1 demo demo   636000 May 23 23:04 mach/libmachuser-link.so
>       -rwxrwxr-x 1 demo demo   639368 May 24 19:34 mach/libmachuser.so
>     * lrwxrwxr-x 1 demo demo       14 May 24 19:34 mach/libmachuser.so.1 -> 
> libmachuser.so

That looks good indeed.

> Or should I have them in the root build directory next to libc.so?

No, testrun.sh sets the ld search path properly.

> I feel being clueless I'm wasting everybody's time here, sorry. Maybe I 
> should try from a clean
> VM and glibc source tree, although I don't think my changes make any 
> difference.

It could make a difference. Better make sure that a pristine tree works
fine, for a start.

Samuel

Reply via email to