On Friday 20 November 2009 19:19:58 STeve Andre' wrote: > In the spirit of doing homework before asking questions, I am > finally here, having exhausted what I could think of doing. > > My package builder had a filesystem meltdown where I lost so many > files I decided to rebuild it. My first run of the newly built > machine revealed problems. The gcc-4.2.4 monster refsuses to > build, giving the results below. > > I got a new copy of ports.tar.gz and updated that wondering > if cvs did something to me. I know that in the past libc.so.42 > was needed, but that isn't relevent any more. Trying other > older versions of libc haven't helped either. I saw two > updates to gcc/4.2 but they didn't change anything. What am > I missing? > > So some hints would be appreciated. I'm doing the build with > dpb, as root, which works for everything but parrot. Both cores > on the machine are working, etc. I think the simpler parts of > package building are ok since I've built 3400+ ok. > > Clues? Of course this happens as I'm building machines for > work which I wanted a complete package set for. > > Thanks for any ideas/help, > > --STeve Andre' > > [last part of compile of gcc/4.2]
OK, I need some version of libm it seems. I have .so.4.0, 5.0 5.1 and 5.2. I need something older I believe. ? --STeve Andre'
