• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 253 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Regard L27.G.4 Build

kamalakar garikiina
Prodigy 130 points 
Hi,

How I know the build is successful?


I am trying to use the latest release note from OMAP:
http://www.omappedia.org/wiki/L27.G.4_OMAP4_GingerBread_Release_Notes#Building_Android_Filesystem_.28AFS.29_with_TI_Codecs_enabled

on my Blaze.

but the problem is there are a number of error shows up before I can
finish building the Android File System.
Here is the command I used for blaze:
make TARGET_PRODUCT=pandaboard -j4 2>&1 |tee $MYDROID/logs/
android_make.out

make: *** Waiting for unfinished jobs....

After this it is coming out...

 Any idea guys?
  • 0
    Prodigy 130 points 

    Small correction to above message...

    Hi,

    How I know the build is successful?


    I am trying to use the latest release note from OMAP:
http://www.omappedia.org/wiki/L27.G.4_OMAP4_GingerBread_Release_Notes#Building_Android_Filesystem_.28AFS.29_with_TI_Codecs_enabled

on my Blaze.

but the problem is there are a number of error shows up before I can
finish building the Android File System.
Here is the command I used for blaze:
make -j4 2>&1 |tee $MYDROID/logs/android_make.out

make: *** Waiting for unfinished jobs....

    After this it is coming out...

     Any idea guys?

  • 0 in reply to kamalakar garikiina
    TI__Genius 10545 points

    This usually happens to me when one dependency is required by a component, but it was compiled before or some step is jumped,

    for example trying to compile a specific OMX component without compiling all full AFS first.

    and i saw this error too when added a new component to ./mydroid/frameworks/base and it depends on other component that is not compiled already.

    try removing the ./mydroid/out directory and run ./build envsetup.sh then check buildspec.mk file is in ./mydroid;

    by checking the instructions in L27G4 there is missing the setenv.sh, try replacing AFS build with below instructions, and if your PC CPU is of 2 cores use -j2 instead of -j4

    Building Android Filesystem (AFS) with TI Codecs enabled

    on step below use the number of cores you have available; i.e. -j4 or -j12:

    cd $MYDROID
    source build/envsetup.sh
    cp -Rfp device/ti/blaze/buildspec.mk.default buildspec.mk
make clean ;#(required for rebuild only)
make -j4 2>&1 | tee $MYDROID/logs/android_make.out