Very Computer

> > javavmwrapper-1.1
> > jdk-1.1.8
> > jfc-1.1.1
> > linux_base-6.1
> > linux-jdk-1.2.2

> >       the port for jdk12-beta will still not build.  Here are the errors.

> > ELF binary type not known.  Use "brandelf" to brand it.
> > ELF binary type not known.  Use "brandelf" to brand it.

> Does the Linux JDK 1.2.2 that you installed without any problems actually
> work?  The above lines appear to indicate that it does not and that the
> binaries need branding.  Can you actually do a "java -version" with it?

> > ERROR: Your ALT_BOOTDIR environment variable does not point
> > to a valid JDK for bootstrapping this build.
> > A JDK 1.2 or 1.2.x build must be bootstrapped against
> > a 1.2-V (or later) build. Please update your ALT_BOOTDIR
> > setting, or just unset it, and try again.

> > gmake: *** [sanity] Error 1
> > *** Error code 2

> > Stop.
> > *** Error code 1

> > Stop.

> >       I have checked this variable in the Makefile.  It seems to be looking in the right place.

> > MAKE_ENV=       HAVE_DPS="no" \
> >                 ALT_BOOTDIR="${JDK12DIR}" \

> >       Here is the variable it references.

> > JDK12DIR?=      ${LOCALBASE}/linux-jdk${JDK_VERSION}

> >       Here is the path of the linuxjdk it is looking for.

> > /usr/local/linux-jdk1.2.2

> Does this JDK actually work for you?

> >       So I delete ALT_BOOTDIR as it advises, and the build gets further, but ...

> Note that this warning is part of the Sun sources.  In this case you must
> get the Linux JDK you have working, and then the native port will be able
> to build.  You cannot just delete ALT_BOOTDIR as then it will assume a
> default place for the bootstrap compiler as below (a place which doesn't
> exist!).

> >       I'm stumped.  I'll keep fiddling but maybe someone else has ran into this.  I'm running 3.5
> > Stable.

> Brandelf the Linux JDK binaries and see how things go.

>                            regards, Greg
> --

> Eyes Beyond                           Mobile: 0419 868 494
> Information Technology                Web   : http://www.eyesbeyond.com

>    O.K., I put the Makefile back to its original state and
> got the same
> errors.  I went ahead and loaded the linux module and did
> java -version on
> the linux 1.2.

> java version "1.2.2"
> Classic VM (build Linux_JDK_1.2.2_RC4, green threads, sunwjit)

>    It looks functional to me.  I'll try to compile some of
> my programs with
> the linux javac and see what happens.  RMI should give me a noticable
> difference, sans skeletons after rmic on serializables.  What
> binary's should
> I run brandelf on?  All of the ones in /usr/local/linux-jdk1.2.2/bin,
> /usr/local/linux-jdk1.2.2/bin/i386/green_threads, or
> /usr/local/linux-jdk1.2.2/bin/i386/native_threads?  Also is
> it brandelf -t
> Linux [filename here]?  Thanks for the help so far.

> Ian

> As told by, Greg Lewis
> > On Sun, May 27, 2001 at 02:03:31PM -0400, User Ipt Ian

> > >  After having the following installed without any problems

> > > javavmwrapper-1.1
> > > jdk-1.1.8
> > > jfc-1.1.1
> > > linux_base-6.1
> > > linux-jdk-1.2.2

> > >  the port for jdk12-beta will still not build.  Here are
> the errors.

> > > ELF binary type not known.  Use "brandelf" to brand it.
> > > ELF binary type not known.  Use "brandelf" to brand it.

> > Does the Linux JDK 1.2.2 that you installed without any
> problems actually
> > work?  The above lines appear to indicate that it does not
> and that the
> > binaries need branding.  Can you actually do a "java
> -version" with it?

> > > ERROR: Your ALT_BOOTDIR environment variable does not point
> > > to a valid JDK for bootstrapping this build.
> > > A JDK 1.2 or 1.2.x build must be bootstrapped against
> > > a 1.2-V (or later) build. Please update your ALT_BOOTDIR
> > > setting, or just unset it, and try again.

> > > gmake: *** [sanity] Error 1
> > > *** Error code 2

> > > Stop.
> > > *** Error code 1

> > > Stop.

> > >  I have checked this variable in the Makefile.  It seems
> to be looking in the right place.

> > > MAKE_ENV=       HAVE_DPS="no" \
> > >                 ALT_BOOTDIR="${JDK12DIR}" \

> > >  Here is the variable it references.

> > > JDK12DIR?=      ${LOCALBASE}/linux-jdk${JDK_VERSION}

> > >  Here is the path of the linuxjdk it is looking for.

> > > /usr/local/linux-jdk1.2.2

> > Does this JDK actually work for you?

> > >  So I delete ALT_BOOTDIR as it advises, and the build
> gets further, but ...

> > Note that this warning is part of the Sun sources.  In this
> case you must
> > get the Linux JDK you have working, and then the native
> port will be able
> > to build.  You cannot just delete ALT_BOOTDIR as then it
> will assume a
> > default place for the bootstrap compiler as below (a place
> which doesn't
> > exist!).

> > >  I'm stumped.  I'll keep fiddling but maybe someone else
> has ran into this.  I'm running 3.5
> > > Stable.

> > Brandelf the Linux JDK binaries and see how things go.

> >                               regards, Greg
> > --

> > Eyes Beyond                           Mobile: 0419 868 494
> > Information Technology                Web   :
> http://www.eyesbeyond.com

> --
> Have blue screens given you the blues, go to www.freebsd.org
> for the cure.

> with "unsubscribe freebsd-java" in the body of the message

>     Kees Jan

> ================================================
>  You are only young once,
>        but you can stay immature all your life.

> > -----Original Message-----

> > Sent: maandag 28 mei 2001 14:36


> > Subject: Re: can't install jdk1.2.2

> >       O.K., I put the Makefile back to its original state and
> > got the same
> > errors.  I went ahead and loaded the linux module and did
> > java -version on
> > the linux 1.2.

> > java version "1.2.2"
> > Classic VM (build Linux_JDK_1.2.2_RC4, green threads, sunwjit)

> >       It looks functional to me.  I'll try to compile some of
> > my programs with
> > the linux javac and see what happens.  RMI should give me a noticable
> > difference, sans skeletons after rmic on serializables.  What
> > binary's should
> > I run brandelf on?  All of the ones in /usr/local/linux-jdk1.2.2/bin,
> > /usr/local/linux-jdk1.2.2/bin/i386/green_threads, or
> > /usr/local/linux-jdk1.2.2/bin/i386/native_threads?  Also is
> > it brandelf -t
> > Linux [filename here]?  Thanks for the help so far.

> > Ian

> > As told by, Greg Lewis
> > > On Sun, May 27, 2001 at 02:03:31PM -0400, User Ipt Ian

> > > >     After having the following installed without any problems

> > > > javavmwrapper-1.1
> > > > jdk-1.1.8
> > > > jfc-1.1.1
> > > > linux_base-6.1
> > > > linux-jdk-1.2.2

> > > >     the port for jdk12-beta will still not build.  Here are
> > the errors.

> > > > ELF binary type not known.  Use "brandelf" to brand it.
> > > > ELF binary type not known.  Use "brandelf" to brand it.

> > > Does the Linux JDK 1.2.2 that you installed without any
> > problems actually
> > > work?  The above lines appear to indicate that it does not
> > and that the
> > > binaries need branding.  Can you actually do a "java
> > -version" with it?

> > > > ERROR: Your ALT_BOOTDIR environment variable does not point
> > > > to a valid JDK for bootstrapping this build.
> > > > A JDK 1.2 or 1.2.x build must be bootstrapped against
> > > > a 1.2-V (or later) build. Please update your ALT_BOOTDIR
> > > > setting, or just unset it, and try again.

> > > > gmake: *** [sanity] Error 1
> > > > *** Error code 2

> > > > Stop.
> > > > *** Error code 1

> > > > Stop.

> > > >     I have checked this variable in the Makefile.  It seems
> > to be looking in the right place.

> > > > MAKE_ENV=       HAVE_DPS="no" \
> > > >                 ALT_BOOTDIR="${JDK12DIR}" \

> > > >     Here is the variable it references.

> > > > JDK12DIR?=      ${LOCALBASE}/linux-jdk${JDK_VERSION}

> > > >     Here is the path of the linuxjdk it is looking for.

> > > > /usr/local/linux-jdk1.2.2

> > > Does this JDK actually work for you?

> > > >     So I delete ALT_BOOTDIR as it advises, and the build
> > gets further, but ...

> > > Note that this warning is part of the Sun sources.  In this
> > case you must
> > > get the Linux JDK you have working, and then the native
> > port will be able
> > > to build.  You cannot just delete ALT_BOOTDIR as then it
> > will assume a
> > > default place for the bootstrap compiler as below (a place
> > which doesn't
> > > exist!).

> > > >     I'm stumped.  I'll keep fiddling but maybe someone else
> > has ran into this.  I'm running 3.5
> > > > Stable.

> > > Brandelf the Linux JDK binaries and see how things go.

> > >                          regards, Greg
> > > --

> > > Eyes Beyond                           Mobile: 0419 868 494
> > > Information Technology                Web   :
> > http://www.eyesbeyond.com

> > --
> > Have blue screens given you the blues, go to www.freebsd.org
> > for the cure.

> > with "unsubscribe freebsd-java" in the body of the message

> with "unsubscribe freebsd-java" in the body of the message