From: Keith M. <kei...@us...> - 2010-08-31 18:59:12
|
I'm fairly certain this used to work on the old Win2K box, but since my company's IT department decided we should all upgrade to vista, I'm seeing this for all attempts to run flex, with any valid input, e.g.: $ flex /e/tmp/pkginfo.l flex: fatal internal error, exec failed The result is the same, with both available MSYS builds of flex-2.35. Everything else in the MSYS tree is bang up to date, per the msys-base manifests we published for mingw-get, just a few weeks ago, and this is the first mysterious failure I've experienced. Anyone else able to reproduce this? Any ideas how I might set about tracking down the problem? -- Regards, Keith. |
From: Hin-Tak L. <hin...@ya...> - 2010-09-01 05:00:45
|
Keith Marshall wrote: > I'm fairly certain this used to work on the old Win2K box, but since > my company's IT department decided we should all upgrade to vista, I'm > seeing this for all attempts to run flex, with any valid input, e.g.: > > $ flex /e/tmp/pkginfo.l > flex: fatal internal error, exec failed > > The result is the same, with both available MSYS builds of flex-2.35. > Everything else in the MSYS tree is bang up to date, per the msys-base > manifests we published for mingw-get, just a few weeks ago, and this is > the first mysterious failure I've experienced. > > Anyone else able to reproduce this? Any ideas how I might set about > tracking down the problem? Possibly UAC related? Vista and Windows 7 have some strange ideas about permissions regarding writing to current directory (desktop) as well as creation of temporary files (which often happens to be C:/windows/temp or thereabouts). I'd look for where temp files are written first. |
From: NightStrike <nig...@gm...> - 2010-09-01 04:17:48
|
On Tue, Aug 31, 2010 at 9:00 AM, Keith Marshall <kei...@us...> wrote: > I'm fairly certain this used to work on the old Win2K box, but since > my company's IT department decided we should all upgrade to vista, I'm > seeing this for all attempts to run flex, with any valid input, e.g.: > > $ flex /e/tmp/pkginfo.l > flex: fatal internal error, exec failed > > The result is the same, with both available MSYS builds of flex-2.35. > Everything else in the MSYS tree is bang up to date, per the msys-base > manifests we published for mingw-get, just a few weeks ago, and this is > the first mysterious failure I've experienced. > > Anyone else able to reproduce this? Any ideas how I might set about > tracking down the problem? What's the value of your M4 env var? flex tries to exec m4. I think. |
From: Keith M. <kei...@us...> - 2010-09-01 09:44:50
|
On 01/09/2010, NightStrike <nig...@gm...> wrote: > On Tue, Aug 31, 2010 at 9:00 AM, Keith Marshall > <kei...@us...> wrote: >> I'm fairly certain this used to work on the old Win2K box, but since >> my company's IT department decided we should all upgrade to vista, I'm >> seeing this for all attempts to run flex, with any valid input, e.g.: >> >> $ flex /e/tmp/pkginfo.l >> flex: fatal internal error, exec failed > > What's the value of your M4 env var? flex tries to exec m4. I think. Thanks. You think a-right; that's pointed me in the right direction. I don't have an M4 env var, and never needed one. I still don't; I simply didn't have m4 installed. Installing it was all that was required; shame the error message wasn't more explicit about *what* it failed to exec! I'll add the missing dependency to my copy of the mingw-get manifest for msys-flex-bin, (already differs from CVS), commit and publish it tonight. -- Regards, Keith. |