Changes between Version 183 and Version 184 of BuildInstructions


Ignore:
Timestamp:
Jul 30, 2012, 2:07:02 AM (12 years ago)
Author:
historic_bruno
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BuildInstructions

    v183 v184  
    385385 * 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`
    386386
    387  * If you get linker errors like '''`cannot find -lboost_signals-mt`''' (particularly users of Slackware 13.37 and -current), 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.
     387 * 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.
    388388
    389389 * 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