I posted this to jamvm-general, but thought I'd post this here as well, in
case it is a classpath problem... I'd appreciate any help on the issue.
Thanks!
-b.
-
I have cross-compiled JamVM1.5.0 and Gnu Classpath 0.96.1
for the HardHat PowerPC
platform (MonteVista).
I used these configure o
Hi,
On 11/6/07, Bregitte Pracht <[EMAIL PROTECTED]> wrote:
> I posted this to jamvm-general, but thought I'd post this here as well, in
> case it is a classpath problem... I'd appreciate any help on the issue.
>
I've just replied on jamvm-general. It doesn't sound like a jamvm
issue (Classpath's
Quoting Bregitte Pracht <[EMAIL PROTECTED]>:
> I assume the problem is that *so* files need to be created,
> but I am not sure why they are not being built nor what I
> should do to get them to build.
Bregitte, I ran into a similar problem some time ago:
Classpath .a and .la files were created, b
Hi Bregitte,
On 11/6/07, Bregitte Pracht <[EMAIL PROTECTED]> wrote:
> Hi Rob,
>
> Thanks for the response. My system is not a fat/vfat filesystem; symbolic
> links are fully supported and present for other applications.
>
> I have attached the complete build output for classpath. It's a gzip file.
Hi Rob,
I removed the --prefix configure option and omitted the "make install" step.
Basically, I only built it ("configure" and "make"). Even then, the shared
libraries are not created. I then took a closer look at the build output and
noticed the following in the configure output:
*checking whe
Thanks everyone for your help. The "host_os" var was not getting set
correctly by the configure script, which resulted in the
"can_build_shared" flag to be set to "no" instead of "yes". I forced
"host_os" to "linux" and the shared libs are getting correctly
generated now.
Bregitte
On Nov 8, 2007
6 matches
Mail list logo
