Problem for compiling software that I downloaded

From: takashi (twakeshi_at_telus.net)
Date: 07/30/03


Date: Wed, 30 Jul 2003 21:59:31 GMT

Hi, I am having trouble to compile some of the softwares that I
downloaded off the internet. I have gcc-3.2.2-5 that came with redhat9.
When I uncompressed some tar files (e.g tar xzvf <filename.tar.gz>),and
used the command "make" in that folder, I have got the message that
> In file included from /usr/include/c++/3.2.2/backward/iostream.h:31,
> from common.h:32,
> from csound.cc:20: >

/usr/include/c++/3.2.2/backward/backward_warning.h:32:2: warning:
#warning This
> file includes at least one deprecated or antiquated header. Please consider using one of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples
> include substituting the <X> header for the <X.h> header for C++ includes, or <sstream> instead of the deprecated header <strstream.h>. To disable this warning
> use -Wno-deprecated.
> In file included from /usr/include/c++/3.2.2/i386-redhat-linux/bits/c++locale.h:39

So I looked into some files, and foud the file called common.h that
contains:

> #include <stdlib.h>
> #include <stdio.h>
> #include <string.h>
> #include <time.h>
> #include <gnome.h>
> #include <iostream.h>
> #include <fstream.h>
> #include <math.h>
> #include "config.h"
So I thought that I can just make it like

> #include <stdlib.h>
> #include <stdio.h>
> #include <string>
> #include <time.h>
> #include <gnome.h>
> #include <iostream>
> #include <fstream>
> #include <cmath> //this has been changed from <math.h> to <cmath>
> #include "config.h"
> using namespace std;

When I used "make" again, it again gave me some error message like

  -g -O2 -c csound.cc
In file included from
/usr/include/c++/3.2.2/i386-redhat-linux/bits/c++locale.h:39,
                  from /usr/include/c++/3.2.2/bits/localefwd.h:46,
                  from /usr/include/c++/3.2.2/ios:48,
                  from /usr/include/c++/3.2.2/ostream:45,
                  from /usr/include/c++/3.2.2/iostream:45,
                  from common.h:32,
                  from csound.cc:20:
/usr/include/libintl.h:40: parse error before `__const'
/usr/include/libintl.h:44: parse error before `__const'
/usr/include/libintl.h:52: parse error before `__const'
/usr/include/libintl.h:81: parse error before `__const'
/usr/include/libintl.h:86: parse error before `__const'
make[2]: *** [csound.o] Error 1

Do you think I am on the right track? I am wondering if I can install
older version of gcc compiler, so that I would not see this sort of
problems.
  I really appreciate if you could give me any suggestions on this.
Thank you, and have a good day.



Relevant Pages

  • Problem for compiling software that I downloaded
    ... I am having trouble to compile some of the softwares that I ... I have gcc-3.2.2-5 that came with redhat9. ... When I uncompressed some tar files,and ... it again gave me some error message like ...
    (alt.linux)
  • Re: [SLE] Please! I could use some help!
    ... I don't know what SuSE distribution you are running -- I came in late on ... "NULL" error message ... to ensure he was getting a working installation. ... and do some simple compile development exercises until you gain the ...
    (SuSE)
  • Re: Error exiting database
    ... without error if you choose 'Compile ' form the Debug ... > The Load Event looks like this but I don't understand why it would fire ... >> The error message, though, indicates that the problem is in the Load ... >> GlobalSign digital certificate is a forgery and should be deleted without ...
    (microsoft.public.access.formscoding)
  • Re: using #ifndef
    ... > gone to the newsgroup as well. ... that was ERT's fault for sending his response both by ... but nothing that anyone else could actually compile. ... cut-and-paste the actual error message. ...
    (comp.lang.c)
  • Re: Make Exe problem
    ... When compiling an ActiveX component with binary compatibility set to the ... LINK fatal error LNK1104 cannot open file. ... Set binary compatibility to the copied file, and compile ... If you click "Yes," the following error message appears: ...
    (microsoft.public.vb.bugs)