From: Danny S. <dan...@cl...> - 2008-02-10 22:42:44
|
> Hi, > > did someone ever build gcc-4.3 for MinGW? The new snapshots don't > contain a working configure anymore (at least the one from 20080208). I haven't noticed any difficulties with SVN I've just built 20080210 and am running testsuite now. Danny |
From: Doug S. <dsc...@ro...> - 2008-02-11 06:09:44
|
>> Hi, >> >> did someone ever build gcc-4.3 for MinGW? The new snapshots don't >> contain a working configure anymore (at least the one from 20080208). > >I haven't noticed any difficulties with SVN >I've just built 20080210 and am running testsuite now. > > Danny Hi Danny, Would you be able to share your build script for 4.3 (if you haven't already). I'd like to do some testing of my own. Doug |
From: Danny S. <dan...@cl...> - 2008-02-11 08:34:42
Attachments:
config1.sh
|
> > >> Hi, > >> > >> did someone ever build gcc-4.3 for MinGW? The new snapshots don't > >> contain a working configure anymore (at least the one > from 20080208). > > > >I haven't noticed any difficulties with SVN > >I've just built 20080210 and am running testsuite now. > > > > Danny > > Hi Danny, > > Would you be able to share your build script for 4.3 (if you haven't > already). I'd like to do some testing of my own. > This is the minimalist one that I've been using for testing. Danny |
From: Stephen L. <sld...@so...> - 2008-02-11 12:27:56
|
Danny Smith <dan...@cl...> wrote: > > This is the minimalist one that I've been using for testing. > ../src/configure --enable-libgomp ... Can you tell me what version of pthreads you used, and where you put them so it would be found by gcc during the build? I suppose you are using <http://sourceware.org/pthreads-win32/>? I tried the 4.2.1-2 source on the project page, but building libgomp fails because it can't find libpthread and its headers. I got it to build by modifying the build scripts but I wonder if you got it to build cleanly. Which pthreads should be used for -dw2, libpthreadGC2 or libpthreadGCE2? Regards Stephen -- Stephen Lee <sld...@so...> |
From: Doug S. <dsc...@ro...> - 2008-02-11 15:49:50
|
Danny Smith wrote: >> >> Hi, >> >> >> >> did someone ever build gcc-4.3 for MinGW? The new snapshots don't >> >> contain a working configure anymore (at least the one >> from 20080208). >> > >> >I haven't noticed any difficulties with SVN >> >I've just built 20080210 and am running testsuite now. >> > >> > Danny >> >> Hi Danny, >> >> Would you be able to share your build script for 4.3 (if you haven't >> already). I'd like to do some testing of my own. >> >> > > This is the minimalist one that I've been using for testing. > > Danny > Thanks Danny, I'll give that a try. Also, I was wondering what you used for a build environment, cygwin or msys? I've had issues with both and would like to replicate yours as much as possible. Doug. |
From: Danny S. <dan...@cl...> - 2008-02-11 18:06:40
|
Doug Schaefer > > > > Thanks Danny, I'll give that a try. Also, I was wondering > what you used > for a build environment, cygwin or msys? I've had issues with > both and > would like to replicate yours as much as possible. I use cygwin, with "identity" mount, so that in development environment posix pathnames can be understood by DOS. eg mount c:/develop /develop and do the build in /develop/gcc/gcc-4.3.0/build You may run into problems with libgomp configure. I had to use a newish version of autoconf to rebuild configure there because of bugs with line endings. Tell me if that is a problem and I'll send the patch for c.m4 or configure Danny > > Doug. > |
From: Doug S. <dsc...@ro...> - 2008-02-12 03:03:18
|
Danny Smith wrote: > Doug Schaefer > >>> >>> >> Thanks Danny, I'll give that a try. Also, I was wondering >> what you used >> for a build environment, cygwin or msys? I've had issues with >> both and >> would like to replicate yours as much as possible. >> > > I use cygwin, with "identity" mount, so that in development environment > posix pathnames can be understood by DOS. > eg > mount c:/develop /develop > and do the build in /develop/gcc/gcc-4.3.0/build > > You may run into problems with libgomp configure. I had to use a newish > version of autoconf to rebuild configure there because of bugs with line > endings. Tell me if that is a problem and I'll send the patch for c.m4 > or configure > > Danny > I've got a start on it. Life was better when I made my develop directory a binary mount instead of a text mount. I was wondering which compiler you use for stage1. It appears to be using the cygwin compiler (i.e, I don't see -mno-cygwin anywhere). Is this correct? Or should I have /mingw/bin first in my path and build gmp and mpfr with mingw 3.4? Doug. |
From: S.Coffin <sc...@je...> - 2008-02-14 01:50:37
|
Hi! I have been using mingw+msys for a few months on Vista x86 with good results, including windows apps and device driver. Now I have some problems with missing functions trying to port to Vista x64. User apps are fine, but I have searched around the libraries without finding these driver functions. Perhaps I am missing something simple? Or maybe these functions have changed name in Vista x64? Or maybe the mingw x64 does not include them? Any comments appreciated.... Thanks! =S.Coffin sc...@je... =================================================================== $ make gcc -Wall -Werror -I/mingw/include -c -o gui.o gui.c gcc -Wall -Werror -I/mingw/include -c -o shutdown.o shutdown.c gcc -Wall -Werror -I/mingw/include -c -o idle.o idle.c gcc -Wall -Werror -I/mingw/include -c -o argv.o argv.c gcc -Wall -Werror -I/mingw/include -c -o loaddrv.o loaddrv.c gcc gui.o shutdown.o idle.o argv.o loaddrv.o -o SCsm.exe -mwindows -lPowrProf -lIPHLPAPI gcc -Wall -Werror -I/mingw/include -c -o drv.o drv.c gcc -Wall -Werror -I/mingw/include -c -o reg.o reg.c gcc -shared -Wl,--entry,_DriverEntry@8 drv.o reg.o -lntdll -nostartfiles -nostdlib -o SCsm.sys drv.o:drv.c:(.text+0x71): undefined reference to `__imp__IoCreateDevice' drv.o:drv.c:(.text+0xb1): undefined reference to `__imp__IoCreateSymbolicLink' drv.o:drv.c:(.text+0xe7): undefined reference to `__imp__IoDeleteDevice' drv.o:drv.c:(.text+0x1fe): undefined reference to `__imp__IofCompleteRequest' drv.o:drv.c:(.text+0x27d): undefined reference to `__imp__IofCompleteRequest' drv.o:drv.c:(.text+0x59e): undefined reference to `__imp__IofCompleteRequest' drv.o:drv.c:(.text+0x5f9): undefined reference to `__imp__IoDeleteSymbolicLink' drv.o:drv.c:(.text+0x60a): undefined reference to `__imp__IoDeleteDevice' drv.o:drv.c:(.text+0x83c): undefined reference to `__imp__IofCompleteRequest' $ =================================================================== |
From: Jonathan W. <jf...@tp...> - 2008-02-14 02:02:49
|
> gcc -shared -Wl,--entry,_DriverEntry@8 drv.o reg.o -lntdll -nostartfiles > -nostdlib -o SCsm.sys ntdll is not the correct library to link to for device drivers, the correct library to link to for a device driver is ntoskrnl |
From: S.Coffin <sc...@je...> - 2008-02-15 00:29:03
|
>> > gcc -shared -Wl,--entry,_DriverEntry@8 drv.o reg.o -lntdll >> > -nostartfiles -nostdlib -o SCsm.sys >> ntdll is not the correct library to link to for device drivers, >> the correct library to link to for a device driver is ntoskrnl Well I used ntoskrnl in Vista x86 to compile the driver but I can't find this in x64: $ make gcc -shared -Wl,--entry,_DriverEntry@8 drv.o reg.o -lntoskrnl -nostartfiles -nostdlib -o SCsm.sys ld: cannot find -lntoskrnl make: *** [SCsm.sys] Error 1 Perhaps I am missing something? Or if this library is not available for x64, is there some reason it is not available? Is anyone working on this? Any comments appreciated.... Thanks! =S.Coffin sc...@je... |
From: Brian D. <br...@de...> - 2008-02-15 01:34:36
|
"S.Coffin" wrote: > Well I used ntoskrnl in Vista x86 to compile the driver but I can't > find this in x64: If you're using the 64 bit port of MinGW then that is (quite unfortunately) a separate project with its own mailing list, you might want to ask there. Brian |
From: 오승훈 <os...@et...> - 2008-02-15 06:30:20
|
Hello I would like to use shared memory of IPC (interprocess communication) on the MINGW (+MSYS) envrionrment. While gcc-compiling some sources, I have got such a error message: shm1.c:7:21: sys/ipc.h: No such file or directory shm1.c:8:21: sys/shm.h: No such file or directory Does anyone know where I can find sys/ipc.h and sys/shm.h and in detail how I can use IPC library within MINGW? Thanks in advance Best regards, Seunghun ----- Original Message ----- From: "Brian Dessent" <br...@de...> To: "MinGW Users List" <min...@li...> Sent: Friday, February 15, 2008 10:34 AM Subject: Re: [Mingw-users] mingw vs. Vista x64 driver ?? > > "S.Coffin" wrote: > >> Well I used ntoskrnl in Vista x86 to compile the driver but I can't >> find this in x64: > > If you're using the 64 bit port of MinGW then that is (quite > unfortunately) a separate project with its own mailing list, you might > want to ask there. > > Brian > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > 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: Brian D. <br...@de...> - 2008-02-15 06:52:36
|
> ??? wrote: > Hello Please don't commandeer a thread for an unrelated question. Start a new thread. > shm1.c:7:21: sys/ipc.h: No such file or directory > shm1.c:8:21: sys/shm.h: No such file or directory > > > Does anyone know where I can find sys/ipc.h and sys/shm.h and in > detail how I can > > use IPC library within MINGW? You're asking about a POSIX API that doesn't exist on native Win32. The purpose of MinGW is to target native Windows, so if you are using MinGW you must use the Win32 APIs to do shared memory -- you must port your application. If it isn't your intention to do a Windows port (i.e. you just want to build the software unmodified) then MinGW isn't the right tool. The Win32 APIs are all documented on MSDN. You might start here: <http://msdn2.microsoft.com/en-us/library/aa366878(VS.85).aspx>. Brian |
From: arthur <mai...@gm...> - 2008-02-15 14:40:58
|
Will this help? http://www.research.att.com/sw/tools/uwin/ ----- Original Message ----- From: "Brian Dessent" <br...@de...> To: "MinGW Users List" <min...@li...> Sent: Friday, February 15, 2008 1:52 AM Subject: Re: [Mingw-users] IPC programming in MINGW? > > ??? wrote: > > > Hello > > Please don't commandeer a thread for an unrelated question. Start a new > thread. > > > shm1.c:7:21: sys/ipc.h: No such file or directory > > shm1.c:8:21: sys/shm.h: No such file or directory > > > > > > Does anyone know where I can find sys/ipc.h and sys/shm.h and in > > detail how I can > > > > use IPC library within MINGW? > > You're asking about a POSIX API that doesn't exist on native Win32. The > purpose of MinGW is to target native Windows, so if you are using MinGW > you must use the Win32 APIs to do shared memory -- you must port your > application. If it isn't your intention to do a Windows port (i.e. you > just want to build the software unmodified) then MinGW isn't the right > tool. > > The Win32 APIs are all documented on MSDN. You might start here: > <http://msdn2.microsoft.com/en-us/library/aa366878(VS.85).aspx>. > > Brian > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > 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: Dave K. <dav...@ar...> - 2008-02-15 14:53:56
|
On 15 February 2008 14:41, arthur wrote: > Will this help? > > http://www.research.att.com/sw/tools/uwin/ Not as much as this one, most likely: http://cygwin.com/ It's got a much more active user base. cheers, DaveK -- Can't think of a witty .sigline today.... |
From: Keith M. <kei...@us...> - 2008-02-16 11:33:47
|
On Friday 15 February 2008 06:52, Brian Dessent wrote: > Please don't commandeer a thread for an unrelated question. Start a > new thread. Thanks for this admonishment, Brian. In fact this was the *second* hijack of Doug Schaefer's original thread on `Building GCC-4.3.0'. However, having so admonished the OP, please *do* *not* go ahead and answer his question -- that only serves to legitimise his antisocial behaviour. The only effective deterrent to such behaviour is to deny the offender the audience he seeks; let him post his question again, in an appropriate context, before answering. Regards, Keith. |
From: Danny S. <dan...@cl...> - 2008-02-11 18:06:41
|
> -----Original Message----- > From: min...@li... > [mailto:min...@li...] On Behalf > Of Stephen Lee > Sent: Tuesday, 12 February 2008 1:28 a.m. > To: min...@li... > Subject: Re: [Mingw-users] building gcc-4.3.0 > > > Danny Smith <dan...@cl...> wrote: > > > > This is the minimalist one that I've been using for testing. > > > ../src/configure --enable-libgomp ... > > Can you tell me what version of pthreads you used, and where you put > them so it would be found by gcc during the build? > > I suppose you are using <http://sourceware.org/pthreads-win32/>? Yes > I tried the 4.2.1-2 source on the project page, but > building libgomp fails because it can't find libpthread and its > headers. I got it to build by modifying the build scripts > but I wonder > if you got it to build cleanly. > I renamed libpthread32GCE2.a to libpthread.a. It is installed in mingw/bin/ The headers are installed in /mingw/include. (looking closer I see they are also in /mingw/mingw32/lib|include. I don't rember why.) The dll is in mingw/bin > Which pthreads should be used for -dw2, libpthreadGC2 or > libpthreadGCE2? > libpthreadGCE2 Danny |
From: Danny S. <dan...@cl...> - 2008-02-12 06:50:35
|
> -----Original Message----- > From: min...@li... > [mailto:min...@li...] On Behalf > Of Doug Schaefer > Sent: Tuesday, 12 February 2008 4:03 p.m. > To: MinGW Users List > Subject: Re: [Mingw-users] building gcc-4.3.0 > > > Danny Smith wrote: > > Doug Schaefer > > > >>> > >>> > >> Thanks Danny, I'll give that a try. Also, I was wondering > >> what you used > >> for a build environment, cygwin or msys? I've had issues with > >> both and > >> would like to replicate yours as much as possible. > >> > > > > I use cygwin, with "identity" mount, so that in development > environment > > posix pathnames can be understood by DOS. > > eg > > mount c:/develop /develop > > and do the build in /develop/gcc/gcc-4.3.0/build > > > > You may run into problems with libgomp configure. I had to > use a newish > > version of autoconf to rebuild configure there because of > bugs with line > > endings. Tell me if that is a problem and I'll send the > patch for c.m4 > > or configure > > > > Danny > > > I've got a start on it. Life was better when I made my > develop directory > a binary mount instead of a text mount. I was wondering which > compiler > you use for stage1. It appears to be using the cygwin > compiler No it uses MSVCRT-dependent mingw compiler (i.e, I > don't see -mno-cygwin anywhere). Is this correct? Or should I have > /mingw/bin first in my path and build gmp and mpfr with mingw 3.4? Yes. My PATH is c:\users\danny\bin;c:/mingw/bin;c:\cygwin\bin;%SystemRoot%\system32;%Sys temRoot%;%SystemRoot%\system32\WBEM;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\ATI Technologies\ATI.ACE\;C:\Program Files\QuickTime\QTSyste --- -mno-cygwin should not be needed. bi dansmister > > Doug. > > -------------------------------------------------------------- > ----------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > 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: Doug S. <dsc...@ro...> - 2008-02-14 02:12:33
|
Danny Smith wrote: >> Danny Smith wrote: >> >>> Doug Schaefer >>> >>>> Thanks Danny, I'll give that a try. Also, I was wondering >>>> what you used >>>> for a build environment, cygwin or msys? I've had issues with >>>> both and >>>> would like to replicate yours as much as possible. >>>> >>>> >>> I use cygwin, with "identity" mount, so that in development >>> >> environment >> >>> posix pathnames can be understood by DOS. >>> eg >>> mount c:/develop /develop >>> and do the build in /develop/gcc/gcc-4.3.0/build >>> >>> You may run into problems with libgomp configure. I had to >>> >> use a newish >> >>> version of autoconf to rebuild configure there because of >>> >> bugs with line >> >>> endings. Tell me if that is a problem and I'll send the >>> >> patch for c.m4 >> >>> or configure >>> >>> Danny >>> >>> >> I've got a start on it. Life was better when I made my >> develop directory >> a binary mount instead of a text mount. I was wondering which >> compiler >> you use for stage1. It appears to be using the cygwin >> compiler >> > > No it uses MSVCRT-dependent mingw compiler > > (i.e, I > >> don't see -mno-cygwin anywhere). Is this correct? Or should I have >> /mingw/bin first in my path and build gmp and mpfr with mingw 3.4? >> > Yes. > My PATH is > c:\users\danny\bin;c:/mingw/bin;c:\cygwin\bin;%SystemRoot%\system32;%Sys > temRoot%;%SystemRoot%\system32\WBEM;C:\Program Files\ATI > Technologies\ATI Control Panel;C:\Program Files\ATI > Technologies\ATI.ACE\;C:\Program Files\QuickTime\QTSyste --- > > -mno-cygwin should not be needed. > > > bi > dansmister > I have the build finished. I notice that I didn't get a shared libgcc or libstdc++. Is this still a limitation of gcc 4.3? Stephen's instructions for 4.2.1 (i.e. make install-shared stuff) didn't work here. Doug. |
From: Rolf E. <rol...@gm...> - 2008-02-12 06:11:28
|
Danny Smith schrieb: >> Hi, >> >> did someone ever build gcc-4.3 for MinGW? The new snapshots don't >> contain a working configure anymore (at least the one from 20080208). > > I haven't noticed any difficulties with SVN > I've just built 20080210 and am running testsuite now. Sorry for the noise. The problem was on my side, or let's say on tar's side. I use my own build script that also extracts the sources from a .tar.bz2 file using 'tar xfj'. The tar command dumped core (whatever tnat means on Windows) before actually extracting the top level configure but after configure.ac. I therefore thought that the snapshot tarballs don't contain configure anymore. I now use a pipe with separate commands for bunzip2 and tar. Rolf |
From: Bob R. <bob...@co...> - 2008-02-12 11:08:54
|
On Tue, Feb 12, 2008 at 07:11:25AM +0100, Rolf Ebert wrote: > Danny Smith schrieb: > >> Hi, > >> > >> did someone ever build gcc-4.3 for MinGW? The new snapshots don't > >> contain a working configure anymore (at least the one from 20080208). > > > > I haven't noticed any difficulties with SVN > > I've just built 20080210 and am running testsuite now. > > Sorry for the noise. The problem was on my side, or let's say on tar's > side. I use my own build script that also extracts the sources from a > .tar.bz2 file using 'tar xfj'. The tar command dumped core (whatever > tnat means on Windows) before actually extracting the top level > configure but after configure.ac. I therefore thought that the snapshot > tarballs don't contain configure anymore. I now use a pipe with > separate commands for bunzip2 and tar. Yeah, my tar dumps core too. I have to use Cygwin tar. Bob Rossi |
From: Earnie B. <ea...@us...> - 2008-02-12 12:37:11
|
Quoting Rolf Ebert <rol...@gm...>: > Danny Smith schrieb: >>> Hi, >>> >>> did someone ever build gcc-4.3 for MinGW? The new snapshots don't >>> contain a working configure anymore (at least the one from 20080208). >> >> I haven't noticed any difficulties with SVN >> I've just built 20080210 and am running testsuite now. > > Sorry for the noise. The problem was on my side, or let's say on tar's > side. I use my own build script that also extracts the sources from a > .tar.bz2 file using 'tar xfj'. The tar command dumped core (whatever > tnat means on Windows) before actually extracting the top level > configure but after configure.ac. I therefore thought that the snapshot > tarballs don't contain configure anymore. I now use a pipe with > separate commands for bunzip2 and tar. > I assume you mean the MSYS tar command. Would you please open a bug report [1] for that? [1] http://mingw.org/MinGWiki/index.php/ReportBugs Earnie |
From: Rolf E. <rol...@gm...> - 2008-02-12 19:02:12
|
Earnie Boyd schrieb: > I assume you mean the MSYS tar command. Would you please open a bug > report [1] for that? Done https://sourceforge.net/tracker/index.php?func=detail&aid=1892151&group_id=2435&atid=102435 Rolf |