Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Ok, been working on this for a few hours now (no biggie to me; trying to learn), and I'm taking all of the great advice given but also trying to follow the instructions from the developers. In order to even "get to" enlightenment, I need EFL (libraries I'm assuming?) installed. So I lazily tried to ./configure EFL (knowing I'd likely get error(s) due to lack of dependencies and I did:
SO, I dl'd luajit 2.0.4 tarball, extracted, read README and other "instructions" and followed them. I used make and make install and all went well. I'm still getting the same error: configure: error: pkg-config missing luajit >= 2.0.0
Ok, been working on this for a few hours now (no biggie to me; trying to learn), and I'm taking all of the great advice given but also trying to follow the instructions from the developers. In order to even "get to" enlightenment, I need EFL (libraries I'm assuming?) installed. So I lazily tried to ./configure EFL (knowing I'd likely get error(s) due to lack of dependencies and I did:
SO, I dl'd luajit 2.0.4 tarball, extracted, read README and other "instructions" and followed them. I used make and make install and all went well. I'm still getting the same error: configure: error: pkg-config missing luajit >= 2.0.0
Any advice is greatly appreciated.
Auroch
you need to install luajit-devel packages so it can use the header files. when ever you're compiling from source you have to have the developer packages installed.
you need to install luajit-devel packages so it can use the header files. when ever you're compiling from source you have to have the developer packages installed.
I haven't been able to unzip it though. I executed the command and got no error, but there is no directory (still just the tar.xz). I tried the re-download and the same recommended commands, but same result.
In the days of old you would have a /usr/src/ path that was meant for compiling. These days I just create a directory under the home of a particular user. And I tend to create a ./temp/ path that I cd into before I untar. In case there is no defined "path" that it all falls under. I then move the resultant extracted stuff. Normally ../ as in the parent path of ./temp/. Or I rename ./temp/ if it doesn't have a path. It doesn't really matter much as long as the user has read and write access to the path and it's parent directory.
So:
/usr/src/
or
~/sources/
For most of the times that I build stuff or have to extract things from other things. Although I mostly call it ~/linux/ these days since it is more than just sources these days. Like firmware, fonts, packages, and such. Most tarballs have an INSTALL or README once extracted that explains how to build and install the package. Or a ./doc/ path with html contents for viewing in a web browser.
I hear ya brother. And I always read everything I can after I extract the tarball just so I know what I'm supposed to do.
I appreciate all of the help, but I'm done for the evening, unfortunately. Family aggro and all. I'm gonna give it hell tomorrow and hopefully succeed and learn some shit in the process.
I haven't been able to unzip it though. I executed the command and got no error, but there is no directory (still just the tar.xz). I tried the re-download and the same recommended commands, but same result.
Auroch
I did that too, look for a directory called usr inside the directory you unzipped it. then read my post about moving it to /usr and read @Shadow_7 post
Guys, I'm not having any luck here. It seems that this is way over my head at this point, and I'm not going to waste any more of your time. I think I might try something simpler and revisit this another time. Besides, I'm down to taking shots in the dark, and if I do get it to work, I'm not going to learn anything anyway, as it'll be pure luck.
Fantastic idea. I originally did want the latest Enlightenment, but I just gave myself a crash course in SlackBuilds (thanks for the nudge).
So, if I understand correctly (all using only SlackBuilds.org, btw), I need to download the tarballs for both the slackbuild script and the source for the main package and all of the dependencies. I have done that.
Next, I extracted the script tarball for each.
Next, I dropped the source tarball in to the newly created folder matching each. (I initially tried to install the first listed dependency [lua, if it matters] and it didn't work because it was looking for the source tarball inside the directory).
Now, I have folders for each dependency, as well as enlightenment itself. I also went in to each directory and made the scripts executable, using chmod +x.
Am I ok so far? And if I am, should I move all of those files to, and run the executable scrips from /tmp?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.