Mail Archives: cygwin/1998/02/04/22:01:42
In article <052201bd316e$33481ed0$2a0110ac AT sam DOT ethernet>,
Samuel James Liddicott <sam AT campbellsci DOT co DOT uk> wrote:
>-----Original Message-----
>From: David Gasul <davidg AT telegate DOT co DOT il>
>To: gnu-win32 AT cygnus DOT com <gnu-win32 AT cygnus DOT com>
>Date: 04 February 1998 13:02
>Subject: Problem with symbolic links in b18
>
>
> Hi,
>
> Here's a problem I encountered with symbolic links:
>
> 1. Assume you have a DOS executable in directory c:\xxx called yyy.exe.
> 2. Assume bash is run from directory c:\zzz.
> 3. Enter bash
> 4. Do "ln -s c:\xxx\yyy.exe yyy.exe".
> 5. Verify that there's a file "yyy.exe" in c:\zzz.
> 6. Run yyy.exe from bash - everything works fine.
> 7. Now exit bash.
> 8. Run yyy.exe. You get a window telling you that the program has
>performed an illegal operation.
> Opening the details button says that the program tried to execute an
>illegal instruction
> at 1F00:8AC3.
>
>
> This is because your are now running yyy.exe from c:\zzz, and this
>yyy.exe is not a real exe file, but one of your cygwin shortcuts that
>windows doesn't like.
Ah. I smell a discussion of why we can/can't/ought-to use Win95, WinN% 4.0
shortcuts in place of cygwin symbolic links coming...
After all it has been several weeks.
--
http://www.bbc.com/ cgf AT bbc DOT com "Strange how unreal
VMS=>UNIX Solutions Boston Business Computing the real can be."
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".
- Raw text -