From: "Benjamin Menküc" <benmen@gmx.de>
To: Daniel Jacobowitz <dan@debian.org>
Cc: linux-mips@linux-mips.org
Subject: Re: compiling glibc
Date: Sun, 11 May 2003 02:35:14 +0200 [thread overview]
Message-ID: <200305110235.14606.benmen@gmx.de> (raw)
In-Reply-To: <20030510194351.GA15891@nevyn.them.org>
Hi,
now I get this weird error:
...
make[2]: Entering directory `/home/benmen/mips/glibc-cvs/misc'
rm -f /home/benmen/mips/mipsel-glibc/misc/syscall-list.d-t
{ \
echo '/* Generated at libc build time from kernel syscall list. */';\
echo ''; \
echo '#ifndef _SYSCALL_H'; \
echo '# error "Never use <bits/syscall.h> directly; include <sys/syscall.h>
instead."'; \
echo '#endif'; \
echo ''; \
rm -f /home/benmen/mips/mipsel-glibc/misc/syscall-list.h.newt; \
SUNPRO_DEPENDENCIES='/home/benmen/mips/mipsel-glibc/misc/syscall-list.d-t
/home/benmen/mips/mipsel-glibc/misc/syscall-list.d' \
mipsel-linux-gcc -mabi=32 -E -x c -I /home/benmen/mips/mipsel-glibc -nostdinc
-isystem /home/benmen/mipsel/lib/gcc-lib/mipsel-linux/3.2.3/include -isystem
/home/benmen/mips/kernel/mips-2.4.20/include
../sysdeps/unix/sysv/linux/mips/sys/syscall.h -D_LIBC -dM | \
sed -n 's@^#define __NR_\([^ ]*\) .*$@#define SYS_\1 __NR_\1@p' >
/home/benmen/mips/mipsel-glibc/misc/syscall-list.h.newt; \
if grep SYS_O32_ /home/benmen/mips/mipsel-glibc/misc/syscall-list.h.newt >
/dev/null; then \
echo '#if defined _ABI64 && _MIPS_SIM == _ABI64'; \
sed -n 's/^\(#define SYS_\)N64_/\1/p' <
/home/benmen/mips/mipsel-glibc/misc/syscall-list.h.newt; \
echo '#elif defined _ABIN32 && _MIPS_SIM == _ABIN32'; \
sed -n 's/^\(#define SYS_\)N32_/\1/p' <
/home/benmen/mips/mipsel-glibc/misc/syscall-list.h.newt; \
echo '#else'; \
sed -n 's/^\(#define SYS_\)O32_/\1/p' <
/home/benmen/mips/mipsel-glibc/misc/syscall-list.h.newt; \
echo '#endif'; \
sed -n '/^#define SYS_\([ON]32\|N64\)_/p' <
/home/benmen/mips/mipsel-glibc/misc/syscall-list.h.newt; \
else \
cat /home/benmen/mips/mipsel-glibc/misc/syscall-list.h.newt; \
fi; \
rm /home/benmen/mips/mipsel-glibc/misc/syscall-list.h.newt; \
} > /home/benmen/mips/mipsel-glibc/misc/syscall-list.h.new
/bin/sh: line 1: /home/benmen/mips/mipsel-glibc/misc/syscall-list.h.new: Datei
oder Verzeichnis nicht gefunden
mv -f /home/benmen/mips/mipsel-glibc/misc/syscall-list.h.new
/home/benmen/mips/mipsel-glibc/misc/syscall-list.h
mv: Aufruf von stat für
»/home/benmen/mips/mipsel-glibc/misc/syscall-list.h.new« nicht möglich: Datei
oder Verzeichnis nicht gefunden
make[2]: *** [/home/benmen/mips/mipsel-glibc/misc/syscall-list.d] Fehler 1
make[2]: Leaving directory `/home/benmen/mips/glibc-cvs/misc'
make[1]: *** [misc/subdir_lib] Fehler 2
make[1]: Leaving directory `/home/benmen/mips/glibc-cvs'
make: *** [all] Fehler 2
Verzeichnis: ~/mips/mipsel-glibc
[benmen@linuxpc1 mipsel-glibc]
regards,
Ben
next prev parent reply other threads:[~2003-05-11 0:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 19:45 compiling glibc Benjamin Menküc
2003-05-09 21:45 ` Thiemo Seufer
2003-05-10 1:03 ` Benjamin Menküc
2003-05-10 4:25 ` Daniel Jacobowitz
2003-05-10 9:56 ` Benjamin Menküc
2003-05-10 11:21 ` Benjamin Menküc
2003-05-10 19:43 ` Daniel Jacobowitz
2003-05-11 0:35 ` Benjamin Menküc [this message]
2003-05-11 9:28 ` Guido Guenther
2003-05-11 10:52 ` Benjamin Menküc
2003-05-11 11:00 ` Benjamin Menküc
2003-05-11 21:48 ` Guido Guenther
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200305110235.14606.benmen@gmx.de \
--to=benmen@gmx.de \
--cc=dan@debian.org \
--cc=linux-mips@linux-mips.org \
--cc=menkuec@auto-intern.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox