Skip to main content.
Navigation:
DENX
>
DULG
>
ELDKRebuildingComponents
Translations:
Edit
|
Attach
|
Raw
|
Ref-By
|
Printable
|
More
DULG
Sections of this site:
DENX Home
|
DULG
|
ELDK-5
|
Know
|
Training
|
U-Boot
|
U-Bootdoc
Topics
DULG Home
BoardSelect
Manual
FAQ
Application Notes
Changes
Index
List of pages in DULG
Search
%SECTION0{name=ELDKRebuildingComponents}% Rebuilding ELDK Components %SECTION1{name=ELDKSources}% ELDK Source Distribution The ELDK is distributed with the full sources of all the components, so you may rebuild any ELDK package. The sources are provided in the form of SRPM packages, distributed as a separate ISO image. To rebuild a target or ELDT package, you must first install the appropriate source RPM package from the ISO image into the ELDK environment. This can be done using the following command: <verbatim> $ ${CROSS_COMPILE}rpm -i /mnt/cdrom/SRPMS/<source_rpm_file_name>.src.rpm </verbatim> After an ELDK source RPM is installed using the above command, its spec file and sources can be found in the subdirectories of the _<ELDK_root>/usr/src/denx_ subdirectory. The sections that follow provide detailed instructions on rebuilding ELDT and target components of the ELDK. %SECTION1{name=ELDKRebuildTargetRpm}% Rebuilding Target Packages All the target packages can be rebuilt from the provided source RPM packages. At first you have to install the Source RPM itself: <verbatim> bash$ ${CROSS_COMPILE}rpm -iv <package_name>.src.rpm </verbatim> Then you can rebuild the binary target RPM using the following command from the ELDK environment: <verbatim> bash$ ${CROSS_COMPILE}rpmbuild -ba <package_name>.spec </verbatim> In order for the rebuilding process to work correctly, the following conditions must be true: * The [[ELDKUsage#Table_CrossCompile][$CROSS_COMPILE]] environment variable must be set as appropriate for the target CPU family. * The %IF{ "%ARCHITECTURE%" eq "powerpc" }% _<ELDK_root>/usr/ppc-linux/bin_ %ENDIF% %IF{ "%ARCHITECTURE%" eq "arm" }% _<ELDK_root>/usr/arm-linux/bin_ %ENDIF% %IF{ "%ARCHITECTURE%" eq "mips" }% _<ELDK_root>/usr/mips-linux/bin_ %ENDIF% directory must be in =PATH= before the _/usr/bin_ directory. This is to make sure that the command =gcc= results in the fact that the ELDK cross compiler is invoked, rather than the host =gcc=. The newly built package can then be installed just as easily: <verbatim> bash$ ${CROSS_COMPILE}rpm -i <package_name>.rpm </verbatim> %SECTION1{name=ELDKRebuildToolRpm}% Rebuilding ELDT Packages All the ELDT packages allow for rebuilding from the provided source RPM packages using the following command from the ELDK environment: <verbatim> $ unset CROSS_COMPILE $ <ELDK_root>/usr/bin/rpmbuild -ba <package_name.spec> </verbatim> In order for the rebuilding process to work correctly, make sure all of the following is true: * The [[ELDKUsage#Table_CrossCompile][$CROSS_COMPILE]] environment variable must *NOT* be set. * Do *NOT* use the [[ELDKUsage#Table_CrossCompile][$CROSS_COMPILE]] command prefix. * The %IF{ "%ARCHITECTURE%" eq "powerpc" }% _<ELDK_root>/usr/ppc-linux/bin_ %ENDIF% %IF{ "%ARCHITECTURE%" eq "arm" }% _<ELDK_root>/usr/arm-linux/bin_ %ENDIF% %IF{ "%ARCHITECTURE%" eq "mips" }% _<ELDK_root>/usr/mips-linux/bin_ %ENDIF% directory must *NOT* be in =PATH=. This is to make sure that the command =gcc= causes invokation of the host =gcc=, rather than the ELDK cross compiler. Note that the newly built package should be installed with the "global" =rpm=, not with the arch specific one: <verbatim> bash$ <ELDK_root>/bin/rpm -i <package_name>.rpm </verbatim>
3.7. Mounting Target Components via NFS
1. Abstract
3.9. ELDK Packages
Prev
Home
Next