On 04 October 2007 15:26, Lynn Winebarger wrote:
>>> you see an error message along those lines, yes? Hm. Does it still
>>> happen if you compile the most basic sort of "hello world" program?
>>
>>
>> It might also be informative to run "cygcheck <path-to-exe>" on your
>> compiled executable; that'll display the dependent DLLs for you. A bit of
>> googling suggests that 193 can be caused by a corrupt/bogus executable, but
>> equally by a good executable thatt depends on a DLL which is faulty.
>>
>
> Thanks, Dave. I did compile a hello-world.c program, and it ran, but
> I had also compiled PLT scheme v360 before (needed to bootstrap
> Larceny) and had run it without problem as well (I had thought this
> might be a permission issue, because what bash actually reports is
> "Access denied" - the underlying error took further investigation)
Actually, I was trying to ask if you'd compiled a basic "helloworld" with
your new larceny compiler, or indeed if this example of yours is already a
very simple test program; i.e. is it only complex larceny executables that
don't work, or even the very simplest ones.
> $ cygcheck ./larcenybin.exe
> .\larcenybin.exe
> C:\cygwin\bin\cygwin1.dll
> C:\WINDOWS\system32\ADVAPI32.DLL
> C:\WINDOWS\system32\ntdll.dll
> C:\WINDOWS\system32\KERNEL32.dll
> C:\WINDOWS\system32\RPCRT4.dll
Unfortunately that all looks completely correct, no clues there.
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
