Removed linking with Boost.System.

Since Boost.System is now header-only, no need to depend on its library.

Fixes https://github.com/boostorg/filesystem/issues/98.

build/Jamfile.v2

@@ -26,17 +26,11 @@ SOURCES =
     ;
 
 lib boost_filesystem
-    : $(SOURCES).cpp ../../system/build//boost_system
+    : $(SOURCES).cpp
     : <link>shared:<define>BOOST_FILESYSTEM_DYN_LINK=1
       <link>static:<define>BOOST_FILESYSTEM_STATIC_LINK=1
     :
-    : # Boost.Filesystem uses some of Boost.System functions in inlined/templated
-      # functions, so clients that use Boost.Filesystem will have direct references 
-      # to Boost.System symbols. On Windows, Darwin, and some other platforms, this
-      # means those clients have to be directly linked to Boost.System. For static
-      # linking this happens anyway, but for shared we need to make it happen. Since
-      # doing so is harmless even when not needed, we do it for all platforms.
-      <link>shared:<library>../../system/build//boost_system
+    :
     ;
 
 boost-install boost_filesystem ;

example/Jamfile.v2

@@ -10,11 +10,10 @@
 project
     : requirements
       <library>/boost/filesystem//boost_filesystem
-      <library>/boost/system//boost_system
       <toolset>msvc:<asynch-exceptions>on
       <link>static
     ;
-    
+
 exe tut0 : tut0.cpp ;
 exe tut1 : tut1.cpp ;
 exe tut2 : tut2.cpp ;

test/Jamfile.v2

@@ -10,9 +10,8 @@ import os ;
 project
     : requirements
       <library>/boost/filesystem//boost_filesystem
-      <library>/boost/system//boost_system
     ;
-    
+
 # Some tests are run both statically and as shared libraries since Filesystem
 # has a history of bugs that appear only in one type of build or the other.