Revision history [back]

This looks like a problem that has historically been common with ros & openni.

The problem is that OSX sed works very differntly from ubuntu sed. The former is the BSD sed flavor, the latter is the GNU sed flavor. In BSD sed, there is basically no way to encode an "endline" (\n) character. In BSD sed, \n means "literally an n" which is why you get all of these weird n characters everywhere.

The solution is to install gsed (gnu sed) using macports (sudo port install gsed), and then to set a SED_EXE variable in all of the bash patch scripts. It can be set to sed by default, but on darwin platforms should be set to gsed.

Then to a global replace in the script from sed to $SED_EXE or something like that.

This looks like a problem that has historically been common with ros & openni.

The problem is that OSX sed works very differntly from ubuntu sed. The former is the BSD sed flavor, the latter is the GNU sed flavor. In BSD sed, there is basically no way to encode an "endline" (\n) character. In BSD sed, \n means "literally an n" which is why you get all of these weird n characters everywhere.

The solution is to install gsed (gnu sed) using macports (sudo port install gsed), and then to set a SED_EXE variable in all of the bash patch scripts. It can be set to sed by default, but on darwin platforms should be set to gsed.

Then to do a global replace in the script from sed to $SED_EXE or something like that.

This looks like a problem that has historically been common with ros & openni.

The problem is that OSX sed works very differntly from ubuntu sed. The former is the BSD sed flavor, the latter is the GNU sed flavor. In BSD sed, there is basically no way to encode an "endline" (\n) character. In BSD sed, \n means "literally an n" which is why you get all of these weird n characters everywhere.

The solution is to install gsed (gnu sed) using macports (sudo port install gsed), and then to set a SED_EXE variable in all of the bash patch scripts. It can be set to sed by default, but on darwin platforms should be set to gsed.

Then do a global replace in the script from sed to $SED_EXE or something like that.