All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Benjamin Menküc" <benmen@gmx.de>
To: linux-mips@linux-mips.org
Subject: compiling glibc
Date: Fri, 9 May 2003 21:45:43 +0200	[thread overview]
Message-ID: <200305092145.43690.benmen@gmx.de> (raw)

Hi,

I cross-compiled binutils 2.13 and gcc-3.2.3 successfully for mips.

[benmen@linuxpc1 mipsel-glibc] LD_LIBRARY_PATH="" CFLAGS="-O2 -g 
-finline-limit=10000" ../glibc-2.3.2/configure --build=i686-linux 
--host=mipsel-linux --enable-add-ons --prefix=/home/benmen/mipsel

...

When I try to compile glibc I get this error:

[benmen@linuxpc1 mipsel-glibc] make
make -r PARALLELMFLAGS="" CVSOPTS="" -C ../glibc-2.3.2 objdir=`pwd` all
...
make[2]: Leaving directory `/home/benmen/mips/glibc-2.3.2/csu'
make[2]: Entering directory `/home/benmen/mips/glibc-2.3.2/csu'
gcc ../sysdeps/unix/sysv/linux/init-first.c -c -std=gnu99 -O2 -Wall -Winline 
-Wstrict-prototypes -Wwrite-strings -finline-limit=10000 -g      -I../include 
-I. -I/home/benmen/mips/mipsel-glibc/csu -I.. -I../libio  
-I/home/benmen/mips/mipsel-glibc -I../sysdeps/mips/elf 
-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 -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 
-I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/mips/mipsel 
-I../sysdeps/mips/fpu -I../sysdeps/mips -I../sysdeps/wordsize-32 
-I../sysdeps/ieee754/flt-32 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754 
-I../sysdeps/generic/elf -I../sysdeps/generic   -D_LIBC_REENTRANT -include 
../include/libc-symbols.h       -DHAVE_INITFINI -o 
/home/benmen/mips/mipsel-glibc/csu/init-first.o
In file included from ../linuxthreads/descr.h:42,
                 from ../linuxthreads/internals.h:29,
                 from ../linuxthreads/sysdeps/pthread/bits/libc-lock.h:27,
                 from ../sysdeps/generic/ldsodefs.h:38,
                 from ../sysdeps/unix/sysv/linux/ldsodefs.h:25,
                 from ../sysdeps/mips/elf/ldsodefs.h:25,
                 from ../sysdeps/unix/sysv/linux/init-first.c:30:
../linuxthreads/sysdeps/mips/pt-machine.h:48: invalid register name for 
`stack_pointer'
In file included from ../sysdeps/unix/sysv/linux/mips/sys/procfs.h:29,
                 from ../linuxthreads_db/proc_service.h:20,
                 from ../linuxthreads_db/thread_dbP.h:7,
                 from ../linuxthreads/descr.h:43,
                 from ../linuxthreads/internals.h:29,
                 from ../linuxthreads/sysdeps/pthread/bits/libc-lock.h:27,
                 from ../sysdeps/generic/ldsodefs.h:38,
                 from ../sysdeps/unix/sysv/linux/ldsodefs.h:25,
                 from ../sysdeps/mips/elf/ldsodefs.h:25,
                 from ../sysdeps/unix/sysv/linux/init-first.c:30:
../sysdeps/unix/sysv/linux/mips/sys/user.h:26:21: asm/reg.h: Datei oder 
Verzeichnis nicht gefunden
In file included from ../sysdeps/unix/sysv/linux/mips/sys/procfs.h:29,
                 from ../linuxthreads_db/proc_service.h:20,
                 from ../linuxthreads_db/thread_dbP.h:7,
                 from ../linuxthreads/descr.h:43,
                 from ../linuxthreads/internals.h:29,
                 from ../linuxthreads/sysdeps/pthread/bits/libc-lock.h:27,
                 from ../sysdeps/generic/ldsodefs.h:38,
                 from ../sysdeps/unix/sysv/linux/ldsodefs.h:25,
                 from ../sysdeps/mips/elf/ldsodefs.h:25,
                 from ../sysdeps/unix/sysv/linux/init-first.c:30:
../sysdeps/unix/sysv/linux/mips/sys/user.h:30: `EF_SIZE' undeclared here (not 
in a function)
../sysdeps/unix/sysv/linux/mips/sys/user.h:41: confused by earlier errors, 
bailing out
make[2]: *** [/home/benmen/mips/mipsel-glibc/csu/init-first.o] Fehler 1
make[2]: Leaving directory `/home/benmen/mips/glibc-2.3.2/csu'
make[1]: *** [csu/subdir_lib] Fehler 2
make[1]: Leaving directory `/home/benmen/mips/glibc-2.3.2'
make: *** [all] Fehler 2
Verzeichnis: ~/mips/mipsel-glibc
[benmen@linuxpc1 mipsel-glibc]

The headers including asm/reg.h are located in /home/benmen/mipsel/include ...
the mipsel-linux-gcc + binutils stuff is in /home/benmen/mipsel/bin ...

Thanks for Your help.

regards,

Ben

             reply	other threads:[~2003-05-09 19:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-09 19:45 Benjamin Menküc [this message]
2003-05-09 21:45 ` compiling glibc 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
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
  -- strict thread matches above, loose matches on Subject: below --
2004-08-11 10:10 Compiling glibc DervishD
2000-03-27 12:01 compiling glibc kd
2000-03-27  1:38 Michael A. Peters
2000-03-27 15:09 ` Matt Porter

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=200305092145.43690.benmen@gmx.de \
    --to=benmen@gmx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.