Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 53218 - glibc-2.3.3.20040420 failed to compile complaining about asm/unistd.h many times
Summary: glibc-2.3.3.20040420 failed to compile complaining about asm/unistd.h many t...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High critical
Assignee: Gentoo Toolchain Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-07 07:14 UTC by Lukas Kutner
Modified: 2004-07-01 05:39 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge output (glibc.log,82.18 KB, text/plain)
2004-06-07 07:32 UTC, Lukas Kutner
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lukas Kutner 2004-06-07 07:14:38 UTC
I tried to update glibc today and this error appeared:

repeats many times : 
In file included from sysdeps/unix/sysdep.h:21,
                 from sysdeps/unix/i386/sysdep.h:19,
                 from sysdeps/unix/sysv/linux/i386/sysdep.h:24,
                 from <stdin>:1:
sysdeps/unix/sysv/linux/sys/syscall.h:25:24: asm/unistd.h: No such file or directory
In file included from sysdeps/unix/sysdep.h:21,
                 from sysdeps/unix/i386/sysdep.h:19,
                 from sysdeps/unix/sysv/linux/i386/sysdep.h:24,
                 from <stdin>:1:
sysdeps/unix/sysv/linux/sys/syscall.h:25:24: asm/unistd.h: No such file or directory
In file included from sysdeps/unix/sysdep.h:21,
                 from sysdeps/unix/i386/sysdep.h:19,
                 from sysdeps/unix/sysv/linux/i386/sysdep.h:24,
                 from <stdin>:1:
sysdeps/unix/sysv/linux/sys/syscall.h:25:24: asm/unistd.h: No such file or directory
mv -f /var/tmp/portage/glibc-2.3.3.20040420/work/glibc-2.3.2/buildhere/sysd-syscallsT /var/tmp/portage/glibc-2.3.3.20040420/work/glibc-2.3.2/buildhere/sysd-syscalls
gawk 'BEGIN { subdirs = ""; inhibit = "" };                     \
/^#/ { next };                                          \
/^[^-]/ { subdirs = subdirs " " $0 };                   \
/^-/ { inhibit = inhibit " " substr($0, 2) };           \
END { printf "sysdep-subdirs =%s\n", subdirs;           \
      printf "sysdep-inhibit-subdirs =%s\n", inhibit;   \
      print "sysd-dirs-done = t" }'                     \
       /dev/null nptl/sysdeps/pthread/Subdirs sysdeps/unix/inet/Subdirs sysdeps/unix/Subdirs > /var/tmp/portage/glibc-2.3.3.20040420/work/glibc-2.3.2/buildhere/sysd-dirs-tmp
mv -f /var/tmp/portage/glibc-2.3.3.20040420/work/glibc-2.3.2/buildhere/sysd-dirs-tmp /var/tmp/portage/glibc-2.3.3.20040420/work/glibc-2.3.2/buildhere/sysd-dirs
make[1]: Leaving directory `/var/tmp/portage/glibc-2.3.3.20040420/work/glibc-2.3.2'
make[1]: Entering directory `/var/tmp/portage/glibc-2.3.3.20040420/work/glibc-2.3.2'
{ echo '#include "posix/bits/posix1_lim.h"';            \
  echo '#define _LIBC 1';                                       \
  echo '#include "misc/sys/uio.h"'; } |                 \
gcc -E -dM -MD -MP -MF /var/tmp/portage/glibc-2.3.3.20040420/work/glibc-2.3.2/buildhere/bits/stdio_lim.dT -MT '/var/tmp/portage/glibc-2.3.3.20040420/work/glibc-2.3.2/buildhere/bits/stdio_lim.h /var/tmp/portage/glibc-2.3.3.20040420/work/glibc-2.3.2/buildhere/bits/stdio_lim.d'     \
      -Iinclude -I. -I/var/tmp/portage/glibc-2.3.3.20040420/work/glibc-2.3.2/buildhere  -Ilibio -Inptl -I/var/tmp/portage/glibc-2.3.3.20040420/work/glibc-2.3.2/buildhere -Isysdeps/i386/elf -Inptl/sysdeps/unix/sysv/linux/i386/i686 -Inptl/sysdeps/unix/sysv/linux/i386 -Inptl/sysdeps/unix/sysv/linux -Inptl/sysdeps/pthread -Isysdeps/pthread -Inptl/sysdeps/unix/sysv -Inptl/sysdeps/unix -Inptl/sysdeps/i386/i686 -Inptl/sysdeps/i386 -Isysdeps/unix/sysv/linux/i386 -Isysdeps/unix/sysv/linux -Isysdeps/gnu -Isysdeps/unix/common -Isysdeps/unix/mman -Isysdeps/unix/inet -Isysdeps/unix/sysv/i386 -Isysdeps/unix/sysv -Isysdeps/unix/i386 -Isysdeps/unix -Isysdeps/posix -Isysdeps/i386/i686/fpu -Isysdeps/i386/i686 -Isysdeps/i386/i486 -Inptl/sysdeps/i386/i486 -Isysdeps/i386/fpu -Isysdeps/i386 -Isysdeps/wordsize-32 -Isysdeps/ieee754/ldbl-96 -Isysdeps/ieee754/dbl-64 -Isysdeps/ieee754/flt-32 -Isysdeps/ieee754 -Isysdeps/generic/elf -Isysdeps/generic -nostdinc -isystem /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.3/include -isystem /lib/modules/2.6.4-rc2-love1/build/include -xc - -o /var/tmp/portage/glibc-2.3.3.20040420/work/glibc-2.3.2/buildhere/bits/stdio_lim.hT
In file included from posix/bits/posix1_lim.h:130,
                 from <stdin>:1:
nptl/sysdeps/unix/sysv/linux/bits/local_lim.h:36:26: linux/limits.h: No such file or directory
make[1]: *** [/var/tmp/portage/glibc-2.3.3.20040420/work/glibc-2.3.2/buildhere/bits/stdio_lim.st] Error 1
make[1]: Leaving directory `/var/tmp/portage/glibc-2.3.3.20040420/work/glibc-2.3.2'
make: *** [all] Error 2

!!! ERROR: sys-libs/glibc-2.3.3.20040420 failed.
!!! Function src_compile, Line 547, Exitcode 2
!!! (no error message)

Reproducible: Always
Steps to Reproduce:
1. emerge -u glibc
2.
3.

Actual Results:  
glibc failed to emerge

Expected Results:  
It should emerge glibc-2.3.3.20040420

Portage 2.0.50-r7 (default-x86-1.4, gcc-3.3.3, glibc-2.3.3_pre20040420-r0,
2.6.4-rc2-love1)
=================================================================
System uname: 2.6.4-rc2-love1 i686 Celeron (Mendocino)
Gentoo Base System version 1.4.16
distcc 2.14 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
ccache version 2.3 [enabled]
Autoconf: sys-devel/autoconf-2.59-r4
Automake: sys-devel/automake-1.8.5
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-march=pentium2 -O3 -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref
/usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=pentium2 -O3 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="http://gentoo.ynet.sk/pub
ftp://ftp.ipv6.uni-muenster.de/pub/linux/distributions/gentoo
ftp://vlaai.snt.ipv6.utwente.nl/pub/os/linux/gentoo/ http://128.213.5.34/gentoo/
http://vlaai.snt.ipv6.utwente.nl/pub/os/linux/gentoo/"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage /usr/local/bmg-main"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="X apache2 berkdb crypt cups encode foomaticdb gd gdbm gif gpm gtk gtk2
imlib ipv6 java jpeg leim libwww mmx motif mozilla mysql ncurses nls nptl opengl
pam pdflib perl png python qt readline sdl slang spell ssl svga tcpd truetype
type1 x86 xml xml2 xmms zlib"
Comment 1 Lukas Kutner 2004-06-07 07:32:59 UTC
Created attachment 32861 [details]
emerge output
Comment 2 Lukas Kutner 2004-06-07 09:35:49 UTC
well I changed my kernel to 2.6.5-love5 and it works now
Comment 3 Jared Rhine 2004-06-30 17:57:48 UTC
Same thing happens for me.  It broke around the same time I did a linux-headers remerge and I can see a possible relationship given the "asm/unistd.h" error.   I'm running 2.6.7 stock.  Is it ok to be running linux-headers-2.4.22 when I'm running a 2.6 kernel?  I can remerge linux-headers without problems, but not glibc.  I do have a /usr/include/asm/unistd.h file in place.  I will investigating issues related to my /usr/src tree.  There's probably a problem in include directory there, or with one of the symlinks pointed there.  A kernel rebuild/reinstall might do the trick.
Comment 4 Jared Rhine 2004-06-30 21:22:08 UTC
Yup, a kernel rebuild/install cycle fixed whatever include files and/or symlinks had gotten out of whack with my actual runtime, and glibc now emerges fine.

Recommend closing this bug as not a bug.  It's not in glibc, it's not in emerge, it's not reproducible.  (Though I'm sure toolchain@gentoo.org already knew that :)  The official workaround can be "reinstall the kernel".  
Comment 5 Travis Tilley (RETIRED) gentoo-dev 2004-07-01 05:39:36 UTC
btw, linux-headers 2.6.6-r1 seems pretty bug-less. these are currently the suggested 2.6 headers. and no, it isnt a problem to use 2.4 headers while running a 2.6 kernel.