On Sat, Jun 28, 2014 at 07:33:30PM -0700, logical american wrote: > To all: > > Here are some things I noticed while currently following v7.5 of the LFS > book > > 1. In the Chapter 3.1 Introduction for creating the LFS partition, I > actually > was able to successfully do this as an original logged-in usr on openSuse > v13.1 by > running the Partition editor inside Yast while running under the live > openSuse v13.1 KDE Desktop dvd which I had to download and iso image burn, > and then reboot to, in order to avoid problems with mount setting up on > the original /sda drive as / which stopped everything as the partition > editor will > not work on a mounted partition (well it will, but chaos can result) > > After coming up under live KDE desktop, I could then access all 3 hard > drives and partition them at will (and my own peril) > > The partition editor both created the partition and formatted the filesystem > as ext4, and I choose my 3rd drive just to be safe on both. > > However when it came time to actually create directories, I was forced to > use root privileges to do so, since the partition editor had created > everything as root owner and group. > > So my first question? > > Should creating the lfs user and lfs group be done before doing any > work on creating work spaces on the hard drive? > That seems unnecessary - you need to have root privileges to create a filesystem. Yes, you do need root privileges to let the lfs user write to the new filesystem.
> 2. After creating the lfs user and lfs group, and setting up the bash > environment, I used the following commands on the $LFS partition. > > %chown -R lfs sources > %chown -R lfs tools > %chgrp -R lfs sources > %chgrp -R lfs tools > > Running > > %ls -adl * > > showed what I expected to see: (plus also all nested subdirectories and > files) > > drwx------ 2 root root 16384 Jun 28 10:54 lost+found > drwxrwxrwt 3 lfs lfs 4096 Jun 28 18:38 sources > drwxr-xr-x 2 lfs lfs 4096 Jun 28 18:46 tools > > (The lost+found folder came from the partition editor operations) > > 3. I am now stopped at Section 5.3 General Compilation Instructions because > the assumed CLI commands do NOT match > > %which bash > /bin/bash > > %which sh > /bin/sh > Seems correct in itself. Try ls -l /bin/sh but I don't think it is likely to point to anything other than bash on opensuse. > %which gawk > /bin/gawk > > %which bison > which: no bison in (/tools/bin:/bin:/usr/bin) > > I am on openSuse which uses Yast, not bison or yacc. Does bison need to > be installed? I assume that the "sh" is set incorrectly also, although > syntactically it is correct. > You are making guesses, but coming up with the wrong answers ;-) We all have to start somewhere, so I will point out two things: 1. Yast is a package manager, it does not give the functionality provided by bison or yacc. You definitely need to install whichever package provides those (almost certainly, 'bison' in opensuse). First, try 'which yacc' just in case that is installed. 2. There is a list of host system requirements in the Prologue, and within that is a script version-check.sh : you need to run that, and to read and understand the results. If anything is missing, you need to install it. In general, distros provide binaries so that you can run their version of linux. But being able to _compile_ programs often requires additional packages : a compiler (gcc), header files from several of the packages, other packages such as bison. If the headers are packaged separately, they are probably called "development" versions of the package. Google found a very old link which suggests that you need to use yast to _at_least_ install "C/C++ Compiler and Tools". As a quick "rule of thumb", if you have not previously compiled anything on this system then get to the stage where you think you have met the requirements, and then try to compile binutils. By that, I mean you should create a binutils-build directory and run ../binutils-x.y.z/configure from there (for a test build, just use configure without options, as if you were going to build it for /usr/local, then run make, then make DESTDIR=/somewhere/you/can/write/binutils-test install. Do all that as a regular user (preferably, as yourself, not user lfs - so the DESTDIR might be /home/randall/binutils-test if your username is randall. If that completes ok (echo $? gets a value of 0) then you will be able to see what got installed in the DESTDIR, and you are probably in a position to start - since most people here know almost nothing about opensuse, it might be that you will still need to install other packages. > - Randall > > -- > CONFIDENTIAL: This email message and/or any attachments is for the sole use > of the intended recipient(s) and may contain confidential information. Any > unauthorized review, use, copying, dissemination, disclosure, retention or > distribution is strictly prohibited. If you are not the intended recipient, > please contact the sender by reply email and destroy all copies of the > original message along with any attachments. This communication (including > attachments) is covered by the Electronic Communication Privacy Act, U.S.C. > Sections 2510-2521. > LOL. You are sending what appears to be your personal mail (i.e. not through your company's mailserver) to a public list which gets archived. ĸen -- Nanny Ogg usually went to bed early. After all, she was an old lady. Sometimes she went to bed as early as 6 a.m. -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
