I have a simple newbie question on LFS:
Section 5.3.1 of version 6.1 of the book instructs you
to enter:
mkdir ../binutils-build
cd ../binutils-build
and later
../binutils-2.15.94.0.2.2/configure --prefix=/tools
--disable-nls
I understand that ../ implies the parent directory of
the current
ralph jefferies wrote:
I have a simple newbie question on LFS:
Section 5.3.1 of version 6.1 of the book instructs you
to enter:
mkdir ../binutils-build
cd ../binutils-build
and later
../binutils-2.15.94.0.2.2/configure --prefix=/tools
--disable-nls
I understand that ../ implies the
ralph jefferies wrote:
I have a simple newbie question on LFS:
Section 5.3.1 of version 6.1 of the book instructs you
to enter:
mkdir ../binutils-build
cd ../binutils-build
and later
../binutils-2.15.94.0.2.2/configure --prefix=/tools
--disable-nls
I understand that ../ implies the parent
Ilja Honkonen wrote:
Archaic wrote:
On Sun, Sep 04, 2005 at 12:11:08PM +0300, Ilja Honkonen wrote:
No it did not, I noticed this when Groff wouldn't configure
complaining that
it couldn't compile c++ programs. There were no gcc or c++ or even cc in
/usr/bin. Very strange, but everyting
Chris Staub wrote:
[snipped a lot of the previous thread]
You shouldn't have to symlink anything unless it tells you to in the
book. If you do have to then you need to go back and figure out what's
wrong before going any further. You should go back to the gcc
installation in chap. 6, and
Dan McGhee wrote these words on 09/05/05 15:48 CST:
What I lose with this method is the delete_package of the hint. For
packages that have a 'make uninstall' target this is irrelevant.
Meaning you trust a package developer to clean up your disk for
you? And I'm sure all those packages where
Randy McMurchy wrote:
Dan McGhee wrote these words on 09/05/05 15:48 CST:
What I lose with this method is the delete_package of the hint. For
packages that have a 'make uninstall' target this is irrelevant.
Meaning you trust a package developer to clean up your disk for
you? And
LFS-6.1 build
I build a kernel (2.6.11.12) for my scratch built system and it populates
/dev with the wrong permissions, ie /dev/null with crw-rw permissions.
Non root users can not access it example: echo Cat shit /dev/null.
Fails with Permission denied. (because of 660 perms)
Why would
On 9/3/05, S. Anthony Sequeira [EMAIL PROTECTED] wrote:
This is NOT a problem, unless one of the functions sets a variable, or cd's to
a directory (typically in the configure_commands function, the way I use it
at least), and the variable needs to be accessible later, or later commands
need to
