Hi Guys,
I hope this is the correct mailing list for this question.
I have a dual 1.6 Ghz Itanium with 4 Gb of memory. Yes, a lot of power
for Asterisk. I am running SuSE Enterprise Server with the
2.6.5-7.97-default kernel. I have just started to look into Asterisk and
I am in the building
Jonas Arndt wrote:
The problem I am currently facing seem to be in the codecs/gsm
directory. I am getting the error:
===
make[2]: Entering directory `/usr/src/asterisk/codecs/gsm'
if [ ! -d ./lib ] ; then mkdir ./lib ; fi
gcc -pipe
On Tuesday 09 Aug 2005 17:26, Jonas Arndt wrote:
Hi Guys,
I hope this is the correct mailing list for this question.
I have a dual 1.6 Ghz Itanium with 4 Gb of memory. Yes, a lot of power
for Asterisk. I am running SuSE Enterprise Server with the
2.6.5-7.97-default kernel. I have just
Thanks Guys,
I should have mentioned that I have already tried to remove the flag.
What happens then is that I run into other issues.
=
gcc -pipe -Wall -Wstrict-prototypes -Wmissing-prototypes
-Wmissing-declarations
-g
Hi Again,
I removed codec_gsm.so from codecs/Makefile and the build work. Like I
said, I am not too familiar with Asterisk yet. What implications will
this have to the functionality?
Thanks,
// Jonas
Jonas Arndt wrote:
Thanks Guys,
I should have mentioned that I have already tried to
Hi,
The story never ends After a succesful buld without gsm codec, I
installed it and ran:
itanium:/etc/asterisk # /usr/sbin/asterisk -cvvv
== Parsing '/etc/asterisk/asterisk.conf': Not found (No such file or
directory)
== Parsing '/etc/asterisk/extconfig.conf': Not found (No such file
Did you ever try asterisk on a non itanium ?
You dont have a single configuration file on your machine, of course it
doesnt work :p
zoa
Jonas Arndt wrote:
Hi,
The story never ends After a succesful buld without gsm codec, I
installed it and ran:
itanium:/etc/asterisk #
Hi Zoa,
Nope, I didn't. I thought I was VERY clear on that point. What I did was
following the guidlines in the An introduction to Asterisk document.It
told me to create certain conf files in /etc/asterisk and then start it,
which I did.
In any case, I find it EXTREMELY hard to believe that
why not go back into your * src tree and 'make samples'?
On Tue, 2005-08-09 at 10:59, Jonas Arndt wrote:
Hi Zoa,
Nope, I didn't. I thought I was VERY clear on that point. What I did was
following the guidlines in the An introduction to Asterisk document.It
told me to create certain conf
Hi,
I will do that. I think you are missing the point here though. If a
program would SegFault from missing conf files, it would be a HUGE bug.
The problem I am facing is most likely due to my plattform. As they
have build Debian packages for Itanium I was hoping that somebody would
have
On Tue, 2005-08-09 at 13:55 -0600, Jonas Arndt wrote:
I will do that. I think you are missing the point here though. If a
program would SegFault from missing conf files, it would be a HUGE
bug.
Why is it a _huge_ bug? The software _will not_ run without it's config
files in place. This is
Dave,
A segmentation fault is usually caused by the program writing in a
memory area that is not allocated (it could be a result of the optimizer
sometime as well). That means that it can potentially overwrite code
that are executing there. In worst case scenario you could even cause a
Jose,
It might help to have a look at the debian SOURCE package for Asterisk.
Here is the Debian DIFF File
http://ftp.debian.org/debian/pool/main/a/asterisk/asterisk_1.0.7.dfsg.1-2.diff.gz
They've obviously been successful in compiling it for Itanium - maybe something
obvious will jump out.
I
Ben,
This is an enormous help. This is exactly what I was looking for.
THANKS,
// Jonas
Asterisk wrote:
Jose,
It might help to have a look at the debian SOURCE package for Asterisk.
Here is the Debian DIFF File
One must keep in mind that the config files specify how hardware is to be handled.
If config files are present, the defaults in them are adequate to keep really bad
things from happening. If not . . . . . .
By the nature of this beast, it can easily seg fault if hardware drivers don't have
proper
Hi Rollin,
I am using SuSE's SLE 9.0, which is built for Itanium. The compiler
works for other 32 and 64 bits applications. There could still be a
problem with my environment though. I have not excluded that.
I can make it compile if I exclude the GSM codec. Now, how will that
affect the
Hi Jonas,
You may know this already, a codec is an algorithm for compressing and
uncompressing some signal. Often the signal was originally analog, but has
been digitized to reduce size/bandwidth and to store it in files. The GSM
codec is important in asterisk, because most or all music playback
Jonas Arndt wrote:
Dave,
A segmentation fault is usually caused by the program writing in a
memory area that is not allocated (it could be a result of the
optimizer sometime as well). That means that it can potentially
overwrite code that are executing there. In worst case scenario you
Steve,
Indeed a kernel oops can happen. I am not going to in detail explain,
but I can tell you that I have seen it happen with dar (Linux backup
software) using zlib. This has been confirmed by the dar community.
Regarding a sheltered life, no I have not such a life. I work with
software
19 matches
Mail list logo