Tag Info

Hot answers tagged

6

Short answer: You can use the same swap partition as the data in swap is not preserved from one boot to the next. It is totally normal to have multiple linux installations on a disk with a single swap. There is one exception/caveat I know of, however: if you use hibernate (aka, 'suspend to disk'), hibernate uses your swap space for storage. If you then ...


4

You need to build bash with a better bison (yacc) on your host. bash uses yacc grammer rules and only GNU bison will generate the correct parsing code for the bash build.


4

You /mnt/lfs directory is restricted to user leo (mode 0700), no-one else can enter it. Change that to 755 (chmod go+rx /mnt/lfs) and things should work out.


4

Make is simply for convenience. You can build software without it, it is just more difficult. When you run make to build something, it shows you the commands it is running. You can run those commands manually and get the same effect. $ echo "int main() {}" > test.c $ make test cc test.c -o test Which created a file called test. I can get the ...


3

do I need to have a swap partition for each distro or can LFS use the swap partition I already have? As goldilock says, unless you are hibernating (suspend to disk), yes. Otherwise no, because you could overwrite swap of a hibernated system - either it's saved state or the part that was used as regular swap at suspend time. If so, would the swap ...


3

Correct. As the Dragon Book explains, you must first build a host binary that builds for the target, and then you use that to build a target binary that builds for the target.


3

You can only claim to have done something from scratch if you really wrote the software yourself. If you just bundling some software you can give the bundle/distribution a name but that's it. If you expect to receive karma points/get famous/improve your cv by creating a distribution and just giving it your own name you are mistaken. It can even backfire if ...


3

No, of course not. You did not write any of the software, you just compiled it. All the licenses and copyrights that the software was distributed with apply to an LFS system just like any other.


3

Short answer: You don't. Long answer: If you know what you are doing, you certainly can organize the directories in whatever way you want, and give them names in Swahili too. But that means that you'd have to adjust each and every package you install to use this non-standard layout. You will find that some packages' configuration silently ignores the ...


3

This value of PS1 is set by the bash system-wide configuration file /etc/bash.bashrc. You can override it by setting it from your ~/.bashrc. PS1 is a shell variable. Its meaning depends on the shell. It should normally not be exported since it is not supposed to be in process's environments, though you can get away with it if you only ever use one shell. ...


3

A less time consuming option is Gentoo Linux. The install process starts further along than the Linux From Scratch book and there are options to install some of the bigger packages from binary to avoid compiling your Desktop Environment from scratch for example. As a side note the only reason to install Linux from Scratch is as a educational experience.


3

The errors you're getting are all listed in the LFS book as known and safe to ignore. Run make check again after the failure and it should complete without errors. The reason it doesn't fail the second time is because it skips tests that have already been run (even the failed ones).


2

You need to make sure quotes, parentheses and any other grouping structures are nested properly within your script. This error is a typical result of such issues.


2

According to the doc you link, you should be in the unix subdirectory of tcl8.5.9 to run the configure script, not in the tools subdirectory.


2

That segment is for if you were building a script to compile glibc automatically in order to run it on this system. The "i?86" is a pattern; if the outut of uname -m matches it, it will run the following commands until it gets to ;;. You probably don't need it; it was specifically meant to figure out if your architecture type was i386 since glibc doesn't ...


2

This appears to me to be a bug in align.c 2.6.39 and previous with respect to GCC >= 4.6. I am guessing that you are building on a recent Fedora that has GCC 4.6 as the default installed GCC. The bug should not appear using GCC < 4.6 IMHO. The variable "instruction" is declared on line 704 and initialized to zero. It is then re-assigned on line 746. This ...


2

You could build your own. While this clearly seems to be a chicken-and-egg problem, I just had a deeper look at SUSE Studio and it could be of great use here. Just login/create an account, choose a base template (say, "minimal X"), add software, choose "Live CD" in the Build tab. Since all OpenSUSE repositories are available, you should find everything ...


2

Debian is built from scratch in the sense that each package maintainer builds his package from the source, so that you don't have to. Most distros work that way (exceptions are for example Gentoo or LFS). So the "tools" to build the software are depending on each component, and the packaging into a .deb or .rpm is often handled by a distro specific tool. To ...


2

Beyond LFS shows you how to add additional packages to LFS beyond the minimal installation. But LFS/BLFS doesn't really provide you a good way to build a Live CD. Gentoo, another source-based distribution, has a step-by-step guide for making a custom Gentoo-based Live CD/DVD. If you want to build a custom source-based distribution this is probably your best ...


2

I found a fix for this. If you're having the same problem, try this. Before configuring, try this in your gcc folder: ./contrib/download_prerequisites


2

According to the HLFS page: Hardened Linux From Scratch (HLFS) is a project that provides you with step-by-step instructions for building your own customized and hardened Linux system entirely from source The project will only be "initially geared towards building production-quality servers, routers, and firewalls" the list you quote from that page. You ...


2

I don't know whether the previous answer I submitted is correct or not. I decided to continue doing LFS-7.5 in Linux Mint, where user lfs was present in the sudoers file. After finishing Chapter 5, I again got an error at Chapter 6.7 make mrproper. So, I deleted all folder under $LFS except $LFS/sources and started from the beginning. After finishing the ...


2

I was also trying to build LFS system on my system. I am using Ubuntu 14.04. I got the same message during version-check. I went ahead with chapter 5 and during installing gcc, make failed with error. Checking few online help and mailing lists, I found that I had to point to the place where the libraries existed i.e. /usr/lib which I found out from this ...


2

The way I would solve this problem is by having what is called an "initrd". I don't know how familiar you became with initrd when doing Linux from scratch, but they have a page about initrd here: http://www.linuxfromscratch.org/blfs/view/svn/postlfs/initramfs.html What initrd does is act as a small root filesystem the kernel boots in to after loading the ...


2

Will it have a negative effect on my LFS build later on? I can't imagine how. For one thing, cal is an end user application than nothing else is likely to need or depend upon. Even if it is required at some point, it will still meet the criteria specified by POSIX regardless of this particular flaw: The cal utility shall write a calendar to ...


2

The correct virtual link is: ln -s /tools/lib/crt*.o /tools/lib/gcc/i686-lfs-linux-gnu/4.8.2/


1

After running the second pass of gcc, ldd was pointing that gcc was using the host libraries. I didnt know how to solve it, so I simply ran again the second pass of gcc but using the gcc binary of the last second pass. Without passing an CC variable. Then ldd started to show that gcc was using the stuff under /tools. But the binaries of binutils was also ...


1

The problem seems to be missing texinfo, which causes the build process to abort (search the log for lines of the form *** [directory_name] Error X). It also tells you, that you normally shouldn't need it, unless you modified sources for the info manuals. I assume this is in one of the bootstrapping parts of LFS, since otherwise you should have makeinfo ...


1

Take a look at Arch Linux. Arch Linux allows you to build your system from the first floor up. You start with nearly nothing and install packages to your desire. Take a look at the Arch wiki for installation instructions. Arch makes it easy to create custom installation media.


1

Ok, I am going on a limb here and suggest you shouldn't do this project and don't open the system to anyone because you have to secure your system rigorously but if you still want to do it here are some things you should at least consider: Restrict/deny outgoing traffic and have all the source for LFS already in place Use something like selinux to secure ...



Only top voted, non community-wiki answers of a minimum length are eligible