2009/12/3 Ed W <[email protected]> > Shinkan wrote: > >> >> I tested it and emerge failed on some ports because installing them use >> binaries that complain about not finding required versions of "CXXABI" or so >> in libstdc++. >> What could I do to fix that ? >> > > > Are you sure emerge failed or that the binary failed to run on the new > system? > > In the later case it's because certain lib files are part of GCC and hence > won't be installed on your target - I find this on a few packages and I just > copy across the relevant libs from the host system >
lzma failed to run because of something it didn't like in libstdc++ from /usr/lib/gcc/my-other-gcc-version/ or something like that. It seems that retrying a gcc-config + env-update + source /etc/profile made it pass. I'm not exactly on the TinyGentoo case because I would prefer host to serves as a build env instead of untaring another stage3. As I have many various targets to build and maintain, it would be hard to also maintain their respective build chroots. Playing with different compilers on the host seems to do the trick. For now I play with gcc-config on host every time I work with a target which needs a different gcc, but that's much pain (what if I forget to gcc-config back to my actual host gcc version ??! I'll lscrew my host I guess.) I would really like if there was an option on make.conf to specify default compiler. As each of my targets have its own make.conf and profile link, it would be very comfortable if I could tell emerge to use the compiler specified in make.conf, so that each time I'd cross-emerge, the good compiler for my target would be selected. Thanks a lot for your directions, TinyGentoo wiki page is really useful. -- Pierre. "Sometimes when I'm talking, my words can't keep up with my thoughts. I wonder why we think faster than we speak. Probably so we can think twice." - Bill Watterson
