|
From: NightStrike <nig...@gm...> - 2009-10-04 21:43:41
|
On Sun, Oct 4, 2009 at 3:23 PM, Ronald Pijnacker <pij...@ds...> wrote: >> > > > I'll be sure to build the binutils 2.20 release with >> > > > --with-sysroot to overcome this issue. >> > > >> > > That would be a mistake unless you are building a cross-linker. As >> > > documented in gcc and ld info, the -sysroot option is designed >> > > for cross-compilers and cross-linkers. >> > >> > Like Danny says, that would be a mistake. The real question to be >> > asked, (of the OP)... >> > >> > > I've been trying to get llvm-gcc compiled under mingw. >> > >> > Did you also build a cross-binutils, (with --target=llvm), to go with >> > your cross-gcc? That's the one that needs to be configured with >> > the --with-sysroot option. >> >> I am not buildling a cross compiler (as far as I'm aware of), I'm just >> trying to build llvm-gcc as a replacement for gcc. >> To keep msys/mingw clean, I choose to install this to /llvm, but for >> the linker there should not be any difference. >> >> To quote NightStrike: >> >> > When you configure binutils, use the --with-sysroot option. This is >> > how binutils (and gcc) should pretty much always be built these days, >> > with the current configury system that is present in sourceware's top >> > level configure. You point binutils to the location of the sysroot, >> > and you get bonus points if the sysroot is equal to or decendent from >> > your prefix. >> >> This isn't true then? I understand from this that it doesn't hurt to specify >> --with-sysroot if it is the same as --prefix. > > I recompiled the binutils with --prefix=/mingw --with-sysroot=/mingw, and now > things are ok. Glad it worked for you! |