Update pitfall trap 2

Author: yannoff

README.md

@@ -173,12 +173,19 @@ Compile it (Oops... one Unknown File Object has not been included)
 phpcc -e bin/acme.php -f bin/acme.php -d src/ -o bin/acme
 ```
 
+##### Problem
+
 Launching the `bin/acme` compiled archive should raise an error because of the missing file.
 
 Well...not. What happens here then ?
 
 If the `bin/acme` compiled archive stays in its place,the `lib/Ufo.php` can still be found from its point of view.
 
+##### Solution
+
+Always move the compiled executable **out** of the project's working directory before testing it.
+
+
 #### Trap 2: different files with the same relative path
 
 Eg: 
@@ -187,7 +194,29 @@ Eg:
 require "vendor/autoload.php"
 ```
 
-TODO: explain, give workaround
+Chances are, there might be such a `vendor/autoload.php` file in the project to be compiled.
+
+##### Problem
+
+From the compiled app point of view, `vendor/autoload.php` refers to a relative path in the PHAR archive.
+
+##### Workaround
+
+The phpcc execution dir (i.e the compiled project's top directory) must be added first in the include path.
+
+For example in the main entrypoint script:
+
+```php
+// bin/main.php
+
+// ensure we load the execution directory's autoload, not the
+// one included in the compiled phar executable
+set_include_path(getcwd() . PATH_SEPARATOR . get_include_path());
+
+require 'vendor/autoload.php';
+
+// ...
+```
 
 ### Size too big