From: "kjlin" <kj.lin@viditec-netmedia.com.tw>
To: "Keith M Wesolowski" <wesolows@chem.unr.edu>
Cc: <linux-mips@oss.sgi.com>
Subject: Re: Run the cross-compiled program.
Date: Fri, 22 Dec 2000 14:38:38 +0800 [thread overview]
Message-ID: <062f01c06be1$d1ca8ce0$056aaac0@kjlin> (raw)
In-Reply-To: 20001220183938.A20077@chem.unr.edu
----- Original Message -----
> I guess I don't quite understand why you would want to use kernel 2.2
> with glibc 2.2. For embedded purposes, glibc 2.0 will save you a lot
> of space; if you just want the newest stuff unconditionally, use
> kernel 2.4. The specific libc you are using is rather dated anyway.
> While it worked for most purposes it is hardly bug-free. Consider
> using CVS glibc, or the glibc from Florian's Debian build environment.
>
> --
The original system of my embedded mips board is the kernel 2.2 with the
libc-2.0.4.
But the libc-2.0.4 seems not to support POSIX 1003.1c, which cause my
program to fail.
That's the reasion why i want to upgrade the library.
In fact, i prefer to upgrade to libc-2.0.6, but i am not sure whether it
supports POSIX 1003.1c.
On the other hand, i can not find the cross-usable libc-2.0.6 source and
patches or binary tarball for my cross-compiler.
Any suggestions ?
Thanks,
KJ
WARNING: multiple messages have this Message-ID (diff)
From: "kjlin" <kj.lin@viditec-netmedia.com.tw>
To: Keith M Wesolowski <wesolows@chem.unr.edu>
Cc: linux-mips@oss.sgi.com
Subject: Re: Run the cross-compiled program.
Date: Fri, 22 Dec 2000 14:38:38 +0800 [thread overview]
Message-ID: <062f01c06be1$d1ca8ce0$056aaac0@kjlin> (raw)
Message-ID: <20001222063838.3Yfvyh-TtPriA1o3i48yQ5ltKTMQoX3nJ01b53j2d4g@z> (raw)
In-Reply-To: 20001220183938.A20077@chem.unr.edu
----- Original Message -----
> I guess I don't quite understand why you would want to use kernel 2.2
> with glibc 2.2. For embedded purposes, glibc 2.0 will save you a lot
> of space; if you just want the newest stuff unconditionally, use
> kernel 2.4. The specific libc you are using is rather dated anyway.
> While it worked for most purposes it is hardly bug-free. Consider
> using CVS glibc, or the glibc from Florian's Debian build environment.
>
> --
The original system of my embedded mips board is the kernel 2.2 with the
libc-2.0.4.
But the libc-2.0.4 seems not to support POSIX 1003.1c, which cause my
program to fail.
That's the reasion why i want to upgrade the library.
In fact, i prefer to upgrade to libc-2.0.6, but i am not sure whether it
supports POSIX 1003.1c.
On the other hand, i can not find the cross-usable libc-2.0.6 source and
patches or binary tarball for my cross-compiler.
Any suggestions ?
Thanks,
KJ
next prev parent reply other threads:[~2000-12-22 7:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-20 10:09 Run the cross-compiled program kjlin
2000-12-20 10:09 ` kjlin
2000-12-20 22:54 ` Nicu Popovici
2000-12-21 2:39 ` Keith M Wesolowski
2000-12-22 6:38 ` kjlin [this message]
2000-12-22 6:38 ` kjlin
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='062f01c06be1$d1ca8ce0$056aaac0@kjlin' \
--to=kj.lin@viditec-netmedia.com.tw \
--cc=linux-mips@oss.sgi.com \
--cc=wesolows@chem.unr.edu \
/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