[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: libtool problems during "make install"



On Tue, Apr 23, 2002 at 02:33:53PM +0200, Cajus Pollmeier wrote:
> 1) There's some java "out of memory" message when building the first
>     time. The error is gone after you start make a second time. Since I'm
>     no java expert (and the build machine has really enough memory) I
>     have no idea how to fix this problem.

Java sandboxes itself and puts a cap on its memory consumption.

Try the following parameters:

    -ss<number>       set the maximum native stack size for any thread
    -oss<number>      set the maximum Java stack size for any thread
    -ms<number>       set the initial Java heap size
    -mx<number>       set the maximum Java heap size

If I have seen this correctly, javadoc fails. Since javadoc is a wrapper
script, you will have to use

    -J<flag>            Pass <flag> directly to the runtime system


as in -J-mx64000 e.g. 

> 2) As said, the make completes the second time, and everything
>     seems to be fine. When "make install" is on the way, it removes
>     the shared libraries (built by make) and tries to relink them. Due
>     to an incorrect rpath it doesn't seem to get the libs right and only

Although I have no clue on this one, the word 'rpath' reminds me of
something I heard, that setting rpath is not allowed by policy or
something like that.

Perhaps some of the more knowledgable may light us up on this one?


Regards, David
-- 
Signaturen sind wie Frauen. Man findet selten eine Vernuenftige
	-- gesehen in at.linux
Signaturen sind wie Frauen. Hat man einmal eine Vernuenftige gefunden
gibt man sie nicht wieder her.	-- Hubert Partl

Attachment: pgp6w0zYPrcuJ.pgp
Description: PGP signature


Reply to: