On Tue, 2006-05-02 at 14:39 +0000, Edjard Mota wrote: > On Wed, Apr 26, 2006 at 02:28:42PM +0000, Edjard Mota wrote: > > ARM toolchain for glibc and the other for uClibc. I created two > > toolchains > > to test. One (A) with arm-gcc3.4-glibc2.3_1.0.2_i386 as compiler and > > other (B) with arm-gcc3.4-uclibc0.9.27_1.0.3_i386 as compiler. > > > > I extracted rootstrap to compile pacakges for a particular ARM > > architecture with toolchain (A). No problems, extraction went well. > > But when I tried to extract rootstrap with toolchain (B) it raise the > > following message: > > > > Unpacking rootstrap... > > /scratchbox/tools/bin/tar: ./usr/include/asm/arch: Cannot create symlink to > > `arch-ebsa285': File exists > > > > Did anybody found a similar problem? What do I have do do to solve it?
> What I wonder is what could I possibly be doing wrong since I got > two ready made toolchains, created two separeted targerts, and the > rootstrap straction worked ok for one but not for the other? I don't know what rootstrap you are using, but I assume it is one that is meant for a glibc toolchain. You see, rootstrap contains binaries built with a specific toolchain. Anyway, the problem is caused by the /usr/include/asm/arch *directory* provided by the uClibc toolchain which conflicts with the /usr/include/asm/arch *symlink* provided by glibc toolchains. You could solve the problem by extracting the rootstrap on an empty target; now you have installed runtime libraries and files provided by the toolchain. But using binaries from an arbitrary rootstrap with an arbitrary toolchain doesn't make sense in the first place. timo _______________________________________________ Scratchbox-devel mailing list [email protected] http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-devel
