14 Jan
2011
14 Jan
'11
1:53 p.m.
Hi,
I just started playing around with this great project and am ashamed to say I'm
stumped with an annoying error when compiling.
I'm compiling on a Backtrack 4 RC2 (*buntu based distro) and that may be why I'm
having problems.
Basically I downloaded the proper packages as per the instructions on the wiki,
exported the PATH and all that, but when I run make I get this error:
cd shared/libosmocore/build-target && ../configure \
--host=arm-elf-linux --disable-vty
--enable-panic-infloop \
--disable-shared --disable-talloc --disable-tests \
CC="arm-elf-gcc" CFLAGS="-Os -ffunction-sections
-I/root/GSM/osmocom-bb/src/target/firmware/include"
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
configure: error: cannot find install-sh or install.sh in ".." "../.."
"../../.."
make: *** [shared/libosmocore/build-target/Makefile] Error 1
Attached is my config.log and you can see the PATH are there.
The error can be seen on this line in the log "configure:1766: error: cannot
find install-sh or install.sh in ".." "../.." "../../.."
Now i've checked to see if I have autoconf and automake installed (I do, I have
autoconf 2.61 and automake 1.10) since my searches on the internet seem to
indicate that maybe the problem.
Now I usually do all my own leg work and I read and read before asking
questions, but I'm afraid I can't resolve this on my own. Before I spend another
afternoon searching for the solution, I remembered to ask here.
Anyone have any hints on what I'm doing wrong? Do I need different automake or
autoconf versions?
Thanks and keep up the great work. It's been fascinating to watch the evolution
of GSM hacking these last few years.
14 Jan
14 Jan
10:52 p.m.
Hi,
if you didn't install "libtool" (apt-get install libtool), you'll get
this error if you try to compile the source for the second time.
Install libtool, clean up your source tree (delete the temp files
generated by the autotools; cloning again may be easier for you) and try
again.
Cheers,
Stephan
On 01/14/2011 01:53 PM, quem tu quiseres wrote:
Hi,
I just started playing around with this great project and am ashamed to say I'm
stumped with an annoying error when compiling.
I'm compiling on a Backtrack 4 RC2 (*buntu based distro) and that may be why I'm
having problems.
Basically I downloaded the proper packages as per the instructions on the wiki,
exported the PATH and all that, but when I run make I get this error:
cd shared/libosmocore/build-target && ../configure \
--host=arm-elf-linux --disable-vty
--enable-panic-infloop \
--disable-shared --disable-talloc --disable-tests \
CC="arm-elf-gcc" CFLAGS="-Os -ffunction-sections
-I/root/GSM/osmocom-bb/src/target/firmware/include"
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
configure: error: cannot find install-sh or install.sh in ".."
"../.."
"../../.."
make: *** [shared/libosmocore/build-target/Makefile] Error 1
Attached is my config.log and you can see the PATH are there.
The error can be seen on this line in the log "configure:1766: error: cannot
find install-sh or install.sh in ".." "../.." "../../.."
Now i've checked to see if I have autoconf and automake installed (I do, I have
autoconf 2.61 and automake 1.10) since my searches on the internet seem to
indicate that maybe the problem.
Now I usually do all my own leg work and I read and read before asking
questions, but I'm afraid I can't resolve this on my own. Before I spend another
afternoon searching for the solution, I remembered to ask here.
Anyone have any hints on what I'm doing wrong? Do I need different automake or
autoconf versions?
Thanks and keep up the great work. It's been fascinating to watch the evolution
of GSM hacking these last few years.
15 Jan
15 Jan
2:19 p.m.
Thanks for your help Stephan.
I had libtool installed already but for some reason it wasn't working well in
the BT4 install.
After much frustration I ended up doing a fresh ubuntu install on virtualbox and
ran into other problems that others may experience if they try this route.
Basically my problem has to do with the recognition of the USB/serial prolific
cable by the guest OS (ubuntu). If you experience this issue too I recommend a
reboot of both host and guest with the cable hooked up (and previously installed
on your host). After much head scratching a good 'ole reboot did the trick.
Now I can finally talk to my C115 and can't wait to to explore the different
tools.
Anyone have any recommendations on where to start, what apps to try first,
guides, etc (besides the wiki)?
Thanks again,
John
P.S. I gather that Sylvain's code to "strip" the encryption from the stream
passed by the DSP isn't available. Are there any plans to share that too?
----- Original Message ----
From: Stephan Meier <stephan.meier(a)unitybox.de>
To: quem tu quiseres <quemtuquiseres1(a)yahoo.com>
Cc: baseband-devel(a)lists.osmocom.org
Sent: Fri, January 14, 2011 9:52:42 PM
Subject: Re: Problem compiling OsmocomBB on BT4 RC2
Hi,
if you didn't install "libtool" (apt-get install libtool), you'll get
this error if you try to compile the source for the second time.
Install libtool, clean up your source tree (delete the temp files
generated by the autotools; cloning again may be easier for you) and try
again.
Cheers,
Stephan
On 01/14/2011 01:53 PM, quem tu quiseres wrote:
Hi,
I just started playing around with this great project and am ashamed to say I'm
stumped with an annoying error when compiling.
I'm compiling on a Backtrack 4 RC2 (*buntu based distro) and that may be why
I'm
having problems.
Basically I downloaded the proper packages as per the instructions on the wiki,
exported the PATH and all that, but when I run make I get this error:
cd shared/libosmocore/build-target && ../configure \
--host=arm-elf-linux --disable-vty
--enable-panic-infloop \
--disable-shared --disable-talloc --disable-tests \
CC="arm-elf-gcc" CFLAGS="-Os -ffunction-sections
-I/root/GSM/osmocom-bb/src/target/firmware/include"
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
configure: error: cannot find install-sh or install.sh in ".."
"../.."
"../../.."
make: *** [shared/libosmocore/build-target/Makefile] Error 1
Attached is my config.log and you can see the PATH are there.
The error can be seen on this line in the log "configure:1766: error: cannot
find install-sh or install.sh in ".." "../.." "../../.."
Now i've checked to see if I have autoconf and automake installed (I do, I have
autoconf 2.61 and automake 1.10) since my searches on the internet seem to
indicate that maybe the problem.
Now I usually do all my own leg work and I read and read before asking
questions, but I'm afraid I can't resolve this on my own. Before I spend
another
afternoon searching for the solution, I remembered to ask here.
Anyone have any hints on what I'm doing wrong? Do I need different automake or
autoconf versions?
Thanks and keep up the great work. It's been fascinating to watch the evolution
of GSM hacking these last few years.
17 Jan
17 Jan
5:20 p.m.
Hi again,
In case anyone was wondering, I had libtool installed but for some reason it wasn't
working right when compiling so I reinstalled it, deleted the osmocom branch and started
over from scratch. This time it worked without a problem and i managed to get layer21 up
and running on my C115. So if you get similar error messages I recommend deleting and
starting over from scratch.
Now I tried to play around with sylvain's testing branch and I'm getting compile
errors. I know this is a bit long to post here but maybe someone here knows what these
errors are all about. You can see that the errors begin with the simtest app:
rm-elf-gcc -mcpu=arm7tdmi -Iinclude/ -I../../../include -I../../shared/libosmocore/include
-Wall -Wextra -Wcast-align -Wimplicit -Wunused -Wswitch -Wredundant-decls -Wreturn-type
-Wshadow -Wnested-externs -Wbad-function-cast -Wsign-compare -Waggregate-return -Os
-ffunction-sections -gdwarf-2
-DGIT_REVISION=\"osmocon_v0.0.0-756-g999254a-modified\" -DCONFIG_TX_ENABLE
-DCONFIG_FLASH_WRITE -Wa,-adhlns=apps/simtest/main.lst -c -o apps/simtest/main.o
apps/simtest/main.c
apps/simtest/main.c:161: error: parse error before '<<' token
apps/simtest/main.c:168: error: parse error before numeric constant
apps/simtest/main.c:168: warning: type defaults to `int' in declaration of
`memset'
apps/simtest/main.c:168: error: conflicting types for 'memset'
apps/simtest/main.c:168: error: conflicting types for 'memset'
apps/simtest/main.c:168: warning: data definition has no type or storage class
apps/simtest/main.c:169: error: parse error before '(' token
apps/simtest/main.c: In function `sim_run_gsm_algorith':
apps/simtest/main.c:179: warning: declaration of 'status_word' shadows a global
declaration
apps/simtest/main.c:166: warning: shadowed declaration is here
apps/simtest/main.c: At top level:
apps/simtest/main.c:215: error: parse error before '>>' token
apps/simtest/main.c:230: error: parse error before numeric constant
apps/simtest/main.c:237: error: parse error before numeric constant
apps/simtest/main.c:239: error: parse error before string constant
apps/simtest/main.c:239: warning: type defaults to `int' in declaration of `puts'
apps/simtest/main.c:239: warning: redundant redeclaration of 'puts'
apps/simtest/main.c:239: warning: data definition has no type or storage class
apps/simtest/main.c:242: error: parse error before string constant
apps/simtest/main.c:242: warning: type defaults to `int' in declaration of `puts'
apps/simtest/main.c:242: warning: redundant redeclaration of 'puts'
apps/simtest/main.c:242: warning: data definition has no type or storage class
apps/simtest/main.c:243: warning: type defaults to `int' in declaration of
`calypso_sim_init'
apps/simtest/main.c:243: error: conflicting types for 'calypso_sim_init'
include/calypso/sim.h:184: error: previous declaration of 'calypso_sim_init' was
here
apps/simtest/main.c:243: error: conflicting types for 'calypso_sim_init'
include/calypso/sim.h:184: error: previous declaration of 'calypso_sim_init' was
here
apps/simtest/main.c:243: warning: data definition has no type or storage class
apps/simtest/main.c:246: error: parse error before string constant
apps/simtest/main.c:246: warning: type defaults to `int' in declaration of `puts'
apps/simtest/main.c:246: warning: redundant redeclaration of 'puts'
apps/simtest/main.c:246: warning: data definition has no type or storage class
apps/simtest/main.c:247: error: parse error before numeric constant
apps/simtest/main.c:248: warning: type defaults to `int' in declaration of
`atrLength'
apps/simtest/main.c:248: error: conflicting types for 'atrLength'
apps/simtest/main.c:228: error: previous definition of 'atrLength' was here
apps/simtest/main.c:248: error: initializer element is not constant
apps/simtest/main.c:248: warning: data definition has no type or storage class
apps/simtest/main.c:249: warning: type defaults to `int' in declaration of
`myHexdump'
apps/simtest/main.c:249: warning: parameter names (without types) in function declaration
apps/simtest/main.c:249: error: conflicting types for 'myHexdump'
apps/simtest/main.c:51: error: previous definition of 'myHexdump' was here
apps/simtest/main.c:249: warning: data definition has no type or storage class
apps/simtest/main.c:252: error: parse error before string constant
apps/simtest/main.c:252: warning: type defaults to `int' in declaration of `puts'
apps/simtest/main.c:252: warning: redundant redeclaration of 'puts'
apps/simtest/main.c:252: warning: data definition has no type or storage class
apps/simtest/main.c:253: error: parse error before numeric constant
apps/simtest/main.c:254: warning: type defaults to `int' in declaration of
`atrLength'
apps/simtest/main.c:254: error: redefinition of 'atrLength'
apps/simtest/main.c:248: error: previous definition of 'atrLength' was here
apps/simtest/main.c:254: error: redefinition of 'atrLength'
apps/simtest/main.c:248: error: previous definition of 'atrLength' was here
apps/simtest/main.c:254: error: initializer element is not constant
apps/simtest/main.c:254: warning: data definition has no type or storage class
apps/simtest/main.c:255: warning: type defaults to `int' in declaration of
`myHexdump'
apps/simtest/main.c:255: warning: parameter names (without types) in function declaration
apps/simtest/main.c:255: warning: redundant redeclaration of 'myHexdump'
apps/simtest/main.c:249: warning: previous declaration of 'myHexdump' was here
apps/simtest/main.c:255: warning: data definition has no type or storage class
apps/simtest/main.c:259: warning: type defaults to `int' in declaration of
`testDataBody'
apps/simtest/main.c:259: error: conflicting types for 'testDataBody'
apps/simtest/main.c:222: error: previous declaration of 'testDataBody' was here
apps/simtest/main.c:259: error: invalid initializer
apps/simtest/main.c:259: warning: data definition has no type or storage class
apps/simtest/main.c:260: warning: type defaults to `int' in declaration of
`testDataBody'
apps/simtest/main.c:260: error: conflicting types for 'testDataBody'
apps/simtest/main.c:259: error: previous definition of 'testDataBody' was here
apps/simtest/main.c:260: error: conflicting types for 'testDataBody'
apps/simtest/main.c:259: error: previous definition of 'testDataBody' was here
apps/simtest/main.c:260: error: invalid initializer
apps/simtest/main.c:260: warning: data definition has no type or storage class
apps/simtest/main.c:261: error: parse error before numeric constant
apps/simtest/main.c:261: warning: type defaults to `int' in declaration of
`calypso_sim_transceive'
apps/simtest/main.c:261: error: conflicting types for 'calypso_sim_transceive'
apps/simtest/main.c:261: note: an argument type that has a default promotion can't
match an empty parameter name list declaration
include/calypso/sim.h:175: error: previous declaration of 'calypso_sim_transceive'
was here
apps/simtest/main.c:261: error: conflicting types for 'calypso_sim_transceive'
apps/simtest/main.c:261: note: an argument type that has a default promotion can't
match an empty parameter name list declaration
include/calypso/sim.h:175: error: previous declaration of 'calypso_sim_transceive'
was here
apps/simtest/main.c:261: warning: data definition has no type or storage class
apps/simtest/main.c:262: error: parse error before numeric constant
apps/simtest/main.c:262: warning: type defaults to `int' in declaration of
`calypso_sim_transceive'
apps/simtest/main.c:262: warning: redundant redeclaration of
'calypso_sim_transceive'
apps/simtest/main.c:261: warning: previous declaration of 'calypso_sim_transceive'
was here
apps/simtest/main.c:262: warning: data definition has no type or storage class
apps/simtest/main.c:263: error: parse error before numeric constant
apps/simtest/main.c:263: warning: type defaults to `int' in declaration of
`myHexdump'
apps/simtest/main.c:263: warning: redundant redeclaration of 'myHexdump'
apps/simtest/main.c:255: warning: previous declaration of 'myHexdump' was here
apps/simtest/main.c:263: warning: data definition has no type or storage class
apps/simtest/main.c:265: error: parse error before string constant
apps/simtest/main.c:265: warning: type defaults to `int' in declaration of `puts'
apps/simtest/main.c:265: warning: redundant redeclaration of 'puts'
apps/simtest/main.c:265: warning: data definition has no type or storage class
apps/simtest/main.c:267: error: parse error before string constant
apps/simtest/main.c:267: warning: type defaults to `int' in declaration of `puts'
apps/simtest/main.c:267: warning: redundant redeclaration of 'puts'
apps/simtest/main.c:267: warning: data definition has no type or storage class
apps/simtest/main.c:268: error: parse error before string constant
apps/simtest/main.c:270: error: parse error before string constant
apps/simtest/main.c:270: warning: type defaults to `int' in declaration of `puts'
apps/simtest/main.c:270: warning: redundant redeclaration of 'puts'
apps/simtest/main.c:270: warning: data definition has no type or storage class
apps/simtest/main.c:271: error: parse error before string constant
apps/simtest/main.c:273: error: parse error before string constant
apps/simtest/main.c:273: warning: type defaults to `int' in declaration of `puts'
apps/simtest/main.c:273: warning: redundant redeclaration of 'puts'
apps/simtest/main.c:273: warning: data definition has no type or storage class
apps/simtest/main.c:274: error: parse error before string constant
apps/simtest/main.c:276: error: parse error before string constant
apps/simtest/main.c:276: warning: type defaults to `int' in declaration of `puts'
apps/simtest/main.c:276: warning: redundant redeclaration of 'puts'
apps/simtest/main.c:276: warning: data definition has no type or storage class
apps/simtest/main.c:277: error: parse error before string constant
apps/simtest/main.c:279: error: parse error before string constant
apps/simtest/main.c:279: warning: type defaults to `int' in declaration of `puts'
apps/simtest/main.c:279: warning: redundant redeclaration of 'puts'
apps/simtest/main.c:279: warning: data definition has no type or storage class
apps/simtest/main.c:280: error: parse error before string constant
apps/simtest/main.c:282: error: parse error before numeric constant
apps/simtest/main.c:283: error: parse error before string constant
apps/simtest/main.c:283: warning: type defaults to `int' in declaration of `puts'
apps/simtest/main.c:283: warning: redundant redeclaration of 'puts'
apps/simtest/main.c:283: warning: data definition has no type or storage class
apps/simtest/main.c:284: error: parse error before string constant
apps/simtest/main.c:285: error: parse error before string constant
apps/simtest/main.c:285: warning: type defaults to `int' in declaration of
`printf'
apps/simtest/main.c:285: error: conflicting types for 'printf'
apps/simtest/main.c:285: note: a parameter list with an ellipsis can't match an empty
parameter name list declaration
apps/simtest/main.c:285: error: conflicting types for 'printf'
apps/simtest/main.c:285: note: a parameter list with an ellipsis can't match an empty
parameter name list declaration
apps/simtest/main.c:285: warning: data definition has no type or storage class
apps/simtest/main.c:286: error: parse error before numeric constant
apps/simtest/main.c:286: warning: type defaults to `int' in declaration of
`myHexdump'
apps/simtest/main.c:286: warning: redundant redeclaration of 'myHexdump'
apps/simtest/main.c:263: warning: previous declaration of 'myHexdump' was here
apps/simtest/main.c:286: warning: data definition has no type or storage class
apps/simtest/main.c:288: error: parse error before numeric constant
apps/simtest/main.c:289: error: parse error before string constant
apps/simtest/main.c:289: warning: type defaults to `int' in declaration of
`memcpy'
apps/simtest/main.c:289: error: conflicting types for 'memcpy'
apps/simtest/main.c:289: error: conflicting types for 'memcpy'
apps/simtest/main.c:289: warning: data definition has no type or storage class
apps/simtest/main.c:290: error: parse error before string constant
apps/simtest/main.c:290: warning: type defaults to `int' in declaration of `puts'
apps/simtest/main.c:290: warning: redundant redeclaration of 'puts'
apps/simtest/main.c:290: warning: data definition has no type or storage class
apps/simtest/main.c:291: error: parse error before string constant
apps/simtest/main.c:292: error: parse error before string constant
apps/simtest/main.c:292: warning: type defaults to `int' in declaration of
`printf'
apps/simtest/main.c:292: warning: redundant redeclaration of 'printf'
apps/simtest/main.c:285: warning: previous declaration of 'printf' was here
apps/simtest/main.c:292: warning: data definition has no type or storage class
apps/simtest/main.c:293: error: parse error before numeric constant
apps/simtest/main.c:293: warning: type defaults to `int' in declaration of
`myHexdump'
apps/simtest/main.c:293: warning: redundant redeclaration of 'myHexdump'
apps/simtest/main.c:286: warning: previous declaration of 'myHexdump' was here
apps/simtest/main.c:293: warning: data definition has no type or storage class
apps/simtest/main.c:295: error: parse error before numeric constant
apps/simtest/main.c:295: warning: type defaults to `int' in declaration of
`delay_ms'
apps/simtest/main.c:295: error: conflicting types for 'delay_ms'
apps/simtest/main.c:207: error: previous definition of 'delay_ms' was here
apps/simtest/main.c:295: warning: data definition has no type or storage class
apps/simtest/main.c:297: warning: type defaults to `int' in declaration of
`calypso_sim_powerdown'
apps/simtest/main.c:297: error: conflicting types for 'calypso_sim_powerdown'
include/calypso/sim.h:161: error: previous declaration of 'calypso_sim_powerdown'
was here
apps/simtest/main.c:297: error: conflicting types for 'calypso_sim_powerdown'
include/calypso/sim.h:161: error: previous declaration of 'calypso_sim_powerdown'
was here
apps/simtest/main.c:297: warning: data definition has no type or storage class
apps/simtest/main.c:299: error: parse error before string constant
apps/simtest/main.c:299: warning: type defaults to `int' in declaration of `puts'
apps/simtest/main.c:299: warning: redundant redeclaration of 'puts'
apps/simtest/main.c:299: warning: data definition has no type or storage class
apps/simtest/main.c: In function `console_rx_cb':
apps/simtest/main.c:311: warning: `return' with no value, in function returning
non-void
apps/simtest/main.c: In function `main':
apps/simtest/main.c:350: warning: passing arg 2 of `sercomm_register_rx_cb' from
incompatible pointer type
apps/simtest/main.c:352: warning: implicit declaration of function `do_sim_test'
apps/simtest/main.c:352: warning: nested extern declaration of `do_sim_test'
apps/simtest/main.c: At top level:
apps/simtest/main.c:51: warning: 'myHexdump' defined but not used
make[1]: *** [apps/simtest/main.o] Error 1
make[1]: Leaving directory `/root/install/osmocom-bb/src/target/firmware'
make: *** [firmware] Error 2
Any hints are appreciated.
Thanks,
John
P.S. After telnetting to osmocon and running enable, how do I configure it to use my sim?
I know I'm supposed to add "sim reader" to
my osmocom.cfg, but I'm not sure where to add it or whether I have to change anything
else in that file.
--- On Sat, 1/15/11, quem tu quiseres <quemtuquiseres1(a)yahoo.com> wrote:
From: quem tu quiseres
<quemtuquiseres1(a)yahoo.com>
Subject: Re: Problem compiling OsmocomBB on BT4 RC2
To: "Stephan Meier" <stephan.meier(a)unitybox.de>
Cc: baseband-devel(a)lists.osmocom.org
Date: Saturday, January 15, 2011, 5:19 AM
Thanks for your help Stephan.
I had libtool installed already but for some reason it
wasn't working well in
the BT4 install.
After much frustration I ended up doing a fresh ubuntu
install on virtualbox and
ran into other problems that others may experience if they
try this route.
Basically my problem has to do with the recognition of the
USB/serial prolific
cable by the guest OS (ubuntu). If you experience this
issue too I recommend a
reboot of both host and guest with the cable hooked up (and
previously installed
on your host). After much head scratching a good 'ole
reboot did the trick.
Now I can finally talk to my C115 and can't wait to to
explore the different
tools.
Anyone have any recommendations on where to start, what
apps to try first,
guides, etc (besides the wiki)?
Thanks again,
John
P.S. I gather that Sylvain's code to "strip" the encryption
from the stream
passed by the DSP isn't available. Are there any plans to
share that too?
----- Original Message ----
From: Stephan Meier <stephan.meier(a)unitybox.de>
To: quem tu quiseres <quemtuquiseres1(a)yahoo.com>
Cc: baseband-devel(a)lists.osmocom.org
Sent: Fri, January 14, 2011 9:52:42 PM
Subject: Re: Problem compiling OsmocomBB on BT4 RC2
Hi,
if you didn't install "libtool" (apt-get install libtool),
you'll get
this error if you try to compile the source for the second
time.
Install libtool, clean up your source tree (delete the temp
files
generated by the autotools; cloning again may be easier for
you) and try
again.
Cheers,
Stephan
On 01/14/2011 01:53 PM, quem tu quiseres wrote:
--host=arm-elf-linux
--disable-vty
> --enable-panic-infloop \
--disable-shared
--disable-talloc --disable-tests \
CC="arm-elf-gcc"
CFLAGS="-Os
-ffunction-sections
Hi,
I just started playing around with this great project
and am ashamed to say
I'm
stumped with an annoying error when compiling.
I'm compiling on a Backtrack 4 RC2 (*buntu based
distro) and that may be why
I'm
having problems.
Basically I downloaded the proper packages as per the
instructions on the wiki,
exported the PATH and all that, but when I run make I
get this error:
cd shared/libosmocore/build-target &&
../configure \
-I/root/GSM/osmocom-bb/src/target/firmware/include"
configure: WARNING: If you wanted to set the --build
type, don't use --host.
If a cross compiler is
detected then
cross compile mode will be used.
configure: error: cannot find install-sh or
install.sh
in ".." "../.."
"../../.."
make: *** [shared/libosmocore/build-target/Makefile]
Error 1
Attached is my config.log and you can see the PATH are
there.
The error can be seen on this line in the log
"configure:1766: error: cannot
find install-sh or install.sh in ".."
"../.."
"../../.."
Now i've checked to see if I have autoconf and
automake installed (I do, I
have
autoconf 2.61 and automake 1.10) since my searches on
the internet seem to
indicate that maybe the problem.
Now I usually do all my own leg work and I read and
read before asking
questions, but I'm afraid I can't resolve
this on my
own. Before I spend
another
afternoon searching for the solution, I remembered to
ask here.
Anyone have any hints on what I'm doing wrong? Do I
need different automake or
autoconf versions?
Thanks and keep up the great work. It's been
fascinating to watch the
evolution
>
> of GSM hacking these last few years. 
5:26 p.m.
On 01/17/2011 05:20 PM, quem tu quiseres wrote:
Hi again,
In case anyone was wondering, I had libtool installed but for some reason it wasn't
working right when compiling so I reinstalled it, deleted the osmocom branch and started
over from scratch. This time it worked without a problem and i managed to get layer21 up
and running on my C115. So if you get similar error messages I recommend deleting and
starting over from scratch.
Now I tried to play around with sylvain's testing branch and I'm getting compile
errors. I know this is a bit long to post here but maybe someone here knows what these
errors are all about. You can see that the errors begin with the simtest app:
rm-elf-gcc -mcpu=arm7tdmi -Iinclude/ -I../../../include
-I../../shared/libosmocore/include -Wall -Wextra -Wcast-align -Wimplicit -Wunused -Wswitch
-Wredundant-decls -Wreturn-type -Wshadow -Wnested-externs -Wbad-function-cast
-Wsign-compare -Waggregate-return -Os -ffunction-sections -gdwarf-2
-DGIT_REVISION=\"osmocon_v0.0.0-756-g999254a-modified\" -DCONFIG_TX_ENABLE
-DCONFIG_FLASH_WRITE -Wa,-adhlns=apps/simtest/main.lst -c -o apps/simtest/main.o
apps/simtest/main.c
apps/simtest/main.c:161: error: parse error before '<<' token
apps/simtest/main.c:168: error: parse error before numeric constant
this is not C++... so you have a merge error... on the merge you did... fix
the merge error...
5:35 p.m.
Hi,
this is because of the simtest-app in sylvain/testing being currently
broken. Simply remove it from the "APPLICATIONS?="-line in the firmware
Makefile (src/target/firmware).
Regards,
Steve
5:43 p.m.
We should just stop giving answer ...
It's like a "test" ... It's an experimental branch. if you can't
compile it you shouldn't be running it in the first place.
Sylvain
6:07 p.m.
Easy there. I realize it's only a test and I did search the list before asking.
While I'm a newbie here I am learning and I did manage to compile it and have it
running already and am having fun watching the broadcast traffic go by. Slowly I'm
starting to dig deeper and understand it better.
And I do appreciate all the work you guys have been doing for years now and your
willingness to share and help out others.
If we don't start exploring, make mistakes and ask silly questions how will we ever
progress? I remember over 10 years ago getting similar reactions when I first started out
trying to clone my SIM card and everyone said it was impossible and/or the network would
never allow 2 identical SIMs to be connected at the same time. Well they were wrong
because I managed to clone my SIM onto a gold wafer card and I was able to register both
at the same time (although only the latest phone to register would actually receive calls,
etc.).
Anyway, to make a long story short, although we may be newbies in GSM and osmocom, and
many maybe come here to find a click and record script to listen to GSM (because
that's what they read in the silly media), many of us are actually here trying to
learn and appreciate some help since it's hard to find any thorough documentation.
Thanks again,
John
--- On Mon, 1/17/11, Sylvain Munaut <246tnt(a)gmail.com> wrote:
From: Sylvain Munaut <246tnt(a)gmail.com>
Subject: Re: Problem compiling OsmocomBB on BT4 RC2
To: "Steve Markgraf" <steve(a)steve-m.de>
Cc: baseband-devel(a)lists.osmocom.org, "quem tu quiseres"
<quemtuquiseres1(a)yahoo.com>
Date: Monday, January 17, 2011, 8:43 AM
We should just stop giving answer
...
It's like a "test" ... It's an experimental branch. if you
can't
compile it you shouldn't be running it in the first place.
Sylvain
6:21 p.m.
Easy there. I realize it's only a test and I did
search the list before asking.
Well, you obviously didn't do THE FIRST THING you should have: open
the damn file that failed !
It should then have become obvious where the problem was. (and if it
wasn't you've got more serious problems ...)
I have nothing against GSM newbies, but before asking I think you always should:
- Check the Wiki
- Check the Mailing list
- Just plain google for it
- Try to fix it yourself for at least a few hours
- Read the relevant specifications / schematics / whatever doc may be
applicable
(the two last items are not applicable to all questions obviously)
And if it's a build error, then you should even try harder to fix it
yourself because you should just know how all theses things work
already ...
And only if all the above failed, then ask on the ml or IRC.
Don't take it personally, but lately all questions on IRC and the ML
have mostly been around:
- Building
- Serial cable
- Finding phones on ebay
All things you really should be able to solve by yourself without
asking ... all the info is out there, and frankly it's getting
annoying.
Cheers,
Sylvain
18 Jan
18 Jan
10:28 a.m.
Hi,
what about a baseband-users mailing list to keep this one free of the 'git'
and 'make' help requests that keep coming?
Sebastien
On Mon, Jan 17, 2011 at 6:21 PM, Sylvain Munaut <246tnt(a)gmail.com> wrote:
Easy there. I
realize it's only a test and I did search the list before
asking.
Well, you obviously didn't do THE FIRST THING you should have: open
the damn file that failed !
It should then have become obvious where the problem was. (and if it
wasn't you've got more serious problems ...)
I have nothing against GSM newbies, but before asking I think you always
should:
- Check the Wiki
- Check the Mailing list
- Just plain google for it
- Try to fix it yourself for at least a few hours
- Read the relevant specifications / schematics / whatever doc may be
applicable
(the two last items are not applicable to all questions obviously)
And if it's a build error, then you should even try harder to fix it
yourself because you should just know how all theses things work
already ...
And only if all the above failed, then ask on the ml or IRC.
Don't take it personally, but lately all questions on IRC and the ML
have mostly been around:
- Building
- Serial cable
- Finding phones on ebay
All things you really should be able to solve by yourself without
asking ... all the info is out there, and frankly it's getting
annoying.
Cheers,
Sylvain
10:56 a.m.
New subject: splitting the list into user and developer list
Hi Sebastien,
On Tue, Jan 18, 2011 at 10:28:47AM +0100, Sébastien Lorquet wrote:
what about a baseband-users mailing list to keep this
one free of the 'git'
and 'make' help requests that keep coming?
I think the traffic on this list is not that high, and we should avoid
fragmenting the number of lists. I did that with some projects in the past,
and didn't make particularly good experiences with it.
My suggestion would be for Sylvain, Andreas, Steve, myself and others to simply
refrain from answering the same question over and over again. Either other
people from the community will respond to those kind of questions, or the
original poster may consider reading the archive if he doesn't get any
response.
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
17 Jan
17 Jan
6:04 p.m.
On 01/17/2011 05:20 PM, quem tu quiseres wrote:
Any hints are appreciated.
Thanks,
John
The "dirty and easy" way: delete lines with >>>>> or
<<<< (they are old
diffs) and comment the targets that don't compile.
Base apps work this way.
Anyway Sylvain is right: a testing branch isn't expected to compile as
the trunk should :).
5279
days inactive
5282
days old
baseband-devel@lists.osmocom.org
13 comments
10 participants
participants (10)
-
Dario Lombardo -
Harald Welte -
Holger Hans Peter Freyther -
Mathias Dalheimer -
Peter Stuge -
quem tu quiseres -
Stephan Meier -
Steve Markgraf -
Sylvain Munaut -
Sébastien Lorquet