From: "Sangmoon Kim" <dogoil@etinsys.com>
To: 전혜영 <hychon@corebell.co.kr>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: looking for source files for MPC8xx --- help me~~~
Date: Tue, 30 Apr 2002 11:39:56 +0900 [thread overview]
Message-ID: <004e01c1eff0$50f70500$1a11efcb@industrialDiv.hanasys.co.kr> (raw)
In-Reply-To: 001201c1efdd$301e7d80$3200a8c0@genetelhychon
Hi,
> 1. Could you tell me how to find the sources ??
>
> and I read a following message in mailling web site ( http://lists.linuxppc.org/linuxppc-embedded/200003/msg00077.html )
> I go to the http://www.mvista.com site , but I can't anyting source
>
>
Montavista's Hardhat Linux is not available on internet any more. If you're gonna make a ramdisk or nfs root for linux root file system. I think Wolfgang denk's CDK and SELF is a good starting point. You can find them at...
ftp://ftp.denx.de/pub/LinuxPPC/usr/src/
> 2. and I found some source for bash-xxx.tar.gz ..etc from gnu.org
> when I complile the sources using powerpc-linux compiler ( gcc-2.95 , glibc-2.2.3 )
> it's giving error that
>
> checking whetehr setvbuf argument are reserved... configure: error cannot run test program while cross compiling
>
>
> I was compiled following option
> #./configure --host=poweprc-linux --build=i386-linux
>
> what's problem?? I'm not understanding.....
>
I encountered the same error before. I don't think bash support cross compiling.
Good Luck
- Sangmoon Kim -
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-30 2:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-30 0:22 looking for source files for MPC8xx --- help me~~~ 전혜영
2002-04-30 2:39 ` Sangmoon Kim [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-02 7:13 Mészáros Lajos
2002-05-02 7:17 Michael Habermann
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='004e01c1eff0$50f70500$1a11efcb@industrialDiv.hanasys.co.kr' \
--to=dogoil@etinsys.com \
--cc=hychon@corebell.co.kr \
--cc=linuxppc-embedded@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).