This is the mail archive of the
mailing list for the GDB project.
Re: MinGW compilation warnings in libiberty's waitpid.c
- From: DJ Delorie <dj at redhat dot com>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: eliz at gnu dot org, gcc-patches at gcc dot gnu dot org, gdb-patches at sourceware dot org
- Date: Fri, 26 May 2017 14:04:03 -0400
- Subject: Re: MinGW compilation warnings in libiberty's waitpid.c
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx03.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx03.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=dj at redhat dot com
- Dkim-filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 15C967EBA1
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 15C967EBA1
Joel Brobecker <email@example.com> writes:
> Normally, I'd expect someone pushing to GCC's libibert to also
> update our repo accordingly.
Note that I used to auto-sync libiberty from gcc to binutils/gdb, but
when binutils/gdb switched to git, that script broke, and as I don't
like using git, I announced that I would no longer be auto-syncing. So
it's up to the projects using copies of libiberty to make sure they stay
in sync with the gcc master copy.