| [AD] extra note for Mac OS X build doc |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: [AD] extra note for Mac OS X build doc
- From: Matthew Leverton <meffer@xxxxxxxxxx>
- Date: Tue, 17 May 2005 01:58:26 -0500
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type; b=SyUuDEjrIVEeQ9DKfwUxhbJle9IauJ/GWnRAny71uMmkRFwIn/s0kXoIRe/nc5OVsSOc9wozHVy5uzCui4lzbNBht4MRVMf7QLmNuQyUKB3WUtadwLLyheSgk3X5x/D/mdxORhtXrPrFHyJXJv3H6/i71/r1gfSghxgOBLuzkSQ=
Attached is a simple addition to the build docs for Mac OS X that
warns about compatibility problems when using gcc 4 (standard on
10.4). Basically if Allegro (or the programmer's application) is built
with gcc 4, then the binaries will not run on 10.2 and some 10.3
systems.
--
Matthew Leverton
http://www.allegro.cc
--- docs/src/build/macosx._tx Tue Apr 6 07:34:25 2004 UTC
+++ docs/src/build/macosx._tx Tue May 17 06:51:12 2005 UTC
@@ -303,6 +303,10 @@
@heading
Final notes
+ There is a known compatibility problem when using gcc 4 on MacOS X 10.4
+ that prevents binaries from working on older versions of MacOS X. While it
+ is anticipated that a future update from Apple will fix this problem, you
+ can use gcc 3 to work around it.
+
As a final note, when coding Allegro programs don't forget that you
need to use the <code>END_OF_MAIN()</code> macro right after your <code>main()</code> function!
-