search for: configure_llvm_1

...gt; Sebastian, this looks like it is most likely some kind of fallout from > your changes. Thanks for letting me know about these failing testcases. In the logs of the buildbot: http://lab.llvm.org:8011/builders/llvm-gcc-build-x86_64-darwin10-x-mingw32-x-armeabi/builds/273/steps/run.build.step.configure_llvm_1/logs/stdio I see that the bot is configuring llvm with: --build=x86_64-apple-darwin10 --host=x86_64-apple-darwin10 --target=i686-pc-mingw32 Before my patches, specifying --target had no effect as it was the --host value that was taken. So by default we used to compile code for the host that is &q...

...ike it is most likely some kind of fallout from >> your changes. > > Thanks for letting me know about these failing testcases. > > In the logs of the buildbot: > http://lab.llvm.org:8011/builders/llvm-gcc-build-x86_64-darwin10-x-mingw32-x-armeabi/builds/273/steps/run.build.step.configure_llvm_1/logs/stdio > I see that the bot is configuring llvm with: > --build=x86_64-apple-darwin10 --host=x86_64-apple-darwin10 > --target=i686-pc-mingw32 > > Before my patches, specifying --target had no effect as it was the > --host value that was taken.  So by default we used to compile...

...me kind of fallout from >>> your changes. >> >> Thanks for letting me know about these failing testcases. >> >> In the logs of the buildbot: >> http://lab.llvm.org:8011/builders/llvm-gcc-build-x86_64-darwin10-x-mingw32-x-armeabi/builds/273/steps/run.build.step.configure_llvm_1/logs/stdio >> I see that the bot is configuring llvm with: >> --build=x86_64-apple-darwin10 --host=x86_64-apple-darwin10 >> --target=i686-pc-mingw32 >> >> Before my patches, specifying --target had no effect as it was the >> --host value that was taken.  So by de...