The top of the file says that it is deprecated in favor of LNT. Is
this document still needed? It makes mention of llvm-gcc as well...
-- Sean Silva
Unfortunately, LNT still uses the Makefiles underneath, and the
Makefiles support a few users who use the more advanced hackery they
support. We should keep it for the time being.
- Daniel
Sorry for the bother Jim, but I'm calling on you again for guidance
about llvm-gcc mentions. What should be done about the mention of
llvm-gcc on <http://llvm.org/docs/TestSuiteMakefileGuide.html>? Can we
just roughly s/llvm-gcc/clang/ ? Daniel, feel free to provide guidance
as well.
-- Sean Silva
Hi Sean,
The language in "Running the test suite" can be simplified a fair bit, I think. I don't think there's any need to do the multiple stage build, for example. Daniel will probably be better able to provide specifics here.
-Jim
Hi Sean,
Sorry for the bother Jim, but I'm calling on you again for guidance
about llvm-gcc mentions. What should be done about the mention of
llvm-gcc on <http://llvm.org/docs/TestSuiteMakefileGuide.html>? Can we
just roughly s/llvm-gcc/clang/ ? Daniel, feel free to provide guidance
as well.
to some extent llvm-gcc lives on in dragonegg, for example to build the
testsuite using dragonegg you need to use the --with-llvmgccdir flag and
do some tricks. While I've got nothing against you substituting clang
for llvm-gcc in the document, it would be nice to have a section that
explains how to use dragonegg. Even nicer would be to make the makefiles
more generic, rather than hard-wiring in clang/llvm-gcc[*], so that pretty
much any compiler can be easily used.
Ciao, Duncan.
[*] They used to be more generic, but in making life better for clangers
Eric made life worse for dragoneggers, though I don't remember what the
changes were exactly.
I was simplifying and removing a bunch of the duplication as well as moving some of the llvm-gcc detection into the test-suite where it belongs (since it wasn’t being used at the top level).
That said, I can’t recall what problems you were running into after the changes. Could you file a bug for me so it doesn’t get lost?
Thanks!
-eric
to some extent llvm-gcc lives on in dragonegg, for example to build the
testsuite using dragonegg you need to use the --with-llvmgccdir flag and
do some tricks. While I've got nothing against you substituting clang
for llvm-gcc in the document, it would be nice to have a section that
explains how to use dragonegg. Even nicer would be to make the makefiles
more generic, rather than hard-wiring in clang/llvm-gcc[*], so that pretty
much any compiler can be easily used.
I haven't changed anything yet. In fact, it seems like you are
probably one of the best informed on competing forces for what the
document needs to say in that section, so maybe you could try your
hand at it?
-- Sean Silva