This is the mail archive of the
mailing list for the GDB project.
Re: GDB 7.99.91 available for testing
- From: Yao Qi <qiyaoltc at gmail dot com>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: Joel Brobecker <brobecker at adacore dot com>, gdb-patches at sourceware dot org, sergiodj at redhat dot com
- Date: Wed, 17 May 2017 12:36:46 +0100
- Subject: Re: GDB 7.99.91 available for testing
- Authentication-results: sourceware.org; auth=none
- References: <20170504194442.63AAF60B72@joel.gnat.com> <firstname.lastname@example.org>
Eli Zaretskii <email@example.com> writes:
> I've built this with MinGW and bumped into a few problems. Two
> problems related to GDB sources, the rest to libiberty and readline.
> I will report the GDB problems in separate messages. As to problems
> with libiberty and readline (all of them minor), what should I do to
> fix them in GDB in addition to reporting them to their respective
> upstream maintainers? Should I push the fixes to the GDB repository,
> master and branch?
Can we add a MinGW buildslave to our buildbot? We can install the
desired MinGW cross-toolchain on some Linux machine in gcc compile farm,
and start a buildslave instance there? We only do the build. This is
very helpful to find such build issues.