Some modules .so are stripped while others are not

[g4-lisz at tonarchiv.ch]

May 18, 2026 at 4:33 PM, "Alan DeKok via Freeradius-Users" <freeradius-users at lists.freeradius.org mailto:freeradius-users at lists.freeradius.org?to=%22Alan%20DeKok%20via%20Freeradius-Users%22%20%3Cfreeradius-users%40lists.freeradius.org%3E > wrote

> 
> You can run `VERBOSE=1 make install`, and see exactly what commands it's running to build and install things. Then, look at those commands to see which (if any) modules are being stripped.
> 
>  All of the modules are built with the same CFLAGS, LDFLAGS, etc. All of the modules are installed with the same scripts. So there shouldn't be any differences between them.
> 
>  Alan DeKok.
> 
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
> 
Sorry, our last emails crossed...

I didn't complain that something isn't working. I was just wondering if there's some magic configuration.

Thanks for the hint with VERBOSE env  variable.

BTW, the actual problem has now been solved:
Valgrind complained about some read access to uninitialized memory.
I did some debugging and this revealed that it was a false positive from talloc_pool_internal_reads().

This makes valgrind happy:
-suppressions= ...

{
   talloc_pool_internal_reads
   Memcheck:Cond
   obj:*/libtalloc.so*
}

Cheers
Till