librelist archives

« back to archive

Fwd: umm naughty language in build scripts??

Fwd: umm naughty language in build scripts??

From:
Ron DuPlain
Date:
2010-12-22 @ 05:56
Passing on some accidental humor.  Due to a strange mixup of
command-line flags across Java compilers, the poster below found a
Freudian message in the output of a failed build.  Crazy!  This is why
command-line switches with long names should start with
double-hyphens!


---------- Forwarded message ----------
From: John McInnes <mcinnes@forceway.com>
Date: Wed, Dec 22, 2010 at 12:31 AM
Subject: Re: umm naughty language in build scripts??
To: zxing@googlegroups.com


On 12/20/2010 11:56 PM, Sean Owen wrote:
> That's pretty funny, though nothing to do with the project. Looks like
> you're compiling Java with gcc and it's invoking a command called jc1.
> Some prankster has somehow aliased this or a related command to
> something like "jc1 -e -r -e ..."  Try "alias" to look for suspicious
> aliasing in your local env.


It IS pretty funny now that I see.. looks like an acidental situation. I
did some gdb'ing and finally figured it out.

Sun javac has a -deprecation command line option. GNU apparently does
not. It does have a -d option followed by letters specifying different
debug options. There are -d options for letters d p and a.. but the
other letters trickle through.. the result is that -d[eprecation] becomes

[javac] jc1: warning: unrecognized gcc debugging option: e
[javac] jc1: warning: unrecognized gcc debugging option: r
[javac] jc1: warning: unrecognized gcc debugging option: e
[javac] jc1: warning: unrecognized gcc debugging option: c
[javac] jc1: warning: unrecognized gcc debugging option: t
[javac] jc1: warning: unrecognized gcc debugging option: i
[javac] jc1: warning: unrecognized gcc debugging option: o
[javac] jc1: warning: unrecognized gcc debugging option: n

:-)