LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 10-15-2018, 01:17 PM   #1
bsmile
Member
 
Registered: Oct 2017
Posts: 98

Rep: Reputation: Disabled
is symbolic link failure cmake related issue in virtualbox?


I try to compile nlopt package on a linux virtualbox installed in a
Windows 7 host. nlopt makes use of cmake for its build/compilation. After
step cmake, I was told to run make, it then returns the following error
messages,

CMake Error: cmake_symlink_library: System Error: Read-only file system
CMake Error: cmake_symlink_library: System Error: Read-only file system
CMakeFiles/nlopt.dir/build.make:1264: recipe for target 'libnlopt.so.0.9.0'
failed
make[2]: *** [libnlopt.so.0.9.0] Error 1
make[2]: *** Deleting file 'libnlopt.so.0.9.0'
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/nlopt.dir/all' failed
make[1]: *** [CMakeFiles/nlopt.dir/all] Error 2
Makefile:160: recipe for target 'all' failed
make: *** [all] Error 2

Is this a cmake related issue? Since virtualbox cannot set up symbolic link
within a windows host the way linux defines its soft links, is there way to deal with this failure? I am totally new to cmake (but am trying to study it now) and cannot track into it. Any advice, especially step by step guide on how to deal with it would be highly appreciated!
 
Old 10-15-2018, 02:38 PM   #2
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,792

Rep: Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656
Unless you have your VirtualBox set up weird, it generally uses a file on your computer for the "hard drive" of the VM. Then that space is "formatted" to whatever filesystem you choose. In that way, as far as Linux is concerned, if you formatted it as an ext4 filesystem, you get an ext4 filesystem with all the bells and whistles that offers, including symlinks.

I imagine your issue is more related to the "Read-only file system" error at the beginning of the output. What filesystem are you running in the VM and what user are you trying to build nlopt as?
 
Old 10-15-2018, 07:06 PM   #3
bsmile
Member
 
Registered: Oct 2017
Posts: 98

Original Poster
Rep: Reputation: Disabled
Thanks for the new perspective into the problem! The following is what is returned,

john@vb ~/work/software/nlopt/build $ df -Th
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda1 ext4 19G 7.8G 10G 44% /

which seems to show the filesystem for the booting disk is indeed ext4. I never had virtualbox set up symbolic link correctly, don't know why it is the case.
 
Old 10-15-2018, 07:17 PM   #4
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,792

Rep: Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656
Are you using the SlackBuild to build this or compiling it manually? All SlackBuilds are only tested by running it as root.

If you're building it manually, are you doing it as root or your regular user?
 
Old 10-15-2018, 08:44 PM   #5
bsmile
Member
 
Registered: Oct 2017
Posts: 98

Original Poster
Rep: Reputation: Disabled
I think I use cmake and then make.
 
Old 10-15-2018, 09:38 PM   #6
bsmile
Member
 
Registered: Oct 2017
Posts: 98

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by bassmadrigal View Post
Are you using the SlackBuild to build this or compiling it manually? All SlackBuilds are only tested by running it as root.

If you're building it manually, are you doing it as root or your regular user?
Thank you SO SO much!! Now I finally understand what you are saying, and installed nlopt through system packaging service, which is more reliable and easier to maintain than my manual installation (I guess/hope). Also, I realized that I didn't use sudo to install it, which might be why the error message shows up, but I didn't bother to try it.

I will try using the library and come over here for help again if I run into further questions!
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Apache2 "Symbolic link not allowed or link target not accessible" on VirtualBox, Shared Folders sundialsvcs Linux - Virtualization and Cloud 0 03-05-2016 12:45 AM
[SOLVED] Symbolic link issue for a log file rpittala Programming 7 11-30-2015 11:11 AM
Failure in symbolic link to the calling name "g95" hanamilani Linux - Newbie 1 02-10-2013 12:57 PM
creating symbolic link issue? prasad_nyros Linux - Newbie 1 05-08-2011 06:50 AM
Problem related symbolic link raj_sony2001 Linux - General 1 06-01-2006 05:17 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:38 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration