While building the code i got some problems i got the code from
http://code.nsnam.org/iamine/ns-3-wimax/ ,and the errors are
[399/621] cxx: src/applications/MyUdpClientServer/udpServer.cc ->
build/debug/src/applications/MyUdpClientServer/udpServer_1.o
cc1plus: warnings being treated as errors
../src/applications/MyUdpClientServer/udpServer.cc: In member function
âvoid ns3::UdpServer::HandleRead(ns3::Ptr<ns3::Socket>)â:
../src/applications/MyUdpClientServer/udpServer.cc:107: warning:
unused variable ârawBufferâ
Build failed
task failed (err #129): [bld:///root/narendra/newcode/src/
applications/MyUdpClientServer/udpServer_1.o]
On Jan 6, 2:10 pm, narendra <narendrathe...@gmail.com> wrote:
> please give me some suggestions regarding this
Hello Narendra, as your compiler suggests: rawBuffer is unused and
must be removed to compile properly. Anyway, I also tried to compile
the code and realized that successive errors will arise! There are
several of them and I am not sure about the development status of the
WiMAX module. I suggest to use ns-2 at this time.
On Tue, 2009-01-06 at 10:53 -0800, hgn.rocket.scie...@googlemail.com wrote:
> On Jan 6, 2:10 pm, narendra <narendrathe...@gmail.com> wrote:
> > please give me some suggestions regarding this
> Hello Narendra, as your compiler suggests: rawBuffer is unused and > must be removed to compile properly. Anyway, I also tried to compile > the code and realized that successive errors will arise! There are
The code is merely built by its developer with a different compiler. Which compiler are you using ?
> Hi,
> The compiler i am using is
> gcc (GCC) 4.1.2 20070925 (Red Hat 4.1.2-33)
> Copyright (C) 2006 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There
> is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> PURPOSE.
> On Jan 7, 12:07 am, Mathieu Lacage <mathieu.lac...@sophia.inria.fr>
> wrote:
> > On Tue, 2009-01-06 at 10:53 -0800, hgn.rocket.scie...@googlemail.com
> > wrote:
> > > On Jan 6, 2:10 pm, narendra <narendrathe...@gmail.com> wrote:
> > > > please give me some suggestions regarding this
> > > Hello Narendra, as your compiler suggests: rawBuffer is unused and
> > > must be removed to compile properly. Anyway, I also tried to compile
> > > the code and realized that successive errors will arise! There are
> > The code is merely built by its developer with a different compiler.
> > Which compiler are you using ?
> May i know which compiler was used to build the code by the author.
> Regards,
> Narendra
> On Jan 7, 9:46 am, narendra <narendrathe...@gmail.com> wrote:
> > Hi,
> > The compiler i am using is
> > gcc (GCC) 4.1.2 20070925 (Red Hat 4.1.2-33)
> > Copyright (C) 2006 Free Software Foundation, Inc.
> > This is free software; see the source for copying conditions. There
> > is NO
> > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> > PURPOSE.
> > On Jan 7, 12:07 am, Mathieu Lacage <mathieu.lac...@sophia.inria.fr>
> > wrote:
> > > On Tue, 2009-01-06 at 10:53 -0800, hgn.rocket.scie...@googlemail.com
> > > wrote:
> > > > On Jan 6, 2:10 pm, narendra <narendrathe...@gmail.com> wrote:
> > > > > please give me some suggestions regarding this
> > > > Hello Narendra, as your compiler suggests: rawBuffer is unused and
> > > > must be removed to compile properly. Anyway, I also tried to compile
> > > > the code and realized that successive errors will arise! There are
> > > The code is merely built by its developer with a different compiler.
> > > Which compiler are you using ?
On Jan 6, 8:07 pm, Mathieu Lacage <mathieu.lac...@sophia.inria.fr>
wrote:
> The code is merely built by its developer with a different compiler.
> Which compiler are you using ?
gcc (Debian 4.3.2-1) 4.3.2
I run in _really_ fundamental errors as I build the branch, every time
I fixed one problem the next poped up. The original and all subsequent
errors are an indication for me that the branch is not in a usable
stage. At least for a user.
<hgn.rocket.scie...@googlemail.com> wrote:
> On Jan 6, 8:07 pm, Mathieu Lacage <mathieu.lac...@sophia.inria.fr>
> wrote:
> > The code is merely built by its developer with a different compiler.
> > Which compiler are you using ?
> gcc (Debian 4.3.2-1) 4.3.2
> I run in _really_ fundamental errors as I build the branch, every time
> I fixed one problem the next poped up. The original and all subsequent
> errors are an indication for me that the branch is not in a usable
> stage. At least for a user.
Le Thu, 8 Jan 2009 13:15:05 +0100, Providence SALUMU MUNGA <psal...@gmail.com> a écrit :
> After applying it, you will probably need to properly install libblas > and libatlas (apt-get install on debian-like distros) in your system.
To properly link with wimax examples in Ubuntu Jaunty Development branch : 1°) sudo aptitude purge libatlas3gf-base 2°) sudo aptitude install libblas-dev liblapack-dev liblapack-pic liblapack3gf
Regards,
-- Providence SALUMU M.
Doctorant, Département Logiciels-Réseaux TELECOM SudParis
"If you can't be strong, be clever, and make peace with someone who is strong. But it's always better to be strong yourself! Always!" -- B.O. LowLow.
>To properly link with wimax examples in Ubuntu Jaunty Development
>branch :
>1°) sudo aptitude purge libatlas3gf-base
>2°) sudo aptitude install libblas-dev liblapack-dev
>liblapack-pic liblapack3gf
Hi salumu i am very happy to say that the code was build with out any
error after applying ur patch.
The libraries mentioned in the above are not present in fedora. I am
using fedora 8 . so,please give me the details regarding FEDORA and
let me know whether this setup works with FEDORA . I downloaded ur
code from the link u have given .It was build properly and the same
problem occured when i was trying to run the simple-wimax.cc
example.I have installed libblass and libatlas .please go through the
problem.I have attached the probllem .plz go through it
[root@sandbox naren]# ./waf --run scratch/simple-wimax
Entering directory `/root/narendra/naren/build'
Compilation finished successfully
Simple WiMAX Simulation
Starting simulation.....
----------------------frame 1----------------------
DL frame started : 0.00000000000000000000
BS scheduler, burst size: 167 bytes, pkts: 4, connection: Broadcast,
CID: 65535, modulation: 0, DIUC: 1
BS scheduler, number of bursts: 1, symbols left: 306
BS scheduler, queues: IR 0 broadcast 0 basic 0 primary 0 transport 0
SS (00:00:00:00:00:02) starting scanning
SS (00:00:00:00:00:03) starting scanning
SS (00:00:00:00:00:04) starting scanning
SS (00:00:00:00:00:05) starting scanning
UL frame started : 0.00502777777777699969
----------------------frame 2----------------------
DL frame started : 0.01005555555555399938
BS scheduler, burst size: 104 bytes, pkts: 3, connection: Broadcast,
CID: 65535, modulation: 0, DIUC: 1
BS scheduler, number of bursts: 1, symbols left: 326
BS scheduler, queues: IR 0 broadcast 0 basic 0 primary 0 transport 0
UL frame started : 0.01508333333333100081
----------------------frame 3----------------------
DL frame started : 0.02011111111110799876
BS scheduler, burst size: 50 bytes, pkts: 2, connection: Broadcast,
CID: 65535, modulation: 0, DIUC: 1
BS scheduler, number of bursts: 1, symbols left: 343
BS scheduler, queues: IR 0 broadcast 0 basic 0 primary 0 transport 0
UL frame started : 0.02513888888888499845
----------------------frame 4----------------------
DL frame started : 0.03016666666666200161
BS scheduler, burst size: 104 bytes, pkts: 3, connection: Broadcast,
CID: 65535, modulation: 0, DIUC: 1
BS scheduler, number of bursts: 1, symbols left: 326
BS scheduler, queues: IR 0 broadcast 0 basic 0 primary 0 transport 0
UL frame started : 0.03519444444443899783
SS (00:00:00:00:00:02) starting scanning
SS (00:00:00:00:00:03) starting scanning
SS (00:00:00:00:00:04) starting scanning
SS (00:00:00:00:00:05) starting scanning
----------------------frame 5----------------------
DL frame started : 0.04022222222221599752
BS uplink scheduler, initial ranging allocation, size: 32 symbols,
modulation: BPSK 1/2
BS uplink scheduler, total allocations: 1, symbols left: 328
BS scheduler, burst size: 113 bytes, pkts: 3, connection: Broadcast,
CID: 65535, modulation: 0, DIUC: 1
BS scheduler, number of bursts: 1, symbols left: 326
BS scheduler, queues: IR 0 broadcast 0 basic 0 primary 0 transport 0
*** Assertion failed in ../../itpp/base/vec.h on line 1324:
Vec<>::split(): Index out of range (in_range(pos))
Command ['/root/narendra/naren/build/debug/scratch/simple-wimax']
exited with code -6
On Jan 8, 6:00 pm, Providence SALUMU MUNGA <psal...@gmail.com> wrote:
> Le Thu, 8 Jan 2009 13:15:05 +0100,
> Providence SALUMU MUNGA <psal...@gmail.com> a écrit :
> > After applying it, you will probably need to properly install libblas
> > and libatlas (apt-get install on debian-like distros) in your system.
> To properly link with wimax examples in Ubuntu Jaunty Development
> branch :
> 1°) sudo aptitude purge libatlas3gf-base
> 2°) sudo aptitude install libblas-dev liblapack-dev
> liblapack-pic liblapack3gf
> Regards,
> --
> Providence SALUMU M.
> Doctorant, Département Logiciels-Réseaux
> TELECOM SudParis
> "If you can't be strong, be clever, and make peace with someone who is
> strong. But it's always better to be strong yourself! Always!" -- B.O.
> LowLow.
Le Fri, 9 Jan 2009 01:28:39 -0800 (PST), narendra <narendrathe...@gmail.com> a écrit :
> Hi salumu i am very happy to say that the code was build with out any > error after applying ur patch. > The libraries mentioned in the above are not present in fedora. I am > using fedora 8 . so,please give me the details regarding FEDORA and > let me know whether this setup works with FEDORA . I downloaded ur
Since the code compiled well on your fc8, it implies that you don't need to update your libraries. So please, forget all about "sudo aptitude install ..." You're fine!
> code from the link u have given .It was build properly and the same > problem occured when i was trying to run the simple-wimax.cc > example.I have installed libblass and libatlas .please go through the > problem.I have attached the probllem .plz go through it
[...]
> *** Assertion failed in ../../itpp/base/vec.h on line 1324: > Vec<>::split(): Index out of range (in_range(pos)) > Command ['/root/narendra/naren/build/debug/scratch/simple-wimax'] > exited with code -6
I can't reproduce the problem on Ubuntu here, the simple-wimax.cc works fine to me. However, I would suggest that you run simple-wimax.cc under gdb to see what is really going on behind the curtains :-).
Regards,
-- Providence SALUMU M.
Doctorant, Département Logiciels-Réseaux TELECOM SudParis
"If you can't be strong, be clever, and make peace with someone who is strong. But it's always better to be strong yourself! Always!" -- B.O. LowLow.
> Le Fri, 9 Jan 2009 01:28:39 -0800 (PST),
> narendra <narendrathe...@gmail.com> a écrit :
> > Hi salumu i am very happy to say that the code was build with out any
> > error after applying ur patch.
> > The libraries mentioned in the above are not present in fedora. I am
> > using fedora 8 . so,please give me the details regarding FEDORA and
> > let me know whether this setup works with FEDORA . I downloaded ur
> Since the code compiled well on your fc8, it implies that you don't
> need to update your libraries. So please, forget all about "sudo
> aptitude install ..." You're fine!
> > code from the link u have given .It was build properly and the same
> > problem occured when i was trying to run the simple-wimax.cc
> > example.I have installed libblass and libatlas .please go through the
> > problem.I have attached the probllem .plz go through it
> [...]
> > *** Assertion failed in ../../itpp/base/vec.h on line 1324:
> > Vec<>::split(): Index out of range (in_range(pos))
> > Command ['/root/narendra/naren/build/debug/scratch/simple-wimax']
> > exited with code -6
> I can't reproduce the problem on Ubuntu here, the simple-wimax.cc works
> fine to me. However, I would suggest that you run simple-wimax.cc under
> gdb to see what is really going on behind the curtains :-).
> Regards,
> --
> Providence SALUMU M.
> Doctorant, Département Logiciels-Réseaux
> TELECOM SudParis
> "If you can't be strong, be clever, and make peace with someone who is
> strong. But it's always better to be strong yourself! Always!" -- B.O.
> LowLow.
> Doctorant, Département Logiciels-Réseaux
> TELECOM SudParis
> "If you can't be strong, be clever, and make peace with someone who is
> strong. But it's always better to be strong yourself! Always!" -- B.O.
> LowLow.
|
