On 23.10.2013 21:09, LRN wrote:
>> This fixed the problem but using vanilla MSYS2 with Autoconf 2.69
>> doesn't have this issue.
> I've set up bash_msys.bat to set SHELLOPTS=igncr.
Removing the line fixed the issue.
AFAIK, sbuild is by far the most complete method of building a
Mingw/MSYS2 toolc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23.10.2013 21:38, Teemu Nätkinniemi wrote:
> On 23.10.2013 20:29, LRN wrote:
>> Alternatively you can do autoreconf, which will (or should, at least)
>> rebuild configure with patched status.m4 that you get from the autoconf
>> package that sbuild i
On 23.10.2013 20:29, LRN wrote:
> Alternatively you can do autoreconf, which will (or should, at least)
> rebuild configure with patched status.m4 that you get from the autoconf
> package that sbuild installed.
This fixed the problem but using vanilla MSYS2 with Autoconf 2.69
doesn't have this is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23.10.2013 21:19, Teemu Nätkinniemi wrote:
> On 21.10.2013 23:01, LRN wrote:
>
>> sbuild[1] was bumped to 3.2 due to the basic toolchain update - mingw
>
> This is the first version of sbuild I've tried and cannot configure
> anything as I get th
On 21.10.2013 23:01, LRN wrote:
> sbuild[1] was bumped to 3.2 due to the basic toolchain update - mingw
This is the first version of sbuild I've tried and cannot configure
anything as I get the following error every time and cannot figure out
what is causing the problem. The system is Windows 8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
sbuild[1] was bumped to 3.2 due to the basic toolchain update - mingw
gcc was updated to 4.8.2 and most of its dependencies were updated as well:
binutils-2.23.90.20131017-1
cloog-0.18.1-1
gcc-4.8.2-1
gmp-5.1.3-1
mingw-w64-crt-svn-r6358-1
mingw-w64-he
