<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>One more thing: manually deleting the standalone check in order
to generate the check-cxxabi target does not work either. First,
<build>/bin/llvm-lit is not generated (and trying to copy
the relevant CMake snippet from the libcxx CMakeLists.txt causes
an error) and executing check-cxxabi executes something, but then
crashes with the following error:</p>
<p><tt>lit.py: llvm/utils/lit/lit/TestingConfig.py:101: fatal:
unable to parse config file 'build/test/lit.site.cfg',
traceback: Traceback (most recent call last):</tt><tt><br>
</tt><tt> File "llvm/utils/lit/lit/TestingConfig.py", line 88, in
load_from_path</tt><tt><br>
</tt><tt> exec(compile(data, path, 'exec'), cfg_globals, None)</tt><tt><br>
</tt><tt> File "build/test/lit.site.cfg", line 153, in
<module></tt><tt><br>
</tt><tt> configuration.configure()</tt><tt><br>
</tt><tt> File "libcxx/utils/libcxx/test/config.py", line 148, in
configure</tt><tt><br>
</tt><tt> self.lit_config</tt><tt><br>
</tt><tt> File "libcxx/utils/libcxx/test/newconfig.py", line 22,
in configure</tt><tt><br>
</tt><tt> feature.enableIn(config)</tt><tt><br>
</tt><tt> File "libcxx/utils/libcxx/test/dsl.py", line 270, in
enableIn</tt><tt><br>
</tt><tt> assert self.isSupported(config), \</tt><tt><br>
</tt><tt> File "libcxx/utils/libcxx/test/dsl.py", line 243, in
isSupported</tt><tt><br>
</tt><tt> return self._isSupported(config)</tt><tt><br>
</tt><tt> File "libcxx/utils/libcxx/test/params.py", line 20, in
<lambda></tt><tt><br>
</tt><tt> when=lambda cfg: hasCompileFlag(cfg,
'-std={}'.format(std)))),</tt><tt><br>
</tt><tt> File "libcxx/utils/libcxx/test/dsl.py", line 125, in
hasCompileFlag</tt><tt><br>
</tt><tt> with _makeConfigTest(config) as test:</tt><tt><br>
</tt><tt> File "libcxx/utils/libcxx/test/dsl.py", line 62, in
_makeConfigTest</tt><tt><br>
</tt><tt> prefix=testPrefix)</tt><tt><br>
</tt><tt> File "/usr/lib/python2.7/tempfile.py", line 475, in
NamedTemporaryFile</tt><tt><br>
</tt><tt> (fd, name) = _mkstemp_inner(dir, prefix, suffix,
flags)</tt><tt><br>
</tt><tt> File "/usr/lib/python2.7/tempfile.py", line 242, in
_mkstemp_inner</tt><tt><br>
</tt><tt> file = _os.path.join(dir, pre + name + suf)</tt><tt><br>
</tt><tt>TypeError: unsupported operand type(s) for +: 'NoneType'
and 'str'</tt></p>
<p>I remember seeing this error in libcxx when I manually tried to
execute a test with python2 instead of python3. But I don't see
any way to tell the test suite to use python3 for the check-cxxabi
target.</p>
<p>Am I missing something or is standalone testing of libcxxabi
currently broken/not supported?</p>
<p>Cheers,</p>
<p>Dominik</p>
<div class="moz-cite-prefix">Am 04.08.20 um 08:59 schrieb Dominik
Montada via libcxx-dev:<br>
</div>
<blockquote type="cite"
cite="mid:c6e626fa-11ab-8cf1-32fd-fc6bf6f71b3d@hightec-rt.com">Hi
Louis,
<br>
<br>
sorry for digging up this old thread. I only just got around to
start working on this again.
<br>
<br>
I wanted to set up the libc++abi tests as standalone and I'm
getting the following error:
<br>
<br>
CMake Warning at CMakeLists.txt:480 (message):
<br>
The libc++abi tests aren't valid when libc++abi is built
standalone (i.e.
<br>
outside of llvm/projects/libcxxabi ) and is built without a
shared library.
<br>
Either build a shared library, build libc++abi at the same time
as you
<br>
build libc++, or do without testing. No check target will be
available!
<br>
<br>
I'm building in-tree but standalone. Is this intended even with
your new patches or a bug?
<br>
<br>
Cheers,
<br>
<br>
Dominik
<br>
<br>
Am 25.06.20 um 18:16 schrieb Louis Dionne:
<br>
<blockquote type="cite">I just landed these patches:
<br>
<br>
commit c55051eea5d3cd57abfd9727f519b670517704d9
<br>
Author: Louis Dionne <a class="moz-txt-link-rfc2396E" href="mailto:ldionne@apple.com"><ldionne@apple.com></a>
<br>
Date: Thu Jun 25 12:02:43 2020 -0400
<br>
<br>
[libunwind] Allow specifying custom Lit config files
<br>
<br>
This is the libunwind counterpart of 0c66af970c80.
<br>
<br>
commit 33c9c10d183371edc95fa936705bef56f55ab611
<br>
Author: Louis Dionne <a class="moz-txt-link-rfc2396E" href="mailto:ldionne@apple.com"><ldionne@apple.com></a>
<br>
Date: Thu Jun 25 11:46:00 2020 -0400
<br>
<br>
[libc++abi] Allow specifying custom Lit config files
<br>
<br>
This is the libc++abi counterpart of 0c66af970c80.
<br>
<br>
Louis
<br>
<br>
<br>
<blockquote type="cite">On Jun 25, 2020, at 11:28, Louis Dionne
via libcxx-dev <a class="moz-txt-link-rfc2396E" href="mailto:libcxx-dev@lists.llvm.org"><libcxx-dev@lists.llvm.org></a> wrote:
<br>
<br>
<br>
<br>
<blockquote type="cite">On Jun 25, 2020, at 08:14, Dominik
Montada <a class="moz-txt-link-rfc2396E" href="mailto:dominik.montada@hightec-rt.com"><dominik.montada@hightec-rt.com></a> wrote:
<br>
<br>
Hi Louis,
<br>
<br>
sorry for bothering you once more about the libcxx test
suite! I was wondering whether you could help with some of
my problems again.
<br>
<br>
After the recent discussion on the mailing list and your
diff, I was able to set up cross-compilation and
remote-execution of the libcxx test suite, so thank you for
that!
<br>
</blockquote>
I'm glad to hear that!
<br>
<br>
<blockquote type="cite">We have split up the build of the
libraries into different stages, so libcxx, libcxxabi and
libunwind are all built in standalone mode. If I understand
correctly, libcxxabi and libunwind tests are not supported
when using this. Is there a way to include those tests when
running the libcxx test suite?
<br>
<br>
If not, what is the recommended way to build and test those
libraries when doing cross-compilation?
<br>
</blockquote>
<br>
Yes, they are supported. It's just that I haven't implemented
the ability to use a 100% custom site config file for
libcxxabi and libunwind, but it should work just the same.
I'll try doing that today -- it should be the same dance as
what I did for libcxx.
<br>
<br>
Louis
<br>
<br>
_______________________________________________
<br>
libcxx-dev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:libcxx-dev@lists.llvm.org">libcxx-dev@lists.llvm.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.llvm.org/cgi-bin/mailman/listinfo/libcxx-dev">https://lists.llvm.org/cgi-bin/mailman/listinfo/libcxx-dev</a>
<br>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
libcxx-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:libcxx-dev@lists.llvm.org">libcxx-dev@lists.llvm.org</a>
<a class="moz-txt-link-freetext" href="https://lists.llvm.org/cgi-bin/mailman/listinfo/libcxx-dev">https://lists.llvm.org/cgi-bin/mailman/listinfo/libcxx-dev</a>
</pre>
</blockquote>
</blockquote>
<pre class="moz-signature" cols="72">--
----------------------------------------------------------------------
Dominik Montada Email: <a class="moz-txt-link-abbreviated" href="mailto:dominik.montada@hightec-rt.com">dominik.montada@hightec-rt.com</a>
HighTec EDV-Systeme GmbH Phone: +49 681 92613 19
Europaallee 19 Fax: +49-681-92613-26
D-66113 Saarbrücken WWW: <a class="moz-txt-link-freetext" href="http://www.hightec-rt.com">http://www.hightec-rt.com</a>
Managing Director: Vera Strothmann
Register Court: Saarbrücken, HRB 10445, VAT ID: DE 138344222
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient please notify the sender immediately
and destroy this e-mail. Any unauthorised copying, disclosure or
distribution of the material in this e-mail is strictly forbidden.
--- </pre>
</body>
</html>