From: Danny S. <dan...@cl...> - 2007-08-09 06:10:50
|
> > Danny, this file seems to be truncated. I get the following error > trying to extract it: > I've uploaded again. Should be fixed now. Danny |
From: Danny S. <dan...@cl...> - 2007-08-09 08:29:11
|
Many Thanks. > > A few questions :- > > 1) Do you have diffs against 4.2.1 ? Yes > 2) If so would could you put them online somewhere ? Sometime, but not a high priority for me. > 3) Do these changes get to be merged back into GCC 4.2 line. I have no interest in doing so. I would rather spend my time on 4.3.0, from whence most of the diffs come Danny > > Aaron > |
From: Aaron G. <aa...@aa...> - 2007-08-09 17:19:48
|
> A GCC 4.2.1 binary release for mingw is available. Thanks for this! I am seeing similar problems when running this to the problems that previous version had when building under Windows Vista. Does this binary include the Vista patch/workaround for stat()? C:\test>echo int main(int argc,char*argv[]){return 0;} >test.c C:\test>gcc test.c gcc: CreateProcess: No such file or directory C:\test>gcc -v test.c Using built-in specs. Target: mingw32 Configured with: ../gcc-4.2.1/configure --with-gcc --enable-libgomp --host=3D3Dmingw32 --build=3D3Dmingw32 --target=3D3Dmingw32 =3D --program-suffix=3D3D-sjlj --with-arch=3D3Di486 --with-tune=3D3Dgeneric --disable-werror =3D --prefix=3D3D/mingw --with-local-prefix=3D3D/mingw --enable-threads --disable-nls --enable-languages=3D3Dc,c++,fortran,objc,obj-c++,ada --disable-win32-registry --enable-sjlj-exceptions --enable-libstdcxx-debug --enable-cxx-flags=3D3D-fno-function-sections -fno-data-sections --enable-version-specific-runtime-libs --disable-bootstrap Thread model: win32 gcc version 4.2.1-sjlj (mingw32 sjlj-unwind) c:/dev/tools/mingw/bin/../libexec/gcc/mingw32/4.2.1-sjlj/cc1.exe -quiet -v -iprefix c:\dev\tools\mingw\bin\../lib/gcc/mingw32/4.2.1-sjlj/ test.c -quiet -dumpbase test.c -mtune=3D3Dgeneric -march=3D3Di486 -auxbase test -version -o C:\Users\aaron\AppData\Local\Temp/ccvPii2Q.s ignoring nonexistent directory "c:\dev\tools\mingw\bin\../lib/gcc/mingw32/4.2.1-sjlj/../../../../mingw3 2/include" ignoring nonexistent directory "/mingw/include" ignoring nonexistent directory "/mingw/lib/gcc/mingw32/4.2.1-sjlj/include" ignoring nonexistent directory "/mingw/mingw32/include" ignoring nonexistent directory "/mingw/include" #include "..." search starts here: #include <...> search starts here: =3D20 c:\dev\tools\mingw\bin\../lib/gcc/mingw32/4.2.1-sjlj/../../../../include c:\dev\tools\mingw\bin\../lib/gcc/mingw32/4.2.1-sjlj/include End of search list. GNU C version 4.2.1-sjlj (mingw32 sjlj-unwind) (mingw32) compiled by GNU C version 4.2.1 (mingw32-dw2-1). GGC heuristics: --param ggc-min-expand=3D3D100 --param ggc-min-heapsize=3D3D131072 Compiler executable checksum: bd8def1ef5493ed9ac50847809f4ced8 as -o C:\Users\aaron\AppData\Local\Temp/cc0t6oMF.o C:\Users\aaron\AppData\Local\Temp/ccvPii2Q.s gcc: CreateProcess: No such file or directory Aaron |
From: Danny S. <dan...@cl...> - 2007-08-09 19:54:46
|
> -----Original Message----- > From: min...@li... > [mailto:min...@li...] On Behalf > Of David Gressett > Sent: Friday, 10 August 2007 6:31 a.m. > To: MinGW Users List > Subject: Re: [Mingw-users] GCC 4.2.1 available > > > Danny Smith wrote: > > A GCC 4.2.1 binary release for mingw is available > Many thanks. It's now bug-chasing time, and I have found one. My > particular interest is in Ada; I use the MinGW Ada daily with GNATCOM > and GWindows, compiled with the 3.4.5 Ada. These can be > downloaded from > the Sourceforge GNAVI project. GNATCOM compiles, with a few warning > messages : "Procedure renamed after being referenced in > assembly". Hmm, Yes I can guess what the problem is, unfortunately the simple fix will break C++ COM usage. Danny |
From: David L. <yak...@ya...> - 2007-08-10 07:53:17
|
--- Danny Smith <dan...@cl...> escribió: > > Hmm, Yes I can guess what the problem is, unfortunately the simple fix > will break C++ > COM usage. > > Danny > So that means no DirectX usage possible? ____________________________________________________________________________________ Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! http://advision.webevents.yahoo.com/reto/entretenimiento.html |
From: Danny S. <dan...@cl...> - 2007-08-10 09:39:13
|
> > > > > Hmm, Yes I can guess what the problem is, unfortunately the > simple fix > > will break C++ > > COM usage. > > > > Danny > > > > So that means no DirectX usage possible? No I didn't say that. Danny |
From: David L. <yak...@ya...> - 2007-08-10 12:54:18
|
--- Danny Smith <dan...@cl...> escribió: > > > > > > > > > Hmm, Yes I can guess what the problem is, unfortunately the > > simple fix > > > will break C++ > > > COM usage. > > > > > > Danny > > > > > > > So that means no DirectX usage possible? > > No I didn't say that. > Danny > But as I have read in DirectX documentation, the DirectX interfaces are implemented as C++ COM objects (although they also can be called from C code as the documentation points). David. ____________________________________________________________________________________ Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden! http://advision.webevents.yahoo.com/reto/entretenimiento.html |
From: Duncan M. <dwm...@gm...> - 2007-08-10 13:42:54
|
Well, I would think that a fix for this problem shouldn't break C++ COM usage - and I think that is what Danny is saying - he needs to find a better fix. On 8/10/07, David Lucena <yak...@ya...> wrote: > > --- Danny Smith <dan...@cl...> escribi=F3: > > > > > > > > > > > > > > Hmm, Yes I can guess what the problem is, unfortunately the > > > simple fix > > > > will break C++ > > > > COM usage. > > > > > > > > Danny > > > > > > > > > > So that means no DirectX usage possible? > > > > No I didn't say that. > > Danny > > > > But as I have read in DirectX documentation, the DirectX interfaces are i= mplemented as C++ COM > objects (although they also can be called from C code as the documentatio= n points). > > David. > > > > _________________________________________________________________________= ___________ > S=E9 un Mejor Amante del Cine > =BFQuieres saber c=F3mo? =A1Deja que otras personas te ayuden! > http://advision.webevents.yahoo.com/reto/entretenimiento.html > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > MinGW-users mailing list > Min...@li... > > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users > |
From: Luke D. <cod...@ho...> - 2007-08-10 16:08:51
|
> Date: Thu, 9 Aug 2007 10:19:30 -0700> From: aa...@aa...> To: min= gw-...@li...> Subject: Re: [Mingw-users] GCC 4.2.1 availa= ble> > > A GCC 4.2.1 binary release for mingw is available.> > Thanks for t= his!> > I am seeing similar problems when running this to the problems that= > previous version had when building under Windows Vista. Does this binary>= include the Vista patch/workaround for stat()?> > C:\test>echo int main(in= t argc,char*argv[]){return 0;} >test.c> > C:\test>gcc test.c> gcc: CreatePr= ocess: No such file or directory =20 You forgot to install binutils. =20 Luke = |
From: Christoph E. <chr...@gm...> - 2007-08-11 09:45:08
|
Luke Dunstan schrieb: >> C:\test>gcc test.c >> gcc: CreateProcess: No such file or directory > > You forgot to install binutils. > > Luke Have you ever tried using MinGW under Win Vista? It's not that easy and it's a real incompatibly-bug with MinGW under Vista. There are workarounds and I've seen some patch that is said to fix this however Christoph |
From: Aaron G. <aa...@aa...> - 2007-08-11 12:33:47
|
> Luke Dunstan schrieb: > >> C:\test>gcc test.c > >> gcc: CreateProcess: No such file or directory > > > > You forgot to install binutils. > > > > Luke >=20 > Have you ever tried using MinGW under Win Vista? It's not that easy and > it's a real incompatibly-bug with MinGW under Vista. >=20 > There are workarounds and I've seen some patch that is said to fix this > however No, actually, he was right. Egg on my face. I somehow forgot that step when updating my toolchain. :) Aaron |
From: Danny S. <dan...@cl...> - 2007-08-11 05:33:44
|
> -----Original Message----- > From: min...@li... > [mailto:min...@li...] On Behalf > Of David Gressett > Sent: Friday, 10 August 2007 6:31 a.m. > To: MinGW Users List > Subject: Re: [Mingw-users] GCC 4.2.1 available > > > Danny Smith wrote: > > A GCC 4.2.1 binary release for mingw is available > Many thanks. It's now bug-chasing time, and I have found one. My > particular interest is in Ada; I use the MinGW Ada daily with GNATCOM > and GWindows, compiled with the 3.4.5 Ada. These can be > downloaded from > the Sourceforge GNAVI project. GNATCOM compiles, with a few warning > messages : "Procedure renamed after being referenced in > assembly". When I tried to reproduce the problem by building GNATCOM, I don't see that problem. Instead the build fails with error about invalid use of keyword 'interface' as a variable name in GNATCOM.VARIANT. I also ran into a problem with finding 'interfaces.adb'. A message like "Procedure renamed after being referenced in assembly" would suggest a problem with Stdcall convention, but I have not been able to get that error using pragma Import (StdCall,...) or pragma Convention (Stdcall,..). How exactly are you building GNATCOM? In what module do error occur? Danny |
From: David G. <jdg...@am...> - 2007-08-12 01:55:33
|
Danny Smith wrote: > > When I tried to reproduce the problem by building GNATCOM, I don't see > that problem. Instead the build fails > with error about invalid use of keyword 'interface' as a variable name > in GNATCOM.VARIANT. I also ran into a problem with finding > 'interfaces.adb'. > You should probably get the version in CVS. There were some patches made to the code so that it would compile with Ada 2005. It's been a long time since I downloaded this stuff. I thought that the released code was up to date with CVS, but that seems to not be true. "interface" was changed to "iinterface" to avoid the new reserved word. > A message like "Procedure renamed after being referenced in assembly" > would suggest a problem with > Stdcall convention, but I have not been able to get that error using > pragma Import (StdCall,...) or pragma Convention (Stdcall,..). > > How exactly are you building GNATCOM? In what module do error occur? > There is a makefile that is intended to work with a Windows command shell, i.e., don't use MSYS. Just do "make install". In any case, here is a fairly minimal demonstration of the problem. Only three other packages from GNATCOM are needed to compile this: GNATCOM.BSTR, GNATCOM.Errors, and GNATCOM.Types Procedure Put_IUnknown is not referenced, but if it is removed, the problem disappears. The code is framed with lines of dashes. Spec: ------------------------------------------- with GNATCOM.Types; package GNATCOM.XSafeArray is type Bound is record Lower_Bound : Integer; Elements : Natural; end record; type SafeArray_Bounds is array (Positive range <>) of Bound; type Index_Array is array (Positive range <>) of Integer; -- Indexes are passed in from right to left, ie. FORTRAN style procedure Put_BSTR (Of_Array : access GNATCOM.Types.SAFEARRAY; Index : in Integer; Value : in GNATCOM.Types.BSTR; Clear : in Boolean := True); ARRAY_LOCKED_ERROR : exception; -- An operation is being attempted on a SAFEARRAY that has been locked ARRAY_CREATION_ERROR : exception; -- OS was unable to create array INVALID_INDEX_ERROR : exception; -- The requested index value is invalid for this array end GNATCOM.XSafeArray; --------------------------------------------------------- Body: --------------------------------------------------------- with Interfaces.C; with GNATCOM.BSTR; with GNATCOM.Errors; package body GNATCOM.XSafeArray is procedure Error_Check (Result : in GNATCOM.Types.HRESULT); -- Check for SAFEARRAY specific errors -- Put_IUnknown -- procedure Put_IUnknown (Of_Array : access GNATCOM.Types.SAFEARRAY; Index : in Index_Array; Value : in GNATCOM.Types.Pointer_To_IUnknown) is type Index_Array is array (Index'Range) of Interfaces.C.long; function SafeArrayPutElement (psa : access GNATCOM.Types.SAFEARRAY; rgIndices : access Index_Array; pv : GNATCOM.Types.Pointer_To_IUnknown) return GNATCOM.Types.HRESULT; pragma Import (StdCall, SafeArrayPutElement, "SafeArrayPutElement"); SAIndex : aliased Index_Array; begin for N in Index'Range loop SAIndex (N) := Interfaces.C.long (Index (N)); end loop; Error_Check (SafeArrayPutElement (Of_Array, SAIndex'Access, Value)); end Put_IUnknown; -- Put_BSTR -- procedure Put_BSTR (Of_Array : access GNATCOM.Types.SAFEARRAY; Index : in Integer; Value : in GNATCOM.Types.BSTR; Clear : in Boolean := True) is type Index_Array is array (1 .. 1) of Interfaces.C.long; function SafeArrayPutElement (psa : access GNATCOM.Types.SAFEARRAY; rgIndices : access Index_Array; pv : in GNATCOM.Types.BSTR) return GNATCOM.Types.HRESULT; pragma Import (StdCall, SafeArrayPutElement, "SafeArrayPutElement"); SAIndex : aliased Index_Array; begin SAIndex (1) := Interfaces.C.long (Index); Error_Check (SafeArrayPutElement (Of_Array, SAIndex'Access, Value)); if Clear then GNATCOM.BSTR.Free (Value); end if; end Put_BSTR; -- Put_BSTR -- -- Error_Check -- procedure Error_Check (Result : in GNATCOM.Types.HRESULT) is begin GNATCOM.Errors.Set_Last_HRESULT (Result); if GNATCOM.Errors.FAILED (Result) then case Result is when DISP_E_ARRAYISLOCKED => raise ARRAY_LOCKED_ERROR; when DISP_E_BADINDEX => raise INVALID_INDEX_ERROR; when others => GNATCOM.Errors.Error_Check (Result); end case; end if; end Error_Check; end GNATCOM.XSafeArray; --------------------------------------------------- |
From: Fredric J. <joh...@ho...> - 2007-08-11 10:34:47
|
> Date: Thu, 9 Aug 2007 07:10:04 +1200> From: dan...@cl...> To: = min...@li...> Subject: [Mingw-users] GCC 4.2.1 availab= le> > A GCC 4.2.1 binary release for mingw is available.Thank you for your = effort in creating and maintaining mingw's gcc releasesThey are very much a= ppreciated.> * Static and dll libraries of libgcc and libstdc++ are in the = release.> By default, linkage is to static libraries. More details later= .I can find the dll library of libstdc++ but not the shared libgcc> 1) Sour= ce distribution, with mingw-local patches incorporated: > gcc-4.2.1-1-src= .tar.gz> (This is the whole shebang. Maybe some day I'll have time to bre= ak> up into language components.)> 3) gcc-4.2.1-build-dw2.sh, which is t= he script I used to configure> and build.Did you do any changes in the s= ources between the release of the dw2and sjlj versions? When I try to compi= le gcc for dw2eh I still sayssjlj-unwind when running gcc -v. is that stat= ic and must be changedin the sources?Another question about compiling gcc. = I cant manage to get the sharedversions of libgcc and libstdc++ built. Is t= here some special actionneeded to get them to build or should the script yo= u used be enough?// Fredric Johansson _________________________________________________________________ Windows Live Spaces =E4r h=E4r! Det =E4r enkelt att skapa en egen personlig= webbplats. http://spaces.live.com/signup.aspx= |
From: Luke D. <cod...@ho...> - 2007-08-11 13:53:18
|
> To: min...@li...> From: chr...@gm...> Date= : Sat, 11 Aug 2007 11:33:47 +0200> Subject: Re: [Mingw-users] GCC 4.2.1 ava= ilable> > Luke Dunstan schrieb:> >> C:\test>gcc test.c> >> gcc: CreateProce= ss: No such file or directory> > > > You forgot to install binutils.> > > >= Luke> > Have you ever tried using MinGW under Win Vista? It's not that eas= y and> it's a real incompatibly-bug with MinGW under Vista.> > There are wo= rkarounds and I've seen some patch that is said to fix this> however> > Chr= istophYes, I have tried using MinGW on Vista. Yes, previous releases did no= t work without a patch. However, MinGW GCC version 4.2.1 already includes t= his patch so it should work on Vista. I have tried building a "Hello World"= program with MinGW GCC 4.2.1 on Vista and it works fine. The reason why I = suggested that "binutils" was missing is because I got the exact same error= message after I had installed the latest release but I had not yet install= ed binutils. =20 Luke = |
From: Tuomo L. <dj...@ik...> - 2007-08-11 19:46:40
|
Luke Dunstan wrote: >> To: min...@li...> From: chr...@gm...> Date: Sat, 11 Aug 2007 11:33:47 +0200> Subject: Re: [Mingw-users] GCC 4.2.1 available> > Luke Dunstan schrieb:> >> C:\test>gcc test.c> >> gcc: CreateProcess: No such file or directory> > > > You forgot to install binutils.> > > > Luke> > Have you ever tried using MinGW under Win Vista? It's not that easy and> it's a real incompatibly-bug with MinGW under Vista.> > There are workarounds and I've seen some patch that is said to fix this> however> > ChristophYes, I have tried using MinGW on Vista. Yes, previous releases did not work without a patch. However, MinGW GCC version 4.2.1 already includes this patch so it should work on Vista. I have tried building a "Hello World" program with MinGW GCC 4.2.1 on Vista and it works fine. The reason why I suggested that "binutils" was missing is because I got the exact same error message after I had installed the latest release but I had not yet installed binutils. You can actually read this? I simply deleted the first "one-liner" post... Did I miss something important or interesting? -- Tuomo ... Volume in drive C is TOO LOUD |
From: Danny S. <dan...@cl...> - 2007-08-11 22:13:20
|
-----Original Message----- From: min...@li... [mailto:min...@li...] On Behalf Of Fredric Johansson Sent: Saturday, 11 August 2007 10:35 p.m. To: MinGW Users List Subject: Re: [Mingw-users] GCC 4.2.1 available > Date: Thu, 9 Aug 2007 07:10:04 +1200 > From: dan...@cl... > To: min...@li... > Subject: [Mingw-users] GCC 4.2.1 available > > A GCC 4.2.1 binary release for mingw is available. | Thank you for your effort in creating and maintaining mingw's gcc releases | They are very much appreciated. > * Static and dll libraries of libgcc and libstdc++ are in the release. > By default, linkage is to static libraries. More details later. | I can find the dll library of libstdc++ but not the shared libgcc I'll have a look. Probably a packaging bug/ > 1) Source distribution, with mingw-local patches incorporated: > gcc-4.2.1-1-src.tar.gz > (This is the whole shebang. Maybe some day I'll have time to break > up into language components.) > 3) gcc-4.2.1-build-dw2.sh, which is the script I used to configure > and build. |Did you do any changes in the sources between the release of the dw2 |and sjlj versions? When I try to compile gcc for dw2eh I still says |sjlj-unwind when running gcc -v. is that static and must be changed |in the sources Sorry there are a few things left out of the script. eg ln gcc/BASE-VER-dw2 gcc/BASE-VER ln gcc/config/i386/t-mingw32dw2 gcc/config/i386/t-mingw32 I'll write up the 'more details later' as soon as ... |Another question about compiling gcc. I cant manage to get the shared |versions of libgcc and libstdc++ built. Is there some special action |needed to get them to build or should the script you used be enough? See above Danny |
From: Danny S. <dan...@cl...> - 2007-08-12 00:30:13
|
> -----Original Message----- There is also the minor problem that six of these files seem to be gzip files with .gz2 extension (not to be confused with .bz2): gcc-ada-4.2.1-dw2-1.tar.gz2 gcc-ada-4.2.1-sjlj-1.tar.gz2 gcc-core-4.2.1-dw2-1.tar.gz2 gcc-core-4.2.1-sjlj-1.tar.gz2 gcc-g++-4.2.1-dw2-1.tar.gz2 gcc-g++-4.2.1-sjlj-1.tar.gz2 Brian Ugh. Sorry. Will fix (along with lots of other unnoticed bugs) with second try. Danny |
From: Danny S. <dan...@cl...> - 2007-08-12 10:13:34
|
> -----Original Message----- > From: min...@li... > [mailto:min...@li...] On Behalf > Of David Gressett > Sent: Sunday, 12 August 2007 1:55 p.m. > To: MinGW Users List > Subject: Re: [Mingw-users] GCC 4.2.1 available > > In any case, here is a fairly minimal demonstration of the > problem. Only > three other packages from GNATCOM are needed to compile this: > GNATCOM.BSTR, GNATCOM.Errors, and GNATCOM.Types > > Procedure Put_IUnknown is not referenced, but if it is removed, the > problem disappears. Thanks That testcase identifies the change stdcall name-change problem, and the fix is simple. FWIW, the bug is also present in GCC trunk. I'm putting through ACATS now. Will include fix in next 4.2.1 update. Danny |
From: Danny S. <dan...@cl...> - 2007-08-12 10:34:58
|
> -----Original Message----- > From: min...@li... > [mailto:min...@li...] On Behalf > Of Charles Wilson > Sent: Sunday, 12 August 2007 8:26 p.m. > To: min...@li... > Subject: Re: [Mingw-users] GCC 4.2.1 available > > > Charles Wilson wrote: > > Danny Smith wrote: > >> * Static and dll libraries of libgcc and libstdc++ are in > the release. > >> By default, linkage is to static libraries. More details later. > > > > I notice that the -build.sh does not specify > > --[enable|disable]-[static|shared]. Does that mean the new > default (for > > libgcc and libstdc++) is to automagically build both DLLs > as part of the > > build procedure, or do you do some voodoo after building > only the static > > versions? > > Downloaded the -src package, and I see that the files t-mingw32* do > indeed build the DLLs/import libs as part of the "normal" > build sequence > -- although it's still "voodoo" in that the actual object > files are only > compiled once and used for both the static libgcc.a and the > libgcc_<variant>_1.dll/libgcc_s.a files. As long as > > (1) there are no data items in libgcc DLL, /OR/ That is the case, after removing __[C|D]TOR_LIST__, which shouldn't be exported anyway (they really belong in crtbegin.o) _chkstk was removed because its an oddball function > (2) you're ok with auto-import/runtime-pseudo-relocs arising from > symbols in the libgcc DLL > > then that's ok. Same logic for libstdc++ DLL. (I see that in > both cases > you deliberate remove some symbols from the respective DLLs, and > manually add them to the appropriate "import" library). In case of libstdc++, -D_DLL turn on class __declspec(dllimport) for all classes with vtables, which represent the majority of data imports > > > I did notice one oddity: obviously t-mingw32 and t-mingw32sjlj are > supposed to be the same (unless you copy *dw2 onto the > former, for a dw2 > build), but: > > $ diff t-mingw32 t-mingw32sjlj > 6c6 > < libgcc_s.a libgcc_sjlj_1.dll: libgcc.a > --- > > libgcc_s.a libgcc_sjlj1.dll: libgcc.a > > One other thing: most platforms put the various unwind stuff into > libgcc_eh.a instead of libgcc.a. We don't. Is that because, > on win32, > there is no such beast as a truly "static" application -- > every prog and > library, at some level, eventually links to MS Win32 libraries (which > are DLLs)? Maybe eventially. I didn't want to use the standard oranization that come with --enabled-shared because for now users expect static linkage of libgcc/libstdc++ by deafult > > > Does this release address the "throwing exceptions across DLL > > boundaries" issue? No. But almost. Still some stupid (on my part) bugs with DW2. sjlj works fine. If so, is that ony when linking to the > DLL runtimes, yes > > or is the problem also handled when linking to the static runtimes? > > -- > Chuck > > -------------------------------------------------------------- > ----------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and > a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > MinGW-users mailing list > Min...@li... > > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users > |
From: Danny S. <dan...@cl...> - 2007-08-12 23:42:25
|
> -----Original Message----- > From: min...@li...=20 > [mailto:min...@li...] On Behalf=20 > Of St=C3=A9phane Larouche > Sent: Friday, 10 August 2007 8:22 a.m. > To: min...@li... > Subject: Re: [Mingw-users] GCC 4.2.1 available >=20 > I compile it using: >=20 > g++-sjlj -c -fopenmp test.cpp > g++-sjlj -o test.exe test.o -lgomp -lpthreadGC2 >=20 > When I execute test.exe, I get something like: >=20 > Executing thread 9 of 10 > Executing thread 9 of 10 > Executing thread 0 of 1 > Executing thread 0 of 1 > Executing thread 0 of 1 > Executing thread 0 of 1 > Executing thread 0 of 1 > Executing thread 0 of 1 > Executing thread 0 of 1 > Executing thread 0 of 1 >=20 > and it crashes at the exit of the parallel block. Can=20 > somebody tell me if I'm > doing anything wrong? >=20 Need to add -mthreads=20 g++-sjlj -mthreads -o test.exe test.o -lgomp -lpthreadGC2 Actually the best way would be to edit libgomp.spec in the = lib/gcc/mingw32/4.2.1-sjlj dir to=20 *link_gomp: -lgomp -lpthreadGC2 and then just=20 g++-sjlj -fopenmp -o test.exe test.o should work Danny > St=C3=A9phane Larouche >=20 >=20 >=20 >=20 > -------------------------------------------------------------- > ----------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and=20 > a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > MinGW-users mailing list > Min...@li... >=20 > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users >=20 |