Is it normally?

Bruce Dubbs bruce.dubbs at gmail.com
Sun Mar 20 11:46:04 PDT 2011


gdsi at mail.com wrote:
> On Sun, 2011-03-20 at 19:20 +0300, gdsi at mail.com wrote:
>> On Sun, 2011-03-20 at 10:28 -0500, Bruce Dubbs wrote:
>>> gdsi at mail.com wrote:
>>>> Good day.
>>>> I done 5.5. GCC-4.5.2 - Pass 1 After "make install" end of screen was:
>>>> make[2]: Leaving directory
>>>> `/mnt/lfs/sources/gcc-build/i686-lfs-linux-gnu/libgcc'
>>>> make[1]: Leaving directory `/mnt/lfs/sources/gcc-build'
>>>>
>>>> After: ln -vs libgcc.a `$LFS_TGT-gcc -print-libgcc-file-name | \
>>>>     sed 's/libgcc/&_eh/'`, 
>>>> screen was:
>>>> `/mnt/lfs/tools/bin/../lib/gcc/i686-lfs-linux-gnu/4.5.2/libgcc_eh.a' ->
>>>> `libgcc.a'.
>>>> I went to "/mnt/lfs/sources" and deleted "gcc-build" and "gcc-4.5.2".
>>>>
>>>> In next chapter was:
>>>> lfs at shpd-78-36-184-253:/mnt/lfs/sources$ make mrproper
>>>> make: *** No rule to make target `mrproper'.  Stop.
>>> Did you extract the linux kernel and change to it's directory first?
>>>
>>>    -- Bruce
>> ------------- gdsi
>> I work exactly by the book, but Debian is sending updates, and I do not
>> know what he does.
>> ----gdsi
> To Bruce, excuse me, are you  speak about the quotation from the book?: 
> "Now test and extract the user-visible kernel headers from the source.
> They are placed in an intermediate local directory and copied to the
> needed location because the extraction process removes any existing
> files in the target directory."
>  If yes, give me a time understand this.

You expand the linux tarball just like any other package.  The 
instructions given "extract the user-visible kernel headers" and install 
them to your system.

   -- Bruce



More information about the lfs-support mailing list