[SQOOP-339] Use of non-portable mknod utility causes build problems on Mac OS X

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.3.0
• Fix Version/s: 1.4.0-incubating
• Assignee: Joey Echeverria
• Reporter: Joseph Boyd
• Created: 16/Sep/11 15:54
• Updated: 26/Sep/11 21:44
• Resolved: 22/Sep/11 00:33

Description

Duplicating this issue from SQOOP-175, which is in the cloudera JIRA

From SQOOP-175's description by Ken Krugler :

On Mac OS X 10.6.3, the TestNamedFifo.testNamedFifo() test fails. The error is caused by the Shell.execCommand() use of mknod, since (at least on my Mac) mknod doesn't know about the --mode=xxx parameter or the -p parameters.

Based on http://stackoverflow.com/questions/4546356/is-mknod-portable-if-not-what-is-the-alternative, I switched the code to use mkfifo and it now passes all tests.

The change to NamedFifo.create() is trivial:

Shell.execCommand("mkfifo", "-m", "0" + modeStr, filename);

But I have no way of trying this out on other OSes, so it might create a different compatibility issue.