#5 Example makefiles have bad install rules

SystemC_v2.0_beta-2
open
nobody
5
2014-12-30
2006-10-31
Anonymous
No

I built SystemC 2.2.beta5Jun06 on Slackware Linux 11 using:

./configure --prefix=/usr/local/systemc-2.2.beta5jun06
make
make install

All was well until the `make install', when I got the
following errors:
-------------------
fMaking install in fft
make[3]: Entering directory
`/local/d0p6/john/systemc/systemc-2.2.05jun06_beta/examples/sysc/fft'
Making install in fft_flpt
make[4]: Entering directory
`/local/d0p6/john/systemc/systemc-2.2.05jun06_beta/examples/sysc/fft/fft_flpt'
make[5]: Entering directory
`/local/d0p6/john/systemc/systemc-2.2.05jun06_beta/examples/sysc/fft/fft_flpt'
make[5]: Nothing to be done for `install-exec-am'.
/bin/sh ../../../../config/mkinstalldirs .
or 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 \ /bin/ginstall -c -m 644 ./$file ./$file; \ done
/bin/ginstall: `./in_imag' and `./in_imag' are the same
file
/bin/ginstall: `./in_imag.1' and `./in_imag.1' are the
same file
/bin/ginstall: `./in_imag.2' and `./in_imag.2' are the
same file
/bin/ginstall: `./in_imag.3' and `./in_imag.3' are the
same file
/bin/ginstall: `./in_imag.4' and `./in_imag.4' are the
same file
/bin/ginstall: `./in_real' and `./in_real' are the same
file
/bin/ginstall: `./in_real.1' and `./in_real.1' are the
same file
/bin/ginstall: `./in_real.2' and `./in_real.2' are the
same file
/bin/ginstall: `./in_real.3' and `./in_real.3' are the
same file
/bin/ginstall: `./in_real.4' and `./in_real.4' are the
same file
/bin/ginstall: `./out_imag.1.golden' and
`./out_imag.1.golden' are the same file
/bin/ginstall: `./out_imag.2.golden' and
`./out_imag.2.golden' are the same file
/bin/ginstall: `./out_imag.3.golden' and
`./out_imag.3.golden' are the same file
/bin/ginstall: `./out_imag.4.golden' and
`./out_imag.4.golden' are the same file
/bin/ginstall: `./out_real.1.golden' and
`./out_real.1.golden' are the same file
/bin/ginstall: `./out_real.2.golden' and
`./out_real.2.golden' are the same file
/bin/ginstall: `./out_real.3.golden' and
`./out_real.3.golden' are the same file
/bin/ginstall: `./out_real.4.golden' and
`./out_real.4.golden' are the same file
/bin/ginstall: `./fft.cpp' and `./fft.cpp' are the same
file
/bin/ginstall: `./main.cpp' and `./main.cpp' are the
same file
/bin/ginstall: `./sink.cpp' and `./sink.cpp' are the
same file
/bin/ginstall: `./source.cpp' and `./source.cpp' are
the same file
/bin/ginstall: `./fft.h' and `./fft.h' are the same file
/bin/ginstall: `./sink.h' and `./sink.h' are the same file
/bin/ginstall: `./source.h' and `./source.h' are the
same file
make[5]: *** [install-data-local] Error 1
--------------------

A work-around is to alter
examples/sysc/fft/fft_flpt/Makefile:
--------------------
406c406
< $(INSTALL_DATA) $(srcdir)/$$file
./$$file; \ ---
> $(INSTALL_DATA) $(srcdir)/$$file
$(prefix)/examples/sysc/fft/fft_flpt/$$file; \ --------------------

and then similarly alter several other examples Makefiles:
---------------------
./examples/sysc/2.1/dpipe/Makefile
./examples/sysc/2.1/forkjoin/Makefile
./examples/sysc/2.1/reset_signal_is/Makefile
./examples/sysc/2.1/sc_export/Makefile
./examples/sysc/2.1/sc_report/Makefile
./examples/sysc/2.1/scx_barrier/Makefile
./examples/sysc/2.1/scx_mutex_w_policy/Makefile
./examples/sysc/2.1/specialized_signals/Makefile
./examples/sysc/fft/fft_flpt/Makefile
./examples/sysc/fft/fft_fxpt/Makefile
./examples/sysc/fir/Makefile
./examples/sysc/pipe/Makefile
./examples/sysc/pkt_switch/Makefile
./examples/sysc/rsa/Makefile
./examples/sysc/simple_bus/Makefile
./examples/sysc/simple_fifo/Makefile
./examples/sysc/simple_perf/Makefile
-----------------------

Of course, a proper fix would involve correcting the
code which generates the Makefiles.

John A. Murdie
Department of Computer Science
University of York
UK
john@cs.york.ac.uk

Discussion


Log in to post a comment.

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

Sign up for the SourceForge newsletter:





No, thanks