Thank you very much, sorry for the delay response.

With '--disable-gcov-tool', gcc 4.10 can be build successfully.
Both patch2 and patch3 failed, please found the attachment for details.

--
Dongsheng

On Tue, Aug 12, 2014 at 2:29 AM, Rong Xu <[email protected]> wrote:
>
> Here is the patch that makes the build of gcov-tool configurable.
> --disable-gcov-tool to disable the build.
>
> Note the default is to build gcov-tool for mingw. Please help to test
> this. Thanks,
>
> -Rong
>
>
>
> On Fri, Aug 8, 2014 at 2:28 PM, Rong Xu <[email protected]> wrote:
> > OK. I'll work on this.
> >
> > At the same time, could you try the attached patch which fixes the
> > problems mentioned in patchset1?
> > I had hard time to setup your build environment.
> >
> > -Rong
> >
> > On Fri, Aug 8, 2014 at 1:27 AM, Dongsheng Song <[email protected]> 
> > wrote:
> >> On Fri, Jul 25, 2014 at 5:16 PM, JonY <[email protected]> wrote:
> >>> On 7/25/2014 12:36, Dongsheng Song wrote:
> >>>> This just fix the ftw issue. But still have "%lld", mkdir, "GCC poison
> >>>> strerror" issue on gcov.
> >>>> You can following the build instructions at:
> >>>>
> >>>> http://sourceforge.net/p/mingw-w64/mingw-w64/ci/master/tree/mingw-w64-doc/howto-build/mingw-w64-howto-build.txt
> >>>>
> >>>
> >>> The guide is fairly outdated, please use mingw-w64 from git and
> >>> disregard the part about SVN checkout.
> >>>
> >>> Link: git://git.code.sf.net/p/mingw-w64/mingw-w64
> >>>
> >>
> >> Hi Rong,
> >>
> >> Could you add an build argument like '--disable-gcov' to make gcc
> >> trunk buildable for Windows ?
> >>
> >> Thanks,
> >> Dongsheng

Attachment: gcov-win32_patch2.log
Description: Binary data

Attachment: gcov-win32_patch3.log
Description: Binary data

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to