public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* Re: One puzzle from cross compilation with 2 different versions of GCC?
       [not found] <5AE055B67BB5764693E2900C7E3699BE4B1DAC@pamail.ad.lsil.com>
@ 2006-02-28  9:44 ` Andrew Haley
  0 siblings, 0 replies; only message in thread
From: Andrew Haley @ 2006-02-28  9:44 UTC (permalink / raw)
  To: Zhang, Vic; +Cc: gcc-help

Zhang, Vic writes:

 > I used to compile my program with gcc-2.7.2 for Sparc, recently I
 > wanted to support Unicode in my program and found gcc-2.7.2 can't
 > support Unicode at all. After that I change to gcc-2.96. However,
 > the output format of the latter one is elf32-sparc and that of the
 > first one is a.out-sunos-big.

No, that isn't so.  It all depends on how you configured gcc when you
built it.  It sounds like the earlier compiler wasn't configured for
an embedded standalone target at all, but for sunos.

 > So I can't partially link the code generated with gcc-2.96 with
 > some old library generated with gcc-2.7.2 with option -r even if
 > --oformat a.out-sunos-big is specified. I think gcc-2.96 maybe
 > support a.out-sunos-big format, but I can't find anything
 > useful. Can you help me solve this problem or give me some useful
 > hint?

You need to tell us what options you used when you built gcc.  

Also, the gcc list is for the developers of gcc: gcc help enquiries
should be sent to gcc-help@gcc.gnu.org.

Andrew.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2006-02-28  9:44 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <5AE055B67BB5764693E2900C7E3699BE4B1DAC@pamail.ad.lsil.com>
2006-02-28  9:44 ` One puzzle from cross compilation with 2 different versions of GCC? Andrew Haley

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