Jump to content
sonalidutta

Error in gmake while installing systemc-2.3.0

Recommended Posts

Hi,

 

I am installing the latest version of systemc-2.3.0 using the following commands:

 

cd systemc-2.3.0

mkdir objdir

cd objdir

export CXX=g++

../configure

cd ..

aclocal

automake

cd objdir

gmake

 

While running gmake I get the following Error:

 

Making all in kernel
gmake[3]: Entering directory `/root/Desktop/CHIMP_ea/systemc-2.3.0/objdir/src/sysc/kernel'
/bin/sh ../../../libtool --tag=CXX   --mode=compile g++ -DSC_INCLUDE_FX   -I. -I../../../../src/sysc/kernel -I../../../../src   -Wall -m64  -O3   -MT sc_attribute.lo -MD -MP -MF .deps/sc_attribute.Tpo -c -o sc_attribute.lo ../../../../src/sysc/kernel/sc_attribute.cpp
mv -f .deps/sc_attribute.Tpo .deps/sc_attribute.Plo
mv: cannot stat `.deps/sc_attribute.Tpo': No such file or directory
gmake[3]: *** [sc_attribute.lo] Error 1

gmake[3]: Leaving directory `/root/Desktop/CHIMP_ea/systemc-2.3.0/objdir/src/sysc/kernel'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory `/root/Desktop/CHIMP_ea/systemc-2.3.0/objdir/src/sysc'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/root/Desktop/CHIMP_ea/systemc-2.3.0/objdir/src'
gmake: *** [all-recursive] Error 1

 

I would like to point out here that gmake produces the following message too:

 

../configure: line 5134: AX_PTHREAD: command not found

 

Also I have the following packages installed in /usr/local:

 

autoconf-2.69

automake-1.10.1

libtool-2.4

aclocal-1.10.1

GNU Make 3.81

 

It will be really helpful if anyone can think of what is wrong here!

 

Thanks

Sonali

Share this post


Link to post
Share on other sites

Dear Sir/Madam,

May we know which OS you are using ?

We have installed SystemC 2.3.0 on Fedora 14, 15 and 17

without any of the issues you report.

 

Furthermore, the steps you list are just too many.

The following is what you need to do:

1. uncompress the tarball -- a directory is created

2, cd to this directory, and type in './configure'

3. type 'gmake' and the executable library is created

3. type 'make install' and then in the same directory

    you would see a sub-directory named 'lib-linux'

    inside is the main SystemC binary library

There is no need to create the objdir and so forth

 

Please remove the present objdir and so forth

with a 'rm -rf <directory name>' executed from

a directory immediately above the directory in

which the tarball was uncompressed.

 

Hope that helps.

Share this post


Link to post
Share on other sites

Dear developer,

 

Thanks for the reply.

 

I followed the steps listed in INSTALL file of systemc-2.3.0 package. If those steps are not the right ones, please change it there.

 

I am using Red Hat 5.9

 

As you said, I am trying to install it now by: ./configure, gmake, make install

 

Do you mean gmake install instead of make install?

 

I get the following error when I run gmake:

 

Making all in include
gmake[4]: Entering directory `/root/Desktop/CHIMP_ea/systemc-2.3.0/examples/sysc/2.3/include'
gmake[4]: *** No rule to make target `sc_rvd.h', needed by `all-am'.  Stop.
gmake[4]: Leaving directory `/root/Desktop/CHIMP_ea/systemc-2.3.0/examples/sysc/2.3/include'
gmake[3]: *** [all-recursive] Error 1
gmake[3]: Leaving directory `/root/Desktop/CHIMP_ea/systemc-2.3.0/examples/sysc/2.3'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory `/root/Desktop/CHIMP_ea/systemc-2.3.0/examples/sysc'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/root/Desktop/CHIMP_ea/systemc-2.3.0/examples'
gmake: *** [all-recursive] Error 1
 

Regards

Sonali

Share this post


Link to post
Share on other sites

I again started from the scratch and tried

 

./configure

gmake

gmake install

 

gmake install gives me the gfollowing error:

 

gmake[5]: Entering directory `/root/Desktop/CHIMP_ea/systemc-2.3.0/examples/sysc/fft/fft_flpt'
gmake[5]: Nothing to be done for `install-exec-am'.
/bin/sh /root/Desktop/CHIMP_ea/systemc-2.3.0/config/install-sh -d .
for file in in_imag in_imag.1 in_imag.2 in_imag.3 in_imag.4 in_real in_real.1 in_real.2 in_real.3 in_real.4 out_imag.1.golden out_imag.2.golden out_imag.3.golden out_imag.4.golden out_real.1.golden out_real.2.golden out_real.3.golden out_real.4.golden  fft.cpp main.cpp sink.cpp source.cpp fft.h sink.h source.h; do \
                /usr/bin/install -c -m 644 ./$file ./$file; \
        done
/usr/bin/install: `./in_imag' and `./in_imag' are the same file
/usr/bin/install: `./in_imag.1' and `./in_imag.1' are the same file
/usr/bin/install: `./in_imag.2' and `./in_imag.2' are the same file
/usr/bin/install: `./in_imag.3' and `./in_imag.3' are the same file
/usr/bin/install: `./in_imag.4' and `./in_imag.4' are the same file
/usr/bin/install: `./in_real' and `./in_real' are the same file
/usr/bin/install: `./in_real.1' and `./in_real.1' are the same file
/usr/bin/install: `./in_real.2' and `./in_real.2' are the same file
/usr/bin/install: `./in_real.3' and `./in_real.3' are the same file
/usr/bin/install: `./in_real.4' and `./in_real.4' are the same file
/usr/bin/install: `./out_imag.1.golden' and `./out_imag.1.golden' are the same file
/usr/bin/install: `./out_imag.2.golden' and `./out_imag.2.golden' are the same file
/usr/bin/install: `./out_imag.3.golden' and `./out_imag.3.golden' are the same file
/usr/bin/install: `./out_imag.4.golden' and `./out_imag.4.golden' are the same file
/usr/bin/install: `./out_real.1.golden' and `./out_real.1.golden' are the same file
/usr/bin/install: `./out_real.2.golden' and `./out_real.2.golden' are the same file
/usr/bin/install: `./out_real.3.golden' and `./out_real.3.golden' are the same file
/usr/bin/install: `./out_real.4.golden' and `./out_real.4.golden' are the same file
/usr/bin/install: `./fft.cpp' and `./fft.cpp' are the same file
/usr/bin/install: `./main.cpp' and `./main.cpp' are the same file
/usr/bin/install: `./sink.cpp' and `./sink.cpp' are the same file
/usr/bin/install: `./source.cpp' and `./source.cpp' are the same file
/usr/bin/install: `./fft.h' and `./fft.h' are the same file
/usr/bin/install: `./sink.h' and `./sink.h' are the same file
/usr/bin/install: `./source.h' and `./source.h' are the same file
gmake[5]: *** [install-data-local] Error 1
gmake[5]: Leaving directory `/root/Desktop/CHIMP_ea/systemc-2.3.0/examples/sysc/fft/fft_flpt'
gmake[4]: *** [install-am] Error 2
gmake[4]: Leaving directory `/root/Desktop/CHIMP_ea/systemc-2.3.0/examples/sysc/fft/fft_flpt'
gmake[3]: *** [install-recursive] Error 1
gmake[3]: Leaving directory `/root/Desktop/CHIMP_ea/systemc-2.3.0/examples/sysc/fft'
gmake[2]: *** [install-recursive] Error 1
gmake[2]: Leaving directory `/root/Desktop/CHIMP_ea/systemc-2.3.0/examples/sysc'
gmake[1]: *** [install-recursive] Error 1
gmake[1]: Leaving directory `/root/Desktop/CHIMP_ea/systemc-2.3.0/examples'
gmake: *** [install-recursive] Error 1
 

 

What are thses wierd errors? Is this the reason the INSTALL file asks to create a new directory objdir and install there?

 

Regards

Sonali

Share this post


Link to post
Share on other sites

Hi Sonali,

  your original approach (with objdir) is the correct one, the INSTALL file is correct.

 

I don't know what your original error is about.

 

Can you start again from a fresh install, and try these commands (i.e. without aclocal etc)

 

 

rm -rf systemc-2.3.0
tar xzf systemc-2.3.0
cd systemc-2.3.0
mkdir objdir
cd objdir
export CXX=g++
../configure
gmake
 

 

 

regards

Alan

Share this post


Link to post
Share on other sites

Problem solved! Thanks Alan.

 

P.S. For systemc-2.2.0 I needed to run aclocal and automake in addition to the INSTALL file steps to install it in Red Hat. It was pretty messy!

 

I tried the same set of steps (by default) for the new version of systemc, systemc-2.3.0. But looks like systemc-2.3.0 is more robust and can be installed just by the steps in its INSTALL file. :)

Share this post


Link to post
Share on other sites

Hey Alan,

 

Could you please tell why is it necessary to put,

export CXX=g++

 

I successfully installed systemc-2.3.0 on Ubuntu 12.04 (64bit) without export CXX.

In my case it is working perfectly fine.

 

P.S. - Compilation : g++ -I/usr/local/systemc-2.3.0/include/ -L/usr/local/systemc-2.3.0/lib-linux64/ -o test hello.cpp -lsystemc

 

regards,

Samyak 

Share this post


Link to post
Share on other sites

Hi Samyak, I guess it doesn't matter unless you have multiple versions of a C++ compiler installed, or a C++ compiler that has a different binary name than g++. You're right on Ubuntu and other common distributions g++ should be in your path anyway,

 

regards

Alan

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×