This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: MinGW compilation errors due to strcasecmp

> Date: Fri, 28 Oct 2016 14:40:29 -0400
> From: Joel Brobecker <>
> Cc: Pedro Alves <>,
> > Pushed to master and cherry-picked to the 7.12 branch.
> Was there a PR number of this issue? Once the first release is
> out for a given branch, the protocol is to make sure that every
> change that goes in is attached to a PR number, and that either:
>   - This PR number is listed as done in the Wiki page for that release; or
>   - The PR's milestone is set to the (minor) release the fix is in.
> That way, it's easy for me to announce the fixes in a corrective
> release. Otherwise, I have to go dig each commit (lost in the sea
> of daily version number updates), and figure out what they fix.


It was a minor build problem with the latest MinGW headers.  Do we
really need this in the list of PRs?  What would it say? include
correct headers to get prototypes of 2 obscure functions?

In any case, can you please point me to the procedure that explains
what should be done in this case?  I just spent 15 minutes looking for
it on the wiki, but failed to find anything.  What did I miss?


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]