Compiling SVN #32 with gcc 4.3.2

Help
2009-03-28
2012-10-06
  • Johan Cwiklinski

    Hello,

    I was trying to compile IIPImage server under my fedora 10 (with gcc 4.3.2) and I encounted some errors. I've corrected some of them (even if I'm not sure my changes are really relevant and well placed in the code) - see the svn diff output below.

    I'm stucked with another one :
    DSOImage.cc: In member function ‘RawTile DSOImage::getTile(int, int, int, int)’:
    DSOImage.cc:273: erreur: no matching function for call to ‘RawTile::RawTile(int&, int&, int&, int&, int&, int&, unsigned char, int, int&)’
    RawTile.h:129: note: candidats sont: RawTile::RawTile(const RawTile&)

    RawTile.h:111: note: RawTile::RawTile(int, int, int, int, int, int, int, int)

    make[1]:
    ** [DSOImage.o] Erreur 1

    Seems that types and the number of arguments passed to RawTile function are not the ones that are expected... And I really do not know what to do for that one.

    Anyways, many thanks for the great job :-)

    $ svn diff
    Index: src/Main.cc
    ===================================================================
    --- src/Main.cc (révision 32)
    +++ src/Main.cc (copie de travail)
    @@ -226,7 +226,7 @@

    map <string, string> moduleList;
    string modulePath;
    - envpara = getenv( "DECODER_MODULES" );
    + char *envpara = getenv( "DECODER_MODULES" );

    if( envpara ){

    Index: src/DSOImage.h

    --- src/DSOImage.h (révision 32)
    +++ src/DSOImage.h (copie de travail)
    @@ -54,6 +54,8 @@
    /// Get error messages from the module
    std::string getError();

    • unsigned int image_width;
    • unsigned int image_height;

    public:

    @@ -87,7 +89,7 @@

    /// Return description of the module
    - const std::string& getDescription() { return description; };
    + const std::string getDescription() { return description; };

    /// Load the module
    /** \param p module path

     
    • Ruven

      Ruven - 2009-03-30

      Hi,

      Thanks for pointing this out. Yes, the DSO code is not up to date. In fact it's only needed if you want to write a module to handle a different file format. I may even remove it as I don't think anyone uses it. To avoid this problem you should compile without activating it. In other words, calling ./configure without the --enable-modules flag.

       
      • Johan Cwiklinski

        Okay, that compiles without any problems once '--enable-modules' flag removed.

        Thanks for your help :-)

         


Anonymous

Cancel  Add attachments





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

Sign up for the SourceForge newsletter:





No, thanks