Hello,
While porting msysGit to MSYS2/MinGW-w64 we ran into this:
$ PATH=/mingw64/bin:"$PATH" gcc --version
gcc.exe (Rev1, Built by MSYS2 project) 4.9.1
$ cat test.c
#include
static inline pid_t fork(void);
void main() {}
$ PATH=/mingw64/bin:"$PATH" gcc test.c
test.c:2:21: warning: conflicting
Ruben Van Boxem
writes:
[snip]
> Anyways, it's a real clusterf*ck and MS should be ashamed of themselves for
> letting it come to this.
Microsoft?
--
Want fast and easy access to all the code in your enterprise? Index
2014-07-22 20:01 GMT+02:00 niXman :
> Does anybody know is SEH-32bit support already implemented in GCC?
>
It's not.
Some more reading:
http://wiki.ffii.org/Wine05En
web.archive.org/web/20070818053531/blogs.codegear.com/dcc/archive/2005/05/12/4294.aspx
http://cygwin.com/ml/cygwin/1999-08/msg0036
Does anybody know is SEH-32bit support already implemented in GCC?
--
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - t
Op 22-jul.-2014 19:23 schreef "niXman" :
>
> massimo 2014-07-22 20:24:
> > Yes
> > http://www.google.com/patents/US5628016
>
> I can not see the expiration date...
US patents are valid for 20 years:
http://en.m.wikipedia.org/wiki/Term_of_patent_in_the_United_States
But you know, IANAL and all tha
I was able to find this:
http://lists.cs.uiuc.edu/pipermail/cfe-dev/2011-March/014130.html
It mentions June 14th, 2014.
(But of course that can be hardly seen as some authoritative source.)
M.
> massimo 2014-07-22 20:24:
>> Yes
>> http://www.google.com/patents/US5628016
>
> I can not see the
massimo 2014-07-22 20:24:
> Yes
> http://www.google.com/patents/US5628016
I can not see the expiration date...
--
Regards, niXman
___
Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:
http://sourceforge.net/projects/mingw-w64
Yes
http://www.google.com/patents/US5628016
--
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software
Massimo 2014-07-22 18:25:
> regarding last MinGW-W64 based on GCC-4.9.1
> will be possible use seh for 32 bit:
> Thanks in advance
Borland the SEH patent already expired?
--
Regards, niXman
___
Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 an
regarding last MinGW-W64 based on GCC-4.9.1
will be possible use seh for 32 bit:
Thanks in advance
--
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a fre
I have error described here:
http://www.qtcentre.org/threads/38060-How-to-fix-this-error-undefined-reference-to-IID_IMultiLanguage
Seems some GUIDs are missing in mingw-w64.
Regards,
Alexey.
--
Want fast and easy access
Yes, the shell that is run is the bash shell for MSYS2 make and
cmd.exe for mingw32-make, and there are some other differences about
the handling of 'special' characters. By default you should use MSYS2
make, unless you have a compelling reason not to.
-
On Tue, Jul 22, 2014 at 3:36 PM, Ray Donnelly
wrote:
> No, you didn't find any bug in MSYS2.
>
> If you want MSYS2 path translation to happen then use an MSYS2
> program, i.e. MSYS2 make, not mingw32-make.
>
Oh, OK, sorry. I thought that any program run from within msys got
automatic path transl
No, you didn't find any bug in MSYS2.
If you want MSYS2 path translation to happen then use an MSYS2
program, i.e. MSYS2 make, not mingw32-make.
--
Want fast and easy access to all the code in your enterprise? Index and
s
Hi,
I (think I) found a bug in msys2. Here is a simple demo case:
main.c:
int main() { return 42; }
Makefile:
CC = gcc
CC2 = $(shell which $(CC))
out_1: clean main.c
$(CC) main.c -o /home/username/out.exe
out_2: clean main.c
$(CC) /home/username/main.c -o out.exe
out_3: clean main.c
$(CC) main.c
15 matches
Mail list logo
