From: Arvind Krishnaswamy <arvind@CS.Arizona.EDU>
To: gcc-help@gcc.gnu.org
Subject: Re: cross compiling for strongarm
Date: Fri, 13 Oct 2000 12:30:00 -0000 [thread overview]
Message-ID: <20001013123030.C1416@banco.CS.Arizona.EDU> (raw)
In-Reply-To: <or1yxkinws.fsf@guarana.lsd.ic.unicamp.br>
On Fri, Oct 13, 2000 at 04:41:55PM -0200, Alexandre Oliva wrote:
"
" Since you're creating a cross compiler, /usr/include is irrelevant.
"
" > Since I'm building at /arvind/local should I copy these files under
" > /arvind/local?
"
" No, you need the headers appropriate for the target machine in there.
"
Where can Iget the headers required for the strongarm? Where exactly should
I put them if I'm buiding under /arvind/local
Thanks
Arvind
next prev parent reply other threads:[~2000-10-13 12:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-12 17:50 Arvind Krishnaswamy
2000-10-13 10:01 ` Alexandre Oliva
2000-10-13 11:28 ` Arvind Krishnaswamy
2000-10-13 11:42 ` Alexandre Oliva
2000-10-13 12:30 ` Arvind Krishnaswamy [this message]
2000-10-13 12:37 ` Alexandre Oliva
2000-10-18 15:48 ` Arvind Krishnaswamy
-- strict thread matches above, loose matches on Subject: below --
2000-10-08 16:11 Arvind Krishnaswamy
2000-10-09 21:59 ` Alexandre Oliva
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=20001013123030.C1416@banco.CS.Arizona.EDU \
--to=arvind@cs.arizona.edu \
--cc=gcc-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).