Welcome![Sign In][Sign Up]
Location:
Search - gcc-3.3.6.t

Search list

[Embeded Linuxsmp86xx_rootfs.tar.bz2

Description:

 sigma smp8634/8635 toolchain rootfs building source.

=================

Readme.txt

=================

 

This is the Sigma Designs customization of the root file system for the

SMP86xx family of chips.

 

This package is of course heavily depending on the toolchain and kernel

packages.

 

Quick HOW-TO

============

a) You need to have a working toolchain package. Once you have built your 

   toolchain, be sure to source toolchain-path.env. This is required for you to

   be able to build the rootfs package.

b) Untar the rootfs package.

c) First, configure your root file system: 'make menuconfig'. All the options 

   in the configuration menus have detailed help. Once you are satisfied with

   your choice of options, exit and save the configuration.

d) If you are using the toolchain composed of gcc 3.4.2, binutils 2.15.91.0.2,

   and uClibc 0.9.27 (defined in the toolchain package) then you must select

   Busybox 1.00 from the 'Package Selection for the target --->' menu.

   If on the other hand you are using the toolchain composed of gcc 4.0.4,

   binutils 2.17, and uClibc 0.9.28.3 then you must select Busybox 1.5 from

   the 'Package Selection for the target --->' menu.

e) If you chose to customize your root file system (option 'customize' in

   submenu 'Package Selection for the target'), be sure to prepare your custom

   files now.

f) Run 'make' to produce your root file system.

 

IMPORTANT NOTE: as of this release, the only supported option in the 'Target 

Options' menu is 'cramfs root filesystem for the target device' (with all its

suboptions). Any other option is currently unsupported and some are known to

not work.

 

Once you are through with step e), your root file system is available in the

main directory of the package as 'root_fs_mipsel.cramfs'.

 

Note about the integration with the toolchain and the kernel source packages

============================================================================

The rootfs package is now integrated with the toolchain package and the 

kernel source package and is able to interact with them in the following

ways:

 

 a) it can grab the necessary runtime libraries from the toolchain package.

 b) it can receive the kernel modules and support files from the kernel source

    package.

 c) the kernel source package can use the produced rootfs image for its initial

    RAM disk.

 

For interaction a) to take place, the SMP86XX_TOOLCHAIN_PATH environment 

variable must be defined and it must point to the main directory of the 

produced toolchain. The easiest way to achieve that is by sourcing the

'toolchain-path.env' environment file after it is produced at the end of the

toolchain production.

 

Note that defining SMP86XX_TOOLCHAIN_PATH is not optional. The build will not

go through unless the environment variable is defined and points to a correct

location. This is because, even if the build went through, the resulting root

file system would be unusable as it would not provide *any* run time library.

 

For interactions b) and c) to take place, the SMP86XX_ROOTFS_PATH environment

variable must be defined and must point to the main directory of the rootfs

package. The easiest way to achieve that is by sourcing the 'rootfs-path.env'

environment file after it is produced, right after your run 'make' or 

'make menuconfig' for the first time.

 

When SMP86XX_ROOTFS_PATH is defined and points to a valid location, the kernel

source package is able to:

 

 b) install its modules to the correct location under the customization 

    directory ('package/customize/source') in the rootfs package. In order to

    then make sure the modules end up in the produced rootfs image, you must

    select the 'customize' option under the 'Package Selection for the target'

    menu in 'make menuconfig'.

 c) grab the produced rootfs image (root_fs_mipsel.cramfs) and use it for its

    initial RAM disk.

 

Thus, in order to produce a rootfs holding the kernel modules and use it as the

kernel initial RAM disk, you need to go through the following steps in order

(note: this is convoluted):

 1) optionally build the toolchain (or use an existing one, more recent than

    2.6.90.0)

 2) source toolchain-path.env in the toolchain package directory

 3) configure the rootfs package with the 'customize' option on in the

    'Package Selection for the target' menu

 4) source 'rootfs-path.env' in the rootfs package directory

 5) configure the kernel, review what is configured as modules, 'make dep'

 6) 'make modules' in the kernel source directory

 7) the 'modules_install' target for the kernel needs that the system map be

    already produced. In order to achieve that, build a first version of the

    kernel: 'make vmlinux'

 8) 'make modules_install' in the kernel source directory. The modules are now

    installed in the rootfs package customization directory.

 9) 'make' in the rootfs package directory. You have now produced a rootfs 

    image holding the kernel modules.

10) 'make' in the kernel source directory. You have now produced a linux ZBF

    image with an initrd holding the kernel modules.

    

Coming features

===============

N/A

 

Troubleshooting

===============

a) when building the cramfs utility tool, the compiler complains that it can't

   find 'zlib.h' or '-lz'.

 

   You need to have the development version of zlib installed on your system.

   How to do that depends on your distribution.

 

 


Platform: | Size: 234248 | Author: mattli001 | Hits:

[SCMAVRcam_rel_1_4

Description: he AVRcam source files were built using the WinAVR distribution (version 3.3.1 of GCC). I haven t tested other versions of GCC, but they should compile without too much difficulty. The makefile used to build the source is included-he AVRcam source files were built using the WinAVR distribution (version 3.3.1 of GCC). I h aven not tested other versions of GCC. but they should compile without too much diffic ulty. The makefile used to build the source is in cluded
Platform: | Size: 140288 | Author: chezhen | Hits:

[ARM-PowerPC-ColdFire-MIPSAVR_Camera

Description: The AVRcam source files were built using the WinAVR distribution (version 3.3.1 of GCC). I haven t tested other versions of GCC, but they should compile without too much difficulty. * The source files for the AVRcam had the author name and copyright information added back into them after the judging of the project, since it states in the competition rules that the author s name can not be present during their inspection. * The included source files are the ones that were submitted for the entry into the Circuit Cellar contest. I have continued to develop the AVRcam, and have added several new features (such as ignoring objects that aren t larger than a minimum size, removing tracked objects that overlap with each, and some general optimizations). If you are interested in the latest source, email me at john@jrobot.net * For more info about the AVRcam, check out http://www.jrobot.net John Orlando August 20, 2004-The AVRcam source files were built using the WinAVR distribution (version 3.3.1 of GCC). I haven t tested other versions of GCC, but they should compile without too much difficulty .* The source files for the AVRcam had the author name and copyrightinformation added back into them after the judging of the project, since it states in the competition rules that the author s name can not be present during their inspection.* The included source files are the ones that were submitted forthe entry into the Circuit Cellar contest. I have continued todevelop the AVRcam, and have added several new features (such asignoring objects that aren t larger than a minimum size, removingtracked objects that overlap with each, and some general optimizations). If you are interested in the latest source, email me at john@jrobot.net* For more info about the AVRcam, check out http://www.jrobot.netJohn OrlandoAugust 20, 2004
Platform: | Size: 55296 | Author: 袁君 | Hits:

[Linux-Unixgcc-3.3.6.tar

Description: linux下的gcc编译器,有需要请支持一下-gcc Compiler
Platform: | Size: 31493120 | Author: 葛军晓 | Hits:

[File Format200841613515595

Description: 下载vsftpd-2.0.6.tar.gz 网上很好找的,附件也提供下载,解压。 tar zxvf vsftpd-2.0.6.tar.gz 修改解压包内文件MakeFile,改交叉编译器,我的路径是 # Makefile for systems with GNU tools CC= /usr/local/arm/3.4.1/bin/arm-linux-gcc 直接编译会出错,还要改一个包含库文件的文件vsf_findlibs.sh 把下面两句屏蔽掉吧-Download vsftpd-2.0.6.tar.gz easy to find online, and accessories are also available for download, unzip. tar zxvf vsftpd-2.0.6.tar.gz modify the extract package files MakeFile, change cross-compiler, my path is# Makefile for systems with GNU tools CC =/usr/local/arm/3.4.1/bin/arm-linux-gcc directly translated to be wrong, but also to change a library file that contains the following two masked vsf_findlibs.sh Bar
Platform: | Size: 197632 | Author: qwe | Hits:

[OtherLinuxmasn

Description: 汇编语言开发指南 一、简介 二、LINUX汇编语法格式(AT&T与INTEL汇编的区别) 三、简单程序 四、LINUX汇编工具 五、系统调用 六、命令行参数 七、GCC内联汇编 八、小结-1, Introduction 2, LINUX compilation syntax (AT & T and the difference between INTEL compilation) 3, a simple procedure 4, LINUX compilation tools 5, system calls 6, command-line parameter 7, GCC inline assembly 8, Summary
Platform: | Size: 168960 | Author: 陈智新 | Hits:

[Special EffectscximageLite_V600

Description: CxImage is a C++ class that can load, save, display, transform images in a very simple and fast way. CxImage is open source and licensed under the zlib license. In a nutshell, this means that you can use the code however you wish, as long as you don t claim it as your own. With more than 200 functions, and with comprehensive working demos, CxImage offers all the tools to build simple image processing applications on a fast learning curve. Supported file formats are: BMP, GIF, ICO, CUR, JBG, JPG, JPC, JP2, PCX, PGX, PNG, PNM, RAS, SKA, TGA, TIF, WBMP, WMF, RAW, CRW, NEF, CR2, DNG, ORF, ARW, ERF, 3FR, DCR, X3F, MEF, RAF, MRW, PEF, SR2. Cximage is highly portable and has been tested with Visual C++ 6 / 2008, C++ Builder 3 / 6, MinGW on Windows, and with gcc 3.3.2 on Linux. The library can be linked statically, or through a DLL or an activex component.
Platform: | Size: 563200 | Author: tayfun karan | Hits:

[OpenGL programglm-0.9.0.6

Description: OpenGL Mathematics (GLM) is a C++ mathematics library for 3D software based on the OpenGL Shading Language (GLSL) specification. The goal of the project is to provide to 3D programmers math classes and functions that miss in C++ when we use to program with GLSL or any high level GPU language. With GLM, the idea is to have a library that works the same way that GLSL which imply a strict following of GLSL specification for the implementation. However, this project isn t limited by GLSL features. An extension system allows to extend GLSL capabilities. It allows GLM to be a great subtitute for some OpenGL 3 deprecated functions, to work following a clean programmable approach. GLM is release under MIT license and available for all version of GCC from version 3.4 and Visual Studio from version 8.0 as a platform independent library.
Platform: | Size: 1390592 | Author: Sukuma Ubhada | Hits:

[uCOSuTenux

Description: µ Tenux嵌入式实时操作系统是基于日本T-Kernel开发而来,从2009年发布升级至今。上传版本为V1.6版本。 1、现在已经支持IAR、Keil、eclipse+gcc三个环境。 2、主要支持ARM7/9、全线支持Cortex-M0、3、4的ARM内核芯片 3、支持CMSIS 4、只要应用医疗电子、工业控制、办公电子等 5、uTenux学习讨论群:218329305(CSDN推荐)-μTenux embedded real-time operating system is based on the Japanese developed from T-Kernel, published from 2009 to upgrade now. Upload version V1.6 version. 1, and now has support for IAR, Keil, eclipse+ gcc three environments. 2, the main support for ARM7/9, across the board support for Cortex-M0, 3,4 ARM core chip 3, support CMSIS 4, as long as the application of medical electronics, industrial control, office electronics 5, uTenux learning discussion groups: 218329305 (CSDN recommended)
Platform: | Size: 2995200 | Author: 马梦雪 | Hits:

[Linux-Unixtype_traits

Description: MSVC can t compile this correctly, and neither can gcc 3.3.5 (at least).
Platform: | Size: 4096 | Author: wnjbher | Hits:

[Linux-Unixstrokes

Description: MSVC can t compile this correctly, and neither can gcc 3.3.5 (at least).
Platform: | Size: 10240 | Author: zuqora | Hits:

CodeBus www.codebus.net