Kai Ruottu <kai.ruottu@xxxxxxxxxxx> writes: > Andrew Haley wrote: > >> Is there something weird going on here, like different libraries >> in x-host and target? > > Nice to see someone else suspecting weirdness in the current > ideas. The first message in this thread told : > > "This is part of a larger script setting up a cross-compiling > toolchain. binutils, glibc and a first-stage gcc for arm is > already built at this point. I have tried gcc-4.2.2 and gcc-4.2.3. > Our codebase isn't quite ready for 4.3 yet... > > When I run on target, a simple test program with exceptions fail:" > > The weird thing here is that installing the produced glibc runtime > onto the target isn't mentioned. People produce glibc when the > target yet hasn't it, if it has it then there is no reason to try to > create that "byte-by-byte identical" target C library... That was certainly a piece of info missing from my emails. The libraries from the cross-compiling toolchains are copied to target. All .so files and relevant symlinks (perhaps skipping a few we don't need) are copied from the "lib" subdirectory in the toolchain. They are, however, first stripped (just running arm-linuxeabi-strip, not with -g), but I see the same behaviour when I skip this step. As far as I can see, the .so files on target /lib match the ones from lib in my toolchain. -- Henrik Grindal Bakken <hgb@xxxxxxxxxx> PGP ID: 8D436E52 Fingerprint: 131D 9590 F0CF 47EF 7963 02AF 9236 D25A 8D43 6E52
