RE : Error in compilation of runTransceiver.cpp in OpenBTS


#1

Thanks for your reply. Actually i tried to build this using the
./bootstrap, ./configure and make commands. It did not work.That’s why I
adopted the other way.

Following appears as i try to build it with standard commands. Do i have
to make changes in the “makefile”? Or how should i build this?

RESULTS OF STANDARD METHOD:

gohar@gohar:~/openbts/Transceiver$ ./bootstrap
bash: ./bootstrap: No such file or directory
gohar@gohar:~/openbts/Transceiver$ ./configure
bash: ./configure: No such file or directory
gohar@gohar:~/openbts/Transceiver$ make
cd … && make am–refresh
make[1]: Entering directory /home/gohar/openbts' /bin/bash ./config.status --recheck running CONFIG_SHELL=/bin/bash /bin/bash ./configure --no-create --no-recursion checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3 checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking whether ln -s works... yes checking whether make sets $(MAKE)... (cached) yes checking for a BSD-compatible install... /usr/bin/install -c checking for rm... /bin/rm checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for fgrep... /bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking the maximum length of command line arguments... 805306365 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking for /usr/bin/ld option to reload object files... -r checking how to recognize dependent libraries... pass_all checking for ar... ar checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking whether we are using the GNU C++ compiler... (cached) yes checking whether g++ accepts -g... (cached) yes checking dependency style of g++... (cached) gcc3 checking how to run the C++ preprocessor... g++ -E checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no checking for ld used by g++... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC -DPIC checking if g++ PIC flag -fPIC -DPIC works... yes checking if g++ static flag -static works... yes checking if g++ supports -c -o file.o... yes checking if g++ supports -c -o file.o... (cached) yes checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking for ANSI C header files... (cached) yes checking for an ANSI C-conforming const... yes checking for inline... inline checking for size_t... yes checking whether time.h and sys/time.h may both be included... yes checking whether byte ordering is bigendian... no checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.18... yes checking for USRP... yes checking for OSIP... yes checking for ORTP... yes configure: creating ./config.status /bin/bash ./config.status config.status: creating Makefile config.status: creating apps/Makefile config.status: creating config/Makefile config.status: creating doc/Makefile config.status: creating AsteriskConfig/Makefile config.status: creating CommonLibs/Makefile config.status: creating Control/Makefile config.status: creating GSM/Makefile config.status: creating RFHardware/Makefile config.status: creating SIP/Makefile config.status: creating SMS/Makefile config.status: creating Transceiver/Makefile config.status: creating TRXManager/Makefile config.status: creating config.h config.status: config.h is unchanged config.status: executing depfiles commands config.status: executing libtool commands make[1]: Leaving directory/home/gohar/openbtscopy’
make[1]: Entering directory /home/gohar/openbtscopy' make[1]: Leaving directory/home/gohar/openbtscopy’
make[1]: Entering directory /home/gohar/openbtscopy' make[1]: Leaving directory/home/gohar/openbtscopy’
make: Nothing to be done for all'. gohar@gohar:~/openbtscopy/Transceiver$ sudo make install [sudo] password for gohar: make[1]: Entering directory/home/gohar/openbtscopy/Transceiver’
make[1]: Nothing to be done for install-exec-am'. test -z "/usr/local/share/usrp/rev2" || mkdir -p -- "/usr/local/share/usrp/rev2" /usr/bin/install -c -m 644 'std_inband.rbf' '/usr/local/share/usrp/rev2/std_inband.rbf' test -z "/usr/local/share/usrp/rev4" || mkdir -p -- "/usr/local/share/usrp/rev4" /usr/bin/install -c -m 644 'std_inband.rbf' '/usr/local/share/usrp/rev4/std_inband.rbf' make[1]: Leaving directory/home/gohar/openbtscopy/Transceiver’
gohar@gohar:~/openbtscopy/Transceiver$

Gohar


From: Johnathan C. removed_email_address@domain.invalid
To: gohar anwar removed_email_address@domain.invalid
Cc: removed_email_address@domain.invalid
Sent: Wednesday, March 18, 2009 7:24:38 PM
Subject: Re: [Discuss-gnuradio] Error in compilation of
runTransceiver.cpp in OpenBTS

2009/3/17 gohar anwar removed_email_address@domain.invalid:

I am facing the following warnings and error when i compile
“runTransceiver.cpp”.

gohar@gohar:~/openbts/Transceiver$ g++
‘/home/gohar/openbts/Transceiver/runTransceiver.cpp’

You should be using the standard ./bootstrap, ./configure, and make
commands to build this, not trying to compile it directly as above.

Johnathan


#2

Gohar -

“bootstrap” is a system utility you should already have, not part of
the OpenBTS distribution. When bootstrap failed with “No such
file…”, you should have stopped and figured this obvious mistake
instead of doing something completely pointless with raw g++ and then
posting it to the list.

In the output below, everything past the failed bootstrap is useless
and irrelevant.

– David

On Mar 18, 2009, at 9:07 AM, gohar anwar wrote:

gohar@gohar:~/openbts/Transceiver$ ./configure
checking for a BSD-compatible install… /usr/bin/install -c
checking for suffix of object files… o
checking for a BSD-compatible install… /usr/bin/install -c
checking whether the shell understands some XSI constructs… yes
checking for sys/stat.h… yes
checking dependency style of g++… (cached) gcc3
checking whether -lc should be explicitly linked in… no
checking for g++ option to produce PIC… -fPIC -DPIC
checking for inline… inline
config.status: creating Makefile
config.status: creating Transceiver/Makefile
make: Nothing to be done for `all’.
/usr/bin/install -c -m 644 ‘std_inband.rbf’ '/usr/local/share/usrp/
Subject: Re: [Discuss-gnuradio] Error in compilation of
You should be using the standard ./bootstrap, ./configure, and make
commands to build this, not trying to compile it directly as above.

Johnathan


Discuss-gnuradio mailing list
removed_email_address@domain.invalid
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio

David A. Burgess
Kestrel Signal Processing, Inc.


#3

Dear David
./bootstrap did not fail when i use it in top level directory.
But the point is that all the process did not produce any
binary/executable like runTransceiver,LoopbackTest and TRXSimulator
…etc
I m interesting in these executables for testing purpose, as mentioned
in openbts/tests/README.test.

Regards,
Gohar


From: David B. removed_email_address@domain.invalid
To: gohar anwar removed_email_address@domain.invalid
Cc: Johnathan C. removed_email_address@domain.invalid;
removed_email_address@domain.invalid
Sent: Wednesday, March 18, 2009 9:25:10 PM
Subject: Re: RE : [Discuss-gnuradio] Error in compilation of
runTransceiver.cpp in OpenBTS

Gohar -

“bootstrap” is a system utility you should already have, not part of the
OpenBTS distribution. When bootstrap failed with “No such file…”, you
should have stopped and figured this obvious mistake instead of doing
something completely pointless with raw g++ and then posting it to the
list.

In the output below, everything past the failed bootstrap is useless and
irrelevant.

– David

On Mar 18, 2009, at 9:07 AM, gohar anwar wrote:

Thanks for your reply. Actually i tried to build this using the
./bootstrap, ./configure and make commands. It did not work.That’s why I
adopted the other way.

Following appears as i try to build it with standard commands. Do i have
to make changes in the “makefile”? Or how should i build this?

RESULTS OF STANDARD METHOD:

gohar@gohar:~/openbts/Transceiver$ ./bootstrap
bash: ./bootstrap: No such file or directory
gohar@gohar:~/openbts/Transceiver$ ./configure
bash: ./configure: No such file or directory
gohar@gohar:~/openbts/Transceiver$ make
cd … && make am–refresh
make[1]: Entering directory /home/gohar/openbts' /bin/bash ./config.status --recheck running CONFIG_SHELL=/bin/bash /bin/bash ./configure --no-create --no-recursion checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3 checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking whether ln -s works... yes checking whether make sets $(MAKE)... (cached) yes checking for a BSD-compatible install... /usr/bin/install -c checking for rm... /bin/rm checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for fgrep... /bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking the maximum length of command line arguments... 805306365 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking for /usr/bin/ld option to reload object files... -r checking how to recognize dependent libraries... pass_all checking for ar... ar checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking whether we are using the GNU C++ compiler... (cached) yes checking whether g++ accepts -g... (cached) yes checking dependency style of g++... (cached) gcc3 checking how to run the C++ preprocessor... g++ -E checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no checking for ld used by g++... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC -DPIC checking if g++ PIC flag -fPIC -DPIC works... yes checking if g++ static flag -static works... yes checking if g++ supports -c -o file.o... yes checking if g++ supports -c -o file.o... (cached) yes checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking for ANSI C header files... (cached) yes checking for an ANSI C-conforming const... yes checking for inline... inline checking for size_t... yes checking whether time.h and sys/time.h may both be included... yes checking whether byte ordering is bigendian... no checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.18... yes checking for USRP... yes checking for OSIP... yes checking for ORTP... yes configure: creating ./config.status /bin/bash ./config.status config.status: creating Makefile config.status: creating apps/Makefile config.status: creating config/Makefile config.status: creating doc/Makefile config.status: creating AsteriskConfig/Makefile config.status: creating CommonLibs/Makefile config.status: creating Control/Makefile config.status: creating GSM/Makefile config.status: creating RFHardware/Makefile config.status: creating SIP/Makefile config.status: creating SMS/Makefile config.status: creating Transceiver/Makefile config.status: creating TRXManager/Makefile config.status: creating config.h config.status: config.h is unchanged config.status: executing depfiles commands config.status: executing libtool commands make[1]: Leaving directory/home/gohar/openbtscopy’
make[1]: Entering directory /home/gohar/openbtscopy' make[1]: Leaving directory/home/gohar/openbtscopy’
make[1]: Entering directory /home/gohar/openbtscopy' make[1]: Leaving directory/home/gohar/openbtscopy’
make: Nothing to be done for all'. gohar@gohar:~/openbtscopy/Transceiver$ sudo make install [sudo] password for gohar: make[1]: Entering directory/home/gohar/openbtscopy/Transceiver’
make[1]: Nothing to be done for install-exec-am'. test -z "/usr/local/share/usrp/rev2" || mkdir -p -- "/usr/local/share/usrp/rev2" /usr/bin/install -c -m 644 'std_inband.rbf' '/usr/local/share/usrp/rev2/std_inband.rbf' test -z "/usr/local/share/usrp/rev4" || mkdir -p -- "/usr/local/share/usrp/rev4" /usr/bin/install -c -m 644 'std_inband.rbf' '/usr/local/share/usrp/rev4/std_inband.rbf' make[1]: Leaving directory/home/gohar/openbtscopy/Transceiver’
gohar@gohar:~/openbtscopy/Transceiver$

Gohar


From: Johnathan C. removed_email_address@domain.invalid
To: gohar anwar removed_email_address@domain.invalid
Cc: removed_email_address@domain.invalid
Sent: Wednesday, March 18, 2009 7:24:38 PM
Subject: Re: [Discuss-gnuradio] Error in compilation of
runTransceiver.cpp in OpenBTS

2009/3/17 gohar anwar removed_email_address@domain.invalid:

I am facing the following warnings and error when i compile
“runTransceiver.cpp”.

gohar@gohar:~/openbts/Transceiver$ g++
‘/home/gohar/openbts/Transceiver/runTransceiver.cpp’

You should be using the standard ./bootstrap, ./configure, and make
commands to build this, not trying to compile it directly as above.

Johnathan


Discuss-gnuradio mailing list
removed_email_address@domain.invalid
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio

David A. Burgess
Kestrel Signal Processing, Inc.