public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: ebony5146@my-deja.com
To: help-gcc@gnu.org
Subject: Cross Compilation Problem
Date: Wed, 05 Jan 2000 21:45:00 -0000	[thread overview]
Message-ID: <85199u$5n7$1@nnrp1.deja.com> (raw)

Hi everybody,
I am new to Linux environment and was trying to cross compile binutils.
The compilation proceeds properly and I do get all the binutils. But
when I try to compile the "hello world" code I get an error stdio not
found. I preprocess the file,the file was being searced in sys-include
directory. I would like to know when this is made in the process of
cross-compilation.



Sent via Deja.com http://www.deja.com/
Before you buy.

WARNING: multiple messages have this Message-ID

From: ebony5146@my-deja.com
To: help-gcc@gnu.org
Subject: Cross Compilation Problem
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <85199u$5n7$1@nnrp1.deja.com> (raw)
Message-ID: <20000401000000.x2gAdBNCkEINAUIxE0vlEmHAZenzBuPPEfmgn16Ve5w@z> (raw)

Hi everybody,
I am new to Linux environment and was trying to cross compile binutils.
The compilation proceeds properly and I do get all the binutils. But
when I try to compile the "hello world" code I get an error stdio not
found. I preprocess the file,the file was being searced in sys-include
directory. I would like to know when this is made in the process of
cross-compilation.



Sent via Deja.com http://www.deja.com/
Before you buy.

             reply	other threads:[~2000-01-05 21:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-05 21:45 ebony5146 [this message]
2000-04-01  0:00 ` ebony5146
2012-03-26 12:25 Cross compilation problem Alexey Umnov
2012-03-26 20:50 ` Ian Lance Taylor
2012-03-27  6:30   ` Alexey Umnov

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='85199u$5n7$1@nnrp1.deja.com' \
    --to=ebony5146@my-deja.com \
    --cc=help-gcc@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).