On 10/25/2012 11:22 PM, H. S. Teoh wrote:
Oh? Did you run the debian/rules patch command in the package source directory? That was supposed to have fixed this issue, and potentially the issue you're seeing below (Debian-based systems break several assumptions that the GCC build system makese, so you really want to be applying the Debian patches to increase your odds of the build succeeding).
Yup. Latest gdc-4.7 sources (which I believe include your patch), GCC 4.7.2 sources from the Ubuntu 12.10 repositories, tweaked the debian/rules.patch file as instructed, ran the debian/rules clean and debian/rules patch functions and update-gcc.sh.
I don't see anything in rules.patch that would get the compiler looking for crtio.o in /usr/lib/x86_64-linux-gnu/ though.
What parameters did you pass to configure? I wonder if you can turn off some stuff that you don't need, that might avoid this problem. I know that for me, I have to use --disable-multilib (at least), otherwise the build will fail. I also have --disable-gomp and --disable-quadmath, since neither are used by GDC. I'm not sure if they're related to your issue though.
Originally I tried with --enable-language=d --disable-multilib --enable-lto. I've since tried without the -lto option, and tried disabling all the parts that are not used by GDC (gomp, quadmath, etc.) Same error. :-(
It's really very, very frustrating, especially when compared to how easy it is to build LDC from source. Even more so because it gets in the way of being able to actually help and contribute to GDC.
