ln: failed to create symbolic link ‘asm’: Read-only file system

dhineshkumarc · 03-12-2015, 04:16 AM

Hi,

I am facing a compilation error (ln: failed to create symbolic link ‘asm’: Read-only file system) while building sboot for kronus board.
And i am using virtualbox (ubuntu) to my windows machine.

dhineshkumarc@dhineshkumarc-VirtualBox:sboot$ make
GEN uboot_module_config.h
GEN uboot_board_config.h
GEN uboot_panel_config.h
Configuring for kronus board...
ln: failed to create symbolic link ‘asm’: Read-only file system

Anyone come across this issue before ?

sag47 · 03-12-2015, 10:23 PM

Is the filesystem read only? What have you tried to troubleshoot so far?

dhineshkumarc · 03-12-2015, 11:54 PM

No, the file system is not read only, it is read & write supported. So far i moved by compilation environment from virtual box to standalone OS in another PC. It is started to work well. Hence i believe virtual box is not allowing to symblink any file system folders. It seems it is a limitation in the virtual box. I don't how to achieve this one through virtual box.

veerain · 03-13-2015, 12:07 AM

It is not a limitation of virtualbox. Perhaps you have errored on setup.

dhineshkumarc · 03-13-2015, 01:57 AM

I don't think so it is a setup issue since i used same version of OS (ubuntu 14.04 LTS) and same softwares in Virtual box as well as in standalone.
Normally ln doesn't work as expected in virtualbox.

sag47 · 03-13-2015, 07:33 AM

Quote:

Originally Posted by dhineshkumarc

Normally ln doesn't work as expected in virtualbox.

I believe more investigation into the root cause is required. I've been using KUbuntu 14.04 (same OS) in virtual box since it was released. I have no problems symlink linking, compiling software, nor writing software. I sincerely doubt your problem lies with virtual box.

How do you know your filesystem isn't read only? Can you give me the commands you used as well as the output? Please provide more info when you troubleshoot. Don't say what you did. Instead, give the terminal output of your troubleshooting.