Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
well i have a few errors. the first, when i cd.. into /binutils-build and extracted binutils-2.17.tar.bz2 there using tar -jxvf filename.tar.bz2. so heres the first thing, whenever i browse to that directory (using vim) there is no configure file, only config, so when i go to type in
No, there's no lock on it. But what do you mean, you do have it now? In your first post you said it wasn't there and later you couldn't access it with ls. If it's there and executable by your user account, you should be able to run it.
its definantely there, when i go to the file browser in vim i can see it there in the right folder, but when i try to access it from anywhere else, like using the ln or doing the ../blabla it says it doesnt exist. i dont get it. if it helps im doing this on a mac using vmware fusion v1.0
Did you do the following?
- Start VMWare;
- Boot the LFS live CD inside VMWare;
- Partition your virtual hard disk inside VMWare;
- Successfully complete the LFS steps prior to binutils, installing everything to the virtual disk inside VMWare.
So at this stage you're up to either step 5.3 or 6.11 to be working on binutils. If so, Vim isn't installed yet - it gets installed at step 6.57.
If you have vim available, either you're not inside the virtual setup, or something has gone wrong with the procedure you're following (or I've misunderstood your post).
What path are you following in vim to be able to select the binutils-2.17/configure file?
Why are you using the vim editor to determine what files you have. Use the ls command instead and make sure you are in the project directory. Opening configure in vim might just lock the file or rename it to "configure~". What are the permissions of it?
I've run into a few projects where there wasn't a configure script but there was a configure.ac script. In this case running autoconf generated the configure script.
ok, i ran that ln thing again but with the full directory, so now it seems like this is working, but when i do that theres a bunch of text on the screen. i see a few error type of things like input/output error. then when i type 'make' it says No Targets. Stop.
If you insist on tackling (C)LFS (which I suggest you put off until you get a little more experience with Linux), do yourself a favor, read section 1.5 of the book, and heed the advice contained therein. You're not following the book verbatim, you're not describing what you're doing that is different from the instructions in the book, and you're not posting even close to enough information about the problem.