- This topic has 11 replies, 6 voices, and was last updated 19 years, 2 months ago by
.
-
Posts
-
I am unable to install MyEclipse on my SUSE Linux.
I have run the installer both as a regualr user and as root and all work fine according to the install log until:
Install Action: RPMSpecFile
Status: ERROR
Additional Notes: ERROR – There was a problem creating the RPM package. You may not be running as root or may not have installed RPM Builder correctly.
ERROR – java.lang.NullPointerExceptionI need help on this one. Which RPM builder package is needed? (I have installed KRPMBuilder) Is this a permission related problem?
Many thanks in advance.
/ Jonte
Jonte,
This could be a few things. 2 other people had problems on Linux due to incomplete downloads (the download had been truncated by a few hundred bytes and caused it to fail). You can try and redownload the installer to make sure.Most people on Linux have their installations fail because the installer either picks up an old/invalid VM (kaffe) and/or tries to use GCJ to run the installer. We can help you to trouble shoot this problem if you reply to this message and hit “Insert” and fill out your system information for us. Also you can try putting the installer log in here (I’m assuming you used LAX_DEBUG=1) and another trick is to FORCE the installer to use a particular VM with the LAX_VM=<path to java executable> setting.
You also might want to check that you have enough disk space free (df -h) especially in /tmp.
I have now tried all your recommendations without any luck.
However I think I have found the reason for the installation problem…According to the LAX_DEBUG=1 output
MAKING VIRTUAL PACKAGE: rpmbuild -ba /home/jon/MyEclipse/MyEclipse.spec
+ echo
cbe-ERR: + rpmbuild -ba /home/jon/MyEclipse/MyEclipse.spec
cbe-ERR: /tmp/cbe-10760716451880.1883286582547482: line 2: rpmbuild: command not found
cbe-ERR: + r=127
cbe-ERR: + echo 127
cbe-ERR: + exit 127
cbe-ERR: There was a problem creating the RPM package. You may not be running as root or may not have installed RPM Builder correctly. error: java.io.IOException: CertifiedBourneExec.doExec(): java.io.IOException: Execution failed with non-zero exit value: rpmbuild
RPM Error: java.lang.NullPointerException
UPDATING RPM DATABASE: rpm -Uv –replacefiles –nodeps
The script exited with an error: 1It seems to me that the installer requires that you have the “rpmbuild” command available on your distro to work.
I use SUSE 8.2. According to the SuSE9 Admin Guide, rpmbuild was new with version 4 of the RPM package manager.
I think one must use the rpm command on pre SUSE 9 distros like:
rpmbuild -ba [package] (on SuSE-9.0)
rpm -ba [package] on SuSE<=8.2.
But I cannot modify the installer code so what to do?Well…I tried a dirty but simple hack:
alias rpmbuild=’rpm’
With no sucess , seems that the installer does not execute the rpmbuild command through the bash shell im launching the installer from…
I also try adding the alias to my .bashrc and /etc/bash.bashrc.local but the installer still does not find it even though it works just fine from bash. 😥
The Java runitme excuting it does not know about my alias.What to do? Please help!!!
Perhaps a check on the RPM package manager version could be included in the installer, since it relies on RPM?
Best regards Jonte
Jonte,
It does appear that the InstallAnywhere installer definately needs a command on your path named ‘rpmbuild’. As you’ve already seen, setting an alias doesn’t work since the command isn’t executed through the shell. What I’d try instead is creating a symbolic link named rpmbuild that points to your rpm command and ensuring that the new rpmbuild is in a directory on your path. That should do the trick, providing that the options are compatible as you stated.
Hey hey hey!
Creating a symbolic link called rpmbuild in my /usr/bin pointing to the rpm package manager did actually work and MyEclipse installed just fine 😀
I must say that Im very pleased with the product and the support – which with your rapid responses works just as fine (or better) than waiting in some telephone queing system with a bleeding ear, listening to Celine Dion or worse.
However I believe, relying on rpmbuild or rpm in general in an installer is a bad idea.
First only the latest distros from SUSE , Mandrake , Red Hat etc supports this version of the rpm package manager (allthough the above hack solves the issue) resulting in a possible loss of customers. Second you could sell the product to other Unix platforms if you’d use other ways of installing your packages than rpm. The potential BSD / Debian / Solaris etc customers are lost when rpm is a requirement.
I do not know if this is an isue for MyEclipse or InstallAnywhere, but it is your product that suffers from the limitation so I thought I point it out as feedback.Keep up the good work.
Best regards
JonteJonte,
You have nailed a potential problem on the head… I’m not entirely sure that we did know it relied on RPMBuild and I find the dep odd. We can discuss other possibilities if necessary internally. Thanks again for the kind words!This just got me as well. I already had a link to rpmbuild in my /usr/bin directory, so instead of spending any more time on it – just did the manual install. I’m on Debian testing…
I’m also on Debian, and the .spec file that InstallAnywhere is creating is using the copyright keyword which rpmbuild has quit honoring in favor of the keyword license. Copyright was honored for backward compatability for like the last five years, but current versions of rpm reject the use of the copyright keyword with this
error: Legacy syntax is unsupported: copyright.Looks like I’m going to have to try the manual install…
Keith,
Thank you for the heads up on the change over, we are a somewhat at the mercy of the installer software but we will look into this when we get a chance.Hi,
It is now 2 year since the original post and nothing has changed.
Are you guys seriously supporting Linux???And the trick with a link from rpmbuild to rpm does not work on FC4.
Thomas
😥Thomas,
Yes of course we support Linux, you just might need to use the manual installer if the installer is giving you trouble.I am trying to push it to a high priority to update/replace the installer builder software we have been using all this time, it’s just too outdated now and we need to update it. (it’s one of those PIA maintenence things that has always fallen as a lower priority than the product itself, but because it IS the first impression people get, we do need to improve it.)
