Closed jamespatrickwhite closed 11 years ago
Re-running the build.sh script seems to continue passed the sed error.
This is a difference betweeen BSD sed and GNU sed. All we're doing is fixing yacc (which is just a sh wrapper around bison) so that it doesn't contain the absolute path to the bison executable (which points to something on your build system, not on the playbook). I think I have a fix and will push it as soon as I am done a clean build testing my fix for the conf dir issue. :-)
I have pushed a fix that should work for both BSD and GNU sed. Thanks!
When using with bbndk 2.1.0 on Ubuntu 12.10 Linux:
The bison executable appears in the pbhome/bin/ directory, and runs if I move it manually to the PlayBook. Unfortunately, I'm not really familiar with sed to understand what it's looking for.