• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 97 subscribers
  • Views 353 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.

Can't compile TargetFS (DVSDK)

IsaacLeung
Intellectual 395 points

I'm just testing with Mistral EVM and I'm trying to recompile the target FS and DVSDK and I'm getting a bunch of errors.

To start, I just follow the instructions and head into

dvsdk_3_00_00_29/targetfs

and enter the command "sudo make -f targetfs_make all"

That's when the problems start.

[1] First issue about missing file was solved with the help of this post <http://e2e.ti.com/forums/t/2400.aspx> . (Maybe someone can explain why the SDK isn't one archive, but many nested ones... and why some of them are in .gz and some in .bz2)

[2] After following that hint, I go through the entire OMAP35x_SDK_1.0.2 directory and unpack everything I can find. Then I go re-run it again, but then this other error pops up:

 $HOME/OMAP35x_SDK_1.0.2/src/linux/kernel_org/2.6_kernel/scripts/Makefile.modpost:42: include/config/auto.conf: No such file or directory
make[4]: *** No rule to make target `include/config/auto.conf'. Stop.

I can see, based on the echo'd messages that pop up, this appears to be occurring in the build step for dvsdk

I searched through the entire directory, can't find any file like that. Where's it supposed to be? Did I accidentally miss un-archiving one set of files?

 

Any hints/tips how to get around this error?

I am running this on a CLEAN install of Ubuntu 9.04, but I assume that should not matter.

  • 0
    Intellectual 395 points

    I'm going to answer my own on this one and save others some pain. Please keep in mind this is an Ubuntu 9.04 install, maybe that has something to do with some of the issues.

    0) Install a bunch of stuff into your Linux distro. Sure, only Red Hat Enterprise Linux, Workstation V4, x86 32 bit is supported, but it doesn't say what options you need and Linux installs are very customizable. Just to be safe install "build-essential", and you will need "libncurses5-dev" and "mtd-utils" for sure, else your build will crap out at various stages. For Ubuntu, just use "sudo apt-get install ... " or the Synaptics Package Manager or whatever you like

    1) Building U-Boot : If you follow the instructions, it won't build. There's an error building in the Hello World program, so just go to the "examples" directory, edit the Makefile and comment it out. Unless you really want to say Hello ...

    2) Building the kernel : Refer to one of the previous posts. As someone else mentioned, you need to unpack some of the sources in there. The guide doesn't mention this and I'm not sure who would guess unpacking the source leaves other sources in subdirectories that need to be unpacked. If you just blindly follow the guide, you'll get errors, it won't work.

    3) Building the DVSDK software : Again, if you follow the guide explicitly, it probably won't work. In addition to what they say, go into the "Rules.make" file and modify some of the directory variables. In particular, pay close attention to LINUXKERNEL_INSTALL_DIR, you want to make sure it matches where you actually built the kernel, don't follow the example in Rules.make. Frankly, I'm not sure the guide instructions would work, since it looks like Rules.make over-rides my environment variable settings that the guide says I should make.

    4) Building the target FS : Now if you managed to get all the above working, rebuilding the target FS should work.

     

    And that's why I love developing "free" software....

    (I'm not knocking TI in particular, I've done this before on various processors and with other software packages and it's always the same sort of half-baked procedure...)

  • 0 in reply to IsaacLeung
    Intellectual 395 points

    Just a quick note:

    In fact most of those glitches with missing packages and stuff is now in the documentation in OMAP35x-PSP-SDK-02.01.01.07

    So that pretty much confirms my findings, I've not been smoking something good...