Good evening! The difference in size is indeed a whopping 19M (8M -> 27M). That might be why the Msys devs chose to split their gdb into a main package and a multi-arch package that depends on the main package.
In case you decide to build gdb with 'enable-targets=all', definitely also configure with '--disable-sim' or it'll build simulators for the additional architectures. Apologies in advance if my mail client does anything weird when replying to this list. This is my first time using a mailing list and I'm forced to use MS Outlook. Best regards Oliver Old Software Developer LÖWEN ENTERTAINMENT GmbH Saarlandstraße 240 55411 Bingen am Rhein Germany T: +49 6721 407319 Email: oliver....@loewen.de www.loewen.de / www.admiral-games.de From: Jon Turney <jon.tur...@dronecode.org.uk> Sent: Monday, October 16, 2023 5:11 PM To: Old, Oliver <oliver....@loewen.de>; The Cygwin Mailing List <cygwin@cygwin.com> Subject: Re: GDB configuration for multi-arch On 11/10/2023 18:26, Old, Oliver via Cygwin wrote: > Good evening! > > I have been looking for a way to debug programs on multiple targets of > different architectures via gdbserver. It seems that Cygwin currently doesn't > provide a gdb configured for this scenario. > > The gdb from the Cygwin distribution isn't configured with > '--enable-targets=all'. I'm now building a gdb with the proper configuration > locally, but it would be quite helpful if Cygwin already included a gdb built > with that flag. > > Is there a specific reason why this isn't being done? Thanks for pointing this out. This is just an oversight, I think. I'll look at adding that for the forthcoming gdb 14.1, assuming it doesn't make the package ridiculously larger. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
