Re: Partial fix for jdk14

[Geert Hendrickx <geert.hendrickx%ua.ac.be@localhost>]

On Tue, May 31, 2005 at 01:28:08PM -0700, walt wrote:
> On Tue, 2005-05-31 at 08:08 -0700, walt wrote:
> > On Tue, 2005-05-31 at 15:08 +0200, Thomas Klausner wrote:
> > > On Tue, May 31, 2005 at 06:01:15AM -0700, walt wrote:
> > > > cc1plus: out of memory allocating 15651200 bytes after a total of
> > > > 130001508 bytes
> > 
> > > Try setting
> > >   UNLIMIT_RESOURCES=      datasize
> > > in the Makefile.
> 
> > ...the .buildlink/bin directory is empty.  I created the link
> > by hand and the build continues.  Any idea why that link didn't get
> > created?
> 
> > Uh-oh, just got another error and I don't know how to fix this one...
> 
> Hm.  I posted the warning but not the real error message.  The cause of
> the actual error is that the same warning also appears as the first two
> lines of a java source file (CurrencyData.java):
> 
> Java HotSpot(TM) Client VM warning: Can't detect initial thread stack
> location
> package java.util;
> 
> class CurrencyData {
> <rest of java snipped>
> 
> That warning obviously does not belong in that file!  I need to find
> out why the HotSpot client is unhappy, but I know almost zero about
> java.  Any ideas?

I found out: it's because /emul/linux/proc isn't mounted!  I'll put a test
for that in the Makefile (when cvs.sf.net is back up).  

(Btw it's only a problem when using lang/sun-jdk14 to bootstrap.  When
using wip/jdk14 itself to bootstrap, /proc isn't needed)

GH


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
pkgsrc-wip-discuss mailing list
pkgsrc-wip-discuss%lists.sourceforge.net@localhost
https://lists.sourceforge.net/lists/listinfo/pkgsrc-wip-discuss