[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ale] gcc-3.4.2 backwards-incompatibility?
- Subject: [ale] gcc-3.4.2 backwards-incompatibility?
- From: fd0man at gmail.com (Michael B. Trausch)
- Date: Thu Apr 28 11:58:24 2005
- In-reply-to: <[email protected]>
- References: <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Mills, John M. wrote:
|
| I don't see the "backwards" compatibility warning in the build trace. How
| should this migration be handled? Do I just need to add '-I...' paths, and
| if so, what should I use?
|
The C++ programming interfaces have changed dramatically to become more
"standards compliant" in the 3.x.x releases. Some programs that haven't
yet been updated may require a 2.x.x release to properly build. This
should be considered a bug and the author should be notified.
It probably won't build on gcc 4.0.0 either.
- Mike
- --
Michael B. Trausch <fd0man at gmail.com>
Website: http://fd0man.chadeux.net/ Jabber: mtrausch at jabber.com
Phone: +1-(678)-522-7934 FAX (US Only): 1-866-806-4647
===================================================================
Do you have PGP or GPG? Key at pgp.mit.edu, Please Encrypt E-Mail!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFCcQYVPXInbkqM7nwRA4UjAJ9fMmGCEDeDyuv4sXwGSc7mjnvQZACfSL+d
JajZBlcV4oVqARaC8RyZSzw=
=BwWs
-----END PGP SIGNATURE-----