SI-3623 Improved error message for "filename too long" build errors

stusmall · stusmall · commit cb8d924ab894 · 2015-08-07T23:52:17.000-06:00
When building on ecryptfs filenames can be limited to ~142 characters.
This limit doesn't take long to hit and can leave the the user with a
hard to diagnosis error message.  Some legacy file systems will have
similarly small limits.  This just adds a hint that the error might
be related to the underlying fs.
diff --git a/src/compiler/scala/tools/nsc/backend/jvm/GenASM.scala b/src/compiler/scala/tools/nsc/backend/jvm/GenASM.scala
@@ -532,6 +532,10 @@ abstract class GenASM extends SubComponent with BytecodeWriters { self =>
         case e: java.lang.RuntimeException if e.getMessage != null && (e.getMessage contains "too large!") =>
           reporter.error(sym.pos,
             s"Could not write class $jclassName because it exceeds JVM code size limits. ${e.getMessage}")
+        case e: java.io.IOException if e.getMessage != null && (e.getMessage contains "File name too long")  =>
+          reporter.error(sym.pos, e.getMessage + "\n" +
+            "This can happen on some encrypted or legacy file systems.  Please see SI-3623 for more details.")
+
       }
     }
 

Original file line number	Diff line number	Diff line change
`@@ -532,6 +532,10 @@ abstract class GenASM extends SubComponent with BytecodeWriters { self =>`
`532`	`532`	`case e: java.lang.RuntimeException if e.getMessage != null && (e.getMessage contains "too large!") =>`
`533`	`533`	`reporter.error(sym.pos,`
`534`	`534`	`s"Could not write class $jclassName because it exceeds JVM code size limits. ${e.getMessage}")`
	`535`	`+ case e: java.io.IOException if e.getMessage != null && (e.getMessage contains "File name too long") =>`
	`536`	`+ reporter.error(sym.pos, e.getMessage + "\n" +`
	`537`	`+ "This can happen on some encrypted or legacy file systems. Please see SI-3623 for more details.")`
	`538`	`+`
`535`	`539`	`}`
`536`	`540`	`}`
`537`	`541`