public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Megharaj" <megharaj@isofttech.com>
To: <linux-kernel@vger.kernel.org>
Subject: GCC tool chain 3.3.2 problem.
Date: Thu, 22 Apr 2004 16:22:54 +0530	[thread overview]
Message-ID: <02e301c42857$f7740c60$cb00a8c0@megharaj> (raw)

hi,

i fallowed the instruction to build the GCC tool  chain 3.3.2 given in the
fallowing link.

http://blackfin.uclinux.org/docman/view.php/18/43/Build%20instructions.doc

after building i compiled the uclinux distribution with nisa-elf gcc tool
chain it got compiled properly.

but when i am compiling the same uclinux distribution with new gcc tool
chain 3.3.2 it shows that the error header file like stddef.h are missing.

if any one could give me the details abt  what is the problem with new gcc
tool chain 3.3.2 or do i  am missing something in building the gccc tool
chin 3.3.2.  it wud be very helpful.


thanx n ragards
megharaj.




             reply	other threads:[~2004-04-22 11:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-22 10:52 Megharaj [this message]
2004-04-22 11:45 ` GCC tool chain 3.3.2 problem Richard B. Johnson

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='02e301c42857$f7740c60$cb00a8c0@megharaj' \
    --to=megharaj@isofttech.com \
    --cc=linux-kernel@vger.kernel.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