From: Maxim Osipov <maxim.osipov@gmail.com>
To: linux-mips@linux-mips.org
Subject: glibc-2.3.4 mips64 compilation failure
Date: Thu, 26 May 2005 20:32:59 +0400 [thread overview]
Message-ID: <6097c4905052609326a4c1232@mail.gmail.com> (raw)
Hello,
I am trying to build glibc-2.3.4 using binutils-2.15 and gcc-3.4.3
from ftp://ftp.linux-mips.org/pub/linux/mips/crossdev/i386-linux/mips64-linux.
Compilation fails with following messages:
clude/libc-symbols.h -DPIC -DASSEMBLER -x assembler-with-cpp -o
/home/maxim/temp/build-glibc/io/sendfile.o -
.././scripts/mkinstalldirs /home/maxim/temp/build-glibc/io
(echo '#include <sysdep.h>'; \
echo 'PSEUDO (sendfile64, sendfile64, 4)'; \
echo ' ret'; \
echo 'PSEUDO_END(sendfile64)'; \
echo 'libc_hidden_def (sendfile64)'; \
) | mips64-linux-gcc -mabi=64 -c -I../include -I.
-I/home/maxim/temp/build-glibc/io -I.. -I../libio
-I/home/maxim/temp/build-glibc -I../sysdeps/mips/elf
-I../linuxthreads/sysdeps/unix/sysv/linux/mips/mips64
-I../linuxthreads/sysdeps/unix/sysv/linux/mips
-I../linuxthreads/sysdeps/unix/sysv/linux
-I../linuxthreads/sysdeps/pthread -I../sysdeps/pthread
-I../linuxthreads/sysdeps/unix/sysv -I../linuxthreads/sysdeps/unix
-I../linuxthreads/sysdeps/mips
-I../sysdeps/unix/sysv/linux/mips/mips64/n64
-I../sysdeps/unix/sysv/linux/mips/mips64
-I../sysdeps/unix/sysv/linux/mips -I../sysdeps/unix/sysv/linux
-I../sysdeps/gnu -I../sysdeps/unix/common -I../sysdeps/unix/mman
-I../sysdeps/unix/inet -I../sysdeps/unix/sysv
-I../sysdeps/unix/mips/mips64/n64 -I../sysdeps/unix/mips/mips64
-I../sysdeps/unix/mips -I../sysdeps/unix -I../sysdeps/posix
-I../sysdeps/mips/mips64/n64 -I../sysdeps/ieee754/ldbl-128
-I../sysdeps/mips/mips64 -I../sysdeps/ieee754/flt-32
-I../sysdeps/ieee754/dbl-64 -I../sysdeps/mips -I../sysdeps/wordsize-64
-I../sysdeps/mips/fpu -I../sysdeps/ieee754 -I../sysdeps/generic/elf
-I../sysdeps/generic -nostdinc -isystem
/usr/lib/gcc/mips64-linux/3.4.3/include -isystem
/usr/local/tools/mips64-linux/mips64-linux/sys-root/usr/include
-D_LIBC_REENTRANT -include ../include/libc-symbols.h -DPIC -DASSEMBLER
-x assembler-with-cpp -o /home/maxim/temp/build-glibc/io/sendfile64.o
-
<stdin>: Assembler messages:
<stdin>:2: Error: absolute expression required `li'
make[2]: *** [/home/maxim/temp/build-glibc/io/sendfile64.o] Error 1
make[2]: Leaving directory `/home/maxim/temp/glibc-2.3.4/io'
make[1]: *** [io/subdir_lib] Error 2
make[1]: Leaving directory `/home/maxim/temp/glibc-2.3.4'
Has anyone seen it before? And one more thing - are there srpms for
the above mentioned tools available?
Best regards,
Maxim
next reply other threads:[~2005-05-26 16:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-26 16:32 Maxim Osipov [this message]
2005-05-26 17:06 ` glibc-2.3.4 mips64 compilation failure Daniel Jacobowitz
2005-05-26 17:26 ` Maciej W. Rozycki
2005-05-26 19:05 ` Daniel Jacobowitz
2005-05-26 19:34 ` Maciej W. Rozycki
2005-05-26 20:08 ` Daniel Jacobowitz
2005-05-26 20:15 ` Daniel Jacobowitz
2005-05-26 20:22 ` Maciej W. Rozycki
2005-05-26 20:24 ` Daniel Jacobowitz
2005-05-26 20:33 ` Maciej W. Rozycki
2005-05-27 10:15 ` Maxim Osipov
2005-05-31 14:28 ` Maciej W. Rozycki
[not found] <429C8F71.6080606@siemens.com>
2005-05-31 16:30 ` Maxim Osipov
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=6097c4905052609326a4c1232@mail.gmail.com \
--to=maxim.osipov@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=maxim@mox.ru \
/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