[lfs-support] problem with glibc

Ken Moffat zarniwhoop at ntlworld.com
Mon Apr 2 05:09:56 PDT 2012

On Mon, Apr 02, 2012 at 08:28:09AM +0530, ankit vishwakarma wrote:
> after having changed the symlink from dash to bash and again starting the
> process the error in glibc still persists please provide help
> In file included from ../sysdeps/unix/sysv/linux/syslog.c:10:0:
> ../misc/syslog.c: In function '__vsyslog_chk':
> ../misc/syslog.c:144:9: warning: variable 'prioff' set but not used
> [-Wunused-but-set-variable]
> ../misc/syslog.c:123:1: sorry, unimplemented: inlining failed in call to
> 'syslog': function body not available
> ../misc/syslog.c:155:9: sorry, unimplemented: called from here
> make[2]: *** [/mnt/lfs/sources/glibc-build/misc/syslog.o] Error 1
> make[2]: Leaving directory `/mnt/lfs/sources/glibc-2.14.1/misc'
> make[1]: *** [misc/subdir_lib] Error 2
> make[1]: Leaving directory `/mnt/lfs/sources/glibc-2.14.1'
> make: *** [all] Error 2
> lfs at ankit-Inspiron-1012:/mnt/lfs/sources/glibc-build$
> Thank You

 Google suggests that you need to add -U_FORTIFY_SOURCE to your
CFLAGS.  One of the reports suggested that you need to do this when
building *gcc*.  The problems seems to be that ubuntu's toolchain is
built with -D_FORTIFY_SOURCE.  No idea why this only bites people

  FWIW, I searched google looking for:
 misc syslog.c 123 sorry unimplemented

 As usual, some of the threads had no solution, but several pointed
to this solution.  Google isn't as easy to use as it used to be (for
"technical" searches - it no longer respects quotes enclosing
strings, and similarly ignores characters such as '/'), but it often
does still know the answers!

das eine Mal als Tragödie, das andere Mal als Farce

More information about the lfs-support mailing list