From: "Benjamin Menküc" <benmen@gmx.de>
To: Daniel Jacobowitz <dan@debian.org>
Cc: linux-mips@linux-mips.org
Subject: Re: compiling glibc
Date: Sat, 10 May 2003 11:56:08 +0200 [thread overview]
Message-ID: <200305101156.08254.benmen@gmx.de> (raw)
In-Reply-To: <20030510042535.GA2336@nevyn.them.org>
Okay, it works now when I set CC=mipsel-linux-gcc and AS=mipsel-linux-as
[benmen@linuxpc1 mipsel-glibc] LD_LIBRARY_PATH="" CFLAGS="-O2 -g
-finline-limit=10000" CC="mipsel-linux-gcc" AS="mipsel-linux-as"
../glibc-2.3.2/configure --build=i686-linux --host=mipsel-linux
--enable-add-ons --prefix=/home/benmen/mipsel
--with-headers=/home/benmen/mips/kernel/mips-2.4.20/include
until this comes:
make[2]: Entering directory `/home/benmen/mips/glibc-2.3.2/misc'
make[2]: *** Keine Regel vorhanden, um das Target
»/home/benmen/mips/mipsel-glibc/misc/cachectl.o«,
benötigt von »/home/benmen/mips/mipsel-glibc/misc/stamp.o«, zu erstellen.
Schluss.
make[2]: Leaving directory `/home/benmen/mips/glibc-2.3.2/misc'
make[1]: *** [misc/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]
PS: shouldn't the Makefile take care of the CC and AS variables?
regards,
Ben
next prev parent reply other threads:[~2003-05-10 9:56 UTC|newest]
Thread overview: 16+ 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 [this message]
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=200305101156.08254.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 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.