Notes |
(0002766)
APOLAUF
09-23-07 09:58
|
the "ft" after "#Ok... that's enough of that" is my OCR software incorrectly identifying the # symbol. I'm running this in a VM, and didn't feel like piping the output over, so there may be a recognition error or two. I took care to correct the rest of the output. |
| |
(0002767)
UlfSamuelsson
09-23-07 11:39
|
I have seen the same thing for the AVR32 build.
I traced it back to "configure" not beeing able to link.
This was because "crt1.o" was not found, when linking.
That disabled creating the *.so files.
I find this strange, since there is no crt1.asm in gcc
except for the SH architecture.
Did not have time to investigate further. |
| |
(0002769)
APOLAUF
09-23-07 12:58
|
So what can I do to get this to compile? I need gcj support or a JVM to run on my busybox build. And I don't have room to statically link GCJ with glibc (47MB for a hello world app). Is there any toolchain that I can use to build gcj cross-compiling support with static linking against uClibc? |
| |
(0002770)
bernhardf
09-23-07 13:21
|
I only tested C, fortran, c++ and those work as expected as far as i'm concerned.
I don't do java (never did and will most likely never do), so please feel free to send in patches. |
| |
(0002789)
APOLAUF
09-24-07 07:21
|
I disabled GCJ support, enabling only C++, but it still fails with the exact same error. What can be done? |
| |
(0002790)
bernhardf
09-24-07 09:55
|
please attach your buildroot .config and your uclibc .config (or let me know if you used a standard one). I'll try to reproduce this locally.
thanks, |
| |
(0002795)
APOLAUF
09-24-07 17:53
|
I've included the .config file that I used. I didn't modify anything as far as uclibc config goes. The target is simply ARM 920T, though it fails equally for "generic ARM." I've included "error.txt", which contains the last instruction that "make" executes before it generates an error. Thanks for taking a look.
-Adrian |
| |
.config [^] (14,732 bytes) 09-24-07 17:52
error.txt [^] (1,146 bytes) 09-24-07 17:52 
