Meta tags:

Headings (most frequently used words):

problems, note, help, things, to, mention, configure, script, compilation, chapter, introduction, linux, from, scratch, version, 12,

Text of the page (most frequently used words):
the (61), make (15), lfs (14), you (11), for (10), and (10), help (9), this (8), not (8), include (8), from (8), #problem (7), that (7), all (7), upstream (7), section (6), error (6), your (6), support (6), information (5), output (5), book (5), resources (4), org (4), questions (4), mnt (4), usr (4), version (4), screen (4), are (4), script (4), configure (4), being (4), note (4), have (4), faq (4), issue (4), about (3), will (3), because (3), wrong (3), should (3), case (3), many (3), file (3), job (3), tmp (3), problems (3), relevant (3), encountered (3), mailing (3), lists (3), answered (3), https (3), www (3), linuxfromscratch (3), question (3), channel (3), home (2), preparing (2), build (2), next (2), prev (2), asking (2), read (2), hints (2), doing (2), need (2), html (2), something (2), went (2), entire (2), example (2), what (2), was (2), gcc (2), share (2), locale (2), function (2), leaving (2), directory (2), recursive (2), files (2), compilation (2), can (2), while (2), may (2), errors (2), ask (2), any (2), procedure (2), possible (2), package (2), host (2), used (2), request (2), these (2), things (2), community (2), offer (2), assistance (2), through (2), first (2), some (2), please (2), find (2), listed (2), search (2), page (2), often (2), directly (2), via (2), projects (2), bug (2), hit (2), building (2), with (2), maintainers (2), excellent, article, internet, available, online, document, follow, increase, likelihood, getting, http, catb, esr, faqs, smart, enough, diagnose, only, notes, above, saved, includes, command, executed, associated, messages, people, would, just, bottom, aliaspath, localedir, libdir, lib, includedir, have_config_h, getopt1, static, arscan, commands, dir, expand, getopt, implicit, main, misc, remake, rule, signame, variable, vpath, default, remote, stub, opt1, lutil, load_too_high, 1565, undefined, reference, getloadavg, collect2, returned, exit, status, both, contents, various, useful, determining, cause, run, helpful, necessary, but, here, type, goes, running, review, contain, during, which, were, printed, lines, config, log, deviating, does, mean, after, personal, preference, front, changes, established, helps, evaluate, determine, causes, whether, deviated, exact, message, clear, description, system, requirements, distribution, create, apart, brief, explanation, experienced, essential, mention, also, wonderful, willing, irc, see, however, get, several, every, day, them, could, been, easily, going, searching, best, research, own, allows, focus, more, unusual, needs, searches, produce, solution, mentioned, below, cannot, working, check, already, there, try, source, following, hint, give, guidance, troubleshooting, downloads, txt, generalfaq, must, shall, least, channels, separated, tracker, reports, considered, invalid, annoy, developers, one, instruction, strongly, discourage, posting, onto, before, discussing, quite, inefficient, rarely, familiar, even, really, still, isolate, wanted, proper, report, chapter, introduction, linux, scratch,

Text of the page (random words):
1 5 help linux from scratch version 12 4 chapter 1 introduction prev resources next preparing for the build up home 1 5 help note in case you ve hit an issue building one package with the lfs instruction we strongly discourage posting the issue directly onto the upstream support channel before discussing via a lfs support channel listed in section 1 4 resources doing so is often quite inefficient because the upstream maintainers are rarely familiar with lfs building procedure even if you ve really hit an upstream issue the lfs community can still help to isolate the information wanted by the upstream maintainers and make a proper report if you must ask a question directly via an upstream support channel you shall at least note that many upstream projects have the support channels separated from the bug tracker the bug reports for asking questions are considered invalid and may annoy upstream developers for these projects if an issue or a question is encountered while working through this book please check the faq page at https www linuxfromscratch org faq generalfaq questions are often already answered there if your question is not answered on that page try to find the source of the problem the following hint will give you some guidance for troubleshooting https www linuxfromscratch org hints downloads files errors txt if you cannot find your problem listed in the faq search the mailing lists at https www linuxfromscratch org search html we also have a wonderful lfs community that is willing to offer assistance through the mailing lists and irc see the section 1 4 resources section of this book however we get several support questions every day and many of them could have been easily answered by going to the faq or by searching the mailing lists first so for us to offer the best assistance possible you should first do some research on your own that allows us to focus on the more unusual support needs if your searches do not produce a solution please include all the relevant information mentioned below in your request for help 1 5 1 things to mention apart from a brief explanation of the problem being experienced any request for help should include these essential things the version of the book being used in this case 12 4 the host distribution and version being used to create lfs the output from the host system requirements script the package or section the problem was encountered in the exact error message or a clear description of the problem note whether you have deviated from the book at all note deviating from this book does not mean that we will not help you after all lfs is about personal preference being up front about any changes to the established procedure helps us evaluate and determine possible causes of your problem 1 5 2 configure script problems if something goes wrong while running the configure script review the config log file this file may contain errors encountered during configure which were not printed to the screen include the relevant lines if you need to ask for help 1 5 3 compilation problems both the screen output and the contents of various files are useful in determining the cause of compilation problems the screen output from the configure script and the make run can be helpful it is not necessary to include the entire output but do include all of the relevant information here is an example of the type of information to include from the make screen output gcc d aliaspath mnt lfs usr share locale d localedir mnt lfs usr share locale d libdir mnt lfs usr lib d includedir mnt lfs usr include d have_config_h i i g o2 c getopt1 c gcc g o2 static o make ar o arscan o commands o dir o expand o file o function o getopt o implicit o job o main o misc o read o remake o rule o signame o variable o vpath o default o remote stub o version o opt1 o lutil job o in function load_too_high lfs tmp make 3 79 1 job c 1565 undefined reference to getloadavg collect2 ld returned 1 exit status make 2 make error 1 make 2 leaving directory lfs tmp make 3 79 1 make 1 all recursive error 1 make 1 leaving directory lfs tmp make 3 79 1 make all recursive am error 2 in this case many people would just include the bottom section make 2 make error 1 this is not enough information to diagnose the problem because it only notes that something went wrong not what went wrong the entire section as in the example above is what should be saved because it includes the command that was executed and all the associated error messages an excellent article about asking for help on the internet is available online at http catb org esr faqs smart questions html read this document and follow the hints doing so will increase the likelihood of getting the help you need prev resources next preparing for the build up home