El Sábado, 25 de Marzo de 2006 22:41, Jeremy Huntwork escribió:
> To me, it just seems easier to work with dependencies all in one file
> rather than separately in each chapter06 file. Especially as we're
> looking at including another page (IIRC) that describes more of the
> rationale for depende
M.Canales.es wrote:
The dependencies for each package are placed in the package file under
chapter06/, and Xincluded from here in the files under chapter05/. When the
dependencies for a package need be updated, only the file for that package
under chapter06/ need be edited.
I can't see any ga
El Sábado, 25 de Marzo de 2006 20:52, Jeremy Huntwork escribió:
> Manuel, I wanted to start adding this stuff into the book. I was
> wondering if it would make sense to have this as some sort of
> dynamically available data. I'm not sure if an entity makes sense (e.g.,
> autoconf-deps) but that's
Chris Staub wrote:
OK, I've got the dependency list done -
http://linuxfromscratch.org/~chris/dependencies.txt. Probably still not
complete, but it's about as close as I'll ever get.
Manuel, I wanted to start adding this stuff into the book. I was
wondering if it would make sense to have this
Chris Staub wrote:
Just added a couple more that I missed earlier...Berkeley DB needs grep,
and Glibc needs gzip.
And one more...I completely forgot to document deps. for the kernel.
Just added that info.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscrat
Chris Staub wrote:
On another note: I've removed the notes about Bzip2 and Gzip needing to
be installed before tar. It seems tar will build with bzip2 and gzip
support by default anyway, and simply searches the PATH for those
programs at runtime.
Just added a couple more that I missed earli
Chris Staub wrote:
Dan Nicholson wrote:
Sorry...those look valid to me...I've updated my own list to reflect
them. The E2fsprogs -> Util-Linux dep. was already there. :)
On another note: I've removed the notes about Bzip2 and Gzip needing to
be installed before tar. It seems tar will build
Dan Nicholson wrote:
On 3/15/06, Chris Staub <[EMAIL PROTECTED]> wrote:
* Bison must be installed before...tar
* Flex must be installed before...Iproute2 Man-DB
* E2fsprogs must be installed before...Util-linux
You didn't mention these. Are they OK to go in, or do you want me to
dig up the ra
On 3/15/06, Chris Staub <[EMAIL PROTECTED]> wrote:
> >
> > * Bison must be installed before...tar
> > * Flex must be installed before...Iproute2 Man-DB
> > * E2fsprogs must be installed before...Util-linux
You didn't mention these. Are they OK to go in, or do you want me to
dig up the rationale?
Dan Nicholson wrote:
Chris, here's what's in my (pathetic compared to yours) dependency notes:
http://www.linuxfromscratch.org/~dnicholson/dn-dependencies.txt
What I have that's not in yours.
* Man-DB: depends on flex
* Kbd: depends on gettext
* Tar: depends on bison and inetutils
All have b
On 3/13/06, Chris Staub <[EMAIL PROTECTED]> wrote:
> OK, I've got the dependency list done -
> http://linuxfromscratch.org/~chris/dependencies.txt. Probably still not
> complete, but it's about as close as I'll ever get.
Chris, here's what's in my (pathetic compared to yours) dependency notes:
ht
Chris Staub wrote:
OK, I've got the dependency list done -
http://linuxfromscratch.org/~chris/dependencies.txt. Probably still not
complete, but it's about as close as I'll ever get.
Oh. That's cool. Thanks for all the hard work, Chris! I won't be
around for the next few days, so either t
On 3/13/06, Chris Staub <[EMAIL PROTECTED]> wrote:
> OK, I've got the dependency list done -
> http://linuxfromscratch.org/~chris/dependencies.txt. Probably still not
> complete, but it's about as close as I'll ever get.
Wow, that is impressive. I'll try to review these tomorrow with the
info I h
OK, I've got the dependency list done -
http://linuxfromscratch.org/~chris/dependencies.txt. Probably still not
complete, but it's about as close as I'll ever get.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above informa
Jeremy Huntwork wrote:
I'll add the order changes you made to the alphabetical branch -
hopefully today. The only thing left is to get Chris' dependency
documentation in as well.
Sorry for the lateness on this. The changes are in now, and as usual,
the book is rendered here:
http://linuxfro
On Wed, Mar 08, 2006 at 09:00:35PM +0100, M.Canales.es wrote:
>
> Of course. That is what 'additional' means ;-)
Sometimes people (especially me) need an extra level of pedanticness to
avoid ambiguity. ;)
--
Archaic
Want control, education, and security from your operating system?
Hardened Lin
El Miércoles, 8 de Marzo de 2006 20:58, Archaic escribió:
> > Testsuite depends on: additional dependencies to run the testsuites
Of course. That is what 'additional' means ;-)
--
Manuel Canales Esparcia
Usuario de LFS nº2886: http://www.linuxfromscratch.org
LFS en castellano: http://www.
On Wed, Mar 08, 2006 at 07:43:27PM +0100, M.Canales.es wrote:
>
> Approximate build time: 0.2 SBU
> Required disk space: 16.4 MB
> Installation depends on: list of build dependencies, like until now
> Testsuite depends on: additional dependencies to run the testsuites
This looks good, but it wo
El Miércoles, 8 de Marzo de 2006 18:10, Dan Nicholson escribió:
> I saw that and started making those same changes in my sandbox.
> However, this could become pretty ugly. Perhaps if there was a
> separate Optional Dependencies heading. Or Testing Dependencies. Or,
> since LFS doesn't include t
On Wed, 8 Mar 2006 09:10:58 -0800
"Dan Nicholson" <[EMAIL PROTECTED]> wrote:
> On 3/8/06, Chris Staub <[EMAIL PROTECTED]> wrote:
> >
> > I think deps. that are needed for testsuites could be labeled as
> > being "optional" (notice I already started doing that for a few
> > packages) but you could
On 3/8/06, Chris Staub <[EMAIL PROTECTED]> wrote:
>
> I think deps. that are needed for testsuites could be labeled as being
> "optional" (notice I already started doing that for a few packages) but
> you could do the same with several others. For example...
I saw that and started making those sam
Dan Nicholson wrote:
On 3/8/06, Chris Staub <[EMAIL PROTECTED]> wrote:
I'm still updating my dependency list here -
http://linuxfromscratch.org/~chris/dependencies.txt
Unfortunately my network connection died yesterday, and I neglected to
copy this file to my own system (shame on me!) so I coul
Lefteris Dimitroulakis wrote:
I do not know about the iana-etc but for the other packages
your build order looks like following the rule :
"try to reduce the influence of tools as soon and as much as possible
under ch6".
This is a very reasonable way of thinking for me specially if it is
combin
Στις Τετ 08 Μαρ 2006 03:03, GMT+2, ο/η Dan Nicholson έγραψε:
> On 3/7/06, Dan Nicholson <[EMAIL PROTECTED]> wrote:
> > On 3/7/06, Dan Nicholson <[EMAIL PROTECTED]> wrote:
> > > Good enough for me. The new build order goes:
> >
> > Oops, forgot about the moved libtool:
>
> My mind is exploding! Li
On 3/8/06, Chris Staub <[EMAIL PROTECTED]> wrote:
>
> I'm still updating my dependency list here -
> http://linuxfromscratch.org/~chris/dependencies.txt
>
> Unfortunately my network connection died yesterday, and I neglected to
> copy this file to my own system (shame on me!) so I couldn't add more
Matthew Burgess wrote:
Jeremy Huntwork wrote:
Matt, Gerard, any idea on how/when you want to start looking at
merging these changes into trunk?
A.S.A.P please, though I'd prefer if you could wait until Chris'
dependency stuff was in before merging. I'm going to have to trust
yours, Dan's a
Jeremy Huntwork wrote:
Matt, Gerard, any idea on how/when you want to start looking at merging
these changes into trunk?
I'm with Matt on this one and do it sooner rather than later. I do want
Chris' dependencies finalized and added to this alphabetical branch so
we can implement this in one
Jeremy Huntwork wrote:
Dan Nicholson wrote:
The build is ICA verified. All tests were run and kernel built with
"allyesconfig". Results contain no regressions from current LFS SVN
except for two GCC test suite failures from applying the patch in
http://wiki.linuxfromscratch.org/lfs/ticket/1718
Jeremy Huntwork wrote:
Matt, Gerard, any idea on how/when you want to start looking at merging
these changes into trunk?
A.S.A.P please, though I'd prefer if you could wait until Chris'
dependency stuff was in before merging. I'm going to have to trust
yours, Dan's and Chris' hard work and
Dan Nicholson wrote:
The build is ICA verified. All tests were run and kernel built with
"allyesconfig". Results contain no regressions from current LFS SVN
except for two GCC test suite failures from applying the patch in
http://wiki.linuxfromscratch.org/lfs/ticket/1718. Will probably wait
un
On 3/7/06, Dan Nicholson <[EMAIL PROTECTED]> wrote:
> Changes are
> relative to the book in
> Jeremy's home dir:
>
> http://www.linuxfromscratch.org/~jhuntwork/lfs-alphabetical/
The build is ICA verified. All tests were run and kernel built with
"allyesconfig". Results contain no regressions fro
On 3/7/06, Dan Nicholson <[EMAIL PROTECTED]> wrote:
> On 3/7/06, Dan Nicholson <[EMAIL PROTECTED]> wrote:
> >
> > Good enough for me. The new build order goes:
>
> Oops, forgot about the moved libtool:
My mind is exploding! Libtool hard codes grep and sed. So, the new
build order is (with grep
On 3/7/06, Dan Nicholson <[EMAIL PROTECTED]> wrote:
>
> Good enough for me. The new build order goes:
Oops, forgot about the moved libtool:
...
gcc
bdb
coreutils
iana-etc
libtool
m4
bison
ncurses
...
--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch
On 3/7/06, Jeremy Herbison <[EMAIL PROTECTED]> wrote:
> Although not in the book, I like to (for instance) build gpm before
> ncurses. This also necessitates moving up Bison (and M4) since gpm needs
> it. Basically, I'm just pointing out the usefulness of having Bison as
> early in the build as pos
> Basically, Bison needs to come before Bash. There's no real question
> about it. Do whatever makes sense to make this happen (ie: move around
> whatever needs to be move around so Bison can be built before Bash and
> taking into account Bison's M4 dependency as you pointed out).
>
> --
> Gerard
Assuming the second suggestion is followed, the placement must be
resolved. Bison hard
codes the location of m4. Therefore, I believe the best courses of
action are to:
* Swap bash and bison.
or
* Move bison between M4 and ncurses.
Thoughts, suggestions, criticisms welcome. Otherwise, every
36 matches
Mail list logo
