Hi Ray,
Thanks. Meanwhile, the build was finished OK. It's a very nice build script.
Beside the MSYS2/gcc paths, these issues took some time to figure out,
maybe could be added to the README:
1 The develop branch should be checked out to get the gcc-4.9.1 script.
(checking out non master is not the default).
2 gettext-devel is required in the build.
3 If packages are missing, the script may suggest to run 'pacman -S p7zip
base-devel gettext-devel' to install all required packages at once.
Yaron
2014-10-03 2:29 GMT+03:00 Ray Donnelly <mingw.andr...@gmail.com>:
> On Thu, Oct 2, 2014 at 10:59 PM, Yaron Keren <yaron.ke...@gmail.com>
> wrote:
> > Well, something went wrong with MSYS2. I uninstalled MSYS2 and
> reinstalled,
> > now libmangle compiles and build goes on. Odd. I did encounter a problem
> > before with MSYS2 while doing pacman -Syu, there were errors and the
> upgrade
> > wasn't complete. Maybe that's releated. This time I did not pacman -Syu.
> >
>
> There's a problem in MSYS2 that when it updates DLLs of core packages
> that pacman (or subsequently called post-install scripts) itself
> depends on, those post-install scripts can fail to execute. If you
> make a list of which packages failed, you can usually exit all your
> MSYS2 shells, launch another one, then do:
>
> pacman -S <list-of-failed-packages>
>
> Yeah, that's really horrible and we need to fix it somehow.
>
> >
> >
> >
> > 2014-10-02 18:00 GMT+03:00 Yaron Keren <yaron.ke...@gmail.com>:
> >>
> >> Hi,
> >>
> >> I am trying to build mingw-w64. I followed all steps from the README and
> >>
> >> git clone https://github.com/niXman/mingw-builds/ --branch develop
> >>
> >> ./build --mode=gcc-4.9.1 --buildroot=/c/mingw491 --rt-version=v3 --rev=1
> >> --bootstrap --jobs=2 --threads=posix --exceptions=dwarf --arch=i686
> >> --bin-compress
> >>
> >> ( the arguments were copied from build-info.txt of
> >> i686-4.9.1-release-posix-dwarf-rt_v3-rev1.7z )
> >>
> >> after gcc is built, it fails to compile libmangle since it does not find
> >> stdio.h. Running
> >> /c/mingw491/i686-491-posix-dwarf-rt_v3-rev1/mingw32/bin/g++ -E -x c++ -
> -v
> >> < /dev/null
> >>
> >> results in:
> >> ...
> >> ignoring duplicate directory
> >>
> "C:/mingw491/i686-491-posix-dwarf-rt_v3-rev1/mingw32/lib/gcc/../../../mingw32/lib/gcc/i686-w64-mingw32/4.9.1/include"
> >> ignoring nonexistent directory
> >>
> "C:/mingw491/i686-491-posix-dwarf-rt_v3-rev1/mingw32/mingw32/lib/gcc/i686-w64-mingw32/4.9.1/../../../../include"
> >> ignoring duplicate directory
> >>
> "C:/mingw491/i686-491-posix-dwarf-rt_v3-rev1/mingw32/lib/gcc/../../../mingw32/lib/gcc/i686-w64-mingw32/4.9.1/include-fixed"
> >> ignoring nonexistent directory "/mingw32/i686-w64-mingw32/include"
> >> ignoring nonexistent directory
> >> "C:/mingw491/i686-491-posix-dwarf-rt_v3-rev1/mingw32/mingw/include"
> >> #include "..." search starts here:
> >> #include <...> search starts here:
> >>
> >>
> C:/mingw491/i686-491-posix-dwarf-rt_v3-rev1/mingw32/bin/../lib/gcc/i686-w64-mingw32/4.9.1/include
> >>
> >>
> C:/mingw491/i686-491-posix-dwarf-rt_v3-rev1/mingw32/bin/../lib/gcc/i686-w64-mingw32/4.9.1/include-fixed
> >>
> >>
> C:/mingw491/i686-491-posix-dwarf-rt_v3-rev1/mingw32/lib/gcc/../../../mingw32/i686-w64-mingw32/include/c++
> >>
> >>
> C:/mingw491/i686-491-posix-dwarf-rt_v3-rev1/mingw32/lib/gcc/../../../mingw32/i686-w64-mingw32/include/c++/i686-w64-mingw32
> >>
> >>
> C:/mingw491/i686-491-posix-dwarf-rt_v3-rev1/mingw32/lib/gcc/../../../mingw32/i686-w64-mingw32/include/c++/backward
> >> ...
> >>
> >> So
> >>
> /c/mingw491/i686-491-posix-dwarf-rt_v3-rev1/mingw32/i686-w64-mingw32/include
> >> does not appear in any of the include directories, unlike the
> >> i686-4.9.1-release-posix-dwarf-rt_v3-rev1.7z from SF in which it of
> course
> >> appears.
> >>
> >> So, what am I doing wrong??
> >>
> >> Yaron
> >>
> >>
> >
> >
> ------------------------------------------------------------------------------
> > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> > _______________________________________________
> > Mingw-w64-public mailing list
> > Mingw-w64-public@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
> >
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
