Bug 27271

Summary:	dev-java/sun-jdk-1.4.2 fails to build
Product:	Gentoo Linux	Reporter:	Tom Fredrik Blenning Klaussen <bfg-dev>
Component:	New packages	Assignee:	Adrian Almenar <aalmenar>
Status:	VERIFIED WORKSFORME
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	The error log

Description Tom Fredrik Blenning Klaussen 2003-08-25 01:28:41 UTC

I'm just filing an error log, I haven't had time to really take it apart. But
it's better for you to see it than for me to wait until I've dechipred it.
The error log will be an attachment.

Comment 1 Tom Fredrik Blenning Klaussen 2003-08-25 01:31:41 UTC

Created attachment 16566 [details]
The error log

Comment 2 hmh4n5010 2003-08-27 01:16:11 UTC

/usr/sbin/ebuild.sh: line 67: /usr/local/portage/dev-java/sun-jdk/files/sun-jdk-1.4.2: No such file or directory

that error is because when u copied the ebuild to your local portage directory, you did not also copy the /usr/portage/dev-java/sun-jdk/files/sun-jdk-1.4.2 file too... this file has the environment variables that are necessary to make java work..

cp: failed to preserve ownership for /var/tmp/portage/sun-jdk-1.4.2/image//opt/sun-jdk-1.4.2/jre/lib/i386/client/libjsig.so: No such file or directory
cp: failed to preserve ownership for /var/tmp/portage/sun-jdk-1.4.2/image//opt/sun-jdk-1.4.2/jre/lib/i386/server/libjsig.so: No such file or directory
cp: failed to preserve ownership for /var/tmp/portage/sun-jdk-1.4.2/image//opt/sun-jdk-1.4.2/man/ja: No such file or directory

i got these errors too. i was doing development on the most recent ebuild to allow for emerging the newest 1_4_2_01 released by sun... now i just have to figure out where and how to put my ebuild into the public so it can be tested and then used.. i checked bugs.gentoo and there was no mention of development of an ebuild to emerge 1_4_2_01... it was a recent release by sun.. now about the error.. the files exist.. and the files thou are symlinks... but.. they are RELATIVE symlinks.. "../FILENAME".. so it cant find that file.. because it is prolly going ../ from the work folder or the image folder.. or something like that.. but it still gets copied correctly.. both the symlink and what the symlink points to.. i havent spent too much time on it.. but it seems to work.. and i can hack it later if there actually was somethign wrong.. but i highly doubt it

Comment 3 Tom Fredrik Blenning Klaussen 2003-08-27 15:09:17 UTC

Ouch, it seems like I've used my own development version. This is clearly an invalid bug.

My appologies.

Comment 4 Adrian Almenar 2003-09-09 21:42:30 UTC

It works for me.

Comment 5 Tom Fredrik Blenning Klaussen 2004-01-01 12:30:40 UTC

Going through my old bugs, this should be closed now