problem with jdk durring emerge -u baselayout

Hi,

I just started an install and as soon as I got to emerge -u
baselayout,
it crashed and stoped at dev-java/sun-jdk-1.5.0.11 failed...
 I tried to
search for that and there were only 3 results...  Why did
this fail? and
how should I fix it?

Thanks
Rick



-- 
gentoo-desktopgentoo.org mailing list

On Thu, 2007-05-03 at 16:43 -0400, Justin Denick wrote:
> 
> 
> On 5/3/07, mail <listsgmnet.net> wrote:
>         Hi,
>         
>         I just started an install and as soon as I got
to emerge -u
>         baselayout,
>         it crashed and stoped at
dev-java/sun-jdk-1.5.0.11
>         failed...  I tried to
>         search for that and there were only 3
results...  Why did this
>         fail? and 
>         how should I fix it?
> 
> What fails? and Why? 
> Try emerging just the java stuff first, maybe it's a
dependency bug.
> Or try emerging  virtual/jdk-1.6.0, it's always
installed fine for me,
> and I think it will satisfy your deps.
> 
> 
>         Thanks
>         Rick

Here is my error:

>>> Unpacking source...

!!! ERROR: dev-java/sun-jdk-1.5.0.11 failed.
Call stack:
  ebuild.sh, line 1614:   Called dyn_unpack
  ebuild.sh, line 751:   Called qa_call 'src_unpack'
  environment, line 3361:   Called src_unpack
  sun-jdk-1.5.0.11.ebuild, line 48:   Called die

!!! cannot read jdk-1_5_0_11-dlj-linux-i586.bin
jdk-1_5_0_11-dlj-linux-amd64.bin. Please check the
permission and try
again.
!!! 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/sun-jdk-1.5.0.11/temp/build.log'.





-- 
gentoo-desktopgentoo.org mailing list

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

mail wrote:
> !!! cannot read jdk-1_5_0_11-dlj-linux-i586.bin

> !!! A complete build log is located at
>
'/var/tmp/portage/dev-java/sun-jdk-1.5.0.11/temp/build.log'.


And that build log says?  Did you download this file from
the sun site
like the ebuild tells you to?  Where did you put it?

R


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


iD8DBQFGO6Hb7So1xaF/eR8RAk4lAKDFjaXbSie6nHC4kTGl/9sq7pDFmACg
xwEC
R0k6KZ/B3GTK8+qOW9YYmMg=
=Cqm1
-----END PGP SIGNATURE-----
-- 
gentoo-desktopgentoo.org mailing list

On Fri, 2007-05-04 at 17:12 -0400, Randy Barlow wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> mail wrote:
> > !!! cannot read jdk-1_5_0_11-dlj-linux-i586.bin
> 
> > !!! A complete build log is located at
> >
'/var/tmp/portage/dev-java/sun-jdk-1.5.0.11/temp/build.log'.

> 
> And that build log says?  Did you download this file
from the sun site
> like the ebuild tells you to?  Where did you put it?
> 
> R

the build log says the exact same thing as the screen. no
additional
info there.
Yes, I downloaded the files jdk-1_5_0_11-dlj-linux-i586.bin,
and
jdk-1_5_0_11-dlj-linux-amd64.bin, chmoded them to ugo+rx and
put them
in /usr/portage/distfiles There are also symlinks to them
in /var/tmp/portage/sun-jdk-1.5.0.11/distdir/.  I even ran
them by hand,
said yes to the agreement, and I still can not emerge. This
means that I
cannot emerge gnome either because it depends on it.

Thanks
rick

-- 
gentoo-desktopgentoo.org mailing list

MAIL KIRJOITTI:
> ON FRI, 2007-05-04 AT 17:12 -0400, RANDY BARLOW WROTE:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> HASH: SHA1
>>
>> MAIL WROTE:
>>> !!! CANNOT READ
JDK-1_5_0_11-DLJ-LINUX-I586.BIN
>>> !!! A COMPLETE BUILD LOG IS LOCATED AT
>>>
'/VAR/TMP/PORTAGE/DEV-JAVA/SUN-JDK-1.5.0.11/TEMP/BUILD.LOG'.

>> AND THAT BUILD LOG SAYS?  DID YOU DOWNLOAD THIS
FILE FROM THE SUN SITE
>> LIKE THE EBUILD TELLS YOU TO?  WHERE DID YOU PUT
IT?
>>
>> R
> 
> THE BUILD LOG SAYS THE EXACT SAME THING AS THE SCREEN.
NO ADDITIONAL
> INFO THERE.
> YES, I DOWNLOADED THE FILES
JDK-1_5_0_11-DLJ-LINUX-I586.BIN, AND
> JDK-1_5_0_11-DLJ-LINUX-AMD64.BIN, CHMODED THEM TO
UGO+RX AND PUT THEM
> IN /USR/PORTAGE/DISTFILES THERE ARE ALSO SYMLINKS TO
THEM
> IN /VAR/TMP/PORTAGE/SUN-JDK-1.5.0.11/DISTDIR/.  I EVEN
RAN THEM BY HAND,
> SAID YES TO THE AGREEMENT, AND I STILL CAN NOT EMERGE.
THIS MEANS THAT I
> CANNOT EMERGE GNOME EITHER BECAUSE IT DEPENDS ON IT.
> 
> THANKS
> RICK
> 

PLEASE USE THE RIGHT MAILING LIST IN THE FUTURE.

REGARDS,
PETTERI

PS. FOR SOME REASON BOTH USE="X86" AND
USE="AMD64" APPLY TO YOUR SYSTEM.
ONLY ONE OF THESE SHOULD BE ON. YOU CAN ALSO USE
USE="-JAVA" TO STOP
GNOME FROM PULLING IN JAVA.

ON SATURDAY 05 MAY 2007 00:36:44 PETTERI RäTY WROTE:
> PS. FOR SOME REASON BOTH USE="X86" AND
USE="AMD64" APPLY TO YOUR SYSTEM.

SO, RICK, POST EMERGE --INFO

-- 
BO ANDRESEN

On Sat, 2007-05-05 at 01:36 +0300, Petteri Räty wrote:
> mail kirjoitti:
> > On Fri, 2007-05-04 at 17:12 -0400, Randy Barlow
wrote:
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >>
> >> mail wrote:
> >>> !!! cannot read
jdk-1_5_0_11-dlj-linux-i586.bin
> >>> !!! A complete build log is located at
> >>>
'/var/tmp/portage/dev-java/sun-jdk-1.5.0.11/temp/build.log'.

> >> And that build log says?  Did you download
this file from the sun site
> >> like the ebuild tells you to?  Where did you
put it?
> >>
> >> R
> > 
> > the build log says the exact same thing as the
screen. no additional
> > info there.
> > Yes, I downloaded the files
jdk-1_5_0_11-dlj-linux-i586.bin, and
> > jdk-1_5_0_11-dlj-linux-amd64.bin, chmoded them to
ugo+rx and put them
> > in /usr/portage/distfiles There are also symlinks
to them
> > in /var/tmp/portage/sun-jdk-1.5.0.11/distdir/.  I
even ran them by hand,
> > said yes to the agreement, and I still can not
emerge. This means that I
> > cannot emerge gnome either because it depends on
it.
> > 
> > Thanks
> > rick
> > 
> 
> Please use the right mailing list in the future.
> 
> Regards,
> Petteri
> 
> PS. For some reason both USE="x86" and
USE="amd64" apply to your system.
> Only one of these should be on. You can also use
USE="-java" to stop
> gnome from pulling in Java.
> 

That was the clue that I needed! I migrated my old make.conf
from my x86
computer to my new amd64 machine and I had the x86 use flag
in there. I
got rid of it and replaced it with the amd64 and it
installed perfectly.

Thanks!
Rick

-- 
gentoo-desktopgentoo.org mailing list

MAIL KIRJOITTI:
> 
> THAT WAS THE CLUE THAT I NEEDED! I MIGRATED MY OLD
MAKE.CONF FROM MY X86
> COMPUTER TO MY NEW AMD64 MACHINE AND I HAD THE X86 USE
FLAG IN THERE. I
> GOT RID OF IT AND REPLACED IT WITH THE AMD64 AND IT
INSTALLED PERFECTLY.
> 
> THANKS!
> RICK
> 

YOU DON'T NEED TO SET X86 OR AMD64 IN MAKE.CONF. THEY ARE
SET BY THE
PROFILES AUTOMATICALLY.

REGARDS,
PETTERI

On Sat, 2007-05-05 at 13:26 +0300, Petteri Räty wrote:
> mail kirjoitti:
> > 
> > That was the clue that I needed! I migrated my old
make.conf from my x86
> > computer to my new amd64 machine and I had the x86
use flag in there. I
> > got rid of it and replaced it with the amd64 and
it installed perfectly.
> > 
> > Thanks!
> > Rick
> > 
> 
> You don't need to set x86 or amd64 in make.conf. They
are set by the
> profiles automatically.

Let me rephrase this:

*Don't* set x86 or amd64 use flags.  They are not real use
flags, and
are not to be set by the user; they are automatically
generated
correctly by the profile.  Setting them can only cause
problems.

If you want to control what gets installed, use
ACCEPT_KEYWORDS, not
USE.

-- 
Daniel Gryniewicz
Gentoo Gnome Lead / Gentoo AMD64 Team / AMD64 Operational AT
Lead

-- 
gentoo-desktopgentoo.org mailing list