public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Yeong Jiun How <yeongjh@cwc.nus.edu.sg>
To: David Korn <dkorn@pixelpower.com>, crossgcc@sources.redhat.com
Subject: Successful Compilation Of crossGCC For Arm
Date: Sun, 01 Apr 2001 00:00:00 -0000	[thread overview]
Message-ID: <4.3.0.20010116094946.00aa1ac0@postman.cwc.nus.edu.sg> (raw)
Message-ID: <20010401000000.jQSZ-qB04wSHVJLDtF4sEqHNEgh_UpjLzMr8ufqVWm0@z> (raw)
In-Reply-To: <718D38CAB6E0D011B2C90060970C28A56425B7@EXCHANGESERVER>

Hi David,

Thanks for your help.

I have done the following all over again, and
successfully compiled the crossGCC for Arm:

1. download the tar.gz version of GCC source version 2.95.2 in /src/gcc
2. cd /src/gcc
3. gunzip -vf <source>.tar.gz
4. tar -xvf <source>.tar
5. download gcc patch <ecos-gcc-2952.pat> to support eCos from
     http://sources.redhat.com/ecos/tools/win-arm-elf.html to /src/gcc/gcc-2.95.2
6. cd /src/gcc/gcc-2.95.2
7. tr -d '\r' < ecos-gcc-2952.pat | patch -p0
8. mkdir /tmp/build/gcc
9. cd /tmp/build/gcc
10. mkdir /gcc-src
11. mount -s -t 'C:\<cygpath>\<srcdir>' /gcc-src
12. /gcc-src/configure --target=arm-elf --prefix=/<installdir>
      --exec-prefix=/<execdir> -v 2>&1 | tee configure.out
13. make -w all-gcc install-gcc LANGUAGES="c c" 2>&1 | tee make.out


Hopefully this will be of some help to others.

Thanks and regards,
Yeong


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

  reply	other threads:[~2001-04-01  0:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-12  2:56 Error Compiling " David Korn
2001-01-15 18:06 ` Yeong Jiun How [this message]
2001-04-01  0:00   ` Successful Compilation Of " Yeong Jiun How
2001-04-01  0:00 ` Error Compiling " David Korn

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=4.3.0.20010116094946.00aa1ac0@postman.cwc.nus.edu.sg \
    --to=yeongjh@cwc.nus.edu.sg \
    --cc=crossgcc@sources.redhat.com \
    --cc=dkorn@pixelpower.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).