porting libgcj to PalmOS

Wed Dec 29 10:41:00 GMT 1999

> Alexandre Petit-Bianco wrote on: Wednesday, December 29, 1999 7:06 PM
>> I guess I'll have to give it a try (I never tried the egcs patches,
> since they weren't stable at the time I was looking for a PlamOS
> toolchain. I'm still using prc 0.5.0) How does the build choke? I'm
> guessing that by `no gcj' you mean the gcj build failed...
>
Build of GCC-2.95.2 with prc-0.6.0 alpha patches fails when specifying
"--enable-languages=c,c++,java" as flag. The build fails when building the
java (gcj) support:
cd java; make "AR_FLAGS_FOR_TARGET=rc" "AR_FOR_TARGET=m68k-palmos-ar"
"BISON=bison" "BISONFLAGS=" "CFLAGS=-g -O2" "CLIB="
"GCC_FOR_TARGET=/home/peter/gnusrc/build-gcc/gcc/xgcc -B/home/peter/gnusrc/b
uild-gcc/gcc/ -B/usr/local/m68k-palmos/bin/ -I/usr/local/m68k-palmos/include
" "LDFLAGS=" "LEX=flex" "LEXFLAGS=" "LN=ln" "LN_S=ln -s"
"MAKEINFO=/home/peter/gnusrc/build-gcc/texinfo/makeinfo/makeinfo "
"MAKEINFOFLAGS=" "RANLIB_FOR_TARGET=m68k-palmos-ranlib"
"RANLIB_TEST_FOR_TARGET=[ -f m68k-palmos-ranlib ] || ( [ "i586-pc-linux-gnu"
= "m68k-palmos-coff" ] && [ -f /usr/bin/ranlib -o -f /bin/ranlib ] )"
"SHELL=/bin/sh" "STAGE_PREFIX=" "exeext=" "build_exeext=" "objext=.o"
"exec_prefix=/usr/local" "prefix=/usr/local" "local_prefix=/usr/local"
"gxx_include_dir=/usr/local/lib/gcc-lib/m68k-palmos/2.95.2-kgpd/../../../..`
echo /usr/local | sed -e 's|^/usr/local||' -e
's|/[^/]*|/..|g'`/include/g++-3" "tooldir=/usr/local/m68k-palmos"
"gcc_tooldir=/usr/local/lib/gcc-lib/m68k-palmos/2.95.2-kgpd/../../../../m68k
-palmos" "bindir=/usr/local/bin"
"libsubdir=/usr/local/lib/gcc-lib/m68k-palmos/2.95.2-kgpd"
"datadir=/usr/local/share" "distdir=../tmp/\$(subdir)"
"localedir=/usr/local/share/locale" "CC=gcc" "JAVA_FOR_BUILD=" "JAVAFLAGS="
"JAVA_FOR_TARGET=" ../jc1
make[2]: Entering directory `/home/peter/gnusrc/build-gcc/gcc/java'
rm -f ../jc1
gcc -DIN_GCC -g -O2 -o ../jc1 \
 parse.o class.o decl.o expr.o constants.o lang.o typeck.o except.o
verify.o zextract.o jcf-io.o jcf-parse.o mangle.o jcf-write.o buffer.o
check-init.o jcf-depend.o jcf-path.o xref.o `cat ../stamp-objlist` `if
 xobstack.o != x ]; then echo ../obstack.o; else true; fi`
../../libiberty/libiberty.a
../m68k.o: In function `palmos_valid_machine_decl_attribute':
/home/peter/gnusrc/build-gcc/gcc/../../gcc-2.95.2/gcc/config/m68k/m68k.c:190
: undefined reference to `lang_identifier_value'
collect2: ld returned 1 exit status
make[2]: *** [../jc1] Error 1
make[1]: *** [jc1] Error 2
make: *** [all-gcc] Error 2make[2]: Leaving directory
`/home/peter/gnusrc/build-gcc/gcc/java'
make[1]: Leaving directory `/home/peter/gnusrc/build-gcc/gcc'
>> As far as porting libgcj to PalmOS, I'm just worried about the
> footprint of the resulting library (or libraries, since each library
> has a 32K limit.)
>
If you take a look at http://homepages.enterprise.net/jmarshall/palmos/ .
John mentions that one of the new features is:
"Almost transparent support for multiple code resources. (Finally: the 32K
code size barrier truly broken!) ".
My estimations for a limited class library are about 50k (in class files),
so probably somewhat larger in m68k instructions. So this would appear to be
workable, right?
Thanks,
Peter Mortier