From: "T. P. Saravanan" <sara@procsys.com>
To: David Daney <ddaney@avtrex.com>
Cc: linux-mips@linux-mips.org
Subject: Re: mips linux glibc-2.3.3 build - Unknown ABI problem
Date: Fri, 08 Oct 2004 16:25:26 +0530 [thread overview]
Message-ID: <4166721E.20207@procsys.com> (raw)
In-Reply-To: <4164C1CF.6070708@procsys.com>
T. P. Saravanan wrote:
> OK. I will give the recent CVS version a try some time.
> -Sa.
>
The CVS version fails right at the configure stage itself. It comes out
with no
error, but no Makefile too. Below is the transcript:
sara@eyeore: [over] ~/build/glibc/objdir7$ export CFLAGS="-mips32
-fno-unit-at-a--time -O2 -g"
sara@eyeore: [over] ~/build/glibc/objdir7$ ../glibc_cvs/configure
--prefix=/home/sara/usr/local --enable-add-ons=linuxthreads
--with-headers=/home/sara/build/linux/linux-2.4.25mips/include
checking build system type... mipsel-unknown-linux-gnu
checking host system type... mipsel-unknown-linux-gnu
running configure fragment for add-on linuxthreads
sara@eyeore: [over] ~/build/glibc/objdir7$ make
make: *** No targets specified and no makefile found. Stop.
sara@eyeore: [over] ~/build/glibc/objdir7$
I there something I missed?
-Sa.
next prev parent reply other threads:[~2004-10-08 11:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 4:35 mips linux glibc-2.3.3 build - Unknown ABI problem David Daney
2004-10-06 4:35 ` David Daney
2004-10-07 4:10 ` T. P. Saravanan
2004-10-08 10:55 ` T. P. Saravanan [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-04 5:50 T. P. Saravanan
2004-10-04 16:19 ` David Daney
2004-10-05 9:03 ` T. P. Saravanan
2004-10-06 4:14 ` T. P. Saravanan
2004-10-07 4:05 ` T. P. Saravanan
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=4166721E.20207@procsys.com \
--to=sara@procsys.com \
--cc=ddaney@avtrex.com \
--cc=linux-mips@linux-mips.org \
/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.