[SOLVED] iMX53 Quick Start Board - LTIB Build Succeeded for [FSL gnome release Package] but (VGA) STARTX FAIL !

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

[SOLVED] iMX53 Quick Start Board - LTIB Build Succeeded for [FSL gnome release Package] but (VGA) STARTX FAIL !

9,226 Views
DannyChin_ng
Contributor I

Hi

      I am currently working on i.MX53 QSB following the Freescale manual   "i.MX53_START_Linux_BSP_UserGuide.pdf" and it did mentioned that "Please note that only the profiles of Min profile, FSL gnome release packages and mfg firmware profile pass build tests."Below are some tests carried out to verify the above statement, the goal is to create a minimum Linux Desktop rootfs (with X) similiar to the MicroSD - Ubuntu 10.04 (Lucid) image which is came together inside the iMX53 QSB Box.

Test Procedure
=========================
Using the VM_Ubuntu.zip Vmware image provided by Freescale running in Vmware Player.

[LTIB Home Directory ]> ./ltib -c   OR  ./ltib --selectype (if you run it next time)

Screen 1:
  - Platform choice: (Freescale iMX reference boards)
Screen 2:
  - Choose the platform type: mx5x
  - packages profile: use packages in [FSL gnome release package]
Screen 3 (LTIB main menu):
  - Choose your board for u-boot: mx53_loco

* [Exit] and Start building .....


Below is the Test Result for each build profile type.

*** Pls Note that each test could take from 20 minutes to 4-7 hours.***

#############################################################################
Preconfig Min Profile - OK
#############################################################################


Test1: Succeed
==================================

- Follow the above Test Procedure
- Build success !
- Flashed the newly built u-boot,kernel and rootfs inside a MicroSD, follow Freescale guide and tweaking the u-boot prompt to boot from MMC an it tested OK inside iMX53 QSB with user root (without any password required).

- However, this rootfs is without X like Ubuntu Desktop , so I need to proceed to build the FSL gnome release package.

#############################################################################
FSL gnome release package - OK
#############################################################################

Test1: Fail !

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

- Follow the above Test Procedure

- Build Fail !

- LTIB will start configuring and building, after long hours during building gnome-vfs ....

- Main Error =>

"cannot find -lgssapi_krb5"

- Suspect => Missing Kerberos 5 authentication

 

 

Test2: Fail !

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

- Goal => Trying to solve "cannot find -lgssapi_krb5"

- Follow up from Test1:

- [LTIB]> ./ltib -m config

- Screen 3 -> Package list, add:
    [ * ] Kerberos 5 authentication

- [LTIB]> ./ltib

- LTIB will start fetching krb5-1.3.4, during configuring ....

- Build Fail !

- Main Error =>

checking for res_search... no
checking for res_search in -lresolv... no
configure: error: Cannot find resolver support routine res_search in -lresolv.

 

Test3: Fail !

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

- Goal => Trying to bypass "Cannot find resolver support routine res_search in -lresolv"

- Follow up from Test2:

- Make change to [LTIB]/dist/lfs-5.1/krb5/krb5.spec
config_opts='ac_cv_func_regcomp=yes ac_cv_file__etc_environment=yes ac_cv_file__etc_TIMEZONE=yes ac_cv_func_res_search=yes'

- [LTIB]> ./ltib

- LTIB will start configuring and building ...

- Build Fail !

- Main Error =>

hst_realm.c: In function 'krb5int_translate_gai_error':
hst_realm.c:442: error: 'EAI_NODATA' undeclared (first use in this function)
hst_realm.c:442: error: (Each undeclared identifier is reported only once
hst_realm.c:442: error: for each function it appears in.)
make[3]: *** [hst_realm.o] Error 1
make[3]: *** Waiting for unfinished jobs....
In file included from ../../../include/k5-int.h:143,
                 from krbfileio.c:42:

 

Test4: Fail !

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

- Goal => Trying to solve Test3 build errors

- Patching ....

Patch Manually => [ltib]/rpm/BUILD/krb5-1.3.4/src/lib/krb5/os/hst_realm.c
with => http://repository.timesys.com/buildsources/k/krb5/krb5-1.4.4/krb5-1.4.4-eai_nodata.patch

Patch Manually => [ltib]/rpm/BUILD/krb5-1.3.4/src/lib/krb5/os/locate_kdc.c
with => http://repository.timesys.com/buildsources/k/krb5/krb5-1.4.4/krb5-1.4.4-eai_nodata.patch

- [LTIB]> ./ltib

- LTIB will start configuring and building ...

- Build Fail !

- Main Error =>

client.c:54: warning: 'target' may be used uninitialized in this function
gcc -L../../../lib -Wl,-rpath -Wl,/usr/lib -g -O2 -Wall -Wmissing-prototypes -Wcast-qual  -Wcast-align -Wconversion -Wshadow -Wno-comment -pedantic  -o client client.o rpc_test_clnt.o \
        -lgssrpc -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err 
../../../lib/libkrb5.so: undefined reference to `__res_search'
../../../lib/libkrb5.so: undefined reference to `__dn_expand'
collect2: ld returned 1 exit status
make[3]: *** [server] Error 1
make[3]: *** Waiting for unfinished jobs....
../../../lib/libkrb5.so: undefined reference to `__res_search'
../../../lib/libkrb5.so: undefined reference to `__dn_expand'
collect2: ld returned 1 exit status
make[3]: *** [client] Error 1

 

Test5: Succeed

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

Perhaps need to find a suitable libresolv src and manually build and add it to the LTIB rpm/BUILD or use alternative resolver during the krb5 configure stage.

 

To solve the resolver error

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

./configure --prefix=%{_prefix} --host=$CFGHOST --build=%{_build} \
            --enable-shared  --without-tcl --with-netlib=/home/danny/test/training_mx53/linux/ltib/rootfs/lib/libresolv-2.11.1.so

 

Patch if you got these error

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

In file included from ./ftpcmd.y:71:
ftpd_var.h:92: error: conflicting types for 'getline'
/opt/freescale/usr/local/gcc-4.4.4-glibc-2.11.1-multilib-1.0/arm-fsl-linux-gnueabi/bin/../lib/gcc/arm-fsl-linux-gnueabi/4.4.4/../../../../arm-fsl-linux-gnueabi/include/stdio.h:651: note: previous declaration of 'getline' was here


Patch Manually => [LTIB]/rpm/BUILD/krb5-1.3.4/src/appl/gssftp/ftpd/ftpcmd.y
with => http://mailman.mit.edu/pipermail/kerberos/2006-June/009953.html

Patch Manually => [LTIB]/rpm/BUILD/krb5-1.3.4/src/appl/gssftp/ftpd/ftpd_var.h
with => http://mailman.mit.edu/pipermail/kerberos/2006-June/009953.html

Patch Manually => [LTIB]/rpm/BUILD/krb5-1.3.4/src/appl/gssftp/ftpd/ftpd.c
with => http://mailman.mit.edu/pipermail/kerberos/2006-June/009953.html


#############################################################################
Test Summary
#############################################################################

      Currently stopped at Test4, not sure how to proceed, seem like it is side effect of temporary bypassing the Resolver error earlier on using config_opts inside krb5.spec.

     Test succeeded at Test 5 

 

     Anyone from Freescale Technical involved in testing and verifying the LTIB building of  FSL gnome release package as mentioned inside " i.MX53_START_Linux_BSP_UserGuide.pdf" which clearly mention that "Please note that only the profiles of Min profile, FSL gnome release packages and mfg firmware profile pass build tests."or anyone has somehow successfully build the FSL gnome release package before, appreciate if you can share your secret. Currently, I can't find anything inside Freescale official guidelines which could make this work . Pls help !

 

Many Thank in advance.


Tags (1)
0 Kudos
22 Replies

235 Views
DannyChin_ng
Contributor I

Hi Claude,

 

Thanks for your reply. I have tested in 2 environment setup as below:

 

1.)

Host: Windows Vista

Client: Vmware Image (VM_Ubuntu.zip) from Freescale

Source: L2.6.35_11.01.00_ER_source_bundle.tar.gz

 

2.)

Host: Windows Vista

Client: Ubuntu 10.10 in VirtualBox with iMX53 LTIB installed

Source: L2.6.35_11.01.00_ER_source_bundle.tar.gz

 

* Both setup are run in parallel using 2 machine and basically showing same behavior and error message when building FSL gnome release package.

 

The ltib commands used are from i.MX53 START Linux User’s Guide, Rev 11.01.00 and LTIB help as shown below:

./ltib -c - from ltib command help page

./ltib -m config  - Chapter 2.2 Page 9

./ltib --selectype  - Chapter 2.8 Page 12

 

      I am quite interested in using the lightweight windows manager-Matchbox, wondering is it that you select the package X and Matchbox from the ltib package list or you download the source and build manually into the rootfs tree ? How do we configure the StartX script for both VGA/LCD/LVDS/HDMI then ?

 

      Have been using Ubuntu Desktop for years but really having no idea on how to build a MINIMUM linux rootfs with X and Windows Manager so that we can use it inside the embedded board like the marvelous iMX53 QSB which Freescale has done a great job and our custom iMX53 Board later. Do we just need packages like X and a Windows Manager like Matchbox ? or any other packages are needed.

 

     Btw, can you let me know where can we find the L2.6.35_11.03_ER_source_bundle.tar.gz because from Freescale iMX53 download site ( https://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=IMX...) , I can only find the 11.01 and not the 11:03 source.

 

     Thanks.

 


0 Kudos

235 Views
Claude_Sylvain
Contributor I

Hello Danny,

- I have successfully build from source a i.MX53 QSB BSP including
  X and Matchbox.
  The built process was fairly long, but it works (no need to do
  any special modifications).

- The source package I used is L2.6.35_11.01.00_ER_source_bundle.tar.gz

- The host I use is Ubuntu 9.04 under VirtualBox under WindowsXP.


- Remarks:

    - You do not have to use "ltib -c" or "ltib --selecttype".
      From where you got these instructions?
      Just follow the Freescale documentation.  See
      "i.MX53_START_Linux_BSP_UserGuide.pdf", chapter 2.

    - To make X and Matchbox working, it is possible that you
      have to modify "startx" script; depending if you are
      using the VGA (TVE) output or a LCD panel.

    - I tried to do the same things with
      L2.6.35_11.03_ER_source_bundle.tar.gz, without success.
      The built process can be achieved, but the Kernel seems
      to not be able to manage the VGA (TVE) output.
      Also, the default settings in the Kernel configuration is
      bad, and must be modified to get the video driver included
      into the Kernel.


Claude



0 Kudos