From: Mike Hearn <mike@navi.cx>
To: gcc@gcc.gnu.org
Subject: -fabi-version doing nothing?
Date: Fri, 03 Dec 2004 22:41:00 -0000 [thread overview]
Message-ID: <pan.2004.12.03.22.10.40.78229@navi.cx> (raw)
Hi,
I am using this configuration:
[mike@littlegreen frontend-gtk]$ g++ -v
Reading specs from /usr/lib/gcc/i386-redhat-linux/3.4.2/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-java-awt=gtk --host=i386-redhat-linuxThread model: posix
gcc version 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)
ie a stock FC3 build of g++ 3.4 which defaults to abi version 2.
The following series of commands does not do what I expected:
[mike@littlegreen tmp]$ g++ -o one b.cpp
[mike@littlegreen tmp]$ g++ -fabi-version=1 -o two b.cpp
[mike@littlegreen tmp]$ md5sum one two
093f7ddc1290fa9668fe89c494791aa3 one
093f7ddc1290fa9668fe89c494791aa3 two
ie, the symbol and libstdc++ versions required by the abi-version=1 and
abi-version=2 binaries are identical. I was sort of expecting
-fabi-version=1 to make g++ 3.4 produce binaries like version 3.3
and 3.2 did, ie that depend on libstdc++.so.5 and use GLIBCPP style
symvers not GLIBCXX style.
Am I doing something wrong, am I misunderstanding what this flag is
supposed to do, or is this a bug in g++?
thanks -mike
next reply other threads:[~2004-12-03 22:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 22:41 Mike Hearn [this message]
2004-12-06 11:53 ` Nathan Sidwell
2004-12-06 12:40 ` Mike Hearn
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=pan.2004.12.03.22.10.40.78229@navi.cx \
--to=mike@navi.cx \
--cc=gcc@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).