Vishal S., Would you like to report or discuss the issue to msys2
project? Here are the ways to contact
* GitHub project: https://github.com/msys2/MSYS2-packages (for msys2
environment only)
* Gitter: https://gitter.im/msys2/msys2
* Discord: https://discord.gg/JT49nk6hyv
在 3/2/22 16:50, Vishal Subramanyam 写道:
On Wed, 2 Mar 2022 09:30:37 +0800
LIU Hao wrote:
I suggest you use MSYS2 because they actively maintain new toolchains.
MSYS2 doesn't seem to work on my computer. Getting an error related to
cygheap or something. Anyway, I managed to find a Windows build
On Wed, 2 Mar 2022 09:30:37 +0800
LIU Hao wrote:
> I suggest you use MSYS2 because they actively maintain new toolchains.
MSYS2 doesn't seem to work on my computer. Getting an error related to
cygheap or something. Anyway, I managed to find a Windows build of GCC
11 with MinGW-64 9.0 (on winlibs.
在 3/1/22 20:38, Vishal Subramanyam 写道:
Hey,
Whenever I include in any of my programs, with the "-std=c++17"
option, I get a huge output with a lot of errors.
I suggest you use MSYS2 because they actively maintain new toolchains.
You only need the package manager. Once complete environments
Hey,
Whenever I include in any of my programs, with the "-std=c++17"
option, I get a huge output with a lot of errors.
Pastebin: https://pastebin.com/DiwQAzpW
Apparently, this has been fixed in a later release of GCC, but the Windows
binaries for gcc (latest: 8.1) still doesn't have these fixes
- Original Message -
From: "Matthew Bentham" <[EMAIL PROTECTED]>
.
.
> Maybe the access() problem doesn't even exist in SP1.
Oh, shit ... I think that's right !!
Before installing SP1, with a certain MinGW32 installation, I got:
---
C:\_64\C>\strawberry\c\bin\gcc -o t
- Original Message
> From: NightStrike <[EMAIL PROTECTED]>
> To: Matthew Bentham <[EMAIL PROTECTED]>
> Cc: mingw-w64-public@lists.sourceforge.net
> Sent: Tuesday, June 3, 2008 8:06:13 AM
> Subject: Re: [Mingw-w64-public] Cannot #include
>
> On 5/23/
On 5/23/08, Matthew Bentham <[EMAIL PROTECTED]> wrote:
> My experience with the binary builds from mingw64 SourceForge has also been
> that they suffer from the Vista access() problem, as we discussed on this
> mailing list on Feb 24th 2008. I've included my notes from the time
> (discussing th
On 6/2/08, Sisyphus <[EMAIL PROTECTED]> wrote:
>
> - Original Message - From: "NightStrike" <[EMAIL PROTECTED]>
> To: "Sisyphus" <[EMAIL PROTECTED]>
> Cc:
> Sent: Tuesday, June 03, 2008 1:05 AM
> Subject: Re: [Mingw-w64-p
- Original Message -
From: "NightStrike" <[EMAIL PROTECTED]>
To: "Sisyphus" <[EMAIL PROTECTED]>
Cc:
Sent: Tuesday, June 03, 2008 1:05 AM
Subject: Re: [Mingw-w64-public] Cannot #include
.
.
> I'm running with SP1
> installed and all the recen
On 6/2/08, Sisyphus <[EMAIL PROTECTED]> wrote:
>
> - Original Message - From: "Sisyphus" <[EMAIL PROTECTED]>
> .
> .
> >
> > C:\_64\C>gcc -o try.exe try.c
> > gcc: CreateProcess: No such file or directory
> >
> >
>
> Hmmm ... this is slightly different to what happens when I try to build
>
- Original Message -
From: "Sisyphus" <[EMAIL PROTECTED]>
.
.
>
> C:\_64\C>gcc -o try.exe try.c
> gcc: CreateProcess: No such file or directory
>
Hmmm ... this is slightly different to what happens when I try to build
try.c using a mingw32 that *doesn't* have the access() fix:
C:\_64\C
- Original Message -
From: "NightStrike" <[EMAIL PROTECTED]>
.
.
>
> Please try the latest version, dated 0528 for x86_64-mingw. You will
> probably have to specify the link time libraries on the command line
> (-lkernel32, etc). That bug will be fixed tomorrow. However, this
> should
On 5/18/08, Sisyphus <[EMAIL PROTECTED]> wrote:
>
> - Original Message - From: "NightStrike" <[EMAIL PROTECTED]>
> .
> .
> >
> > I will spin a completely new fresh version of the toolchain (maybe
> > there was an error in there somewhere), run it on my Vista64 machine,
> > compile Hello Wor
ublic@lists.sourceforge.net
> Sent: Monday, May 19, 2008 4:45:06 AM
> Subject: Re: [Mingw-w64-public] Cannot #include
>
>
> - Original Message -
> From: "NightStrike"
> .
> .
> >
> > I will spin a completely new fresh version of the toolch
- Original Message -
From: "NightStrike" <[EMAIL PROTECTED]>
.
.
>
> I will spin a completely new fresh version of the toolchain (maybe
> there was an error in there somewhere), run it on my Vista64 machine,
> compile Hello World, and if it works, I'll upload it.
Let me know when that's
On 5/18/08, Sisyphus <[EMAIL PROTECTED]> wrote:
> As to what the problem *was* is now a little unclear to me. Perhaps it was
> because I originally unzipped into C:\_64\mingw64 instead of a top level
> folder. Or perhaps it was something to do with the way I had jumped through
> all those hoops.
F
- Original Message -
From: "NightStrike" <[EMAIL PROTECTED]>
.
.
>> C:\_64>gcc -o try.exe try.c -v
>> Using built-in specs.
>> Target: x86_64-pc-mingw32
>> Configured with:
>> ../build/gcc-svn/gcc/configure --target=x86_64-pc-mingw32
>> --pre
>> fix=/var/tmp/w64 --with-sysroot=/var/tmp/w
On 5/18/08, Sisyphus <[EMAIL PROTECTED]> wrote:
> Hi,
>
> C:\>type try.c
> #include
>
> int main(void) {
>return 1;
> }
>
This should be no problem. Maybe you did not properly set the
environments. I use different source that already has mthread
(openmp). For example,
C:\temp\c>more a.c
#in
On 5/18/08, Sisyphus <[EMAIL PROTECTED]> wrote:
>
> - Original Message - From: "NightStrike" <[EMAIL PROTECTED]>
> To: "Sisyphus" <[EMAIL PROTECTED]>
> Cc:
> Sent: Sunday, May 18, 2008 4:47 PM
> Subject: Re: [Mingw-w64-publi
- Original Message -
From: "NightStrike" <[EMAIL PROTECTED]>
To: "Sisyphus" <[EMAIL PROTECTED]>
Cc:
Sent: Sunday, May 18, 2008 4:47 PM
Subject: Re: [Mingw-w64-public] Cannot #include
> On 5/18/08, Sisyphus <[EMAIL PROTECTED]> wrote:
>>
On 5/18/08, Sisyphus <[EMAIL PROTECTED]> wrote:
> Hi,
>
> C:\>type try.c
> #include
>
> int main(void) {
>return 1;
> }
>
> C:\>gcc -o try.exe try.c
Do this:
gcc -o try.exe try.c -v
(ie, add -v to your compile command)
Post the output of that.
-
Hi,
C:\>type try.c
#include
int main(void) {
return 1;
}
C:\>gcc -o try.exe try.c
In file included from
C:\_64\mingw64\x86_64-pc-mingw32\include/xmmintrin.h:44,
from
C:\_64\mingw64\x86_64-pc-mingw32\include/emmintrin.h:43,
from C:\_64\mingw64\x86_64-pc-ming
23 matches
Mail list logo
