On Mon, Oct 31, 2016 at 2:15 AM, Douglas R. Reno <[email protected]> wrote:
> > > On Sun, Oct 30, 2016 at 9:13 PM, Jared lima <[email protected]> > wrote: > >> okay so do i uncompress and extract it anyways? also ialready did the >> glibc-2.24 archive and there isnt a /build directory in it... does that get >> created at a later time? >> >> On Mon, Oct 31, 2016 at 2:10 AM, Douglas R. Reno <[email protected]> >> wrote: >> >>> >>> >>> On Sun, Oct 30, 2016 at 9:09 PM, Jared lima <[email protected] >>> > wrote: >>> >>>> ok, so when i run that command, i should expect the creation of a >>>> folder containing the contents like what the other packages make? >>>> >>>> because when i ran the command to extract a tar.gz file, this archive >>>> dumped all the contents into the "root directory" for /sources. it didn't >>>> create its own folder. >>>> >>>> On Mon, Oct 31, 2016 at 2:07 AM, Douglas R. Reno <[email protected]> >>>> wrote: >>>> >>>>> >>>>> >>>>> On Sun, Oct 30, 2016 at 9:05 PM, Jared lima < >>>>> [email protected]> wrote: >>>>> >>>>>> okay, but when i ran the wget-list command to download all the >>>>>> packages in a previous chapter, it downloaded a "tzdata2016f.tar.gz" >>>>>> archive. do i ignore the archive thats all by itsself or what? >>>>>> >>>>>> On Mon, Oct 31, 2016 at 2:04 AM, Douglas R. Reno < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> On Sun, Oct 30, 2016 at 9:02 PM, Jared lima < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> I have already asked this but i figured i should make a dedicated >>>>>>>> post for this, plus my question still hasnt exactly been answered >>>>>>>> >>>>>>>> Using LFS 7.10 stable, >>>>>>>> >>>>>>>> Chapter 5.3, the part where you extract all the downloaded packages >>>>>>>> before compiling. >>>>>>>> >>>>>>>> When i extract the tzdata2016f.tar.gz archive, it puts all the >>>>>>>> contents into the source directory /mnt/lfs/sources , aka the folder >>>>>>>> where >>>>>>>> all the downloaded packages are. >>>>>>>> >>>>>>>> it doesn't create its own "protected" directory for all the files >>>>>>>> like all the other packages make. >>>>>>>> >>>>>>>> so im a bit confused if thats normal or not. i was told that the >>>>>>>> book extracts tzdata from within the glibc-2.24/build directory. >>>>>>>> >>>>>>>> so should i just move on, and let the extracted files rest inside >>>>>>>> the "root directory" of the location of all the extracted sources >>>>>>>> (/mnt/lfs/sources), or do i need to create a directory for tzdata2016f >>>>>>>> and >>>>>>>> change the permissions to what the others are? >>>>>>>> >>>>>>>> >>>>>>>> im sorry, this stuff is just a bit confusing to me. >>>>>>>> >>>>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> In the book, tzdata is installed as part of the glibc page. We >>>>>>> assume that you are in the glibc-(insert version here)/build directory >>>>>>> when >>>>>>> you unpack that tarball. Yes, it is a separate package theoretically, >>>>>>> but >>>>>>> as far as I understand, it made sense for us to keep it in that page. >>>>>>> >>>>>>> -- >>>>>>> http://lists.linuxfromscratch.org/listinfo/lfs-support >>>>>>> FAQ: http://www.linuxfromscratch.org/blfs/faq.html >>>>>>> Unsubscribe: See the above information page >>>>>>> >>>>>>> Do not top post on this list. >>>>>>> >>>>>>> A: Because it messes up the order in which people normally read text. >>>>>>> Q: Why is top-posting such a bad thing? >>>>>>> A: Top-posting. >>>>>>> Q: What is the most annoying thing in e-mail? >>>>>>> >>>>>>> http://en.wikipedia.org/wiki/Posting_style >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>> tzdata2016f is a separate file archive. We use that "tar -xf ..." >>>>> command to untar it. >>>>> >>>>> >>>>> -- >>>>> http://lists.linuxfromscratch.org/listinfo/lfs-support >>>>> FAQ: http://www.linuxfromscratch.org/blfs/faq.html >>>>> Unsubscribe: See the above information page >>>>> >>>>> Do not top post on this list. >>>>> >>>>> A: Because it messes up the order in which people normally read text. >>>>> Q: Why is top-posting such a bad thing? >>>>> A: Top-posting. >>>>> Q: What is the most annoying thing in e-mail? >>>>> >>>>> http://en.wikipedia.org/wiki/Posting_style >>>>> >>>>> >>>> >>>> >>> When you decompress that package, because of the way that it is created, >>> it does not create a separate directory. Our instructions have it unpacked >>> in the "glibc-2.24/build" directory. >>> >>> -- >>> http://lists.linuxfromscratch.org/listinfo/lfs-support >>> FAQ: http://www.linuxfromscratch.org/blfs/faq.html >>> Unsubscribe: See the above information page >>> >>> Do not top post on this list. >>> >>> A: Because it messes up the order in which people normally read text. >>> Q: Why is top-posting such a bad thing? >>> A: Top-posting. >>> Q: What is the most annoying thing in e-mail? >>> >>> http://en.wikipedia.org/wiki/Posting_style >>> >>> >> You create that directory as part of the compilation process. > > Do not unpack all of the tarballs at one time. Some of them are rebuilt in > Chapter 6 - and you will cause yourself a ton of problems that way. Unpack > them as you need them and delete the build directories after you have > finished compiling the package. > > Also, and I just noticed this thanks to my crappy mail client - please > don't top post. > > -- > http://lists.linuxfromscratch.org/listinfo/lfs-support > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page > > Do not top post on this list. > > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing in e-mail? > > http://en.wikipedia.org/wiki/Posting_style > > oh so, just go down the list of the compiling process, and extract the one needed?
-- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
