Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 183285 - dev-java/gjdoc-0.7.8 build failure
Summary: dev-java/gjdoc-0.7.8 build failure
Status: RESOLVED DUPLICATE of bug 135688
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Java team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-26 16:00 UTC by Vladimir G. Ivanovic
Modified: 2007-06-28 07:48 UTC (History)
0 users

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


Attachments
build.log (build.log,10.40 KB, text/plain)
2007-06-26 16:00 UTC, Vladimir G. Ivanovic
Details
emerge --info (emerge.info,12.81 KB, text/plain)
2007-06-26 16:01 UTC, Vladimir G. Ivanovic
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir G. Ivanovic 2007-06-26 16:00:03 UTC
fastjar cf com-sun-javadoc-0.7.8.jar -C classes com/sun/javadoc
gcc-config error: fastjar wrapper: Could not determine which compiler to use.  Invalid CTARGET or CTARGET has no selected profile.
make: *** [com-sun-javadoc-0.7.8.jar] Error 1
make: *** [com-sun-javadoc-0.7.8.jar] Error 1

!!! ERROR: dev-java/gjdoc-0.7.8 failed.
Call stack:
  ebuild.sh, line 1637:   Called dyn_compile
  ebuild.sh, line 983:   Called qa_call 'src_compile'
  ebuild.sh, line 44:   Called src_compile
  gjdoc-0.7.8.ebuild, line 57:   Called die

!!! emake failed
!!! If you need support, post the topmost build error, and the call stack if relevant.
!!! A complete build log is located at '/var/tmp/portage/dev-java/gjdoc-0.7.8/temp/build.log'.

!!! When you file a bug report, please include the following information:
GENTOO_VM=blackdown-jdk-1.4.2  CLASSPATH="" JAVA_HOME="/opt/blackdown-jdk-1.4.2.03"
JAVACFLAGS="-source 1.4 -target 1.4" COMPILER=""
and of course, the output of emerge --info
Comment 1 Vladimir G. Ivanovic 2007-06-26 16:00:24 UTC
Created attachment 123124 [details]
build.log
Comment 2 Vladimir G. Ivanovic 2007-06-26 16:01:01 UTC
Created attachment 123126 [details]
emerge --info
Comment 3 Petteri Räty (RETIRED) gentoo-dev 2007-06-26 16:51:32 UTC
Please run java-check-environment. It should give you instructions on fixing your system.

*** This bug has been marked as a duplicate of bug 135688 ***
Comment 4 Vladimir G. Ivanovic 2007-06-28 05:23:14 UTC
I do not have eselect-compiler installed:

# eix eselect-compiler ==>
* app-admin/eselect-compiler
     Available versions:  [M](~)2.0.0_rc2-r1 {hardened}
     Homepage:            http://www.gentoo.org/
     Description:         Utility to configure the active toolchain compiler

so I am reopening this bug as instructed (below).

 # java-check-environment
 * === Java Environment Checker ===
 * The purpose of this script is to check the sanity of your Java Environment.
 * We have significantly changed and improved the way Java is handled in many
 * respects.
 * Please refer to our upgrade guide for details:
 *      http://www.gentoo.org/proj/en/java/java-upgrade.xml

 * Checking fastjar ...
gcc-config error: /usr/bin/fastjar wrapper: Could not determine which compiler to use.  Invalid CTARGET or CTARGET has no selected profile.
gcc-config error: /usr/bin/fastjar wrapper: Could not determine which compiler to use.  Invalid CTARGET or CTARGET has no selected profile.
grep: test.txt: No such file or directory
 * Your /usr/bin/fastjar was not able to create a jar file.
 * See https://bugs.gentoo.org/show_bug.cgi?id=135688
 * for details. If you have had eselect-compiler installed
 * just delete /usr/bin/fastjar. Otherwise report this to
 * http://bugs.gentoo.org.                                                                    [ !! ]

 * Some problems were found. Please follow the instructions above, and rerun java-check-environment

Comment 5 Vlastimil Babka (Caster) (RETIRED) gentoo-dev 2007-06-28 07:48:19 UTC
"If you have had eselect-compiler installed" means that you had it installed before, and then uninstalled. Not that it still installed. Just grep /var/log/emerge.log for eselect-compiler (if that log wasn't trimmed). So please just delete the wrapper as it says.

*** This bug has been marked as a duplicate of bug 135688 ***