AnsweredAssumed Answered

Who can give me some guide about how to compile and package a new package in ltib?

Question asked by zhiyan cao on Jun 16, 2013
Latest reply on Jun 18, 2013 by zhiyan cao

In ltib, I can compile all package provided by ltib release L2.6.35_10.11.01_ER_source_bundle.tar.gz, it can generate a rootfs directory.

But, this time, Provided the rootfs is not exist. I create a new package, for example vmware-open-client, I got source tar, and create the spec, I run ./ltib -m prep -p vmware-open-client, it is ok.

next step, ./ltib -m scbuild -p vmware-open-client, it can not work:


czy@czy-virtual-machine:~/imx51/ltib$ ./ltib -m scbuild vmware-open-client

The options prep, scbuild, scinstall and scdeploy are only allowed when working

on a single package, not a list.  You need to supply the option -p|--pkg <pkg>

czy@czy-virtual-machine:~/imx51/ltib$ ./ltib -m scbuild -p vmware-open-client



Processing: vmware-open-client


Build path taken because: directory build, build key set, no prebuilt rpm,



rpmbuild --dbpath /home/czy/imx51/ltib/rootfs//var/lib/rpm --target arm --define '_unpackaged_files_terminate_build 0' --define '_target_cpu arm' --define '__strip strip' --define '_topdir /home/czy/imx51/ltib/rpm' --define '_prefix /usr' --define '_tmppath /home/czy/imx51/ltib/tmp' --define '_rpmdir /home/czy/imx51/ltib/rpm/RPMS'  --define '_mandir /usr/share/man' --define '_sysconfdir /etc' --define '_localstatedir /var' -bc --short-circuit  /home/czy/imx51/ltib/dist/lfs-5.1/vmware-open-client/vmware-open-client.spec

Building target platforms: arm

Building for target arm

Executing(%build): /bin/sh -e /home/czy/imx51/ltib/tmp/rpm-tmp.60960

+ umask 022

+ cd /home/czy/imx51/ltib/rpm/BUILD

+ cd vmware-open-client-4.5.0

+ ./configure --prefix=/usr --host=arm-linux --build=i686-pc-linux-gnu

Configuring VMware-view-open-client 4.5.0-297975

checking build system type... i686-pc-linux-gnu

checking host system type... arm-unknown-linux-gnu

checking which interface to build... Gtk+

checking for arm-linux-pkg-config... no

checking for pkg-config... /opt/freescale/ltib/usr/bin/pkg-config

configure: WARNING: In the future, Autoconf will not detect cross-tools

whose name does not start with the host triplet.  If you think this

configuration is useful to you, please write to

checking pkg-config is at least version 0.9.0... yes

checking for GLIB... configure: error: Package requirements (glib-2.0 >= 2.6.0 gmodule-2.0 >= 2.6.0) were not met:



No package 'glib-2.0' found

No package 'gmodule-2.0' found



Consider adjusting the PKG_CONFIG_PATH environment variable if you

installed software in a non-standard prefix.



Alternatively, you may set the environment variables GLIB_CFLAGS

and GLIB_LIBS to avoid the need to call pkg-config.

See the pkg-config man page for more details.



error: Bad exit status from /home/czy/imx51/ltib/tmp/rpm-tmp.60960 (%build)





RPM build errors:

    Bad exit status from /home/czy/imx51/ltib/tmp/rpm-tmp.60960 (%build)

Build time for vmware-open-client: 1 seconds



Failed building vmware-open-client





f_scbuild() returned an error, exiting





Exiting on error or interrupt


I want to know the following 2 tips:

No package 'glib-2.0' found

No package 'gmodule-2.0' found


how to solve it, I need to build and install glib-2.0 and gmodule-2.0 using ltib, and when they are in rootfs/usr/lib or some other directory?