#371 closed defect (invalid)
bug with glibc-2.2.5
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Book | Version: | 3.0-pre3 |
| Severity: | normal | Keywords: | |
| Cc: |
Description
when I try to install glibc-2.2.5 on my linux from scratch, I have the following problem : error 127 after the make
echo 'sysd-rules-done = t') >
/usr/src/pack/lfs-packages-3.3/glibc-build/sysd-rulesT mv -f /usr/src/pack/lfs-packages-3.3/glibc-build/sysd-rulesT /usr/src/pack/lfs-packages-3. 3/glibc-build/sysd-rules '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 linuxthreads/sysdeps/pthread/Subdirs sysdeps/unix/inet/Subdirs
sysdeps/un ix/Subdirs > /usr/src/pack/lfs-packages-3.3/glibc-build/sysd-dirs-tmp /bin/sh: BEGIN { subdirs = ""; inhibit = "" }; /#/ { next }; /[-]/ { subdirs = subdirs " " $0 }; /-/ { inhibit = inhibit " " subs tr($0, 2) }; END { printf "sysdep-subdirs =%s\n", subdirs;
printf "s
ysdep-inhibit-subdirs =%s\n", inhibit; print "sysd-dirs-done = t" }: No such file or dir ectory make[1]: * usr/src/pack/lfs-packages-3.3/glibc-build/sysd-dirs Error 127 make[1]: Leaving directory `/usr/src/pack/lfs-packages-3.3/glibc-2.2.5' make: * [all] Error 2
please help me if you have already got this problem or if you know how to solve it.
Change History (2)
comment:1 by , 22 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:2 by , 22 years ago
I haven't checked the support list yet, can't do it tonight so I"ll post my comment here for the time being (will follow up on the support list as well if I find your post there): the error from Glibc is probably caused by your 'mawk' not present or not statically linked.
Exit chroot, go back to chapter 5, reinstall Mawk and try Glibc again.
Hi!
Can you please send the full error message to the lfs-support mailing list?
The address is lfs-support@… - if you're not subscribed, either subscribe or ask people to CC you in their replies.
What you've pasted below isn't really enough to help - if the full log is too big, gzip or bzip2 it and send it as an attachment.
Hope this helps
Mark