pastebin - collaborative debugging tool
rovema.kpaste.net RSS


Cygwin 3.5.0-0.388.g1a646ad7970a.x86_64 failure, /home/rmainz/path/... vs. H:/path/...
Posted by Anonymous on Mon 14th Aug 2023 18:21
raw | new post

  1. #
  2. # Cygwin 3.5.0-0.388.g1a646ad7970a.x86_64 failure, /home/rmainz/path/... vs. H:/path/...
  3. #
  4.  
  5. $ uname -a
  6. CYGWIN_NT-10.0-19045 WINGRENDEL01 3.5.0-0.388.g1a646ad7970a.x86_64 2023-08-11 14:14 UTC x86_64 Cygwin
  7.  
  8. $ cat /etc/fstab
  9. # /etc/fstab
  10. #
  11. #    This file is read once by the first process in a Cygwin process tree.
  12. #    To pick up changes, restart all Cygwin processes.  For a description
  13. #    see https://cygwin.com/cygwin-ug-net/using.html#mount-table
  14.  
  15. # This is default anyway:
  16. none /cygdrive cygdrive binary,posix=0,user 0 0
  17. H:      /home/rmainz    none    binary,posix=0,user     0       0
  18.  
  19.  
  20. $ mount -a
  21.  
  22. $ /home/rmainz/tmp/winnfstest/hummingbirdnfstest1/try10_rde_new_rds/Dependencies/win/qt/qt_5_15_2/Tools/mingw810_64/bin/c++ /home/rmainz/tmp/winnfstest/hummingbirdnfstest1/try10_rde_new_rds/RDE-Development/build_windows5/tmp/x.cpp
  23. c++.exe: error: /home/rmainz/tmp/winnfstest/hummingbirdnfstest1/try10_rde_new_rds/RDE-Development/build_windows5/tmp/x.cpp: No such file or directory
  24. c++.exe: fatal error: no input files
  25. compilation terminated.
  26.  
  27. $ /home/rmainz/tmp/winnfstest/hummingbirdnfstest1/try10_rde_new_rds/Dependencies/win/qt/qt_5_15_2/Tools/mingw810_64/bin/c++ H:/tmp/winnfstest/hummingbirdnfstest1/try10_rde_new_rds/RDE-Development/build_windows5/tmp/x.cpp
  28.  
  29. $ ./a
  30. Hello World!

Submit a correction or amendment below (click here to make a fresh posting)
After submitting an amendment, you'll be able to view the differences between the old and new posts easily.

Syntax highlighting:

To highlight particular lines, prefix each line with {%HIGHLIGHT}




All content is user-submitted.
The administrators of this site (kpaste.net) are not responsible for their content.
Abuse reports should be emailed to us at