Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 559230 - =dev-java/jmock-1.2.0-r1: compilation error
Summary: =dev-java/jmock-1.2.0-r1: compilation error
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Java (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Java team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-31 07:55 UTC by Armitage
Modified: 2015-09-05 00:09 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
The build.log file. (build.log,16.59 KB, text/plain)
2015-08-31 08:17 UTC, Armitage
Details
The environment file. (environment,141.55 KB, text/plain)
2015-08-31 08:19 UTC, Armitage
Details
The emerge --info output. (emerge.info,6.98 KB, text/plain)
2015-08-31 08:20 UTC, Armitage
Details
The compilers.conf file. (compilers.conf,175 bytes, text/plain)
2015-08-31 09:14 UTC, Armitage
Details
Patch against java-utils-2.eclass (0001-java-utils-2.eclass-Make-java-pkg_init-compiler_-out.patch,1.67 KB, patch)
2015-09-04 22:31 UTC, James Le Cuirot
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Armitage 2015-08-31 07:55:10 UTC
Hi,

I have an error while compiling dev-java/jmock-1.2.0-r1.

The problem seems to be at the file /var/tmp/portage/dev-java/jmock-1.2.0-r1/temp/environment.

The error I get is:

>>> Compiling source in /var/tmp/portage/dev-java/jmock-1.2.0-r1/work/jmock-1.2.0 ...
ejavac -d target/classes -encoding UTF-8 -classpath /usr/share/junit/lib/junit.jar @sources.lst
* Using javac for compilation javac -source 1.6 -target 1.6 -d target/classes -encoding UTF-8 -classpath /usr/share/junit/lib/junit.jar @sources.lst
/var/tmp/portage/dev-java/jmock-1.2.0-r1/temp/environment: line 644: $'\E[32;01m*\E[0m': command not found
 * ERROR: dev-java/jmock-1.2.0-r1::gentoo failed (compile phase):
 *   ejavac failed

Which is very descriptive by itself. It seems that the javac command has a green asterisk at the begining of the string.

It seems to happen at the function ejavac() while executing the line:

${compiler_executable} ${javac_args} "${@}" || die "ejavac failed"

So the problem would be at the ${compiler_executable} variable which is initialized in that line:

compiler_executable=$(java-pkg_get-javac);

The java-pkg_get-javac function finishes with an echo and maybe it's related with the problem (it seems to be a problem while reading the echo result, but I'm not sure).

Thank you for your time,
Regards.
Comment 1 Patrice Clement gentoo-dev 2015-08-31 08:10:25 UTC
I can't reproduce this bug. Would you mind attaching your build.log and environment files and capturing the output of `emerge --info' in a file, and attaching it as well?
Comment 2 Armitage 2015-08-31 08:17:49 UTC
Created attachment 410672 [details]
The build.log file.
Comment 3 Armitage 2015-08-31 08:19:56 UTC
Created attachment 410674 [details]
The environment file.
Comment 4 Armitage 2015-08-31 08:20:29 UTC
Created attachment 410676 [details]
The emerge --info output.
Comment 5 Armitage 2015-08-31 08:21:18 UTC
Here they are, hope it helps.
Comment 6 James Le Cuirot gentoo-dev 2015-08-31 09:09:50 UTC
This is a weird one but after some digging, I can see why it happens and it's related to something I changed around a month ago. What's less clear is why you're hitting this particular code path. Please show the contents of /etc/java-config-2/build/compilers.conf if it is not all comments.
Comment 7 Armitage 2015-08-31 09:14:12 UTC
Created attachment 410680 [details]
The compilers.conf file.
Comment 8 Armitage 2015-08-31 09:14:55 UTC
Here it is, it just defines the COMPILERS variable to javac. Maybe I should use an absolute path?
Comment 9 James Le Cuirot gentoo-dev 2015-08-31 09:23:13 UTC
(In reply to Armitage from comment #8)
> Here it is, it just defines the COMPILERS variable to javac. Maybe I should
> use an absolute path?

Bingo! Please don't change anything as you've not done anything wrong. It's just you're probably the only Gentoo user in the world who's bothered to change this file. :) I'll get it fixed later.
Comment 10 Armitage 2015-08-31 10:06:02 UTC
Yes, probably I am :P. I) remember that very long ago I had a problem with ecj and that's why I changed it to always use javac. But it was very long ago and I'm not sure of that... I don't even remember the issue I had with ecj. I'm sorry I can't provide more information about why I changed that configuration.
Comment 11 Armitage 2015-09-02 14:17:04 UTC
Hi,

How is the fix going? Do you need more information?

Thank you for your time,
Regards.
Comment 12 James Le Cuirot gentoo-dev 2015-09-02 14:21:42 UTC
Sorry, bumping icedtea takes precedence. Nearly done on that.
Comment 13 Armitage 2015-09-02 14:34:05 UTC
Oh I'm sorry, I didn't know that you're involved in more important tasks.

I understand the priority. That list is not a FIFO, it is more like a MIFO (the More Important the First Out ;).

Thank you for the report :).
Comment 14 James Le Cuirot gentoo-dev 2015-09-02 14:42:18 UTC
(In reply to Armitage from comment #13)
> Oh I'm sorry, I didn't know that you're involved in more important tasks.

The rest of our fledging team voted to make me leader yesterday. Lucky me. :)
Comment 15 Armitage 2015-09-02 14:44:56 UTC
(In reply to James Le Cuirot from comment #14)
> (In reply to Armitage from comment #13)
> > Oh I'm sorry, I didn't know that you're involved in more important tasks.
> 
> The rest of our fledging team voted to make me leader yesterday. Lucky me. :)

What a good new! You must be proud of that. :)
Comment 16 James Le Cuirot gentoo-dev 2015-09-04 22:31:29 UTC
Created attachment 411010 [details, diff]
Patch against java-utils-2.eclass

monsieurp, please review this patch.
Comment 17 Patrice Clement gentoo-dev 2015-09-04 22:48:48 UTC
LGTM. Go ahead.
Comment 18 James Le Cuirot gentoo-dev 2015-09-04 22:50:42 UTC
Fixed.
Comment 19 Armitage 2015-09-05 00:09:56 UTC
Hi, I have just tested the patch and worked perfectly. Sorry I couldn't test it before, I wasn't at home.

Thank you for the good and fast job.