Changes between Version 178 and Version 179 of BuildInstructions

Timestamp:

Jun 19, 2012, 9:38:55 PM (12 years ago)

Author:

Almin

Comment:

Just very few and little changes. Accommodation for new build/premake/extern_libs4.lua.

BuildInstructions

@@ -369 +369 @@
  * If you get linker errors like '''`/usr/bin/ld: Undefined symbols: ___stack_chk_fail, ___stack_chk_guard`''', this comes from using a libc that is not glibc >=2.4. Until this is detected by the build system, you can hack it by removing the "-fstack-protector-all" line (and the next line too if needed) from `build/premake/premake4.lua`
 
- * If you get linker errors like '''`cannot find -lboost_signals-mt`''' (particularly users of Slackware 13.37 and -current), edit the file `build/premake/extern_libs4.lua` and remove the `-mt` suffixes from the boost definitions in line 221 and line 230, and then run `update-workspaces.sh` again. It should look like
-{{{
-unix_names = { "boost_filesystem", "boost_system" },
-}}}
-   for line 221 and
-{{{
-unix_names = { "boost_signals" },
-}}}
-   for 230 respectively.
+ * If you get linker errors like '''`cannot find -lboost_signals-mt`''' (particularly users of Slackware 13.37 and -current), edit the file `build/premake/extern_libs4.lua` and remove the `-mt` suffix from the boost definition in line 220, and then run `update-workspaces.sh` again. It should look like
+{{{
+unix_names = { "boost_system" },
+}}}
+   for line 220.
 
  * If !SpiderMonkey has compile errors during `update-workspace.sh`, throwing errors like '''`'r13' is not a member of 'JSC::X86Registers'`''', then you likely have a 32-bit userspace with a 64-bit kernel. Run