From: Tom de Vries <tdevries@suse.de>
To: Simon Marchi <simark@simark.ca>, Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] [gdbsupport] Add gdb::{waitpid,read,write,close}
Date: Fri, 29 Nov 2024 18:28:41 +0100 [thread overview]
Message-ID: <d7c69c2c-5d9e-4040-becf-99556600057c@suse.de> (raw)
In-Reply-To: <493fa47f-1c21-46e7-a2bf-fac11c5e58f8@simark.ca>
On 11/29/24 18:23, Simon Marchi wrote:
>
>>> The problem is that you might have to cross build the packages gdb
>>> requires. If you're lucky, your distro also packages them for
>>> mingw-w64. For instance, it looks like Suse packages libgmp:
>>>
>>> https://software.opensuse.org/package/mingw64-gmp?locale=ro
>>>
>>> These are the configure flags I currently use for this build:
>>>
>>> '--host=x86_64-w64-mingw32' \
>>> 'CFLAGS=-g3 -O0' \
>>> 'CC=ccache x86_64-w64-mingw32-gcc' \
>>> 'CXXFLAGS=-g3 -O0 -fmax-errors=1' \
>>> 'CXX=ccache x86_64-w64-mingw32-g++' \
>>> '--disable-source-highlight' \
>>> '--disable-gold' \
>>> '--disable-ld' \
>>> '--disable-binutils' \
>>> '--disable-gprof' \
>>> '--disable-gas' \
>>> '--without-python' \
>>> '--disable-nls'
>>>
>>> I'll try to get it to build inside a Suse container.
>>>
>>
>> Oh, I see, that's a good idea, thanks, I'll try that.
>>
>> - Tom
>
> Ok, I think I got it to work. See attached Dockerfile.
>
> Use with (fixup the path to the source tree in the `-v` flag):
>
> $ docker build -t opensuse-gdb-mingw-w64 .
> $ docker run -v /home/simark/src/binutils-gdb:/src -it opensuse-gdb-mingw-w64:latest
> # ./build.sh
>
> Of course, since you likely have a tumbleweed system already, you can
> simply install the required packages on that machine.
>
Hi Simon,
thanks for the help.
I've reproduced the build error now (on my Leap 15.5 system), I'll take
a look.
Thanks,
- Tom
next prev parent reply other threads:[~2024-11-29 17:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 17:49 Tom de Vries
2024-10-28 17:49 ` [PATCH 2/3] [gdb] Use gdb::waitpid more often Tom de Vries
2024-10-28 17:49 ` [PATCH 3/3] [gdbsupport] Add gdb::wait Tom de Vries
2024-11-01 17:35 ` [PATCH 1/3] [gdbsupport] Add gdb::{waitpid,read,write,close} Tom Tromey
2024-11-05 12:07 ` Tom de Vries
2024-11-22 16:46 ` Tom de Vries
2024-11-29 16:15 ` Simon Marchi
2024-11-29 16:23 ` Tom de Vries
2024-11-29 16:27 ` Simon Marchi
2024-11-29 16:32 ` Tom de Vries
2024-11-29 17:23 ` Simon Marchi
2024-11-29 17:28 ` Tom de Vries [this message]
2024-12-02 9:38 ` Kévin Le Gouguec
2024-12-02 11:07 ` Tom de Vries
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=d7c69c2c-5d9e-4040-becf-99556600057c@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=tom@tromey.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