Package: qemu-user-static
Version: 1.0~rc4+dfsg-1
Severity: important

the 1.0 series of qemu seems to have implemented some portions of the 
qemu-user static variants that require shared libraries... worked fine with 
qemu 0.15 and earlier.

during build, i see these warnings:

  
/usr/lib/gcc/i486-linux-gnu/4.6/../../../i386-linux-gnu/libglib-2.0.a(gutils.o):
 In function `g_get_any_init_do':
  (.text+0xe37): warning: Using 'getpwuid' in statically linked applications 
requires at runtime the shared libraries from the gli
  bc version used for linking
  
/usr/lib/gcc/i486-linux-gnu/4.6/../../../i386-linux-gnu/libglib-2.0.a(gutils.o):
 In function `g_get_any_init_do':
  (.text+0xe2a): warning: Using 'setpwent' in statically linked applications 
requires at runtime the shared libraries from the gli
  bc version used for linking
  
/usr/lib/gcc/i486-linux-gnu/4.6/../../../i386-linux-gnu/libglib-2.0.a(gutils.o):
 In function `g_get_any_init_do':
  (.text+0xe40): warning: Using 'endpwent' in statically linked applications 
requires at runtime the shared libraries from the gli
  bc version used for linking
  
/usr/lib/gcc/i486-linux-gnu/4.6/../../../i386-linux-gnu/libglib-2.0.a(gutils.o):
 In function `g_get_any_init_do':
  (.text+0xb7a): warning: Using 'getpwnam_r' in statically linked applications 
requires at runtime the shared libraries from the g
  libc version used for linking
  
/usr/lib/gcc/i486-linux-gnu/4.6/../../../i386-linux-gnu/libglib-2.0.a(gutils.o):
 In function `g_get_any_init_do':
  (.text+0xbbb): warning: Using 'getpwuid_r' in statically linked applications 
requires at runtime the shared libraries from the g
  libc version used for linking


which also shown on the buildds:

  
https://buildd.debian.org/status/fetch.php?pkg=qemu&arch=amd64&ver=1.0%7Erc4%2Bdfsg-1&stamp=1322591568
   

not surprisingly, calls to programs such as adduser within a cross 
architecture chroot fail, which limit their usefulness.

live well,
  vagrant



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to