From: Martin von Loewis <martin@mira.isdn.cs.tu-berlin.de>
To: tann@exchange.SanDiegoCA.NCR.com
Cc: egcs@cygnus.com
Subject: Re: GNU compatibility with HP-UX aC++
Date: Tue, 14 Jul 1998 23:08:00 -0000 [thread overview]
Message-ID: <199807150607.IAA00255@mira.isdn.cs.tu-berlin.de> (raw)
In-Reply-To: <199807141829.LAA18004@ncr-sd.SanDiegoCA.NCR.COM>
> I would like to know if binaries/applications generated/built with GNU
> compiler are compatible with HP-UX aC++. If not, is there a newer
> version of GCC that will be compatible?
No. In general, two different C++ compilers are not binary-compatible.
There are many reasons for that: different class layout, different
virtual table structures, different mangling.
So if you have binary-only libraries compiled with aC++, you have to
ask the author to recompile with g++, or you have to use aC++
yourself.
For C code, things are better in general; I can't give a definite
answer for HP-UX, though.
Regards,
Martin
prev parent reply other threads:[~1998-07-14 23:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-14 11:29 Nguyen, Tan
1998-07-14 18:59 ` Jeffrey A Law
1998-07-14 23:08 ` Martin von Loewis [this message]
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=199807150607.IAA00255@mira.isdn.cs.tu-berlin.de \
--to=martin@mira.isdn.cs.tu-berlin.de \
--cc=egcs@cygnus.com \
--cc=tann@exchange.SanDiegoCA.NCR.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).