[cfe-dev] Expanding the Clang Status page to report the status of several OSes and projects

[Sandeep Patel]

On Thu, Aug 4, 2011 at 9:19 PM, Ruben Van Boxem
<vanboxem.ruben at gmail.com> wrote:
> 2011/8/4 Sandeep Patel <deeppatel1987 at gmail.com>
>>
>> On Wed, Aug 3, 2011 at 9:54 PM, Ruben Van Boxem
>> <vanboxem.ruben at gmail.com> wrote:
>> > Op 3 aug. 2011 21:28 schreef "Sandeep Patel" <deeppatel1987 at gmail.com> het
>> > volgende:
>> >
>> >>
>> >> Buildbots that test MinGW in one way or another:
>> >>
>> >> http://google1.osuosl.org:8011/builders/llvm-gcc-native-mingw32
>> >> http://google1.osuosl.org:8011/builders/llvm-gcc-native-mingw32-win7
>> >>
>> >> http://google1.osuosl.org:8011/builders/llvm-gcc-mingw32-cross-arm-linux-gnueabi-hard-float
>> >>
>> >> http://google1.osuosl.org:8011/builders/llvm-gcc-build-x86_64-darwin10-x-mingw32-x-armeabi
>> >> http://google1.osuosl.org:8011/builders/clang-x86_64-darwin10-self-mingw32
>> >>
>> >> http://google1.osuosl.org:8011/builders/clang-x86_64-darwin10-cross-mingw32
>> >>
>> >> What additional coverage would you like to see?
>> >
>> > Yes, i noticed these; they test the llvm/clang build, but don't touch real
>> > world projects. This is important for a compiler, as some (most) changes
>> > won't directly affect the internal clang build/test process. My first email
>> > on the subject suggested some external common libraries with extensive test
>> > suites that could help a build bot find more exotic bugs.
>>
>> Would adding an LNT bot cover this?
>
> You're tickling my curiosity, what's an LNT bot?

http://llvm.org/docs/lnt/

>> > Completely orthogonal to this, is a test for MinGW-w64, including 64-bit. Or
>> > even a visual studio test bot. All these would be nice to have. I understand
>> > the later might be harder (visual studio won't run in Unix environments...)
>
>> A MinG4-w64 test would be great. I wasn't under the impression that
>> build could even bootstrap yet.
>
> Good point. Testing that now:
> CMake  builds with MinGW Makefiles and clang(++) as compiler fails at
> link stage:
> Linking CXX executable ..\..\bin\tblgen.exe
> m:/development/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.6.2/../../../../x86_64-w64-mingw32/bin/ld.exe:
> cannot find -limagehlp.lib
> m:/development/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.6.2/../../../../x86_64-w64-mingw32/bin/ld.exe:
> cannot find -lpsapi.lib
> m:/development/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.6.2/../../../../x86_64-w64-mingw32/bin/ld.exe:
> cannot find -limagehlp.lib
> m:/development/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.6.2/../../../../x86_64-w64-mingw32/bin/ld.exe:
> cannot find -lpsapi.lib
> collect2: ld returned 1 exit status
> clang++: error: linker (via gcc) command failed with exit code 1 (use
> -v to see invocation)
>
> Those ".lib"s shouldn't be there.
>
> I have built LLVM/Clang with my prebuilt LLVM/Clang using MSYS and
> configure. The prebuilt version I used is located here (in case you
> missed it the first time):
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/rubenvb/4.6.2-1/
> I configured with "/m/development/mingw64/source/llvm/configure
> --host=x86_64-w64-mingw32 --disable-pthreads --enable-optimized
> --disable-assertions"
> make check all failed with:
> make[2]: Leaving directory `/usr/home/Ruben/llvm/tools/clang/test'
> ( ulimit -t 600 ; ulimit -d 512000 ; ulimit -m 512000 ; ulimit -v 1024000 ; \
>          /m/development/source/llvm/utils/lit/lit.py -s -v .
> /usr/home/Ruben/llvm/test/../tools/clang/test )
> /bin/sh: line 0: ulimit: cpu time: cannot modify limit: Invalid argument
> /bin/sh: line 0: ulimit: data seg size: cannot modify limit: Invalid argument
> /bin/sh: line 0: ulimit: -m: invalid option
> ulimit: usage: ulimit [-SHacdfilmnpqstuvx] [limit]
> /bin/sh: line 0: ulimit: virtual memory: cannot modify limit: Invalid argument
> lit.py: TestingConfig.py:53: fatal: unable to load config from
> '/m/development/source/llvm/test/lit.cfg'
> make[1]: *** [check-local-all] Error 2
>
> Otherwise, Clang on mingw-w64 is self-hosting (with libstdc++ and gcc
> for linking of course).
>
> What can I do to help get a mingw-w64 build bot set up?

I think the first step is to get the MinGW-w64 build to work. Submit
patches, walk them through the review process making requested
changes/improvements, and then commit them.

Once that's done, we appeal to the community to see who is willing to
dedicate a box to testing this build. Chances are good somebody is
willing to do so. I certainly have interest.

After that, we worry about LNT, additional real-world tests, etc.

deep