From: Pedro Alves <pedro@palves.net>
To: Eric Pouech <eric.pouech@orange.fr>, jcb62281@gmail.com
Cc: Jacek Caban <jacek@codeweavers.com>,
fortran@gcc.gnu.org, NightStrike <nightstrike@gmail.com>,
DejaGnu mailing list <dejagnu@gnu.org>
Subject: Re: testsuite under wine
Date: Wed, 4 Jan 2023 15:52:47 +0000 [thread overview]
Message-ID: <4ddf8aa0-d3e2-56de-63c3-ea6f17e845a1@palves.net> (raw)
In-Reply-To: <3b5622f7-377e-bc7d-6e4a-6c8f731ad97f@orange.fr>
On 2023-01-04 3:45 p.m., Eric Pouech wrote:
> Le 04/01/2023 à 16:21, Pedro Alves a écrit :
>> On 2022-12-23 3:51 a.m., Jacob Bachmeyer wrote:
>>> it will not work when someone decides they want to test MinGW GDB using Wine.
>> This has been on my wish list for years. Unfortunately, I can't even get plain cross-compiled MinGW GDB
>> working properly on a Linux/Bash terminal, as I can't get it (I guess readline) to recognize/accept lines
>> of input.
>>
>> E.g., on Ubuntu 22.04, with system Wine ('wine-6.0.3 (Ubuntu 6.0.3~repack-1)') :
>
> hi
>
> they've been a couple of improvements in Wine 7.x that will help here
>
> so upgrading might be a solution (wine 8.0 is likely to be released by the end of this month...). wine 6.x tree is two year old :-(
...
>
> (notepad is wine's notepad)
>
> -------------------------------------------
>
> [eric:~/work/output-wine/wine64]$ ./wine --version
> wine-8.0-rc2-14-g48c0a75432b
> [eric:~/work/output-wine/wine64]$ ./wine /usr/x86_64-w64-mingw32/sys-root/mingw/bin/gdb.exe notepad
> GNU gdb (GDB) 12.1
(snip gdb working as expected)
Woo, awesome & finally! Thanks a lot.
prev parent reply other threads:[~2023-01-04 15:52 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 2:20 NightStrike
2022-12-16 6:44 ` Thomas Koenig
2022-12-17 0:26 ` NightStrike
2022-12-17 10:52 ` Thomas Koenig
2022-12-17 23:24 ` NightStrike
2022-12-18 3:44 ` Jacob Bachmeyer
2022-12-18 21:13 ` NightStrike
2022-12-19 4:29 ` Jacob Bachmeyer
2022-12-19 10:43 ` Torbjorn SVENSSON
2022-12-19 11:00 ` NightStrike
2022-12-19 11:13 ` NightStrike
2022-12-20 3:51 ` Jacob Bachmeyer
2022-12-21 17:37 ` Jacek Caban
2022-12-22 1:01 ` NightStrike
2022-12-22 4:37 ` Jacob Bachmeyer
2022-12-23 10:36 ` NightStrike
2022-12-23 12:43 ` Eric Pouech
2022-12-24 4:00 ` Jacob Bachmeyer
2022-12-24 11:05 ` Mark Wielaard
2023-01-05 2:50 ` NightStrike
2023-01-06 3:33 ` Jacob Bachmeyer
2023-01-06 3:44 ` Jerry D
2023-01-08 7:12 ` NightStrike
2023-01-11 2:30 ` Jacob Bachmeyer
2023-01-11 9:33 ` NightStrike
2023-01-12 4:11 ` Jacob Bachmeyer
2023-01-06 3:41 ` Jerry D
2022-12-22 4:16 ` Jacob Bachmeyer
2022-12-22 8:40 ` Eric Pouech
2022-12-23 3:51 ` Jacob Bachmeyer
2022-12-23 23:32 ` Jacek Caban
2022-12-24 5:33 ` Jacob Bachmeyer
2023-01-07 1:45 ` Jacek Caban
2023-01-07 3:58 ` Jacob Bachmeyer
2023-01-09 16:03 ` Jacek Caban
2023-01-10 9:19 ` NightStrike
2023-01-11 9:10 ` NightStrike
2023-01-11 18:41 ` NightStrike
2023-01-14 23:36 ` NightStrike
2023-01-11 2:44 ` Jacob Bachmeyer
2023-01-08 6:47 ` NightStrike
2023-01-04 15:21 ` Pedro Alves
2023-01-04 15:45 ` Eric Pouech
2023-01-04 15:52 ` Pedro Alves [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=4ddf8aa0-d3e2-56de-63c3-ea6f17e845a1@palves.net \
--to=pedro@palves.net \
--cc=dejagnu@gnu.org \
--cc=eric.pouech@orange.fr \
--cc=fortran@gcc.gnu.org \
--cc=jacek@codeweavers.com \
--cc=jcb62281@gmail.com \
--cc=nightstrike@gmail.com \
/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).