This is what I'm seeing. I had an old version of systemtap that caused the header file issue. At this point, there was no elfutils. To overcome the systemtap fail, I had to upgrade to a newer of systemtap. From the systemtap docs, I saw that it needed elfutils and so installed that also. After this sytemtap & elfutils install, the gcc build progressed and it failed at the morestack assembler stage. I later found that systemtap could be installed with binutils also. So, I tried installing systemtap, without elfutils and went with binutils. With this combination, I am hitting the systemtap error when gcc was compiled. On Wed, Mar 27, 2013 at 2:57 PM, Ian Lance Taylor <iant@xxxxxxxxxx> wrote: > On Wed, Mar 27, 2013 at 1:42 PM, Kalai Rajah N <kalairajah@xxxxxxxxx> wrote: >> I tried to run make NM=<binutils_nm> and I'm hitting my earlier >> problem of erroring out due to systemtap issue. It seems that >> systemtap requires the elfutils nm, while the morestack compilation >> prefers the binutils nm. Seems like a catch-22 situation. > > I thought the problem you had with systemtap was a bug in their header > files. I don't see how using the elfutils nm fixes that. > > Using the elfutils nm will cause the build to fail earlier than the > problem you reported earlier. The elfutils nm will cause the build > fail in libgcc. You reported a failure building libstdc++. libgcc is > built before libstdc++. So I think you installed elfutils to avoid > the libstdc++ problem, but it didn't fix it. It just broke earlier. > > Ian
