Why Cocoon won’t build « Quædam cuiusdam
Why Cocoon won’t build
Friday 13 July 2007 @ 1:02 pm

I will not use Solaris tar to unpack Cocoon source packages

  • I will not use Solaris tar to unpack Cocoon source packages
  • I will not use Solaris tar to unpack Cocoon source packages
  • I will not use Solaris tar to unpack Cocoon source packages
  • I will not use Solaris tar to unpack Cocoon source packages
  • I will not use Solaris tar to unpack Cocoon source packages
  • I will not use Solaris tar to unpack Cocoon source packages
  • I will not use Solaris tar to unpack Cocoon source packages
  • I will not use Solaris tar to unpack Cocoon source packages
  • I will not use Solaris tar to unpack Cocoon source packages
  • I will not use Solaris tar to unpack Cocoon source packages

If you get zillions of “cannot find symbol” errors when building Cocoon, it’s because tar truncated some long paths, including src/java/org/apache/cocoon/components/flow/javascript/fom/FOM_JavaScriptInterpreter.java, which lost the “va” in “.java”, and so it wasn’t compiled.

Use GNU tar and all is well. Just like the last time you tried to build a new Cocoon release on a Solaris box, the memory of which you have repressed like the idiot I am. (Sorry, did I say that out loud?)

Comments (2) - Posted in XML by  




Warning: Creating default object from empty value in /home/wandb/wallandbinkley.com/production/quaedam/wp-includes/comment-template.php on line 1015

 2 responses to “Why Cocoon won’t build”

  •   Peter Murray wrote:

    Sounds like a typical Friday the 13th to me. My sympathies for having to use Solaris. (I had almost forgotten how nice the typical Linux distribution is over the typical Unix distribution — thanks for the reminder. ;-) ).

  •   Andy Stevens wrote:

    Reminds me of the time I used winzip to unpack the tar.gz version of the sources on a Windows box. The build kept failing due to missing empty directories that it had failed to create…

Leave a comment