Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Pak Woon <pak.woon@nec.com.au>
To: Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>
Cc: linux-mips@linux-mips.org
Subject: Re: Roll-your-own Toolchain Builds
Date: Thu, 05 Oct 2006 16:51:21 +1000	[thread overview]
Message-ID: <4524AB69.4040802@nec.com.au> (raw)
In-Reply-To: <20061005151756.6911f9de.yoichi_yuasa@tripeaks.co.jp>

>>I am now trying to build a simple program with my new toolchain and I've 
>>come across the "can't find crt1.o" problem again. I am struggling with 
>>this.
> 
> 
> You need glibc or uClibc for MIPS target.
> 
> If you want to use uClibc, see buildroot link in
> http://www.linux-mips.org/wiki/Toolchains .

Okay, this is going to be a stupid question, but when I built the kernel 
for the MIPS target, I had no issues or a need for those libs. I assumed 
that for such a simple hello.c program, I would not need glibc or uClibc 
either.

Pak

  reply	other threads:[~2006-10-05  6:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-02 14:14 [PATCH] remove Momentum / PMC-Sierra Jaguar ATX evaluation board Yoichi Yuasa
2006-10-02 15:18 ` Ralf Baechle
2006-10-03  1:44   ` Yoichi Yuasa
2006-10-03  7:55     ` Roll-your-own Toolchain Builds Pak Woon
2006-10-03  8:33       ` Yoichi Yuasa
2006-10-03  8:50         ` Pak Woon
2006-10-03  8:37       ` Daniel Stenberg
2006-10-05  6:02         ` Pak Woon
2006-10-05  6:17           ` Yoichi Yuasa
2006-10-05  6:51             ` Pak Woon [this message]
2006-10-05  7:10               ` Yoichi Yuasa
2006-10-05  7:39                 ` Yoichi Yuasa
2006-10-03 20:25       ` Jim Wilson
2006-10-03  9:45     ` [PATCH] remove Momentum / PMC-Sierra Jaguar ATX evaluation board Maciej W. Rozycki
  -- strict thread matches above, loose matches on Subject: below --
2006-10-03 17:45 Roll-your-own Toolchain Builds Kaz Kylheku
2006-10-03 17:45 ` Kaz Kylheku

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=4524AB69.4040802@nec.com.au \
    --to=pak.woon@nec.com.au \
    --cc=linux-mips@linux-mips.org \
    --cc=yoichi_yuasa@tripeaks.co.jp \
    /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