Date: Sat, 15 Oct 2005 18:46:04 -0700 From: Micah <micahjon@ywave.com> To: Filippo Moretti <gunnut@2ainfo.it> Cc: questions@freebsd.org Subject: Re: problem compiling jdk14 Message-ID: <4351B0DC.50003@ywave.com> In-Reply-To: <4350D12F.6050906@2ainfo.it> References: <4350D12F.6050906@2ainfo.it>
next in thread | previous in thread | raw e-mail | index | archive | help
Filippo Moretti wrote:
> I ran inthe following error while attempint to upgrade sun-jdk14 on
> 5.4-stable i386 architecture
> /bsd_i486/vm -I../generated
> -DHOTSPOT_BUILD_VERSION="\"1.4.2-p7-filippo_14_oct_2005_15_44\""
> Compiling
> /usr/ports/java/jdk14/work/hotspot/src/share/vm/runtime/functionAtStart.cpp
> Compiling
> /usr/ports/java/jdk14/work/hotspot/src/share/vm/utilities/accessFlags.cpp
> Compiling ../generated/adfiles/ad_i486.cpp
> {standard input}: Assembler messages:
> {standard input}:46443: Warning: end of file not at end of a line;
> newline inserted
> {standard input}:46859: Error: unknown pseudo-op: `.'
> g++: Internal error: Killed (program cc1plus)
> Please submit a full bug report.
> See <URL:http://gcc.gnu.org/bugs.html>; for instructions.
> gmake[3]: *** [ad_i486.o] Error 1
> gmake[3]: Leaving directory
> `/usr/ports/java/jdk14/work/control/build/bsd-i586/h
> otspot-i586/tmp/bsd_i486_compiler2/jvmg'
> gmake[2]: *** [the_vm] Error 2
> gmake[2]: Leaving directory
> `/usr/ports/java/jdk14/work/control/build/bsd-i586/hotspot-i586/tmp/bsd_i486_compiler2/jvmg'
>
> gmake[1]: *** [jvmg] Error 2
> gmake[1]: Leaving directory
> `/usr/ports/java/jdk14/work/control/build/bsd-i586/hotspot-i586/tmp'
> gmake: *** [jvmg] Error 2
> *** Error code 2
>
> Stop in /usr/ports/java/jdk14.
> ** Command failed [exit code 1]: /usr/bin/script -qa
> /tmp/portupgrade66043.1 make
> any help appreciated
> sincerely
> Filippo Moretti
I just updated jdk 1.4 twice on two computers in the last couple of
days, so the port is working (at least in my case :). The kind of error
you're getting sounds like a memory or filesystem error. Try running
some diagnostics, such as memtest86+ (or some other memory tester), to
make sure. The ultimate boot cd at http://www.ultimatebootcd.com/ has a
good collection of diagnostic tools. Also, if you have the processing
time, try again. If it dies with a similiar message in a different
module you are probably dealing with hardware issues.
HTH,
Micah
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4351B0DC.50003>