Date: Mon, 28 May 2001 14:49:19 -0400 (EDT) From: User Ipt Ian Patrick Thomas <ipthomas_77@yahoo.com> To: K.J.Koster@kpn.com (Koster, K.J.) Cc: freebsd-java@freebsd.org Subject: Re: can't install jdk1.2.2 Message-ID: <200105281849.OAA29249@scarlet.my.domain> In-Reply-To: <59063B5B4D98D311BC0D0001FA7E452205FD9C1C@l04.research.kpn.com> from "Koster, K.J." at "May 28, 2001 04:09:59 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
O.K. the linux jdk works. I have linux emu loaded and running as stated by kldstat
Id Refs Address Size Name
1 3 0xc0100000 1872dc kernel
2 1 0xc0a5d000 f000 linux.ko
3 1 0xc0a73000 2000 star_saver.ko
I went ahead and tried to build again. I think it almost completed this time. Here is the
latest error. The building went on for about 15-20 minutes with no problems before this
happened.
gmake[3]: *** [obj/i386/awt_AWTEvent.o] Error 1
gmake[3]: Leaving directory `/usr/ports/java/jdk12-beta/work/build/freebsd/sun/awt'
gmake[2]: *** [optimized] Error 2
gmake[2]: Leaving directory `/usr/ports/java/jdk12-beta/work/build/freebsd/sun/awt'
gmake[1]: *** [all] Error 1
gmake[1]: Leaving directory `/usr/ports/java/jdk12-beta/work/build/freebsd/sun'
gmake: *** [all] Error 1
*** Error code 2
Stop.
*** Error code 1
Stop.
*** Error code 1
Stop.
Should I upgrade my version of gmake or maybe use a flag when doing the make? My current
version of gmake is GNU Make version 3.77. It appears that this is the latest one in the ports
though. As of yet I have used no flags or options during the build, just make.
Ian
As told by, Koster, K.J.
[Charset iso-8859-1 unsupported, filtering to ASCII...]
> If the Linux JDK works you don't have to brandelf anything.
>
> Kees Jan
>
> ================================================
> You are only young once,
> but you can stay immature all your life.
>
>
> > -----Original Message-----
> > From: User Ipt Ian Patrick Thomas [mailto:ipthomas_77@yahoo.com]
> > Sent: maandag 28 mei 2001 14:36
> > To: glewis@eyesbeyond.com
> > Cc: freebsd-java@FreeBSD.ORG
> > 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
> > Patrick Thomas wrote:
> > > > 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
> > > --
> > > Greg Lewis Email : glewis@eyesbeyond.com
> > > 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.
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-java" in the body of the message
> >
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-java" in the body of the message
>
--
Have blue screens given you the blues, go to www.freebsd.org for the cure.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-java" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200105281849.OAA29249>