OpenCores
URL https://opencores.org/ocsvn/or1k/or1k/trunk

Subversion Repositories or1k

[/] [or1k/] [trunk/] [linux/] [uClibc/] [INSTALL] - Diff between revs 1325 and 1765

Only display areas with differences | Details | Blame | View Log

Rev 1325 Rev 1765
SOFTWARE REQUIREMENTS
SOFTWARE REQUIREMENTS
   Compiling uClibc requires Linux kernel header files.  uClibc will
   Compiling uClibc requires Linux kernel header files.  uClibc will
   be compiled to match the interfaces available in the provided
   be compiled to match the interfaces available in the provided
   version of the Linux kernel headers.  Linux kernel version 2.0,
   version of the Linux kernel headers.  Linux kernel version 2.0,
   version 2.2, version 2.4 and version 2.6 are known to work.  Other
   version 2.2, version 2.4 and version 2.6 are known to work.  Other
   kernel versions may work but havn't been tested.  Its also helpful
   kernel versions may work but havn't been tested.  Its also helpful
   to have a working version of GNU binutils, and GNU gcc -- using
   to have a working version of GNU binutils, and GNU gcc -- using
   excessively old versions of these packages can cause very strange
   excessively old versions of these packages can cause very strange
   errors that are difficult to find and fix.
   errors that are difficult to find and fix.
CONFIGURING uClibc:
CONFIGURING uClibc:
 - Use must have a valid configuration file to compile uClibc.  Do not
 - Use must have a valid configuration file to compile uClibc.  Do not
    skip this step.  New configuration options are added in each
    skip this step.  New configuration options are added in each
    release, and odd configuration options are sometimes removed.
    release, and odd configuration options are sometimes removed.
    To configure uClibc, you can run:
    To configure uClibc, you can run:
            make menuconfig
            make menuconfig
    or
    or
            make config
            make config
    If you have an existing .config file, you can update this file
    If you have an existing .config file, you can update this file
    using the
    using the
            make oldconfig
            make oldconfig
    command, which will only ask you about new configuration options.
    command, which will only ask you about new configuration options.
    Available configuration commands are:
    Available configuration commands are:
        "make config"       Text based configuration, no menus or colors.
        "make config"       Text based configuration, no menus or colors.
        "make menuconfig"   Text based color menus, radiolists & dialogs.
        "make menuconfig"   Text based color menus, radiolists & dialogs.
        "make oldconfig"    Default all questions based on the contents of
        "make oldconfig"    Default all questions based on the contents of
                             your existing ./.config file.
                             your existing ./.config file.
        "make defconfig"    Use defaults for all options.
        "make defconfig"    Use defaults for all options.
        "make randconfig"   Use random values for all options.
        "make randconfig"   Use random values for all options.
        "make allyesconfig" Set all values to "yes" for all options.
        "make allyesconfig" Set all values to "yes" for all options.
        "make allnoconfig"  Set all values to "no" for all options.
        "make allnoconfig"  Set all values to "no" for all options.
COMPILING uClibc:
COMPILING uClibc:
 - uClibc does not have proper dependancy checking (yet) so if you
 - uClibc does not have proper dependancy checking (yet) so if you
    change your uClibc configuration, you must current rebuild the
    change your uClibc configuration, you must current rebuild the
    entire library, by first running
    entire library, by first running
            make clean
            make clean
 - Once you have a valid configuration file, just run
 - Once you have a valid configuration file, just run
            make
            make
    to compile uClibc.  or if you are cross compiling, you would
    to compile uClibc.  or if you are cross compiling, you would
    instead run something like:
    instead run something like:
            make CROSS=arm-linux-
            make CROSS=arm-linux-
INSTALLING the uClibc development environment:
INSTALLING the uClibc development environment:
 - As root, if necessary, run something like:
 - As root, if necessary, run something like:
        make PREFIX= install
        make PREFIX= install
    This will install the uClibc runtime and development system (i.e.
    This will install the uClibc runtime and development system (i.e.
    all the header files, libraries, etc) into the directories defined
    all the header files, libraries, etc) into the directories defined
    within your .config file.
    within your .config file.
USING uClibc:
USING uClibc:
 - To compile programs with uClibc you will need a complete toolchain
 - To compile programs with uClibc you will need a complete toolchain
    (i.e. binutils, gcc, and uClibc) that was built expressly for use
    (i.e. binutils, gcc, and uClibc) that was built expressly for use
    with uClibc.
    with uClibc.
 - Native and cross compiling toolchains, as well as makefiles for creating
 - Native and cross compiling toolchains, as well as makefiles for creating
   uClibc toolchains, are available from the uClibc website.  You may want
   uClibc toolchains, are available from the uClibc website.  You may want
   to check out "buildroot", which is available from the uClibc download area,
   to check out "buildroot", which is available from the uClibc download area,
   which provides examples of how to build your own uClibc based system.
   which provides examples of how to build your own uClibc based system.
 
 

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.