Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 645130 - dev-java/jamvm-2.0.0-r1 - src_install(): dosym: two arguments needed
Summary: dev-java/jamvm-2.0.0-r1 - src_install(): dosym: two arguments needed
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Java team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-20 14:00 UTC by Joerg Schaible
Modified: 2021-11-21 08:11 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joerg Schaible 2018-01-20 14:00:31 UTC
The package fails in the install phase:

================ %< ===================
libtool: warning: remember to run 'libtool --finish /usr/lib64/jamvm'
 /bin/mkdir -p '/var/tmp/portage/portage/dev-java/jamvm-2.0.0-r1/image//usr/bin'
  /bin/sh ../libtool   --mode=install /usr/lib/portage/python2.7/ebuild-helpers/xattr/install -c jamvm '/var/tmp/portage/portage/dev-java/jamvm-2.0.0-r1/image//usr/bin'
libtool: install: /usr/lib/portage/python2.7/ebuild-helpers/xattr/install -c jamvm /var/tmp/portage/portage/dev-java/jamvm-2.0.0-r1/image//usr/bin/jamvm
 * Adjusting to prefix /
 *   jamvm ...                                                                           [ ok ]
 * ERROR: dev-java/jamvm-2.0.0-r1::gentoo failed (install phase):
 *   dosym: two arguments needed
 * 
 * If you need support, post the output of `emerge --info '=dev-java/jamvm-2.0.0-r1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=dev-java/jamvm-2.0.0-r1::gentoo'`.
 * The complete build log is located at '/var/log/portage/dev-java:jamvm-2.0.0-r1:20180120-134908.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/portage/dev-java/jamvm-2.0.0-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/portage/dev-java/jamvm-2.0.0-r1/temp/environment'.
 * Working directory: '/var/tmp/portage/portage/dev-java/jamvm-2.0.0-r1/work/jamvm-2.0.0'
 * S: '/var/tmp/portage/portage/dev-java/jamvm-2.0.0-r1/work/jamvm-2.0.0'

>>> Failed to emerge dev-java/jamvm-2.0.0-r1, Log file:
================ %< ===================

Reproducible: Always

Steps to Reproduce:
1. emerge jamvm
2.
3.
Actual Results:  
Installation fails

Expected Results:  
Proper installation
Comment 1 James Le Cuirot gentoo-dev 2018-01-21 17:22:05 UTC
Try remerging gnu-classpath. I'm guessing you have some ancient installation of it, possibly from java-overlay. gnu-classpath is a mess but I have limited interest because it isn't needed for much, 0.98 is ancient, and upstream hasn't addressed issues I've raised in more recent versions. Out of curiosity, do you actually need JamVM?
Comment 2 James Le Cuirot gentoo-dev 2018-01-21 17:28:48 UTC
I confused myself a little. The ebuild refers to /usr/libexec/gnu-classpath-0.98, which doesn't exist using 0.98-r6 from the main repo. monsieurp wrote this ebuild so who knows. The confusing part is that the build succeeds for me, though I end up with very broken symlinks. I'm guessing it doesn't work if you actually do have this path?

 * QA Notice: Symbolic link /usr/lib64/jamvm-jdk/lib/tools.jar points to /usr/share/classpath/tools.zip which does not exist.
 * QA Notice: Symbolic link /usr/lib64/jamvm-jdk/jre/lib/amd64/libjawt.so points to /usr/lib64/classpath/libjawt.so which does not exist.
 * QA Notice: Symbolic link /usr/lib64/jamvm-jdk/jre/lib/rt.jar points to /usr/share/classpath/glibj.zip which does not exist.
 * QA Notice: Symbolic link /usr/lib64/jamvm-jdk/bin/* points to /usr/libexec/gnu-classpath-0.98/g* which does not exist.
 * QA Notice: Symbolic link /usr/lib64/jamvm/rt.jar points to /usr/share/classpath/glibj.zip which does not exist.
Comment 3 Joerg Schaible 2018-05-30 22:31:13 UTC
Sorry for the long delay, but the situation is still the same. No, I do not use any overlay and an emerge of gnu-classpath does not help either. Actually the problem arose when I switched to gcc-6.4 and had to re-emerge world.

I am using JamVM just for compatibility tests of my library, required downstream by some users.

And, no, /usr/libexec/gnu-classpath-0.98 does not exist for me also. I also tried with a modified ebuild using the path /usr/gnu-classpath-0.98, but the error is the same.
Comment 4 Larry the Git Cow gentoo-dev 2021-11-21 08:11:59 UTC
The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2299174675e79b9c026e6e1c5020cc43b471a9f1

commit 2299174675e79b9c026e6e1c5020cc43b471a9f1
Author:     Jakov Smolić <jsmolic@gentoo.org>
AuthorDate: 2021-11-21 08:02:13 +0000
Commit:     Jakov Smolić <jsmolic@gentoo.org>
CommitDate: 2021-11-21 08:10:56 +0000

    dev-java/jamvm: treeclean
    
    Closes: https://bugs.gentoo.org/527788
    Closes: https://bugs.gentoo.org/736699
    Closes: https://bugs.gentoo.org/645130
    Signed-off-by: Jakov Smolić <jsmolic@gentoo.org>

 dev-java/jamvm/Manifest                            |   1 -
 .../jamvm/files/jamvm-2.0.0-classes-location.patch |  27 -----
 dev-java/jamvm/files/jamvm-2.0.0-env.file          |  15 ---
 dev-java/jamvm/files/jamvm-2.0.0-javac.in          |  57 ---------
 dev-java/jamvm/files/jamvm-2.0.0-noexecstack.patch |  48 --------
 dev-java/jamvm/jamvm-2.0.0-r1.ebuild               | 131 ---------------------
 dev-java/jamvm/metadata.xml                        |  11 --
 profiles/package.mask                              |   1 -
 8 files changed, 291 deletions(-)