I finally got a full catalyst build up and running, and I'm really happy. I actually alread found a workaround for this bug, but I thought I would let zhen know. Basically, several libraries in /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.3/ are unmerged in the stage2 portion of the livecd script. This causes several programs to break. A quick, and pretty easy fix (after finishing stage1) is to chroot into /var/tmp/catalyst/tmp/default/livecd-stage1-i686-20040615 and cp /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.3/lib* /usr/lib Then run the stage2 script. I'm not sure this could be done in the livecd-stage2 script of catalyst, but at very least alert users of this problem. Thanks again to John Davis for all his hard work! Bryan York Reproducible: Always Steps to Reproduce: 1. Emerge Catalyst 2. Create stage1 and stage2 livecd spec files with programs such as partimage. 3. Run the catalyst scripts. Actual Results: CD Booted great, but the programs were missing libraries. Expected Results: The program should have run normally.
bryan - thanks for your testing! The default behavior is in fact to remove gcc for our normal LiveCDs, and we have had no problems. The only time that I have had the libstdc++ problems is when making X LiveCDs. Is this what you are trying to do? If not, what programs are failing? For release sakes, we will most likely keep on removing gcc to keep our size down, but if your workaround works, I may incorporate it into the X LiveCD stuff.
Yes, I'm making an X livecd. Lot's of programs whine about libstdc++.so.5, such has partimage, fluxbox. I just did some extra testing, vlnx(mcafee anti-virus) complains about libstdc++.so.2.8... I'll check where this is located when I get home.
Just to let everyone know: I solved this by keeping lib-compat in my CD. As long as this was removed from the unmerge list in my stage2, all programs ran fine. It seems it was my ignorance to think it was gcc. Feel free to marked this as invalid or fixed, whichever you choose. Just remember to update the documentation to keep lib-compat if they want to run programs. Note that programs such as partimage, which do not need X, still need these libraries. So lib-compat shouldn't be an optional package to remove. Hope this helps. Regards, Bryan York
thanks, closing
