Forum Replies Created
-
AuthorPosts
-
jovParticipant
SmarTTY seems to copy files by using the traditional X:\ Windows file naming, which limits the maximum path length to the infamous MAXPATH (260 chars). As I understand, maximum path length on Linux is practically unlimited, so SmarTTY could always run into this problem. I suggest to switch to the Unix naming convention \\?\ for Windows files. That way, SmarTTY can use path lengths up to 2^15 characters (Microsoft info here).
For now, I’m back to NetBeans because I can’t get this toolchain synchronized. In the VisualGDB properties of a project the Synchronize toolchain button now is grayed out, don’t know the cause of that. Too bad I’m not getting it all working yet, because I’d really like to continue using Visual Studio. With my first goal to get this up and running with VisualGDB.
jovParticipantThe above was based on a file-by-file transfer. Changing to tar I get this:
... /usr/lib/xorg/modules/libvbe.so /usr/lib/xorg/protocol.txt tar: cups/backend/vnc: Cannot open: Permission denied tar: Exiting with failure status due to previous errors
After that, UpdateSystools.bat continues and reports a successful synchronization. I have no idea which files are synchronized, probably none …
jovParticipantChanging arm-Linux-gnueabihf\sysroot\ in a\s\ doesn’t do the trick. It just goes wrong here: /usr/lib/node_modules/node-red-node-serialport/node_modules/serialport/node_modules/node-pre-gyp/node_modules/request/node_modules/har-validator/node_modules.
I wonder why I seem to be the only one getting these errors?
jovParticipantHi, that could be the cause. I’m having problems installing the toolchain, please see my recent post on that.
- This reply was modified 7 years, 9 months ago by jov.
-
AuthorPosts