public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: murray <murray@geocom.com.au>
To: gcc-help@gcc.gnu.org
Subject: Why does this now work?
Date: Wed, 09 Oct 2002 07:26:00 -0000	[thread overview]
Message-ID: <3DA43BDE.9827947C@geocom.com.au> (raw)

With gcc 3.2 (binary downloaded from sunfreeware, native ld and as), I
can now build programs against a 3rd party library which I am certain
was compiled in 1999 with SUN Workshop C++ 4.2 (which is the only
compiler the vendor will suppport in the use of their library). Previous
versions of gcc failed in various odd ways (it might have been me being
odd, but I never knew). The gcc executables are slightly smaller but
give results and times identical to executables built with Sun Workshop.
I am using an Ultrasparc 1 running Solaris 2.6.

I am mystified as to what I can get away with, given I was still
expecting some incompatibility in the process (name mangling at the
least). Can anyone point me to some wisdom on this matter?

Thanks
Graeme

             reply	other threads:[~2002-10-09 14:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-09  7:26 murray [this message]
2002-10-09  7:49 ` Eljay Love-Jensen

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=3DA43BDE.9827947C@geocom.com.au \
    --to=murray@geocom.com.au \
    --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).