public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: "GERASIMOV, SERGEY (HP-Roseville, ex1)" <sergey_gerasimov@hp.com>
To: crossgcc@sourceware.cygnus.com
Subject: GCC 2.95.2 for arm-wrs-vxworks
Date: Mon, 30 Oct 2000 13:19:00 -0000	[thread overview]
Message-ID: <312FA084975ED4119C8700D0B74FE85D0DF648@xrose04.rose.hp.com> (raw)

Hello all,

I am struggling to build cross gcc 2.95.2 for arm-wrs-vxworks.
I have found that I cannot build binutils for such target, so, I used WRS
supplied stuff, as well as previously build arm-coff binutil.  Both versions
seem to work the same.  I was successful in building the compiler, however,
the message I got when I ran it with -v option, was that it runs 2.7.9
version of gcc.  That is frustrating, since, this is the version we have
now, and attemp was to upgrade to 2.95.2.  Moreover, I still compiled all of
the source with it, worked fine. However, I have got strange problems during
linking, indicating that none of the entries in teh ctdt table are valid
references.  I checked
the object code, and all are present but referenced locally (small t),
rather than globally (capital T).  The same thing occured when I compiled
all of the code with plain arm-coff gcc, not arm-wrs-vxworks-gcc. 
Has anybody seen this problem, or does anyone have any positive experience
building cross gcc for arm-wrs-vxworks.

Any feedback will be really! appreciated!

Thanks a lot,
Sergey

------
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:[~2000-10-30 13:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-30 13:19 GERASIMOV, SERGEY (HP-Roseville, ex1) [this message]
2000-10-31 10:20 ` Kai Ruottu
2000-10-31 10:40 GERASIMOV, SERGEY (HP-Roseville, ex1)

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=312FA084975ED4119C8700D0B74FE85D0DF648@xrose04.rose.hp.com \
    --to=sergey_gerasimov@hp.com \
    --cc=crossgcc@sourceware.cygnus.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).