Jump to content

damaged symlink, windows and linux

  • Please log in to reply
No replies to this topic

#1 jdigital



  • Members
  • Pip
  • 1 posts

Posted 20 December 2019 - 07:56 PM

Looking for an explanation of how I got into this state...

I have a symlink in my depot.  On Linux, it is correct:
libreadline.so -> libreadline.so.6.2

but on Windows, it points to a bogus location (directory doesn't exist, and it's pointing to another symlink):
libreadline.so -> ..\..\lib64\libreadline.so.6

Now here's the really odd part.  If I do a p4 edit on Linux, the symlink changes to the invalid one:
libreadline.so -> ../../lib64/libreadline.so.6

I know how to fix this, but I'm trying to understand just how I got into this state.  I've heard that submitting a "linux symlink" from a windows machine can cause problems.  Is this true?  If so, could it have caused this problem, and why?  Any insights would be appreciated.  I'd like to avoid this problem in the future!


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users