Martell Malone | 5 Mar 01:33 2015
Picon

[PATCH] legacythreadapi: Fixup and correct header name

The header name was incorrect :)
I added WinStoreCompat support also

Please Review
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@...
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Martell Malone | 5 Mar 00:59 2015
Picon

[PATCH] winbase.h: Add LoadLibraryW for WINSTORECOMPAT

Please Review
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@...
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Martell Malone | 5 Mar 00:52 2015
Picon

[PATCH] shlobj.h: Add SHGetFolderPathW for WINSTORECOMPAT

Please Review :)
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@...
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Martell Malone | 4 Mar 23:33 2015
Picon

[PATCH] update ws2 defs for wack 3.4

I send this is previously but it was never applied.
So I redone a new one.

Yes that is removing a line at the end of a file also
There were 2 blank lines.
Attachment (0001-update-ws2-defs-for-wack-3.4.patch): application/octet-stream, 1896 bytes
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@...
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Martell Malone | 4 Mar 19:41 2015
Picon

[PATCH] add def file for d3dcompiler_47.dll

We need this for windows 8.1 RT apps :)
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@...
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
JonY | 4 Mar 14:51 2015
Picon
Picon

v4.0-rc3 released


Hello all,

The 3rd RC is out for v4, hopefully the last RC. Some changes since RC2
include:

* Fix 32-bit stdcall def file for d3d11.dll
* Fix _lrotl on LLP64

Without further ado:
<http://sourceforge.net/projects/mingw-w64/files/mingw-w64/mingw-w64-release/mingw-w64-v4.0-rc3.tar.bz2>
<http://sourceforge.net/projects/mingw-w64/files/mingw-w64/mingw-w64-release/mingw-w64-v4.0-rc3.tar.bz2.sig>

Attachment (0xD4EBC740.asc): application/pgp-keys, 3145 bytes
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@...
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
David Rysdam | 2 Mar 15:25 2015
Picon

completely lost building/linking DLLs

Basic problem statement: I've got a piece of software here that's
divided into "low" and "high" DLL halves. Using mingw32[1], I can
cross-compile both halves, but the high half won't link to the low
one. (The low one is standalone and works fine when I copy it over to a
Windows machine, so I know the toolchain basically works.)

I'm suffering from variable overload--there are just too many things
where I don't know how they are supposed to work, so there are too many
combinations to try. These low/high DLLs are part of a Tcl package,
which is configured using autotools and Tcl's own set of autotool macros
known as "TEA". I can't guarantee these things are doing The Right Thing
wrt either cross-compiling in general or windows DLLs in particular.

This code did originally build on Windows, but we've made modifications
to it (including splitting it into the low/high halves) and there's
basically no support online anymore. It's possible these changes are
preventing an easy Windows build.

Then there's the added fact that I have no idea how DLLs work at a
source level. I spent some time trying to make a sample low/high DLL
pair to eliminate any Tcl/autotools/TEA variables. However, "making
Windows DLLs from scratch via mingw" is already complicated enough that
I'm lost. Is there a tutorial for this?

As for the larger problem: I don't think I even know enough to ask an
intelligent question. Maybe if I just list out some promising facts,
someone will say something that can shed some light.

a) TEA/autotools generates code to look for DLLs, but not with a .dll
extension. It wants to find a .lib. It looks like this is some kind of
manifest or header type thing that can be linked against...?

b) If I explicitly put a reference to low.dll in my link line, I get a
bunch of "undefined reference"s, just like if I have nothing about low
in there at all. 

c) I found 'dlltool', which seems promising. I can generate a .lib file
from my dll. (Why doesn't the low.dll Makefile do this already?) But
that doesn't fix the references and 'objdump' doesn't show those names
in there. ('nm' does.)

d) I told 'dlltool' to '--export-all-symbols' and most of my undefined
refs resolved. However, there's at least one junk name in there that
looks like a path name to the lib file itself. Like this:

    __head_dir1_dir2_low_lib

e) Thinking about why --export-all-symbols wasn't the default, I assume
it's a public/private data thing. So maybe the real issue is that all
the low.dll API has to be exposed somehow?

[1]That's what the package is called in CentOS 6.5. I don't know which
half of the fork this is actually from. I would have though the older
half, but from comments in an earlier thread maybe it's the newer half.

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
David Rysdam | 24 Feb 13:52 2015
Picon

detailed build errors

To partly re-iterate, I'm following these instructions

    http://sourceforge.net/p/mingw-w64/wiki2/Cross%20Win32%20and%20Win64%20compiler/

to build a Win64-only cross compiler on Debian (later CentOS). There are
some ambiguities in the instructions, and I've taken a stab at resolving
them. I've converted my understanding of the instructions into a script,
which I include here:

    #!/bin/bash

    PREFIX=/home/dr/software/mingwtest

    # clean previous attempt
    cd $PREFIX
    rm -rf bin include lib libexec mingw share x86_64*
    cd src
    rm -rf build*

    # binutils
    echo binutils
    cd $PREFIX/src
    test -d build-binutils && rm -rf build-binutils
    mkdir build-binutils
    cd build-binutils
    (../binutils*/configure --target=x86_64-w64-mingw32 --disable-multilib --with-sysroot=$PREFIX
--prefix=$PREFIX && make -j 8 && make install) > ../binutils.log 2>&1
    export PATH=$PATH:$PREFIX/bin

    # mingw-64 header set
    echo header set
    cd $PREFIX/src
    test -d build-headers && rm -rf build-headers
    mkdir build-headers
    cd build-headers
    (../mingw-w64-v3.3.0/mingw-w64-headers/configure --build=x86_64 --host=x86_64-w64-mingw32
--prefix=$PREFIX/x86_64-w64-mingw32 && make install) > ../headers.log 2>&1

    ln -s $PREFIX/x86_64-w64-mingw32 $PREFIX/mingw 
    mkdir -p $PREFIX/x86_64-w64-mingw32/lib 
    ln -s $PREFIX/x86_64-w64-mingw32/lib $PREFIX/x86_64-w64-mingw32/lib64 

    #gcc core
    echo gcc core
    cd $PREFIX/src
    test -d build-gcc && rm -rf build-gcc
    mkdir build-gcc
    cd build-gcc
    (../gcc*/configure --target=x86_64-w64-mingw32 --disable-multilib --prefix=$PREFIX
--with-sysroot=$PREFIX && make -j 8 all-gcc && make install-gcc) > ../gcc.log 2>&1

    # crt
    echo crt
    cd $PREFIX/src
    test -d build-crt && rm -rf build-crt
    mkdir build-crt
    cd build-crt
    (../mingw*/mingw-w64-crt/configure --host=x86_64-w64-mingw32
--prefix=$PREFIX/x86_64-w64-mingw32 --with-sysroot=$PREFIX/x86_64-w64-mingw32 && make && make
install) > ../crt.log 2>&1

It only goes up as far as crt because that's where things fail. Those
logs are pretty long, so I'll omit them. Here's the end of crt.log:

    x86_64-w64-mingw32-gcc -DHAVE_CONFIG_H -I. -I../mingw-w64-v3.3.0/mingw-w64-crt  -m64
-I../mingw-w64-v3.3.0/mingw-w64-crt/include -D_CRTBLD
-I/home/dr/software/mingwtest/x86_64-w64-mingw32/include  -pipe -std=gnu99 -Wall -Wextra
-Wformat -Wstrict-aliasing -Wshadow -Wpacked -Winline -Wimplicit-function-declaration
-Wmissing-noreturn -Wmissing-prototypes -g -O2 -MT intrincs/lib64_libkernel32_a-ilockadd.o -MD
-MP -MF intrincs/.deps/lib64_libkernel32_a-ilockadd.Tpo -c -o
intrincs/lib64_libkernel32_a-ilockadd.o `test -f 'intrincs/ilockadd.c' || echo '../mingw-w64-v3.3.0/mingw-w64-crt/'`intrincs/ilockadd.c
    In file included from /home/dr/software/mingwtest/lib/gcc/x86_64-w64-mingw32/4.5.1/../../../../x86_64-w64-mingw32/include/intrin.h:41:0,
                     from ../mingw-w64-v3.3.0/mingw-w64-crt/intrincs/ilockadd.c:1:

/home/dr/software/mingwtest/lib/gcc/x86_64-w64-mingw32/4.5.1/../../../../x86_64-w64-mingw32/include/psdk_inc/intrin-impl.h:
In function ‘_umul128’:

/home/dr/software/mingwtest/lib/gcc/x86_64-w64-mingw32/4.5.1/../../../../x86_64-w64-mingw32/include/psdk_inc/intrin-impl.h:774:48:
error: expected ‘:’, ‘,’, ‘;’, ‘}’ or ‘__attribute__’ before ‘v’

/home/dr/software/mingwtest/lib/gcc/x86_64-w64-mingw32/4.5.1/../../../../x86_64-w64-mingw32/include/psdk_inc/intrin-impl.h:775:7:
error: ‘union <anonymous>’ has no member named ‘v’

/home/dr/software/mingwtest/lib/gcc/x86_64-w64-mingw32/4.5.1/../../../../x86_64-w64-mingw32/include/psdk_inc/intrin-impl.h:776:7:
error: ‘union <anonymous>’ has no member named ‘v’

/home/dr/software/mingwtest/lib/gcc/x86_64-w64-mingw32/4.5.1/../../../../x86_64-w64-mingw32/include/psdk_inc/intrin-impl.h:777:21:
error: ‘union <anonymous>’ has no member named ‘sv’

/home/dr/software/mingwtest/lib/gcc/x86_64-w64-mingw32/4.5.1/../../../../x86_64-w64-mingw32/include/psdk_inc/intrin-impl.h:778:14:
error: ‘union <anonymous>’ has no member named ‘sv’
    make[1]: *** [intrincs/lib64_libkernel32_a-ilockadd.o] Error 1
    make[1]: Leaving directory `/home/dr/software/mingwtest/src/build-crt'
    make: *** [all] Error 2

It seems unlikely that the header really is wrong, so I expect some
previous flag/directive is bad. I can't make out what, though.    

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Jeroen Ooms | 23 Feb 21:09 2015

Building native mingw-w64 with multilib with Docker

I'm trying to build a 32 bit native compiler using the cross compiler
that ships with Debian Jessie. Ideally we would like:

 - gcc 4.9.2
 - multilib
 - sjsl exceptions

The dockerfile is here [1] and to see the latest build attempts on my
dockerhub [2]. The current script fails make gcc-all with:

    /.libs/libisl.a(libisl_la-isl_map_simplify.o):isl_map_simplify.c:(.text+0x204b):
undefined reference to `ffs'

I've been getting the same error when building locally. Any guess to
what I'm doing wrong? Has anyone else here succeeded in building a
native compiler using the Debian cross compiler?

[1] https://github.com/jeroenooms/mingw-w64-docker
[2] https://registry.hub.docker.com/u/jeroenooms/mingw32-native-multilib/builds_history/145566/

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
David Rysdam | 23 Feb 15:32 2015
Picon

trouble getting mingw setup

I have a project I want to cross compile for Win64 from my Linux machine
(x86_64 CentOS 6.5 eventually, but x86_64 Debian 7 for the below
test). For reasons, life will be much better and easier for me if I
compile the toolchain from source. (I know that on Debian I can apt-get
install, but I'm testing the compile instructions here before I move
elsewhere.)

I'm following these instructions:

    http://sourceforge.net/p/mingw-w64/wiki2/Cross%20Win32%20and%20Win64%20compiler/

I'm disabling multilib, since I only need Win64. I'm also using the
sysroot/prefix options. I see some supported version numbers for
binutils and gcc there, but the version of mingw itself is unclear. The
latest stable seems to be 3.3, so I'm using that. (The 4.x releases are
all "rc"--maybe I'm reading too much into that.)

binutils 2.25 builds and installs fine. I set my path to have those bins
in there.

Now we come to the "header set" part. First, I'm confused by step 1:
"The source directory for the headers can be
mingw-w64/trunk/mingw-w64-headers, or mingw-w64/mingw-w64-headers
depending on your source."

What am I supposed to do with this information? There doesn't seem to be
anything to do here, so I did nothing other than nod politely.

Step 2 says I should: ../path/to/configure --build=<your build machine> --host=x86_64-w64-mingw32 --prefix=/mypath

Not totally clear how "my build machine" is supposed to be
specified. Machine name? Some kind of indicator string? Machine name
failed, so I tried some possibilities:

    1) ../mingw-w64-v3.3.0/configure --build=x86_64
    --host=x86_64-w64-mingw32 --prefix=<my prefix>/x86_64-w64-mingw32

    result: configure: error: Please check if the mingw-w64 header set and the build/host option are set properly.
            configure: error: ../../mingw-w64-v3.3.0/mingw-w64-crt/configure failed for mingw-w64-crt

    2) ../mingw-w64-v3.3.0/configure --build=x86_64-w64-mingw32
    --host=x86_64-w64-mingw32 --prefix=<my prefix>/x86_64-w64-mingw32

    result: configure: error: Please check if the mingw-w64 header set and the build/host option are set properly.
            configure: error: ../../mingw-w64-v3.3.0/mingw-w64-crt/configure failed for mingw-w64-crt

Same failure either way. Perhaps I've chosen my "build machine" string
badly. OTOH, the error talks about the "header set", so maybe back when
I nodded politely I should have taken some action. But what?

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
Vadim Chugunov | 23 Feb 10:17 2015
Picon

Link-time dead code elimination

Hi,
Is link-time dead code elimination via --function-sections + -Wl,--gc-sections known to work on mingw?

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@...
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Gmane