#30 Revision 640 caused an issue in evutil.c

closed-fixed
nobody
None
5
2008-02-24
2008-02-17
Anonymous
No

It would not compile with gcc 4.2.3

see http://trac.transmissionbt.com/ticket/711

Discussion

  • Nobody/Anonymous

    Logged In: NO

    Using gcc (GCC) 4.2.3 (Ubuntu 4.2.3-1ubuntu2)

    This is the error output:

    Making all in libevent Making all in .

    gcc -DHAVE_CONFIG_H -I. -I./compat -g -O2 -Wall -c event.c -o event.o gcc -DHAVE_CONFIG_H -I. -I./compat -g -O2 -Wall -c evutil.c -o evutil.o

    evutil.c:196:2: error: #error "I don't know how to parse 64-bit integers." evutil.c: In function 'evutil_strtoll': evutil.c:198: warning: control reaches end of non-void function make[4]: *** [evutil.lo] Error 1

     
  • Niels Provos

    Niels Provos - 2008-02-17

    Logged In: YES
    user_id=245089
    Originator: NO

    Here is the information from that bug:

    Using gcc (GCC) 4.2.3 (Ubuntu 4.2.3-1ubuntu2)

    This is the error output:

    Making all in libevent Making all in .

    gcc -DHAVE_CONFIG_H -I. -I./compat -g -O2 -Wall -c event.c -o event.o gcc -DHAVE_CONFIG_H -I. -I./compat -g -O2 -Wall -c evutil.c -o evutil.o

    evutil.c:196:2: error: #error "I don't know how to parse 64-bit integers." evutil.c: In function 'evutil_strtoll': evutil.c:198: warning: control reaches end of non-void function make[4]: *** [evutil.lo] Error 1

     
  • Niels Provos

    Niels Provos - 2008-02-17

    Logged In: YES
    user_id=245089
    Originator: NO

    I cannot reproduce this with gcc-4.2.1; Nick, you have any insights into this one?

     
  • Nick Mathewson

    Nick Mathewson - 2008-02-17

    Logged In: YES
    user_id=499
    Originator: NO

    Have you tried re-running autogen.sh and configure? If that doesn't work, please attach
    your config.h and config.log (compressed)? Thanks!

    Niels: We could change a flag in automake to make sure that configure gets re-built and
    re-run when configure.in has changed. Any reason not to? It would keep people from getting
    some of these spurious compile errors.

     
  • Niels Provos

    Niels Provos - 2008-02-17

    Logged In: YES
    user_id=245089
    Originator: NO

    I thought we already had that flag; let's add it if not.

     
  • Nobody/Anonymous

    Logged In: NO

    I reported the bug originally.
    As sugguested, I ran ./autogen.sh and then ./configure and there no longer appeared an error.
    Sorry.

     
  • Nick Mathewson

    Nick Mathewson - 2008-02-18

    Logged In: YES
    user_id=499
    Originator: NO

    I removed AM_MAINTAINER_MODE from configure.in in r651. If it doesn't cause trouble, I'll backport it to
    the 1.4 branch.

     
  • Nick Mathewson

    Nick Mathewson - 2008-02-24

    Logged In: YES
    user_id=499
    Originator: NO

    Original issue was not a bug; AM_MAINTAINER_MODE now removed from 1.4 branch and trunk so that autoconf re-runs itself in order to avoid confusing users.

     
  • Nick Mathewson

    Nick Mathewson - 2008-02-24
    • status: open --> closed-fixed
     

Log in to post a comment.

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

Sign up for the SourceForge newsletter:





No, thanks