Changes between Version 181 and Version 182 of BuildInstructions
- Timestamp:
- Jul 3, 2012, 9:16:27 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BuildInstructions
v181 v182 335 335 * curl 336 336 * execinfo 337 * gamin338 337 * gmake 339 338 * libGL … … 358 357 {{{ 359 358 #!sh 360 pkg_add -r boost-libs cmake curl execinfo gamin gmake libGL libjpeg-turbo \ 361 libogg libvorbis libxml2 openal png sdl subversion wxgtk2-unicode zip 362 359 pkg_add -r boost-libs cmake curl execinfo gmake libGL libjpeg-turbo libogg \ 360 libvorbis libxml2 openal png sdl subversion wxgtk2-unicode zip 363 361 }}} 364 362 … … 376 374 {{{ 377 375 #!sh 378 pkg_add -i boost cmake curl g amin gmake jpeg libexecinfo libogg libxml\379 openal pngsdl subversion zip376 pkg_add -i boost cmake curl gmake jpeg libexecinfo libogg libxml openal png \ 377 sdl subversion zip 380 378 }}} 381 379 * As OpenBSD's packaged libxml isn't build with threading support, building Atlas is not possible so you should run `update-workspaces.sh` with the `--disable-atlas` option. … … 387 385 * 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` 388 386 389 * 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 2 20, and then run `update-workspaces.sh` again. It should look like390 {{{ 391 unix_names = { "boost_s ystem" },392 }}} 393 for line 220.387 * 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 234, and then run `update-workspaces.sh` again. It should look like this: 388 {{{ 389 unix_names = { "boost_signals" }, 390 }}} 391 If you are using a boost version > 1.43 you should remove (or comment) line 220 too. 394 392 395 393 * 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