• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 1761 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.

warnings being treated as errors?

Gennadiy Kiryukhin
Expert 2800 points

When compiling DVSDK 3.1 for DM355 using 'make all' I get the following error:

...... some other stuff built successfully ....

make[1]: Entering directory `/home/vmplanet/dvsdk/dvsdk_3_10_00_19/dmai_2_10_00_12'
make -C ./packages/ti/sdo/dmai
make[2]: Entering directory `/home/vmplanet/dvsdk/dvsdk_3_10_00_19/dmai_2_10_00_12/packages/ti/sdo/dmai'
Building dmai for dm355_al..

Compiling obj/Buffer.dm355.o470MV from Buffer.c..
Compiling obj/BufferGfx.dm355.o470MV from BufferGfx.c..
Compiling obj/BufTab.dm355.o470MV from BufTab.c..
Compiling obj/Ccv.dm355.o470MV from Ccv.c..
Compiling obj/ColorSpace.dm355.o470MV from ColorSpace.c..
Compiling obj/Framecopy.dm355.o470MV from Framecopy.c..
Compiling obj/Loader.dm355.o470MV from Loader.c..
Compiling obj/VideoStd.dm355.o470MV from VideoStd.c..
Compiling obj/ce/Adec1.dm355.o470MV from ce/Adec1.c..
Compiling obj/ce/Adec.dm355.o470MV from ce/Adec.c..
Compiling obj/ce/Aenc1.dm355.o470MV from ce/Aenc1.c..
Compiling obj/ce/Aenc.dm355.o470MV from ce/Aenc.c..
Compiling obj/ce/Idec1.dm355.o470MV from ce/Idec1.c..
Compiling obj/ce/Idec.dm355.o470MV from ce/Idec.c..
Compiling obj/ce/Ienc1.dm355.o470MV from ce/Ienc1.c..
Compiling obj/ce/Ienc.dm355.o470MV from ce/Ienc.c..
Compiling obj/ce/Sdec1.dm355.o470MV from ce/Sdec1.c..
Compiling obj/ce/Sdec.dm355.o470MV from ce/Sdec.c..
Compiling obj/ce/Senc1.dm355.o470MV from ce/Senc1.c..
Compiling obj/ce/Senc.dm355.o470MV from ce/Senc.c..
Compiling obj/ce/Vdec2.dm355.o470MV from ce/Vdec2.c..
Compiling obj/ce/Vdec.dm355.o470MV from ce/Vdec.c..
Compiling obj/ce/Venc1.dm355.o470MV from ce/Venc1.c..
Compiling obj/ce/Venc.dm355.o470MV from ce/Venc.c..
Compiling obj/linux/Capture.dm355.o470MV from linux/Capture.c..
Compiling obj/linux/Cpu.dm355.o470MV from linux/Cpu.c..
Compiling obj/linux/Display.dm355.o470MV from linux/Display.c..
Compiling obj/linux/Display_fbdev.dm355.o470MV from linux/Display_fbdev.c..
Compiling obj/linux/Display_v4l2.dm355.o470MV from linux/Display_v4l2.c..
Compiling obj/linux/Dmai.dm355.o470MV from linux/Dmai.c..
Compiling obj/linux/Fifo.dm355.o470MV from linux/Fifo.c..
Compiling obj/linux/Pause.dm355.o470MV from linux/Pause.c..
Compiling obj/linux/Rendezvous.dm355.o470MV from linux/Rendezvous.c..
Compiling obj/linux/Sound_alsa.dm355.o470MV from linux/Sound_alsa.c..
cc1: warnings being treated as errors
linux/Sound_alsa.c:75: error: 'setMixerControl' defined but not used
make[2]: *** [obj/linux/Sound_alsa.dm355.o470MV] Error 1
make[2]: Leaving directory `/home/vmplanet/dvsdk/dvsdk_3_10_00_19/dmai_2_10_00_12/packages/ti/sdo/dmai'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/vmplanet/dvsdk/dvsdk_3_10_00_19/dmai_2_10_00_12'
make: *** [dmai] Error 2

Why?

 

  • 0
    Expert 2800 points

    BTW: My custom board does not have sound, so the sound option was disabled in the linux kernel configuration. Would that cause the error?

  • 0
    TI__Genius 12865 points

    Hi Gennadiy,

    The Dmai compile options in packages/ti/sdo/dmai/Makefile includes  the -Werror flag. This was done to ensure Dmai builds with no warnings. In your case you may want to remove it so that you can proceed with the build, given you do not need sound support anyway.

    Best regards,

    Vincent

  • 0 in reply to Vincent W.
    Expert 2800 points

    Hi Vincent,

    I searched the web for thins message and found similar suggestions. Is it possible to tell the compiler to skip the building of the sound. The reason is that I want to make sure other drivers are build without warnings. Do you know how can I remove the sound from being built?

     

    In the mean time, just ot get going I removed the -Werror flag. As it continued compiling I got the following error:

    Compiling obj/linux/Sound_alsa.dm355.o470MV from linux/Sound_alsa.c..
    linux/Sound_alsa.c:75: warning: 'setMixerControl' defined but not used
    Compiling obj/linux/Sound.dm355.o470MV from linux/Sound.c..
    Compiling obj/linux/Sound_oss.dm355.o470MV from linux/Sound_oss.c..
    Compiling obj/linux/_SysFs.dm355.o470MV from linux/_SysFs.c..
    Compiling obj/linux/Time.dm355.o470MV from linux/Time.c..
    Compiling obj/linux/_VideoBuf.dm355.o470MV from linux/_VideoBuf.c..
    Compiling obj/linux/dm355/Blend.dm355.o470MV from linux/dm355/Blend.c..
    Compiling obj/linux/dm355/Ccv_accel.dm355.o470MV from linux/dm355/Ccv_accel.c..
    Compiling obj/linux/dm355/Framecopy_accel.dm355.o470MV from linux/dm355/Framecopy_accel.c..
    Compiling obj/linux/dm355/Ir.dm355.o470MV from linux/dm355/Ir.c..
    linux/dm355/Ir.c:70: error: expected ')' before '*' token
    make[2]: *** [obj/linux/dm355/Ir.dm355.o470MV] Error 1
    make[2]: Leaving directory `/home/vmplanet/dvsdk/dvsdk_3_10_00_19/dmai_2_10_00_12/packages/ti/sdo/dmai'
    make[1]: *** [all] Error 2
    make[1]: Leaving directory `/home/vmplanet/dvsdk/dvsdk_3_10_00_19/dmai_2_10_00_12'
    make: *** [dmai] Error 2

    Line 70 in that file is highlighted:

    /******************************************************************************
     * Ir_delete
     ******************************************************************************/
    Int Ir_delete(Ir_Object *hIr)
    {
    #ifdef CONFIG_INPUT_DM355EVM
        return(_Event_Ir_delete(hIr));
    #else
        Dmai_err0("not implemented\n");
        return Dmai_ENOTIMPL;
    #endif
    }

    What is wrong with the line?

    What is Ir? Is that the IR remote control feature implemented through MSP430?

    Thank you.

     

  • 0 in reply to Gennadiy Kiryukhin
    Expert 2800 points

    Not sure if I am correct but it looks like in dmai, the Makefile tells compiler to compile all the *.c files it can find in certain directories. So, for now I just renamed the Ir.c to Ir.c.disabled. This kinda worked until it decided that it is time to link the objects during demo application build. That application appears to rely on the IR feature. Since my board will not work with the demo application due to the lack of the user interface (IR remote/MSP430), I just decided to remove the 'demo' from the 'all' list in the main Makefile for the dvsdk.

    Let me know if I did something wrong.