Hi, I'm a newbie of kamailio. I'm an Asterisk expert, and I want to explore the
"*SER" world, because I need a real SIP proxy. I planned kamailio project to
begin. I want the radius auth. I have a question about a compile message. If I try to compile kamailio- 1.5.0-tls, I always receive the message "cfg.y: conflicts: 1 shift/reduce"
Before build: # make distclean # make mantainer- clean
and then: # make all
bison -d -b cfg cfg.y cfg.y: conflicts: 1 shift/reduce flex cfg.lex
The rest of build is OK, without errors. Is this a
problem or is normal? And if is not normal, how to avoid this problem? I have a Debian Lenny # uname -a Linux voicelab 2.6.26-1-686 #1 SMP Sat Jan 10 18:29: 31 UTC 2009 i686 GNU/Linux
Uncomment:
Makefile: TLS=1 FREERADIUS=1
Makefile. vars MODS_MYSQL=on and MODS_RADIUS=on
/usr/local/src/kamailio/kamailio-1.5.0- tls/modules/acc/Makefile ENABLE_RADIUS_ACC=true
Many thanks
Priz
priz@libero.it writes:
bison -d -b cfg cfg.y cfg.y: conflicts: 1 shift/reduce flex cfg.lex
The rest of build is OK, without errors. Is this a problem or is normal? And if is not normal, how to avoid this problem?
the conflict message has been there forever so i guess you can call it "normal".
-- juha
On Sunday 19 April 2009, Juha Heinanen wrote:
priz@libero.it writes:
bison -d -b cfg cfg.y cfg.y: conflicts: 1 shift/reduce flex cfg.lex
The rest of build is OK, without errors. Is this a problem or is normal? And if is not normal, how to avoid this problem?
the conflict message has been there forever so i guess you can call it "normal".
Hi Priz,
yes, its only kind some kind of information messages from the bison parser generator (for the configuration file parser), its harmless.
Cheers,
Henning
On 04/20/2009 11:25 AM, Henning Westerholt wrote:
On Sunday 19 April 2009, Juha Heinanen wrote:
priz@libero.it writes:
bison -d -b cfg cfg.y cfg.y: conflicts: 1 shift/reduce flex cfg.lex
The rest of build is OK, without errors. Is this a problem or is normal? And if is not normal, how to avoid this problem?
the conflict message has been there forever so i guess you can call it "normal".
Hi Priz,
yes, its only kind some kind of information messages from the bison parser generator (for the configuration file parser), its harmless.
and it is related to the if-then-else statement: http://docs.freebsd.org/info/bison/bison.info.Shift_Reduce.html
It is resolved to shift, which is ok (else is bound to innermost if).
Cheers, Daniel
-
Daniel-Constantin Mierla -
Henning Westerholt -
jh＠tutpro.com -
priz＠libero.it