Dimitry Naldayev wrote:
I am looking for a way to build a clean production system. ie system
without development parts.
You have two approaches.
A) [preferred] Use Debian Sarge or maybe Etch. Rationale:
1) Its minimal install (for a router) is below 70 MB, and doesn't
contain development st
On Feb 5, 2006, at 4:04 PM, William Harrington wrote:
2) Archive all your headers in an archive and compress it and save
them somewhere. Build a new toolchain except build it so it goes
into home that way when you extract the toolchain it'll always be
in home, or you could keep the toolcha
On Feb 5, 2006, at 12:16 PM, Dimitry Naldayev wrote:
Hi all,
I am looking for a way to build a clean production system. ie system
without development parts.
RATIONALE: I do not need binutils or gcc or something like this on my
router. (if I realy need binutils --- corect me please)
The main
Dimitry Naldayev wrote:
Hi all,
I am looking for a way to build a clean production system. ie system
without development parts.
My immediate thought on this is that you should still follow the LFS
book completely (including installing all toolchain components). Once
it's built, then you can
Hi all,
I am looking for a way to build a clean production system. ie system
without development parts.
RATIONALE: I do not need binutils or gcc or something like this on my
router. (if I realy need binutils --- corect me please)
The main idea is to use the development tools from toolchain to bu
Matthew Burgess wrote:
Hi folks,
Traditionally, when a new release of an upstream package was made, it
was reported via reopening an existing bug in bugzilla and changing its
title to reflect the new version number. With the conversion to 'trac'
this seems like the best time to switch to the
Hi folks,
Traditionally, when a new release of an upstream package was made, it
was reported via reopening an existing bug in bugzilla and changing its
title to reflect the new version number. With the conversion to 'trac'
this seems like the best time to switch to the same process that BLFS
On 2/4/06, Greg Schafer <[EMAIL PROTECTED]> wrote:
> Dan Nicholson wrote:
>
> > After looking over Configure for a while, I would suggest this
> >
> > sed -i 's,/usr/include,/tools/include,g' Configure
>
> Hmmm, yes it should work. But I believe hints/linux.sh is the place to
> sort this stuff ou
