From: Cesar S. <ces...@gm...> - 2007-07-29 18:40:11
|
Hi, I released a new version of the msys-1.0.dll file that contains a workaround for bug in Vista 64. To install it, go to the MSYS download page on Sourceforge: http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=82724&release_id=158862 and select the MSYS-1.0.11-20070729.tar.bz2 file. Then, unpack the files on your existing MSYS "bin" directory. It should overwrite the files: msys-1.0.dll mount.exe ps.exe As I don't have Vista myself, I would be glad to hear from Vista users if it really works. Regards, Cesar Strauss |
From: David L. <yak...@ya...> - 2007-07-29 21:03:36
|
--- Cesar Strauss <ces...@gm...> escribió: > Hi, > > I released a new version of the msys-1.0.dll file that contains a > workaround for bug in Vista 64. > > To install it, go to the MSYS download page on Sourceforge: > > http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=82724&release_id=158862 > > and select the MSYS-1.0.11-20070729.tar.bz2 file. > > Then, unpack the files on your existing MSYS "bin" directory. > It should overwrite the files: > > msys-1.0.dll > mount.exe > ps.exe > > As I don't have Vista myself, I would be glad to hear from Vista users > if it really works. > > Regards, > Cesar Strauss > I am glad to say that it WORKS perfectly. At least for the purpose I want, that is: console works (no more loop), and make subshell commands also works (no more fork fail). Really thank you very much, now I can continue some old work, and you have saved me the headaches of building it by myself, although I would have learn something. Sisyphus, you are delaying in getting Caesar's built version of the .dll 8). Regards, 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: Cesar S. <ces...@gm...> - 2007-07-30 01:22:44
|
David Lucena wrote: > Cesar Strauss escribió: > >> I released a new version of the msys-1.0.dll file that contains a >> workaround for bug in Vista 64. >> > > I am glad to say that it WORKS perfectly. At least for the purpose I want, that is: console works > (no more loop), and make subshell commands also works (no more fork fail). > Great news! I would like to thank a few people who made this possible: - Oscar Bonilla, for providing the first patch, and valuable feedback. - James Darpinian, for fixing a bug on the original patch. - jdrash, for updating the patch and adding Vista detection. - madwizard, for valuable feedback, and pointing to the MSDN thread. - And, of course, all the people behind Cygwin, for finding the bug and fixing their own code in the first place. Cheers, Cesar |
From: Sisyphus <sis...@op...> - 2007-08-20 13:47:31
|
--- Cesar Strauss <ces...@gm...> escribi=C3=B3: . . >=20 > As I don't have Vista myself, I would be glad to hear from Vista users=20 > if it really works. I am glad to say that it WORKS perfectly. At least for the purpose I want, that is: console works (no more loop), and make subshell commands also works (no more fork fail). Really thank you very much, now I can continue some old work, and you have saved me the headaches of building it by myself, although I would have learn something. Sisyphus, you are delaying in getting Caesar's built version of the .dll 8)= . --------------------------------------- Hi David, Are you actually able to successfully run 'gcc -v' in the MSYS shell (using Cesar's patched version of the msys dll, mount.exe and ps.exe) ? For some reason running gcc on my installation (apparently) fires up gccbug.exe (even if gccbug.exe has been deleted). Is it just me ... or do you find the same ? Cheers, Rob --=20 View this message in context: http://www.nabble.com/Vista-users%3A-please-t= est-the-new-MSYS-snapshot-tf4166440.html#a12236268 Sent from the MinGW - User mailing list archive at Nabble.com. |
From: David L. <yak...@ya...> - 2007-08-20 20:24:50
|
--- Sisyphus <sis...@op...> escribió: > Hi David, > Are you actually able to successfully run 'gcc -v' in the MSYS shell (using > Cesar's patched version of the msys dll, mount.exe and ps.exe) ? > > For some reason running gcc on my installation (apparently) fires up > gccbug.exe (even if gccbug.exe has been deleted). > > Is it just me ... or do you find the same ? > > Cheers, > Rob > Using built-in specs. Target: mingw32 Configured with: ../gcc-4.2.1-2-src/configure --with-gcc --enable-libgomp --host=mingw32 --build=mingw32 --target=mingw3 2 --program-suffix=-sjlj --with-arch=i486 --with-tune=generic --disable-werror --prefix=/mingw --with-local-prefix=/ming w --enable-threads --disable-nls --enable-languages=c,c++,fortran,objc,obj-c++,ada --disable-win32-registry --enable-sjl j-exceptions --enable-libstdcxx-debug --enable-cxx-flags=-fno-function-sections -fno-data-sections --enable-version-spec ific-runtime-libs --disable-bootstrap Thread model: win32 gcc version 4.2.1-sjlj (mingw32-2) Sorry for the mess, it has been a direct copy-paste from an cmd.exe console of a Vista 64. As you can see I am already using the technology preview gcc version 4.2.1 released few days ago. Hope it helped. Good luck. 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: David L. <yak...@ya...> - 2007-08-20 20:34:46
|
--- Sisyphus <sis...@op...> escribió: > > Hi David, > Are you actually able to successfully run 'gcc -v' in the MSYS shell (using > Cesar's patched version of the msys dll, mount.exe and ps.exe) ? > > For some reason running gcc on my installation (apparently) fires up > gccbug.exe (even if gccbug.exe has been deleted). > > Is it just me ... or do you find the same ? > > Cheers, > Rob > > Sorry Rob, you told me from the MSYS shell. $ gcc -v Using built-in specs. Target: mingw32 Configured with: ../gcc-4.2.1-2-src/configure --with-gcc --enable-libgomp --host=mingw32 --build=mingw32 --target=mingw32 --program-suffix=-sjlj --with-arch=i486 --with-tune=generic --disable-werror --prefix=/mingw --with-local-prefix=/mingw --enable-threads --disable-nls --enable-languages=c,c++,fortran,objc,obj-c++,ada --disable-win32-registry --enable-sjlj-exceptions --enable-libstdcxx-debug --enable-cxx-flags=-fno-function-sections -fno-data-sections --enable-version-specific-runtime-libs --disable-bootstrap Thread model: win32 gcc version 4.2.1-sjlj (mingw32-2) Well, anyway the result is the same. ____________________________________________________________________________________ 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: Sisyphus <sis...@op...> - 2007-08-21 05:36:21
|
----- Original Message ----- From: "David Lucena" <yak...@ya...> To: "MinGW Users List" <min...@li...> Sent: Tuesday, August 21, 2007 6:34 AM Subject: Re: [Mingw-users] Vista users: please test the new MSYS snapshot > > --- Sisyphus <sis...@op...> escribió: > >> >> Hi David, >> Are you actually able to successfully run 'gcc -v' in the MSYS shell >> (using >> Cesar's patched version of the msys dll, mount.exe and ps.exe) ? >> >> For some reason running gcc on my installation (apparently) fires up >> gccbug.exe (even if gccbug.exe has been deleted). >> >> Is it just me ... or do you find the same ? . . > > $ gcc -v > Using built-in specs. > Target: mingw32 > Configured with: > ../gcc-4.2.1-2-src/configure --with-gcc --enable-libgomp --host=mingw32 > --build=mingw32 --target=mingw32 --program-suffix=-sjlj --with-arch=i486 --with-tune=generic > --disable-werror --prefix=/mingw --with-local-prefix=/mingw --enable-threads > --disable-nls > --enable-languages=c,c++,fortran,objc,obj-c++,ada --disable-win32-registry > --enable-sjlj-exceptions --enable-libstdcxx-debug --enable-cxx-flags=-fno-function-sections > -fno-data-sections --enable-version-specific-runtime-libs --disable-bootstrap > Thread model: win32 > gcc version 4.2.1-sjlj (mingw32-2) > Well ... I finally found out what my problem was. Somehow, in addition to gcc.exe I have a shell script called gcc in the MinGW/bin. Running 'gcc -v' from the cmd shell invokes gcc.exe, but the same command when run from the msys shell invoked this gcc shell script. I don't know how that shell script got there. Pity I didn't think to run 'gcc.exe -v' in the msys shell (as that would certainly have led to a quick resolution of the problem). Pity also that I didn't look a little closer at what was in the MinGW/bin folder. If 'gcc' had been sitting next to 'gcc.exe' I might have noticed it whilst perusing the contents of the MinGW/bin folder (and the penny might have dropped) - but unfortunately they were separated by 'gcc.5' (whatever that is) and 'gcc.dll'. Anyway, now that I've got rid of 'gcc', all seems well. I've just built gmp-4.2.1, and mpfr-2.3.0-rc2 is in the process of being built as I write. Nice job Cesar. Cheers, Rob |
From: Sisyphus <sis...@op...> - 2007-07-30 00:41:22
|
----- Original Message ----- From: "Cesar Strauss" <ces...@gm...> To: <min...@li...> Sent: Monday, July 30, 2007 4:38 AM Subject: [Mingw-users] Vista users: please test the new MSYS snapshot > Hi, > > I released a new version of the msys-1.0.dll file that contains a > workaround for bug in Vista 64. . . > > As I don't have Vista myself, I would be glad to hear from Vista users > if it really works. > Excellent - I can now run the MSYS shell !! One glitch which, faik, is totally unrelated to Vista is that I can't run gcc. Any attempt to execute gcc results in the following : ----------------------------------- Rob@DESKTOP2 ~ $ gcc -v : Cannot file mail program "/usr/lib/sendmail". : Please fix the MAIL_AGENT entry in the file. Rob@DESKTOP2 ~ ----------------------------------- I've tried searching my MSYS installation for files named "sendmail" and for files that contain "MAIL_AGENT" but can't turn up anything. Nor was Google at all helpful wrt the error. Cheers, Rob |
From: Sisyphus <sis...@op...> - 2007-07-30 03:32:09
|
----- Original Message ----- From: "Sisyphus" <sis...@op...> . . > > ----------------------------------- > Rob@DESKTOP2 ~ > $ gcc -v > : Cannot file mail program "/usr/lib/sendmail". > : Please fix the MAIL_AGENT entry in the file. > > Rob@DESKTOP2 ~ > ----------------------------------- > Looks like that comes from MinGW\bin\gccbug (though editing that file doesn't seem to have any effect.) I got past the above error by creating a /usr/lib/sendmail file, but now I get: -------------------------------------- Rob@DESKTOP2 ~ $ gcc -v /mingw/bin/gcc: mktemp: command not found Rob@DESKTOP2 ~ -------------------------------------- That error also seems related to what can be found in MinGW\bin\gccbug. I'll keep playing but I think I'm going to need some help with this. Cheers, Rob |
From: James S. <jam...@op...> - 2007-07-30 04:43:26
|
On Mon, 2007-07-30 at 13:32 +1000, Sisyphus wrote: > ----- Original Message ----- > From: "Sisyphus" <sis...@op...> > > Rob@DESKTOP2 ~ > > $ gcc -v > > : Cannot file mail program "/usr/lib/sendmail". > > : Please fix the MAIL_AGENT entry in the file. > > > Looks like that comes from MinGW\bin\gccbug (though editing that file > doesn't seem to have any effect.) I would be asking why that file is being executed in the first place. Is it because gcc encountered a bug? If I execute that script from the command line on my box I get the same message, but if I execute gcc -v it yields the expected stuff about specs. > I got past the above error by creating a /usr/lib/sendmail file, but now I > get: > $ gcc -v > /mingw/bin/gcc: mktemp: command not found I think this may be a wild goose chase. Regards, James. |
From: Sisyphus <sis...@op...> - 2007-07-30 06:43:44
|
----- Original Message ----- From: "James Steward" <jam...@op...> . . >> Looks like that comes from MinGW\bin\gccbug (though editing that file >> doesn't seem to have any effect.) > > I would be asking why that file is being executed in the first place. Actually, I find that file is *not* being executed. I can rename 'gccbug' to 'gccbug_hide' and the same error persists. It's as though the behaviour has been built into one of the msys executable/dll files. Either that, or it's coming from somewhere else that I've not yet been able to locate. In the cmd.exe shell: -------------------------------------------------- C:\>C:\_32\MinGW\bin\gcc -v Reading specs from C:/_32/MinGW/bin/../lib/gcc/mingw32/3.4.5/specs Configured with: ../gcc/configure --with-gcc --host=mingw32 --build=mingw32 --ta rget=mingw32 --prefix=/mingw --enable-__cxa_exit --enable-threads --disable-nls --enable-languages=c,c++,f77 --disable-win32-registry --disable-shared --enable- sjlj-exceptions Thread model: win32 gcc version 3.4.5 (mingw32 special) -------------------------------------------------- In the msys shell (having removed the bogus 'sendmail' file and with gccbug renamed): -------------------------------------------------- Rob@DESKTOP2 ~ $ /c/_32/mingw/bin/gcc -v : Cannot file mail program "/usr/lib/sendmail". : Please fix the MAIL_AGENT entry in the file. -------------------------------------------------- . . > > I think this may be a wild goose chase. > I think so too :-) I added cygwin/bin to the path (since it contains a 'mktemp.exe') mainly just to see what would happen next, but then got an error about some file in '/etc/' ... at which point I gave up. Thanks James. Cheers, Rob |
From: Greg C. <chi...@co...> - 2007-07-30 13:09:37
|
On 2007-07-30 06:43Z, Sisyphus wrote: > > I added cygwin/bin to the path (since it contains a 'mktemp.exe') mainly > just to see what would happen next, but then got an error about some file in > '/etc/' ... at which point I gave up. MSYS is a fork of cygwin; the MSYS README says: "Using binaries with different runtimes: You can't use Cygwin binaries at all" |
From: Sisyphus <sis...@op...> - 2007-07-30 14:03:05
|
----- Original Message ----- From: "Greg Chicares" <chi...@co...> To: "MinGW Users List" <min...@li...> Sent: Monday, July 30, 2007 11:09 PM Subject: Re: [Mingw-users] Vista users: please test the new MSYS snapshot > On 2007-07-30 06:43Z, Sisyphus wrote: >> >> I added cygwin/bin to the path (since it contains a 'mktemp.exe') mainly >> just to see what would happen next, but then got an error about some file >> in >> '/etc/' ... at which point I gave up. > > MSYS is a fork of cygwin; the MSYS README says: > "Using binaries with different runtimes: > You can't use Cygwin binaries at all" > Yes - it probably makes better sense to try the GNU Win32 version of mktemp (now that I've discovered that such a beast exists). So I remove /c/cygwin/bin from $PATH and after installing the GNU Win32 version of mktemp (1.5-2) and adding its location to $PATH, I get: ----------------------------------------- Rob@DESKTOP2 ~ $ gcc -v cat: /etc/passwd: No such file or directory Usage: gcc [-PVL] [-t address] [-f filename] [-s severity] [-c address] [--request-id] [--version] ----------------------------------------- So (in addition to the already created /usr/lib/sendmail) I then create /etc/passwd: ----------------------------------------- Rob@DESKTOP2 ~ $ gcc -v Usage: gcc [-PVL] [-t address] [-f filename] [-s severity] [-c address] [--request-id] [--version] ----------------------------------------- I then take the advice of the "Usage" statement: ----------------------------------------- Rob@DESKTOP2 ~ $ gcc --version gccbug (GCC) 3.4.5 (mingw special) Copyright (C) 2002 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. ----------------------------------------- Still looks like a "wild goose chase" to me :-) Cheers, Rob |