[2] http://blog.csdn.net/wangzhong1979/archive/2010/02/08/5295777.aspx
[3] http://lists.gnu.org/archive/html/ltib/2010-11/msg00139.html
[4] http://lists.gnu.org/archive/html/ltib/2010-10/msg00008.html --- cross compiler
[5] http://www.linuxselfhelp.com/HOWTO/MIPS-HOWTO-9.html ---- cross compiler
[6] http://www.codesourcery.com/sgpp/lite/arm/portal/target_arch?@action=faq&target_arch=arm --- one provider where can download arm-nonlinux-guneabi
[7] http://www.codesourcery.com/sgpp/lite/arm ---GNU Tool Chain from CodeSourcery
[8] http://lists.gnu.org/archive/html/ltib/2010-10/msg00008.html --- Ltib not installing the cross compiler.
[9] https://wiki.linaro.org/Resources/FAQ ---- Org for Linux On ARM solution
[10]http://web.archiveorange.com/archive/v/zE6LZwICaTeR5uWNSWaW ----- Stuart Reply /proc make nods.
[11]mkfs.jffs2 man
USE DIFFERENT CROSS COMPILING TOOL CHAIN UNDER LTIB
---------------------------------------------
[4] [5]
[6] Why doesn't Sourcery G++ Lite Edition contain libraries for big-endian GNU/Linux? Or for systems with VFP or NEON?
Why does CodeSourcery provide GLIBC? Can I use the version that comes with my GNU/Linux distribution?
Why is the configuration name for GNU/Linux arm-none-linux-gnueabi instead of just arm-none-linux-eabi? Is there a GNU variant of the EABI?
Answer
The Free Software Foundation prefers that configuration names for GNU/Linux contain both the string linux and the string gnu. The configuration arm-none-linux-gnu refers to the legacy ARM ABI for GNU/Linux. Some tools depend on the fact that configuration names have at most three hyphens, so gnu and eabi were combined into a single word.
The ABI used on GNU/Linux is not a special GNU variant of the EABI; it is just the EABI.
-O2 -fsigned-char -mfloat-abi=softfp -mfpu=vfp
/home/quentin/CodeSourcery/arm-2010q1
arm-none-linux-gnueabi-
BUILD FROM SCRATCH
------------------------------------------------
Note:
This will remove rootfs and all configrations.
Build all packages and kernel from scratch.
[root@localhost ltib-qs]#./ltib -m distclean
[root@localhost ltib-qs]#./ltib --config
ADD CUSTOMER BSP INTO LTIB MENU
--------------------------------
Steps to Add your new board into LTIB menu (CM-HS1)
01-MAR-2012
1. Add new machine ID for the new board:
Register a machine ID for the new board via http://www.arm.linux.org.uk/developer/machines/ website and then update mach-types.h under /linux_kernel_dir/arch/arm/tools/ to the latest version;
2. Add new board information into the LTIB menus:
a. Make a folder for the new Board Support Package (BSP) under '/ltib/config/platform/'. The folder name should be the same as that defined in main.lkc, i.e., '/ltib/config/platform/gsncomm'. Please refer to 2.c below.
b. Copy all files from an existing Board Support Package (BSP) folder to the new BSP folder. We use the one we did the evaluation, i.e., from 'phy3250';
c. Make necessary changes to main.lkc under new BSP folder '/ltib/config/platform/$NEW_BOARD/'. All contents in main.lkc that are related to CPU and board need to be modified.
d. Create a Linux kernel pre-configuration file, e.g., 'linux-2.6.34-gsncomm.config'. This file can be manually generated by running the LTIB, which has Linux Kernel configuration GUI. 'linux-2.6.34-gsncomm.config' is generated based on 'linux-2.6.34-phy3250.config' with some modifications to mach GridSense Lpc 3240 board. 'linux-2.6.34-gsncomm.config' has to be stored under path '/ltib/config/platform/$NEW_BOARD/'
e. Overwrite the Linux board configuration file 'defconfig' and 'defconfig.dev' under ''/ltib/config/platform/$NEW_BOARD/' with your own board configuration file, in which different Linux kernel pre-configuration file, and installed Linux packages can be defined. New Linux board configuration file can also be generated with the help of LTIB, which has a Linux board configuration GUI. Basically, board configuration file will decide what application will be installed in Linux Root File System (RFS).
3. Add new BSP into to Linux Kernel (here we use lpc32xx based board as example):
a. Add new board choice to Kconfig under '/linux_kernel_src_dir/arch/arm/mach_lpc32xx/'. Add sub menu items if required;
b. Add board level initialisation BSP source code under the folder. It is recommended the main source code file name follow the board name. i.e., BSP source code 'gsncomm.c' under '/linux_kernel_src_dir/arch/arm/mach_lpc32xx/'.
c. Add board level initialisation code file(s) to the Makefile within the folder.
d. Copy Linux kernel pre-configuration file 'linux-2.6.34-gsncomm.config' to folder '/linux_kernel_src_dir/arch/arm/configs/' and rename it to 'gsncomm_defconfig'.
4. Use LTIB menu-based GUI to do further configuration and then build the kernel. Fix any error raised during porting.
CHOOSE CUSTOMER BSP
-------------------------
UPDATE ALL PACKAGES AND PATCHES FROM CVS
---------------------------------------------
Just run"cvs update" in your ltib directory. It'll fetch the updates and in the ltib config you can see the 2.6.34 kernel support.
MISSING NODES UNDER /DEV/
--------------------------------------
Has to change default phytect 'busybox.config', and add support for 'mdev'.
then /rootfs/sbin/mdev will appear and symbol link to busybox.
Make /DEV/ nodes from device_table.txt
If the target architecture is different from the original one, a different cross compiler will be needed. It will be downloaded and installed in the correct location if it isn't already present.
How to add device nodes
Device nodes with static major/minor numbers can be added to the file ltib/bin/device_table.txt. The format is described in the file itself.
Since there is no dependency checking for device_table.txt, after adding a new entry, force rebuild devices to make sure the new /dev nodes are in the file system:
$ ./ltib -p dev -f
MISSING /PROC/DEVICES
-------------------------------
After changing the property of all files under 'etc/rc.d/init.d/', adding 'x' right, problem is solved.
quentin@ubuntu:~/lpc3250/ltib-qs/rootfs$ sudo chmod a+x etc/rc.d/init.d/*
quentin@ubuntu:~/lpc3250/ltib-qs/rootfs$ ll etc/rc.d/init.d/
total 88
drwxr-xr-x 2 root root 4096 2011-06-10 16:56 ./
drwxr-sr-x 3 root root 4096 2011-06-11 08:14 ../
-rw-r--r-- 1 root root 357 2011-06-10 16:56 boa
-rw-r--r-- 1 root root 176 2011-06-10 16:56 depmod
-rw-r--r-- 1 root root 219 2011-06-10 16:56 devfsd
-rw-r--r-- 1 root root 904 2011-06-10 16:56 dhcp
-rw-r--r-- 1 root root 413 2011-06-10 16:56 dhcpd
-rw-r--r-- 1 root root 651 2011-06-10 16:56 dropbear
-rw-r--r-- 1 root root 1299 2011-06-10 16:56 filesystems
-rw-r--r-- 1 root root 183 2011-06-10 16:56 hostname
-rw-r--r-- 1 root root 342 2011-06-10 16:56 inetd
-rw-r--r-- 1 root root 741 2011-06-10 16:56 mdev
-rw-r--r-- 1 root root 165 2011-06-10 16:56 modules
-rw-r--r-- 1 root root 160 2011-06-10 16:56 mount-proc-sys
-rw-r--r-- 1 root root 5229 2011-06-10 16:56 network
-rw-r--r-- 1 root root 346 2011-06-10 16:56 portmap
-rw-r--r-- 1 root root 722 2011-06-10 16:56 settime
-rw-r--r-- 1 root root 279 2011-06-10 16:56 smb
-rw-r--r-- 1 root root 735 2011-06-10 16:56 sshd
-rw-r--r-- 1 root root 502 2011-06-10 16:56 syslog
-rw-r--r-- 1 root root 797 2011-06-10 16:56 udev
[l.lu@localhost ltib]$ ll rootfs/etc/rc.d/init.d/
total 84
-rwxr-xr-x 1 root root 357 2011-06-01 19:02 boa
-rwxr-xr-x 1 root root 176 2011-06-01 19:02 depmod
-rwxr-xr-x 1 root root 219 2011-06-01 19:02 devfsd
-rwxr-xr-x 1 root root 904 2011-06-01 19:02 dhcp
-rwxr-xr-x 1 root root 413 2011-06-01 19:02 dhcpd
-rwxr-xr-x 1 root root 651 2011-06-01 19:02 dropbear
-rwxr-xr-x 1 root root 1299 2011-06-01 19:02 filesystems
-rwxr-xr-x 1 root root 183 2011-06-01 19:02 hostname
-rwxr-xr-x 1 root root 1170 2011-06-01 19:12 hotplug
-rwxr-xr-x 1 root root 342 2011-06-01 19:02 inetd
-rwxr-xr-x 1 root root 741 2011-06-01 19:02 mdev
-rwxr-xr-x 1 root root 165 2011-06-01 19:02 modules
-rwxr-xr-x 1 root root 160 2011-06-01 19:02 mount-proc-sys
-rwxr-xr-x 1 root root 5229 2011-06-01 19:02 network
-rwxr-xr-x 1 root root 346 2011-06-01 19:02 portmap
-rwxr-xr-x 1 root root 722 2011-06-01 19:02 settime
-rwxr-xr-x 1 root root 279 2011-06-01 19:02 smb
-rwxr-xr-x 1 root root 735 2011-06-01 19:02 sshd
-rwxr-xr-x 1 root root 502 2011-06-01 19:02 syslog
-rwxr-xr-x 1 root root 797 2011-06-01 19:02 udev
HOW TO UNINSTALL LTIB
-----------------------------
[2] 在ubuntu系统上，假如ltib已经安装了，我们只需编译、重新配置ltib，
以非root用户登陆，进入ltib所在文件夹，依次输入以下两条命令：
./ltib clean
./ltib -c
即可先后配置linux应用软件包、linux内核。
编译成功后，~/ltib/rootfs/boot目录下，有新编译的内核文件uImage、设备树mpc8315erdb_default.dtb，分别拷贝到/tftpboot目录下。
MULTIPLE LTIB INSTALLATION
-----------------------------------
[1]Can I have more than one root file system on my host at the same time
Yes, the system will support multiple root file systems, for the same or for different target architectures.
If you are using an iso image, install your ltib archive into an different directory by entering a new directory name for the installation when prompted by the install script..
If you are using CVS, check-out CVS into a different directory by using the -d option to cvs co. For example:
ADD FILES TO THE TARGET ROOT FILE SYSTEM
------------------------------------------
[1] Can I add files to the target root file system without creating a package
Yes, to do this, you need to create a merge directory. There are 2 options:
1 Top level merge directory, that applies to all targets 2 Platform specific merge directory
The platform specific merge directory contents override the top level merge directory, which overrides the corresponding file(s) in your rootfs
Example:
You have a CVS version of LTIB, and you have build the tqm823l default configuration, now:
1 You want to add the a platform specific file /home/fred/myfile1 2 You want all platforms you may build to use your own /etc/hosts file
Here's what you would do:
$ cd
$ mkdir -p config/platform/tqm823l/merge/home/fred
$ cp
$ mkdir -p merge/etc
$ cp
$ ./ltib
CHECK LTIB LOCAL CVS REVISION
------------------------------------
[l.lu@localhost ltib]$ cd CVS/
[l.lu@localhost CVS]$ ll
total 16
-rw-rw-rw- 1 l.lu developer 215 2011-05-30 15:28 Entries
-rw-rw-rw- 1 l.lu developer 86 2011-05-30 15:28 Entries.Log
-rw-rw-rw- 1 l.lu developer 5 2011-05-30 15:28 Repository
-rw-rw-rw- 1 l.lu developer 57 2011-05-30 15:28 Root
-rw-rw-rw- 1 l.lu developer 0 2011-05-30 15:28 Template
[l.lu@localhost CVS]$ cat Entries
/.gitignore/1.1.1.2/Wed Mar 18 17:53:24 2009//
/.ltibrc/1.16/Tue Aug 17 18:18:00 2010//
/COPYING/1.1.1.2/Tue Nov 6 15:44:42 2007//
/README/1.1.1.3/Tue Nov 6 15:44:41 2007//
/ltib/1.75/Sat Apr 2 10:56:01 2011//
[l.lu@localhost CVS]$ cat Root
:pserver:anonymous@cvs.savannah.nongnu.org:/sources/ltib
[l.lu@localhost CVS]$ cat Repository
ltib
[l.lu@localhost CVS]$ cat Entries.Log
A D/bin////
A D/config////
A D/dist////
A D/doc////
A D/internal////
R D/internal////
BUILD RFS ROOT FILE SYSTEM
--------------------------------------
------++++check files/folders size under rootfs
[root@localhost ltib]# du -h rootfs/ | grep M
38M rootfs/boot
7.1M rootfs/usr/lib
1.4M rootfs/usr/include/openssl
3.3M rootfs/usr/include
1.1M rootfs/usr/sbin
7.0M rootfs/usr/bin
236K rootfs/usr/share/locale/uk/LC_MESSAGES
32K rootfs/usr/share/locale/ko/LC_MESSAGES
212K rootfs/usr/share/locale/da/LC_MESSAGES
----++++ trimmed unwanted files/folders in rootfs
----++++ force dev table if don't have enough in /rootfs/dev/
[l.lu@localhost ltib]$ ./ltib -p dev -f
Processing platform: Phytec 3250 board with the NXP LPC32XX SoC
=================================================================
using config/platform/phy3250/.config
Processing: dev
=================
Build path taken because: force set, build key set,
rpmbuild --dbpath /home/l.lu/lpc3250/ltib/rootfs//var/lib/rpm --target arm --define '_unpackaged_files_terminate_build 0' --define '_target_cpu arm' --define '__strip strip' --define '_topdir /home/l.lu/lpc3250/ltib/rpm' --define '_prefix /usr' --define '_tmppath /home/l.lu/lpc3250/ltib/tmp' --define '_rpmdir /home/l.lu/lpc3250/ltib/rpm/RPMS' --define '_mandir /usr/share/man' --define '_sysconfdir /etc' --define '_localstatedir /var' -bb --clean --rmsource /home/l.lu/lpc3250/ltib/dist/lfs-5.1/dev/dev.spec
Building target platforms: arm
Building for target arm
Executing(%prep): /bin/sh -e /home/l.lu/lpc3250/ltib/tmp/rpm-tmp.29641
+ umask 022
+ cd /home/l.lu/lpc3250/ltib/rpm/BUILD
+ cd /home/l.lu/lpc3250/ltib/rpm/BUILD
+ rm -rf dev-1.1
+ /bin/gzip -dc /home/l.lu/lpc3250/ltib/rpm/SOURCES/dev-1.1.tar.gz
+ tar -xvvf -
drwxr-xr-x seh/users 0 2005-03-23 22:48 dev-1.1/
-rw-r--r-- seh/users 5643 2005-03-23 06:49 dev-1.1/device_table.txt
-rwxr-xr-x seh/users 2187 2005-03-23 22:43 dev-1.1/mkrpmdev
-rw-r--r-- seh/users 766 2005-03-23 22:48 dev-1.1/dev.spec
-rw-r--r-- seh/users 34 2005-03-23 22:46 dev-1.1/Makefile
-rw-r--r-- seh/users 262 2005-03-23 22:47 dev-1.1/README
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd dev-1.1
+ exit 0
Executing(%build): /bin/sh -e /home/l.lu/lpc3250/ltib/tmp/rpm-tmp.29641
+ umask 022
+ cd /home/l.lu/lpc3250/ltib/rpm/BUILD
+ cd dev-1.1
+ exit 0
Executing(%install): /bin/sh -e /home/l.lu/lpc3250/ltib/tmp/rpm-tmp.29641
+ umask 022
+ cd /home/l.lu/lpc3250/ltib/rpm/BUILD
+ cd dev-1.1
+ rm -rf /home/l.lu/lpc3250/ltib/tmp/dev
+ '[' -f /home/l.lu/lpc3250/ltib/bin/device_table.txt ']'
+ DEV_TABLE=/home/l.lu/lpc3250/ltib/bin/device_table.txt
+ mkdir -p /home/l.lu/lpc3250/ltib/tmp/dev//opt/freescale/rootfs/arm//dev
+ ln -s /var/tmp/log /home/l.lu/lpc3250/ltib/tmp/dev//opt/freescale/rootfs/arm//dev/log
+ ln -s /proc/mounts /home/l.lu/lpc3250/ltib/tmp/dev//opt/freescale/rootfs/arm//dev/mtab
+ PREFIX=/opt/freescale/rootfs/arm/
+ perl mkrpmdev /home/l.lu/lpc3250/ltib/bin/device_table.txt
+ exit 0
Processing files: dev-1.1-1
Finding Provides: (using /opt/ltib/usr/lib/rpm/find-provides)...
Finding Requires: (using /opt/ltib/usr/lib/rpm/find-requires)...
PreReq: rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1
Requires(rpmlib): rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1
Wrote: /home/l.lu/lpc3250/ltib/rpm/RPMS/arm/dev-1.1-1.arm.rpm
Executing(%clean): /bin/sh -e /home/l.lu/lpc3250/ltib/tmp/rpm-tmp.98556
+ umask 022
+ cd /home/l.lu/lpc3250/ltib/rpm/BUILD
+ cd dev-1.1
+ rm -rf /home/l.lu/lpc3250/ltib/tmp/dev
+ rm -f /tmp/manifest
+ exit 0
Executing(--clean): /bin/sh -e /home/l.lu/lpc3250/ltib/tmp/rpm-tmp.98556
+ umask 022
+ cd /home/l.lu/lpc3250/ltib/rpm/BUILD
+ rm -rf dev-1.1
+ exit 0
Build time for dev: 2 seconds
sudo /opt/ltib/usr/bin/rpm --root /home/l.lu/lpc3250/ltib/rootfs --dbpath /var/lib/rpm -e --allmatches --nodeps --noscripts --define '_tmppath /tmp/ltib' dev 2>/dev/null
sudo /opt/ltib/usr/bin/rpm --root /home/l.lu/lpc3250/ltib/rootfs --dbpath /var/lib/rpm --prefix / --ignorearch -ivh --force --excludedocs --noscripts --define '_tmppath /tmp/ltib' /home/l.lu/lpc3250/ltib/rpm/RPMS/arm/dev-1.1-1.arm.rpm
error: failed to stat /home/l.lu/.gvfs: Permission denied
Preparing... ########################################### [100%]
1:dev ########################################### [100%]
Processing deployment operations
==================================
making filesystem image file
staging directory is /home/l.lu/lpc3250/ltib/rootfs.tmp
removing the boot directory and files
removing man files and directories
removing info files
removing /usr/src directory
removing /usr/include directory
removing /usr/share/locale directory
removing static libraries
removing target rpm database
stripping binaries and libraries
WARN: /home/l.lu/lpc3250/ltib/rootfs.tmp/sbin/sln statically linked
WARN: /home/l.lu/lpc3250/ltib/rootfs.tmp/sbin/ldconfig statically linked
WARN: /home/l.lu/lpc3250/ltib/rootfs.tmp/bin/busybox statically linked
Filesystem stats, including padding:
Total size = 38408k
Total number of files = 1055
running post build user command: . ../GsnComm_FlashRelease_copyUimgRfsToTftp.sh
cp: cannot stat `/home/l.lu/lpc3250/ltib/rootfs/boot/uImage': No such file or directory
Started: Thu Jun 2 10:40:31 2011
Ended: Thu Jun 2 10:40:57 2011
Elapsed: 26 seconds
Build Succeeded
--------++++Manually generate RFS
mkfs.jffs2 [ -p,--pad[=SIZE] ] [ -r,-d,--root directory ] [ -s,--pagesize=SIZE ] [ -e,--eraseblock=SIZE ] [ -c,--cleanmarker=SIZE ] [ -n,--no-cleanmarkers ] [ -o,--output image.jffs2 ] [ -l,--little-endian ] [ -b,--big-endian ] [ -D,--devtable=FILE ] [ -f,--faketime ] [ -q,--squash ] [ -U,--squash-uids ] [ -P,--squash-perms ] [ --with-xattr ] [ --with-selinux ] [ --with-posix-acl ] [ -m,--compression-mode=MODE ] [ -x,--disable-compressor=NAME ] [ -X,--enable-compressor=NAME ] [ -y,--compressor-priority=PRIORITY:NAME ] [ -L,--list-compressors ] [ -t,--test-compression ] [ -h,--help ] [ -v,--verbose ] [ -V,--version ] [ -i,--incremental image.jffs2 ]
Note: /rootfs/ has to be owned by root, so make sure
#chown -R root:root ./rootfs/ before manually generating RFS.
/opt/ltib/usr/bin/mkfs.jffs2 -n -r rootfs_working -m size -e 16 -o /tftpboot/rootfs.jffs2
[l.lu@localhost ltib]$ /opt/ltib/usr/bin/mkfs.jffs2 -n -r ./rootfs -m size -e 16 -o ./manual_rfs.jffs2
[l.lu@localhost ltib]$ /opt/ltib/usr/bin/mkfs.jffs2 -n -r ./manual_trimmed_rootfs_after-p-dev-f_bkup/rootfs/ -m size -e 16 -o ./manual_rfs.jffs2
use LTIB to build RFS auotmatically
-----------------------------------------------
[3]
$./ltib -m clean
$./ltib -m distclean
Removed whole rootfs folder after '-m distclean'
quentin@ubuntu:~/lpc3250/ltib-qs$ ./ltib -m distclean
You are about remove all the work you have been doing, are you really
sure you want to completely remove files from:
/home/quentin/lpc3250/ltib-qs/rootfs
To continue type in 'yes': yes
Removing target root filesystem
[sudo] password for quentin:
Processing: mkdistclean
=========================
Build path taken because: force set, build key set, no prebuilt rpm,
rpmbuild --dbpath ///home/quentin/lpc3250/ltib-qs/cleanupdb --target i686 --define '_unpackaged_files_terminate_build 0' --define '_target_cpu i686' --define '__strip strip' --define '_topdir /home/quentin/lpc3250/ltib-qs/rpm' --define '_prefix /usr' --define '_tmppath /home/quentin/lpc3250/ltib-qs/tmp' --define '_rpmdir /home/quentin/lpc3250/ltib-qs/rpm/RPMS' --define '_mandir /usr/share/man' --define '_sysconfdir /etc' --define '_localstatedir /var' -bb --clean --rmsource /home/quentin/lpc3250/ltib-qs/dist/lfs-5.1/mkdistclean/mkdistclean.spec
Building target platforms: i686
Building for target i686
Executing(%prep): /bin/sh -e /home/quentin/lpc3250/ltib-qs/tmp/rpm-tmp.46763
+ umask 022
+ cd /home/quentin/lpc3250/ltib-qs/rpm/BUILD
+ exit 0
Executing(%build): /bin/sh -e /home/quentin/lpc3250/ltib-qs/tmp/rpm-tmp.46763
+ umask 022
+ cd /home/quentin/lpc3250/ltib-qs/rpm/BUILD
+ exit 0
Executing(%install): /bin/sh -e /home/quentin/lpc3250/ltib-qs/tmp/rpm-tmp.46763
+ umask 022
+ cd /home/quentin/lpc3250/ltib-qs/rpm/BUILD
+ : /home/quentin/lpc3250/ltib-qs/rootfs
+ '[' '!' -d /home/quentin/lpc3250/ltib-qs/rootfs ']'
+ '[' /home/quentin/lpc3250/ltib-qs/rootfs = / ']'
+ '[' 1000 = 0 ']'
+ '[' '!' -O /home/quentin/lpc3250/ltib-qs/rootfs ']'
+ rm -rf /home/quentin/lpc3250/ltib-qs/tmp/mkdistclean
+ mkdir -p /home/quentin/lpc3250/ltib-qs/tmp/mkdistclean//opt/freescale/rootfs/i686
+ cd /home/quentin/lpc3250/ltib-qs/rootfs
+ set +e
+ find -type d -exec mkdir -p '/home/quentin/lpc3250/ltib-qs/tmp/mkdistclean//opt/freescale/rootfs/i686/{}' ';'
+ find . '!' -type d -exec touch '/home/quentin/lpc3250/ltib-qs/tmp/mkdistclean//opt/freescale/rootfs/i686/{}' ';'
+ exit 0
+ mkdir -p /home/quentin/lpc3250/ltib-qs/tmp/mkdistclean//opt/freescale/rootfs/i686/root/.ssh
+ touch /home/quentin/lpc3250/ltib-qs/tmp/mkdistclean//opt/freescale/rootfs/i686/root/.ssh/known_hosts
+ touch /home/quentin/lpc3250/ltib-qs/tmp/mkdistclean//opt/freescale/rootfs/i686/.ash_history
Processing files: mkdistclean-1.0-1
Finding Provides: (using /opt/ltib/usr/lib/rpm/find-provides)...
Finding Requires: (using /opt/ltib/usr/lib/rpm/find-requires)...
PreReq: rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1
Requires(rpmlib): rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1
Wrote: /home/quentin/lpc3250/ltib-qs/rpm/RPMS/i686/mkdistclean-1.0-1.i686.rpm
Executing(%clean): /bin/sh -e /home/quentin/lpc3250/ltib-qs/tmp/rpm-tmp.23031
+ umask 022
+ cd /home/quentin/lpc3250/ltib-qs/rpm/BUILD
+ rm -rf /home/quentin/lpc3250/ltib-qs/tmp/mkdistclean
+ exit 0
Executing(--clean): /bin/sh -e /home/quentin/lpc3250/ltib-qs/tmp/rpm-tmp.23031
+ umask 022
+ cd /home/quentin/lpc3250/ltib-qs/rpm/BUILD
+ exit 0
Build time for mkdistclean: 15 seconds
sudo /opt/ltib/usr/bin/rpm --root / --dbpath /home/quentin/lpc3250/ltib-qs/cleanupdb -e --allmatches --nodeps --noscripts --define '_tmppath /home/quentin/lpc3250/ltib-qs/tmp' mkdistclean 2>/dev/null
sudo /opt/ltib/usr/bin/rpm --root / --dbpath /home/quentin/lpc3250/ltib-qs/cleanupdb --prefix /home/quentin/lpc3250/ltib-qs/rootfs --ignorearch -ivh --force --excludedocs --noscripts --define '_tmppath /home/quentin/lpc3250/ltib-qs/tmp' /home/quentin/lpc3250/ltib-qs/rpm/RPMS/i686/mkdistclean-1.0-1.i686.rpm
error: failed to stat /home/quentin/.gvfs: Permission denied
Preparing... ########################################### [100%]
1:mkdistclean ########################################### [100%]
sudo /opt/ltib/usr/bin/rpm --root / --dbpath /home/quentin/lpc3250/ltib-qs/cleanupdb -e --allmatches --noscripts --define '_tmppath /home/quentin/lpc3250/ltib-qs/tmp' mkdistclean
error: failed to stat /home/quentin/.gvfs: Permission denied
quentin@ubuntu:~/lpc3250/ltib-qs$ ll rootfs_image
lrwxrwxrwx 1 quentin developer 14 2011-05-31 11:05 rootfs_image -> ./rootfs.jffs2
quentin@ubuntu:~/lpc3250/ltib-qs$ ll
total 288
drwxrwxrwx 8 quentin quentin 4096 2011-06-01 08:52 ./
drwxr-xr-x 4 quentin quentin 4096 2011-05-26 12:37 ../
-rwxr--r-- 1 quentin quentin 886 2011-05-25 11:55 2869_ltib.patch*
drwxrwxrwx 3 quentin quentin 4096 2011-06-01 08:52 bin/
drwxrwxrwx 7 quentin quentin 4096 2011-06-01 08:52 config/
-rw-rw-rw- 1 quentin quentin 17989 2007-11-07 02:44 COPYING
drwxrwxrwx 2 quentin quentin 4096 2011-05-24 14:50 CVS/
drwxrwxrwx 4 quentin quentin 4096 2011-05-24 14:50 dist/
drwxrwxrwx 3 quentin quentin 4096 2011-05-24 14:50 doc/
-rw-rw-rw- 1 quentin quentin 436 2009-03-19 04:53 .gitignore
-rwxrwxrwx 1 quentin quentin 110719 2011-05-25 11:57 ltib*
-rwxrwxrwx 1 quentin quentin 110337 2011-04-02 21:56 ltib.orig*
-rw-rw-rw- 1 quentin quentin 2579 2010-08-18 04:18 .ltibrc
-rw-rw-rw- 1 quentin quentin 952 2007-11-07 02:44 README
lrwxrwxrwx 1 quentin developer 14 2011-05-31 11:05 rootfs_image -> ./rootfs.jffs2
drwxrwsr-x 3 quentin quentin 4096 2011-06-01 08:52 rpm/
quentin@ubuntu:~/lpc3250/ltib-qs$
NOTES FROM LtibConvertPcsBsp
-----------------------------------------
-----+++ Deploying the BSP
The primary deployment mechanism in ltib is expected to be NFS. By
default ltib will build a root filesystem suitable for exporting as
a root filesystem in ~/ltib/rootfs . It is the user's responsibility
to export this directory and setup the bootloader parameters to
use this. Note that the built kernel can be located in ~/ltib/rootfs/boot
---++ Saving your work
Once you have booted your board and are happy to check in your work,
you need to do the following:
* copy the updated .config to defconfig
* checking ltib changes to CVS
* copy new source files to the GPP
No comments:
Post a Comment