From: Petr Vorel <pvorel@suse.cz>
To: Detlef Riekenberg <wine.dev@web.de>
Cc: Joerg Vehlow <joerg.vehlow@aox.de>, LTP <ltp@lists.linux.it>
Subject: Re: [LTP] open_posix_testsuite: Replace old -W commandline argument
Date: Wed, 15 May 2024 11:51:37 +0200 [thread overview]
Message-ID: <20240515095137.GA208965@pevik> (raw)
In-Reply-To: <trinity-41dc0eb8-c7cf-4f51-9e88-2b2daa5bd204-1715766325023@msvc-mesg-web002>
Hi,
> Thanks all for your help and patience with a LTP newbie.
yw :).
> Now, OpenWatcom (with my patched owcc frontend) passes >1100 tests
> and more work on the OpenWatcom POSIX runtime can be done
Always interested to see who is using LTP.
> (a big OW issue: "aio.h" and the related implementation is missing)
glibc and musl IMHO support aio.h unconditionally. If you're using uclibc or
uclibc-ng, you need UCLIBC_HAS_REALTIME [1]. But below you mentioned glibc.
Kind regards,
Petr
[1] https://cgit.uclibc-ng.org/cgi/cgit/uclibc-ng.git/tree/extra/Configs/Config.in#n1166
> ---
> Testing with another Compiler on my system:
> Using the Open Posix Testsuite with TinyC and the system installed glibc
> gives one failed test.
> This is the same result as using gcc.
> -----
> When someone has a working setup for "git-send-email" with "[1]web.de",
> please let me know.
> (I tried git-imap-send as fallback, but that only creates the draft mail.
> A web login into the [2]web.de mail interface
> with editing the draft mail and manually sending the patch
> is needed afterwards)
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2024-05-15 9:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 20:47 [LTP] [PATCH] open_posix_testsuite: Replace old -W commandline argument Detlef Riekenberg via ltp
2024-05-14 8:25 ` Cyril Hrubis
2024-05-14 12:15 ` Petr Vorel
2024-05-14 13:02 ` Joerg Vehlow
2024-05-14 18:59 ` Petr Vorel
[not found] ` <trinity-41dc0eb8-c7cf-4f51-9e88-2b2daa5bd204-1715766325023@msvc-mesg-web002>
2024-05-15 9:51 ` Petr Vorel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240515095137.GA208965@pevik \
--to=pvorel@suse.cz \
--cc=joerg.vehlow@aox.de \
--cc=ltp@lists.linux.it \
--cc=wine.dev@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).