Matthias, On Oct 10, 2011, at 04:14, Matthias Klose wrote: > On 10/09/2011 08:49 PM, Moffett, Kyle D wrote: >> Matthias Klose wrote: >>> I don't see this. is /usr/include/asm a symlink? is gcc-multilib the recent >>> version in unstable? If this is a local build, make sure that the >>> gcc-multiarch.diff is applied during the build. >> >> No, this is a regular dpkg-buildpackage of the "gcc-4.6" source package: >> $ apt-get source gcc-4.6=4.6.1-13 >> $ cd gcc-4.6-4.6.1 >> $ dpkg-buildpackage -us -uc -b >> >> My currently installed GCC compiler packages are: >> gcc 4:4.6.1-2 (gcc-defaults 1.107) >> >> If I run this command on my regular system compiler: >> $ cpp -v </dev/null >> [...] >> #include <...> search starts here: >> /usr/lib/gcc/x86_64-linux-gnu/4.6.1/include >> /usr/local/include >> /usr/lib/gcc/x86_64-linux-gnu/4.6.1/include-fixed >> /usr/include/x86_64-linux-gnu >> /usr/include >> End of search list. >> [...] > > fixed in 1.108. although I fail to see that gcc-multilib is built on > powerpcspe?
Hi, I think we've got our wires crossed here. I'm not sure where you got powerpcspe from this email. This build failure is for a native build of an amd64 "gcc-4.6" on an amd64 system (See the "x86_64-linux-gnu" paths). Furthermore, the gcc-defaults package just installs a bunch of symlinks and a few shell scripts on the system. I fail to see how that could "fix" an incorrect search path compiled into the temporary "xgcc" binary during the gcc-4.6 build process. Can you explain what you mean by "fixed in 1.108"? Cheers, Kyle Moffett -- Curious about my work on the Debian powerpcspe port? I'm keeping a blog here: http://pureperl.blogspot.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
