Summary: | sys-fs/mdadm-3.1.4[static] shows warnings that may indicate a real problem | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sebastian Pipping <sping> |
Component: | New packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | CC: | genkernel, sping |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 282100 |
expected behavior for glibc static linking Does that mean, the "static" mdadm binary is in fact NOT static but depends on libc.so ? In that case, an obvious fix is to remove the "static" USEFLAG from mdadm. Alternatively those function could be replaced in the upstream code I suppose ... you're talking a problem specific to *glibc* we're not planning on patching glibc in any way to address this. feel free to complain upstream, but they've already made it clear they dont care. |
# USE=static CFLAGS="-Wall" ebuild mdadm-3.1.4.ebuild clean compile [..] config.o: In function `createline': config.c:(.text+0xc07): warning: Using 'getgrnam' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking config.c:(.text+0xb2a): warning: Using 'getpwnam' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking config.o: In function `createline': config.c:(.text+0xc07): warning: Using 'getgrnam' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking config.c:(.text+0xb2a): warning: Using 'getpwnam' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking >>> Source compiled. Any ideas?