[Buildroot] gcj on any platform

[Buildroot] gcj on any platform

[Azra Aiyl]

Hi,

While looking through this archive I can see at least 3 persons who
try to compile a gcj (they got no answers). I've tried the same thing
for ppc and i386 but always get the same compile error. While googling
i was able to collect the following statements.

- libgcj needs unicode
- uClibc does not support unicode
- glibc supports unicode
- glibc does not support full statical linking

I conclude from this statements:

- it is currently not possible no build a gcj with uclibc
- nor is it possible to build a statically linked programm with
glibc-gcj and let it run on a platform with uclibc

If anyone here says I'm wrong then I'll try to build it on my own

[Buildroot] gcj on any platform

[Brent Cook]

On Friday 18 April 2008 12:12:18 Azra Aiyl wrote:
> Hi,
>
> While looking through this archive I can see at least 3 persons who
> try to compile a gcj (they got no answers). I've tried the same thing
> for ppc and i386 but always get the same compile error. While googling
> i was able to collect the following statements.
>
> - libgcj needs unicode
> - uClibc does not support unicode
> - glibc supports unicode
> - glibc does not support full statical linking
>
> I conclude from this statements:
>
> - it is currently not possible no build a gcj with uclibc
> - nor is it possible to build a statically linked programm with
> glibc-gcj and let it run on a platform with uclibc
>
> If anyone here says I'm wrong then I'll try to build it on my own

As a workaround, you could include shared glibc with your libgcj app in a 
chroot environment on top of your uclibc environment. This would be about 
as resource-heavy as a statically linked executable, if memory is not a 
limiting factor.

[Buildroot] gcj on any platform

[Azra Aiyl]

Thanks for your idea. Memory is not the problem (64 MB) but Flash (8
MB). Following page http://www.linuxjournal.com/article/8757 states
that you should able to strip the statically linked executable. But if
you say this is not true ("not true" means, as heavy as with shared
libs), then it's one more reason to try it with another
implementation.

2008/4/18, Brent Cook <bcook@bpointsys.com>:
> On Friday 18 April 2008 12:12:18 Azra Aiyl wrote:
> > Hi,
> >
> > While looking through this archive I can see at least 3 persons who
> > try to compile a gcj (they got no answers). I've tried the same thing
> > for ppc and i386 but always get the same compile error. While googling
> > i was able to collect the following statements.
> >
> > - libgcj needs unicode
> > - uClibc does not support unicode
> > - glibc supports unicode
> > - glibc does not support full statical linking
> >
> > I conclude from this statements:
> >
> > - it is currently not possible no build a gcj with uclibc
> > - nor is it possible to build a statically linked programm with
> > glibc-gcj and let it run on a platform with uclibc
> >
> > If anyone here says I'm wrong then I'll try to build it on my own
>
> As a workaround, you could include shared glibc with your libgcj app in a
> chroot environment on top of your uclibc environment. This would be about
> as resource-heavy as a statically linked executable, if memory is not a
> limiting factor.
>

[Buildroot] gcj on any platform

[Thiago A. Corrêa]

static compile as well as strip will only attempt to remove unneeded
code from the executable. The gain in size depends heavily on the
application.

On Fri, Apr 18, 2008 at 5:14 PM, Azra Aiyl <azraiyl@gmail.com> wrote:
> Thanks for your idea. Memory is not the problem (64 MB) but Flash (8
>  MB). Following page http://www.linuxjournal.com/article/8757 states
>  that you should able to strip the statically linked executable. But if
>  you say this is not true ("not true" means, as heavy as with shared
>  libs), then it's one more reason to try it with another
>  implementation.
>
>  2008/4/18, Brent Cook <bcook@bpointsys.com>:
>
>
> > On Friday 18 April 2008 12:12:18 Azra Aiyl wrote:
>  > > Hi,
>  > >
>  > > While looking through this archive I can see at least 3 persons who
>  > > try to compile a gcj (they got no answers). I've tried the same thing
>  > > for ppc and i386 but always get the same compile error. While googling
>  > > i was able to collect the following statements.
>  > >
>  > > - libgcj needs unicode
>  > > - uClibc does not support unicode
>  > > - glibc supports unicode
>  > > - glibc does not support full statical linking
>  > >
>  > > I conclude from this statements:
>  > >
>  > > - it is currently not possible no build a gcj with uclibc
>  > > - nor is it possible to build a statically linked programm with
>  > > glibc-gcj and let it run on a platform with uclibc
>  > >
>  > > If anyone here says I'm wrong then I'll try to build it on my own
>  >
>  > As a workaround, you could include shared glibc with your libgcj app in a
>  > chroot environment on top of your uclibc environment. This would be about
>  > as resource-heavy as a statically linked executable, if memory is not a
>  > limiting factor.
>  >
>  _______________________________________________
>  buildroot mailing list
>  buildroot at uclibc.org
>  http://busybox.net/mailman/listinfo/buildroot
>