MSYS and Vista 64

View: New views
7 Messages — Rating Filter:   Alert me  

MSYS and Vista 64

by Sisyphus :: Rate this Message:

| View Threaded | Show Only this Message

Hi,
Anyone managed to get MSYS working on Vista Business (64 bit)?

On my AMD 64 (running Vista Business), the post install dies as follows:

C:\_32\msys\1.0\postinstall>..\bin\sh.exe pi.sh

This is a post install process that will try to normalize between your MinGW
install if any as well as your previous MSYS installs if any.  I don't have
any traps as aborts will not hurt anything.
Do you wish to continue with the post install? [yn ] y
      0 [main] sh 2424 sync_with_child: child 2784(0x1BC) died before
initialization with status code 0x0
    414 [main] sh 2424 sync_with_child: *** child state waiting for longjmp
pi.sh: fork: Resource temporarily unavailable

C:\_32\msys\1.0\postinstall>pause
Press any key to continue . . .

Running MSYS.bat results in the opening of a large number of windows - until
something crashes and the windows close.

On the same box there was no problem at all with MSYS when running XP (32
bit).

Cheers,
Rob



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
MinGW-users mailing list
MinGW-users@...

You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users

Re: MSYS and Vista 64

by Tuomo Latto-3 :: Rate this Message:

| View Threaded | Show Only this Message

Sisyphus wrote:
> Running MSYS.bat results in the opening of a large number of windows - until
> something crashes and the windows close.

Yeah, that's probably my fault..
msys.bat was patched to run in 32-bit compatibility (SysWOW64) mode on XP x64
using the 32-bit cmd.exe. Does 64-bit Vista have such a mode?
If it does, I wonder if you could post the output of "set" on both 64-bit
and 32-bit cmd.exe (or whatever passes for its command-line).


--
Tuomo

... There is always a way, and it usually doesn't work


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
MinGW-users mailing list
MinGW-users@...

You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users

Re: MSYS and Vista 64

by Sisyphus :: Rate this Message:

| View Threaded | Show Only this Message


----- Original Message -----
From: "Tuomo Latto" <djv@...>
To: "MinGW Users List" <mingw-users@...>
Sent: Tuesday, February 27, 2007 5:45 AM
Subject: Re: [Mingw-users] MSYS and Vista 64


> Sisyphus wrote:
>> Running MSYS.bat results in the opening of a large number of windows -
>> until
>> something crashes and the windows close.
>
> Yeah, that's probably my fault..
> msys.bat was patched to run in 32-bit compatibility (SysWOW64) mode on XP
> x64
> using the 32-bit cmd.exe. Does 64-bit Vista have such a mode?

I don't know. There's a Windows/SysWOW64 folder. Here's the "set" output
from the cmd.exe that's located in that folder:

-------------------------------------------
C:\Windows\SysWOW64>set
ALLUSERSPROFILE=C:\ProgramData
APPDATA=C:\Users\Rob\AppData\Roaming
CommonProgramFiles=C:\Program Files (x86)\Common Files
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
CommonProgramW6432=C:\Program Files\Common Files
COMPUTERNAME=DESKTOP2
ComSpec=C:\Windows\system32\cmd.exe
FP_NO_HOST_CHECK=NO
HOMEDRIVE=C:
HOMEPATH=\Users\Rob
LOCALAPPDATA=C:\Users\Rob\AppData\Local
LOGONSERVER=\\DESKTOP2
NUMBER_OF_PROCESSORS=2
OS=Windows_NT
Path=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_ARCHITEW6432=AMD64
PROCESSOR_IDENTIFIER=AMD64 Family 15 Model 75 Stepping 2, AuthenticAMD
PROCESSOR_LEVEL=15
PROCESSOR_REVISION=4b02
ProgramData=C:\ProgramData
ProgramFiles=C:\Program Files (x86)
ProgramFiles(x86)=C:\Program Files (x86)
ProgramW6432=C:\Program Files
PROMPT=$P$G
PUBLIC=C:\Users\Public
SESSIONNAME=Console
SystemDrive=C:
SystemRoot=C:\Windows
TEMP=C:\Users\Rob\AppData\Local\Temp
TMP=C:\Users\Rob\AppData\Local\Temp
USERDOMAIN=Desktop2
USERNAME=Rob
USERPROFILE=C:\Users\Rob
windir=C:\Windows
-------------------------------------------

And here's the "set" output from the cmd.exe in Windows/System32:

-------------------------------------------
C:\Windows\System32>set
ALLUSERSPROFILE=C:\ProgramData
APPDATA=C:\Users\Rob\AppData\Roaming
CommonProgramFiles=C:\Program Files\Common Files
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
COMPUTERNAME=DESKTOP2
ComSpec=C:\Windows\system32\cmd.exe
FP_NO_HOST_CHECK=NO
HOMEDRIVE=C:
HOMEPATH=\Users\Rob
LOCALAPPDATA=C:\Users\Rob\AppData\Local
LOGONSERVER=\\DESKTOP2
NUMBER_OF_PROCESSORS=2
OS=Windows_NT
Path=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
PROCESSOR_ARCHITECTURE=AMD64
PROCESSOR_IDENTIFIER=AMD64 Family 15 Model 75 Stepping 2, AuthenticAMD
PROCESSOR_LEVEL=15
PROCESSOR_REVISION=4b02
ProgramData=C:\ProgramData
ProgramFiles=C:\Program Files
ProgramFiles(x86)=C:\Program Files (x86)
PROMPT=$P$G
PUBLIC=C:\Users\Public
SESSIONNAME=Console
SystemDrive=C:
SystemRoot=C:\Windows
TEMP=C:\Users\Rob\AppData\Local\Temp
TMP=C:\Users\Rob\AppData\Local\Temp
USERDOMAIN=Desktop2
USERNAME=Rob
USERPROFILE=C:\Users\Rob
windir=C:\Windows
-----------------------------------------

If there's any additional info you need, just let me know.

Cheers,
Rob


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
MinGW-users mailing list
MinGW-users@...

You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users

Re: MSYS and Vista 64

by Tuomo Latto-3 :: Rate this Message:

| View Threaded | Show Only this Message

Sisyphus wrote:
>>msys.bat was patched to run in 32-bit compatibility (SysWOW64) mode on XP
>>x64
>>using the 32-bit cmd.exe. Does 64-bit Vista have such a mode?
>
> I don't know. There's a Windows/SysWOW64 folder. Here's the "set" output

...which means that there is. Note the difference:

> C:\Windows\SysWOW64>set
...
> PROCESSOR_ARCHITECTURE=x86

versus:
> C:\Windows\System32>set
...
> PROCESSOR_ARCHITECTURE=AMD64


Sorry to waste your time with that test. I just realized that
there hasn't been an MSYS release containing the patched batch file.
(The forkbombish behaviour suggested that there was a problem with
 the 64-bit detection in msys.bat, leading to unending recursion.)

You could try a snapshot although I don't know if there are any caveats
(anyone?)
http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=82724&release_id=158862
or you could just get the updated msys.bat (v 1.14)
http://mingw.cvs.sourceforge.net/mingw/msys/dvlpr/bin/msys.bat?view=log

Let us know.


--
Tuomo

... [What technical gizmo from Star Trek, Star Wars, or Stargate
     would you most like to own?]
    Lightsaber! No more can openers! Yes!
                       -- http://www.captainbluehen.com/QoWarchive.html#gizmo


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
MinGW-users mailing list
MinGW-users@...

You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users

Re: MSYS and Vista 64

by Sisyphus :: Rate this Message:

| View Threaded | Show Only this Message


----- Original Message -----
From: "Tuomo Latto" <djv@...>
.
.
>
> You could try a snapshot although I don't know if there are any caveats
> (anyone?)
> http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=82724&release_id=158862
> or you could just get the updated msys.bat (v 1.14)
> http://mingw.cvs.sourceforge.net/mingw/msys/dvlpr/bin/msys.bat?view=log
>

I first tried simply updating msys.bat from the second link given above, but
that didn't help.

So I installed the msysCORE,  coreutils and bash snapshots. But the
behaviour is still essentially the same - a cascade of windows opening up,
followed by their disappearance a few seconds later. Is there any other
snapshot I should try ?

Cheers,
Rob


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
MinGW-users mailing list
MinGW-users@...

You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users

Re: MSYS and Vista 64

by Bugzilla from M.Froehlich@science-computing.de :: Rate this Message:

| View Threaded | Show Only this Message


Hi,

On Tuesday 27 February 2007 02:43, Sisyphus wrote:
> I first tried simply updating msys.bat from the second link given above,
> but that didn't help.
>
> So I installed the msysCORE,  coreutils and bash snapshots. But the
> behaviour is still essentially the same - a cascade of windows opening up,
> followed by their disappearance a few seconds later. Is there any other
> snapshot I should try ?

With win2003 server 64bit it appears to work.
Vista 64bit does not.

   Greetings

           Mathias

--
Dr. Mathias Fröhlich, science + computing ag, Software Solutions
Hagellocher Weg 71-75, D-72070 Tuebingen, Germany
Phone: +49 7071 9457-268, Fax: +49 7071 9457-511

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
MinGW-users mailing list
MinGW-users@...

You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users

Re: MSYS and Vista 64

by Oscar Bonilla :: Rate this Message:

| View Threaded | Show Only this Message

The cygwin folks have figured out that Vista's WOW64 works  
differently than XP's WOW64. This patch should fix it.


#### ChangeSet ####
2007-01-22 22:12:41-08:00, ob@...
   Work around what appears to be a bug in Vista 64-bits. The problem
   is related to how fork passes information to the child. Basically
   the child_info struct * is put in the lpReserved2 field of the
   STARTUPINFO struct that gets passed to CreateProcess(). In all
   versions of Windows, the size of the data to be passed is in the
   cbReserved2 field of the same structure, excep on Vista 64-bits.

   It seems that WOW64 (the 32-bit emmulation layer of 64-bit Vista)
   expects the size of the data passed in lpReserved2 to be the first
   word in that same pointer, only it expects the size in "elements"
   of a BYTE[] and HANDLE[] arrays (the MS C runtime has this  
convention).

   We work around it by filling in the size as (sizeof struct)/5 and
   zero padding the end of the child_info_* structs.

==== rt/src/winsup/cygwin/child_info.h ====
2007-01-22 22:12:39-08:00, ob@... +4 -1
   pad the end of the child_info_* structs and change the zero
   at the beginning for a placeholder for the size.

--- 1.3/rt/src/winsup/cygwin/child_info.h 2001-10-15 15:22:32 -07:00
+++ 1.4/rt/src/winsup/cygwin/child_info.h 2007-01-22 22:12:39 -08:00
@@ -29,7 +29,7 @@ enum
class child_info
{
public:
-  DWORD zero[1]; // must be zeroed
+  DWORD msv_cnt; // size of struct on vista64, zero on others
    DWORD cb; // size of this record
    DWORD type; // type of record
    int cygpid; // cygwin pid of child process
@@ -53,6 +53,7 @@ public:
    jmp_buf jmp; // where child will jump to
    void *stacktop; // location of top of parent stack
    void *stackbottom; // location of bottom of parent stack
+  char filler[4];
};
class fhandler_base;
@@ -67,6 +68,7 @@ public:
    int envc;
    char **envp;
    HANDLE myself_pinfo;
+  char filler[4];
};
class child_info_spawn: public child_info
@@ -74,6 +76,7 @@ class child_info_spawn: public child_inf
public:
    cygheap_exec_info *moreinfo;
    HANDLE hexec_proc;
+  char filler[4];
    child_info_spawn (): moreinfo (NULL) {}
    ~child_info_spawn ()

==== rt/src/winsup/cygwin/dcrt0.cc ====
2007-01-22 22:12:40-08:00, ob@... +1 -3
   the child_info_* structs no longer have a zero at the beginning.

--- 1.10/rt/src/winsup/cygwin/dcrt0.cc 2004-03-15 03:51:36 -08:00
+++ 1.11/rt/src/winsup/cygwin/dcrt0.cc 2007-01-22 22:12:40 -08:00
@@ -903,7 +903,6 @@ _dll_crt0 ()
    if (GetEnvironmentVariable ("CYGWIN_TESTING", envbuf, sizeof  
(envbuf) - 1))
      _cygwin_testing = 1;
-  char zeros[sizeof (fork_info->zero)] = {0};
#ifdef DEBUGGING
    strace.microseconds ();
#endif
@@ -924,8 +923,7 @@ _dll_crt0 ()
                   &hMainThread, 0, FALSE, DUPLICATE_SAME_ACCESS);
    GetStartupInfo (&si);
-  if (si.cbReserved2 >= EXEC_MAGIC_SIZE &&
-      memcmp (fork_info->zero, zeros, sizeof (zeros)) == 0)
+  if (si.cbReserved2 >= EXEC_MAGIC_SIZE)
      {
        switch (fork_info->type)
        {

==== rt/src/winsup/cygwin/fork.cc ====
2007-01-22 22:12:40-08:00, ob@... +2 -0
   fill in the size of child_info_fork

--- 1.4/rt/src/winsup/cygwin/fork.cc 2002-10-31 06:32:21 -08:00
+++ 1.5/rt/src/winsup/cygwin/fork.cc 2007-01-22 22:12:40 -08:00
@@ -430,6 +430,8 @@ fork_parent (HANDLE& hParent, dll *&firs
    init_child_info (PROC_FORK1, &ch, 1, subproc_ready);
+  ch.msv_cnt = (sizeof ch)/5;
+
    ch.forker_finished = forker_finished;
    stack_base (ch);

==== rt/src/winsup/cygwin/sigproc.cc ====
2007-01-22 22:12:40-08:00, ob@... +1 -0
   fill in the size of child_info

--- 1.5/rt/src/winsup/cygwin/sigproc.cc 2003-02-12 07:50:27 -08:00
+++ 1.6/rt/src/winsup/cygwin/sigproc.cc 2007-01-22 22:12:40 -08:00
@@ -849,6 +849,7 @@ init_child_info (DWORD chtype, child_inf
{
    TRACE_IN;
    memset (ch, 0, sizeof *ch);
+  ch->msv_cnt = (sizeof *ch)/5;
    ch->cb = sizeof *ch;
    ch->type = chtype;
    ch->cygpid = pid;

==== rt/src/winsup/cygwin/spawn.cc ====
2007-01-22 22:12:40-08:00, ob@... +1 -0
   fill in the size of child_info_spawn

--- 1.22/rt/src/winsup/cygwin/spawn.cc 2003-10-11 07:35:26 -07:00
+++ 1.23/rt/src/winsup/cygwin/spawn.cc 2007-01-22 22:12:40 -08:00
@@ -346,6 +346,7 @@ spawn_guts (HANDLE hToken, const char *
    STARTUPINFO si = {0, NULL, NULL, NULL, 0, 0, 0, 0, 0, 0, 0, 0, 0,  
0, NULL, NULL, NULL, NULL};
    child_info_spawn ciresrv;
+  ciresrv.msv_cnt = (sizeof ciresrv)/5;
    si.lpReserved2 = (LPBYTE) &ciresrv;
    si.cbReserved2 = sizeof (ciresrv);

Let me know if it works...

Regards,

-Oscar

On Feb 27, 2007, at 2:47 AM, Mathias Froehlich wrote:

>
> Hi,
>
> On Tuesday 27 February 2007 02:43, Sisyphus wrote:
>> I first tried simply updating msys.bat from the second link given  
>> above,
>> but that didn't help.
>>
>> So I installed the msysCORE,  coreutils and bash snapshots. But the
>> behaviour is still essentially the same - a cascade of windows  
>> opening up,
>> followed by their disappearance a few seconds later. Is there any  
>> other
>> snapshot I should try ?
>
> With win2003 server 64bit it appears to work.
> Vista 64bit does not.
>
>    Greetings
>
>            Mathias
>
> --
> Dr. Mathias Fröhlich, science + computing ag, Software Solutions
> Hagellocher Weg 71-75, D-72070 Tuebingen, Germany
> Phone: +49 7071 9457-268, Fax: +49 7071 9457-511
>
> ----------------------------------------------------------------------
> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to  
> share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?
> page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> MinGW-users mailing list
> MinGW-users@...
>
> You may change your MinGW Account Options or unsubscribe at:
> https://lists.sourceforge.net/lists/listinfo/mingw-users

--
pgp fingerprint: BC64 2E7A CAEF 39E1 9544  80CA F7D5 784D FB46 16C1


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
MinGW-users mailing list
MinGW-users@...

You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users