Compile errors - fwbuilder-

  • Armz

    Armz - 2011-07-19


    Regarding compile errors;
    Which compile errors or warnings should one pay attention to, even thought the 'make' process completes ?

    For example… with the fwbuilder- build, running ./
    g++: error: unrecognized option '-qversion'
    g++: fatal error: no input files

    configure:16173: gcc -c -g -O2  conftest.c >&5
    conftest.c:34:18: fatal error: util.h: No such file or directory
    compilation terminated.

    /home/user1/Desktop/fwbuilder- undefined reference to `forkpty'
    collect2: ld returned 1 exit status
    configure:16209: $? = 1
    configure: failed program was:
    | /* confdefs.h */

    ../libfwbuilder/src/fwbuilder/uint128.h:471:57: warning: format ‘%lX’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘long long unsigned int’

  • Vadim Kurland

    Vadim Kurland - 2011-07-19

    errors or what might look like errors that you see in the output of configure script are normal. Unless configure aborts and does not produce required build scripts and files, those errors and warnings are just results of its tests.

    Most warnings you see during compile phase are harmless but we always look for ways to get rid of them to make compile process cleaner.


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks