mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Megharaj <megharaj@isofttech.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: GCC tool chain 3.3.2 problem.
Date: Thu, 22 Apr 2004 07:45:25 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0404220741200.8039@chaos> (raw)
In-Reply-To: <02e301c42857$f7740c60$cb00a8c0@megharaj>

On Thu, 22 Apr 2004, Megharaj wrote:

> 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.
>

Type exactly:

ls `gcc --print-file-name=include`/stddef.h

If you don't see the file, your tools were improperly installed.

If you do, see the file, remove `-nostdinc` on the Makefile
command-line and your compile should work.


Cheers,
Dick Johnson
Penguin : Linux version 2.4.26 on an i686 machine (5557.45 BogoMips).
            Note 96.31% of all statistics are fiction.



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

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

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=Pine.LNX.4.53.0404220741200.8039@chaos \
    --to=root@chaos.analogic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=megharaj@isofttech.com \
    /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

all inboxes | Powered by JetHome®