Changes between Version 187 and Version 188 of BuildInstructions

Timestamp:

Aug 25, 2012, 7:02:23 PM (12 years ago)

Author:

historic_bruno

Comment:

Clarify a few OS X things

BuildInstructions

@@ -320 +320 @@
 }}}
 
- * You may need to patch Apple's OpenAL (`/System/Library/Frameworks/OpenAL.Framework/Headers/alc.h`: replace all `ALCvoid` by `void`, except the first one which is a `typedef`). (GCC >=4.2 is stricter about parameters invalidly typedefed to void in C++.)
+ * On Leopard or earlier, you may need to patch Apple's OpenAL (`/System/Library/Frameworks/OpenAL.Framework/Headers/alc.h`: replace all `ALCvoid` by `void`, except the first one which is a `typedef`). (GCC >=4.2 is stricter about parameters invalidly typedefed to void in C++.)
 
  * If you're under Tiger, you'll certainly have to edit [source:/ps/trunk/build/premake/premake4.lua build/premake/premake4.lua] to get rid of the `-fstack-protector-all` line: see the [#Knownproblemsandsolutions known problems section].
@@ -383 +383 @@
  * If you get linker errors like '''`cannot find -lboost_signals-mt`''' (particularly users of Arch Linux or Slackware), edit the file [source:/ps/trunk/build/premake/extern_libs4.lua build/premake/extern_libs4.lua] and remove the `-mt` suffix from the Boost `unix_name` definitions, then run `update-workspaces.sh` again.
 
+ * If you get errors like the following on OS X
+{{{
+ld: warning: ignoring file /usr/local/lib/libpng.dylib, file was built for unsupported file format which is not the architecture being linked (x86_64)
+Undefined symbols for architecture x86_64:
+...
+ld: symbol(s) not found for architecture x86_64
+}}}
+ make sure there are no conflicting libraries in e.g. `/usr/local/lib`. Mac Ports uses `/opt/local` only, and files in `/usr/local` can interfere with the build process by taking precedence over valid OS X and Mac Ports paths. You may be able to simply rename `/usr/local` ''temporarily'' to work around this conflict.
+
  * If you get linker errors like '''`multiple definition of '(anonymous namespace)::_1'`''', particularly when using GCC 4.1, try running `./update-workspaces.sh --without-pch` and then `cd gcc; make clean` and rebuild.