Compiling Wesnoth using scons

Building and Installing Wesnoth from source is supposed to be this easy:

#update the working copy
>svn update

# Build
>scons

#Install
>scons install

Best Instructions I’ve found are at:  http://www.wesnoth.org/wiki/CompilingWesnoth

Some hints:

1. compiling requires dev version of libraries    Development files–
   This package contains files needed if you wish to use the xxxx
   library in your own programs.
2. read the build and install output.  Look for missing libraries!

sample output — read the error messages!!

checking for Boost smart_ptr library… (cached) yes
Checking for Simple DirectMedia Layer library version >= 1.2.7… yes
Checking for SDL_net library… no
Base prerequisites are not met.
Client prerequisites are not met. wesnoth, cutter and exploder cannot be built.
Checking for C library X11… yes
Checking for fribidi_utf8_to_unicode(NULL,0,NULL) in C library fribidi… no
Can’t find libfribidi, disabling freebidi support.
Checking for C header file poll.h… yes
Checking for C header file sys/poll.

was SDL-net in ubuntu … not SDL_net

Failed to load the NVIDIA kernel module!

more /var/log/Xorg.0.log showed:

) NVIDIA(0): enabled.
(EE) NVIDIA(0): Failed to load the NVIDIA kernel module!
(EE) NVIDIA(0): *** Aborting ***
(II) UnloadModule: “nvidia”
(II) UnloadModule: “wfb”
(II) UnloadModule: “fb”
(EE) Screen(s) found, but none have a usable configuration.

Googled “(EE) NVIDIA(0): Failed to load the NVIDIA kernel module!” and found :

http://http.download.nvidia.com/XFree86/Linux-x86/1.0-8174/README/32bit_html/chapter-05.html

My X server fails to start, and my X log file contains the error:

(EE) NVIDIA(0): Failed to load the NVIDIA kernel module!

The X driver will abort with this error message if the NVIDIA kernel module fails to load. If you receive this error, you should check the output of dmesg for kernel error messages and/or attempt to load the kernel module explicitly with modprobe nvidia. If unresolved symbols are reported, then the kernel module was most likely built against a Linux kernel source tree (or kernel headers) for a kernel revision or configuration that doesn’t match the running kernel.

modprobe nvidia

threw errors on my box. My nvidia module was not loading due to an obsolete file I had put in /etc/modprobe.d/ many Ubuntu versions ago. Moved out the old files and the module loads fine!

SSH Port Forwarding – Remote Access behind firewall – a poor man’s VPN

Problem
Needed method to connect software via ssh on machine A to a firewalled machine C. I had ssh access to another machine behind firewall B. Did not want to VPN because only want port 22 traffic to go through to work.

Solution
Forward port 2222 traffic of machine (A) to port 22 of my work machine(B) which in turn connects to the server(C).

/************** TUNNELING **********************/
/********* USE THESE 2 COMMANDS ****************/
/********************************************/
# route through boxB to serverC
sudo ssh -L 2222:serverC.com:22 boxB.com

# to connect to server C from boxA, ssh through 2222
ssh -p 2222 serverCusername@localhost

/********************************************/
restated:

Local to Remote forwarding
With local to remote forwarding, a connection to your machine is forwarded to the remote machine, and made from there. This allows you to access network resources as if you where the remote machine. A common use is to forward your SMTP connections so you can send emails from your normal server (eg when connected to a network which blocks port 25), eg: ssh -L 2525:mailserver.myoffice.com:25 login.myoffice.com
will send all connections to port 2525 on your local machine over the ssh link to login.myoffice.com, which will then connect them to port 25 of mailserver.myoffice.com.
http://www.torchbox.com/blog/ssh_tips_1.html

man ssh to see the -L switch:

-L [bind_address:]port:host:hostport
Specifies that the given port on the local (client) host is to be forwarded to the given host and port on the remote side. This works by allocating a socket to listen to port on the local side, optionally bound to the specified bind_address. Whenever a connection is made to this port, the connection is forwarded over the secure channel, and a connection is made to host port hostport from the remote machine. Port forwardings can also be specified in the configuration file. IPv6 addresses can be specified with an alternative syn?
tax: [bind_address/]port/host/hostport or by enclosing the address in square brackets. Only the superuser can forward privileged ports. By default, the local port is bound in accordance with the GatewayPorts setting. However, an explicit bind_address may be used to bind the connection to a specific address. The bind_address of “localhost” indicates that the listening port be bound for local use only, while an empty address or ‘*’ indicates that the port should be available from all interfaces.