Changes between Version 142 and Version 143 of BuildInstructions


Ignore:
Timestamp:
Oct 16, 2011, 4:18:28 AM (13 years ago)
Author:
historic_bruno
Comment:

Updates Slackware solution; warns users about build system change

Legend:

Unmodified
Added
Removed
Modified
  • BuildInstructions

    v142 v143  
    11[[TOC]]
     2
     3'''NOTE: The build system has changed since Alpha 7 and the instructions are now subtly different. If you want to build Alpha 7 or previous versions of the game, use the [http://trac.wildfiregames.com/wiki/BuildInstructions?version=140 older version] of this page.'''
    24
    35This page describes how to get the very latest unstable version of the code. Unless you want to actively follow and contribute to development, you probably want the [LatestRelease latest relatively-stable release] instead.
     
    251253 * 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/premake.lua`
    252254
    253  * 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_libs.lua` and remove the `-mt` suffixes from the boost definitions in line 79, and then run `update-workspaces.sh` again. It should look like this:
     255 * 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 212, and then run `update-workspaces.sh` again. It should look like this:
    254256{{{
    255257unix_names = { "boost_signals", "boost_filesystem", "boost_system" },