Cannot run any INETMANET examples after new install
Andrew Hardy
When ever I launch an example by opening the example's directory in the
Project Explorer view and finding the corresponding omnetpp.ini file,
right clicking it and selecting Run As / Simulation, I get the following
error message:
Error in module during network setup: Class "ChannelControl" not found
-- perhaps its code was not linked in, or the class wasn't registered
with...
Or something similar.
After this I have tried Debug As / Simulation but get the same error.
I have also tried from mingwenv cd examples/ and "./rundemo", but same
error message
I have had this problem for a while. One of the posts said the person
solved it by installing 4.2.1 and rebuilding everything.
I have Win7 x64 and I did the following
I started my build again from scratch:
Downloaded omnetpp-4.2.1 zip file and unzipped
launched mingwenv
ran ./configure , make makefiles, then make.
Downloaded aarizaq-inetmanet-2.0-f7a4a48 zip file and unzipped
created ws folder under omnetpp-4.2.1
put the aarizaq-inetmanet-2.0-f7a4a48 in workspace
opened IDE using this workspace
Import the project according to install instructions
wait until the indexer finishes
select Project | Build all
The build stopped once with the common mingwenv problem
restarted build, build finihsed
Again I tried to run the examples but I get the same failure.
Am I missing something here?
Am I supposed to implement something else before I run these example?
Am I following the installation instructions wrongly?
Is there any other information about my environment or my installation
actions that I could provide which might help highlight where I am going
wrong?
Any help or advice would be greatly appreciated.
________________________________
Important Notice: the information in this email and any attachments is for the sole use of the intended recipient(s). If you are not an intended recipient, or a person responsible for delivering it to an intended recipient, you should delete it from your system immediately without disclosing its contents elsewhere and advise the sender by returning the email or by telephoning a number contained in the body of the email. No responsibility is accepted for loss or damage arising from viruses or changes made to this message after it was sent. The views contained in this email are those of the author and not necessarily those of Liverpool John Moores University.
Rudolf Hornig
--
Sent from the OMNeT++ mailing list. To configure your membership, visit http://groups.google.com/group/omnetpp
Alfonso Ariza Quintana
in inetmanet-2.0 the correct name is channelControl not ChannelControl, it's
necessary to fix the error
-----Mensaje original-----
From: Andrew Hardy
Sent: Tuesday, February 21, 2012 3:04 PM
To: omn...@googlegroups.com
Subject: [Omnetpp-l] Cannot run any INETMANET examples after new install
Or something similar.
--
Andrew Hardy
Successfully built?:
Dll file is:
Size: 41.7 KB (42,731 bytes)
Size on Disk: 44.0 KB (45,056 bytes)
The build all from the IDE: Console indicated successful build
Present?:
Yes it is present in
C:\omnetpp-4.2.1\my_workspace\aarizaq-inetmanet-2.0-f7a4a48\src
omnet's examples work?:
I am not sure if I am making this check you suggest correctly but...
open mingwenv
run /c/omnetpp-4.2.1/samples/tictoc/tictoc.exe
start simulation - success
run /c/omnetpp-4.2.1/samples/neddemo/neddemo.exe
start simulation - success, but 'no more events' immediately
run /c/omnetpp-4.2.1/samples/fifo/fifo.exe
tried all configurations
start simulation - success for all 3
On 21/02/2012 14:20, Rudolf Hornig wrote:
> Are you sure the file libinet.dll is successfully built and is present in the projectroot/src folder?
>
> Do omnet's examples work correctly?
>
> Rudolf
>
Rudolf Hornig
Thank you so much for taking a look at this.
Successfully built?:
Dll file is:
Size: 41.7 KB (42,731 bytes)
Size on Disk: 44.0 KB (45,056 bytes)
The build all from the IDE: Console indicated successful build
Andrew Hardy
In project explorer at examples\wpan\csma802154\omnetpp.ini
right click - select Run As\1 OMNeT++ Simulation
The text in the resultant error message box is not easily copyable, so I may have miss typed when copying it. Therefore I shall try to attach a screen shot of the actual error message box for clarity.
I have only downloaded omnet++ 4.2.1 and aarizaq-inetmanet-2.0-f7a4a48 and run the installations. I have not introduced any other code (apart from the 1 line fix in OverlayKeyNoGmp.cc).
Further to your comment regarding the erroneous class name, it appears that I did not mistype this name and therefore, as you say, there may be an error to fix.
I am proficient in C++ but not sufficiently in omnet api, could you possibly give me a starting point for this fix?
Many thanks again.
Andrew
On 21/02/2012 14:32, Alfonso Ariza Quintana wrote:
what example? in inetmanet-2.0 the correct name is channelControl not ChannelControl, it's necessary to fix the error -----Mensaje original----- From: Andrew Hardy Sent: Tuesday, February 21, 2012 3:04 PM To: omn...@googlegroups.com
Subject: [Omnetpp-l] Cannot run any INETMANET examples after new install I cannot seem to find any other posts which help me with this problem When ever I launch an example by opening the example's directory in the Project Explorer view and finding the corresponding omnetpp.ini file, right clicking it and selecting Run As / Simulation, I get the following error message: Error in module during network setup: Class "ChannelControl" not found -- perhaps its code was not linked in, or the class wasn't registered with... Or something similar. After this I have tried Debug As / Simulation but get the same error. I have also tried from mingwenv cd examples/ and "./rundemo", but same error message I have had this problem for a while. One of the posts said the person solved it by installing 4.2.1 and rebuilding everything. I have Win7 x64 and I did the following I started my build again from scratch: Downloaded omnetpp-4.2.1 zip file and unzipped launched mingwenv ran ./configure , make makefiles, then make. Downloaded aarizaq-inetmanet-2.0-f7a4a48 zip file and unzipped created ws folder under omnetpp-4.2.1 put the aarizaq-inetmanet-2.0-f7a4a48 in workspace opened IDE using this workspace Import the project according to install instructions wait until the indexer finishes select Project | Build all The build stopped once with the common mingwenv problem restarted build, build finihsed Again I tried to run the examples but I get the same failure. Am I missing something here? Am I supposed to implement something else before I run these example? Am I following the installation instructions wrongly? Is there any other information about my environment or my installation actions that I could provide which might help highlight where I am going wrong? Any help or advice would be greatly appreciated. ________________________________ Important Notice: the information in this email and any attachments is for the sole use of the intended recipient(s). If you are not an intended recipient, or a person responsible for delivering it to an intended recipient, you should delete it from your system immediately without disclosing its contents elsewhere and advise the sender by returning the email or by telephoning a number contained in the body of the email. No responsibility is accepted for loss or damage arising from viruses or changes made to this message after it was sent. The views contained in this email are those of the author and not necessarily those of Liverpool John Moores University.
Andrew Hardy
Since I have the INETMANET project open in the ws already is the
following from the IDE sufficient to rebuild?
select Project | Clean
select Project | Build all
On 21/02/2012 15:15, Rudolf Hornig wrote:
>
> On Tue, Feb 21, 2012 at 4:02 PM, Andrew Hardy<a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk>> wrote:
> Thank you so much for taking a look at this.
>
> Successfully built?:
>
> Dll file is:
> Size: 41.7 KB (42,731 bytes)
> Size on Disk: 44.0 KB (45,056 bytes)
> The build all from the IDE: Console indicated successful build
>
> This is definitely wrong. I'm sure the whole INETMANET codebase cannot fir into 42KB.
>
> Clean the INETMANET project, the rebuild. It should take quite a time. Check the output of the link step (should be somewhere at the end of the log). It must include all object files from INETMANET. There is something definitely wrong with your build configuration...
> Rudolf
>
>
>
> Present?:
> Yes it is present in C:\omnetpp-4.2.1\my_workspace\aarizaq-inetmanet-2.0-f7a4a48\src
>
> omnet's examples work?:
>
> I am not sure if I am making this check you suggest correctly but...
>
> open mingwenv
>
> run /c/omnetpp-4.2.1/samples/tictoc/tictoc.exe
> start simulation - success
>
> run /c/omnetpp-4.2.1/samples/neddemo/neddemo.exe
> start simulation - success, but 'no more events' immediately
>
> run /c/omnetpp-4.2.1/samples/fifo/fifo.exe
> tried all configurations
> start simulation - success for all 3
>
>
>
>
> On 21/02/2012 14:20, Rudolf Hornig wrote:
> Are you sure the file libinet.dll is successfully built and is present in the projectroot/src folder?
>
> Do omnet's examples work correctly?
>
> Rudolf
>
Andrew Hardy
During the build I got one mingwenv failure. I selected Project | Build
All again to continue assuming it would see the objects that were
already made and continue from where it left off.
The dll is exactly the same as before. The last bit of the console
output which I presume includes the linking is as follows:
...
...
...
debug/src/transport/rtp/profiles/avprofile/RTPMpegPacket_m.o
../out/gcc-debug/src/transport/sctp/SCTPMessage_m.o
../out/gcc-debug/src/transport/tcp_common/TCPSegment_m.o
../out/gcc-debug/src/transport/udp/UDPPacket_m.o
../out/gcc-debug/src/underTest/linklayer/Ieee80216/ControlPlane/Ieee80216ManagementMessages_m.o
../out/gcc-debug/src/underTest/linklayer/Ieee80216/ControlPlane/Ieee80216Primitives_m.o
../out/gcc-debug/src/underTest/linklayer/Ieee80216/Mac/Ieee80216MacHeader_m.o
../out/gcc-debug/src/underTest/linklayer/Ieee80216/Mac/WiMAXRadioControl_m.o
../out/gcc-debug/src/world/powercontrol/PowerControlMessages_m.o
../out/gcc-debug/src/wpan/applications/Ieee802154TestApp/Ieee802154AppPkt_m.o
../out/gcc-debug/src/wpan/linklayer/bmac/bmacpkt_m.o
../out/gcc-debug/src/wpan/linklayer/ieee802154/contract/Ieee802154MacPhyPrimitives_m.o
../out/gcc-debug/src/wpan/linklayer/ieee802154/mac/Ieee802154Frame_m.o
../out/gcc-debug/src/wpan/networklayer/contract/Ieee802154NetworkCtrlInfo_m.o
&& ar cr .tmplib$$ @.tmp$$ && g++ -shared -o
../out/gcc-debug/src/libinet.dll -Wl,--no-as-needed .tmplib$$
-L"c:/omnetpp-4.2.1/lib/gcc" -L"c:/omnetpp-4.2.1/lib" -loppenvird
-loppsimd -lwsock32 -lstdc++ -Wl,--enable-auto-import -shared-libgcc
-L/usr/bin -L/usr/lib -Wl,-rpath,c:/omnetpp-4.2.1/lib -Wl,-rpath,. && rm
.tmp$$ && rm .tmplib$$
opp_shlib_postprocess ../out/gcc-debug/src/libinet.dll
ln -sf ../out/gcc-debug/src/libinet.dll .
make[1]: Leaving directory
`/c/omnetpp-4.2.1/my_workspace/aarizaq-inetmanet-2.0-f7a4a48/src'
**** Build Finished ****
On 21/02/2012 15:21, Hardy, Andrew wrote:
> Thank you I shall rebuild.
>
> Since I have the INETMANET project open in the ws already is the
> following from the IDE sufficient to rebuild?
>
> select Project | Clean
> select Project | Build all
>
>
>
>
> On 21/02/2012 15:15, Rudolf Hornig wrote:
>> On Tue, Feb 21, 2012 at 4:02 PM, Andrew Hardy<a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk>> wrote:
>> Thank you so much for taking a look at this.
>>
>> Successfully built?:
>>
>> Dll file is:
>> Size: 41.7 KB (42,731 bytes)
>> Size on Disk: 44.0 KB (45,056 bytes)
>> The build all from the IDE: Console indicated successful build
>>
>> This is definitely wrong. I'm sure the whole INETMANET codebase cannot fir into 42KB.
>>
>> Clean the INETMANET project, the rebuild. It should take quite a time. Check the output of the link step (should be somewhere at the end of the log). It must include all object files from INETMANET. There is something definitely wrong with your build configuration...
>> Rudolf
>>
>>
>>
>> Present?:
>> Yes it is present in C:\omnetpp-4.2.1\my_workspace\aarizaq-inetmanet-2.0-f7a4a48\src
>>
>> omnet's examples work?:
>>
>> I am not sure if I am making this check you suggest correctly but...
>>
>> open mingwenv
>>
>> run /c/omnetpp-4.2.1/samples/tictoc/tictoc.exe
>> start simulation - success
>>
>> run /c/omnetpp-4.2.1/samples/neddemo/neddemo.exe
>> start simulation - success, but 'no more events' immediately
>>
>> run /c/omnetpp-4.2.1/samples/fifo/fifo.exe
>> tried all configurations
>> start simulation - success for all 3
>>
>>
>>
>>
>> On 21/02/2012 14:20, Rudolf Hornig wrote:
>> Are you sure the file libinet.dll is successfully built and is present in the projectroot/src folder?
>>
>> Do omnet's examples work correctly?
>>
>> Rudolf
>>
Andrew Hardy
size. A size that it is being suggested indicates it is deficient in
some way
Any help or advice greatly appreciated.
If I think maybe something is still missing at the end and it hasn't
really finished I hit Project | Build Project and I straight away get:
**** Build of configuration gcc-debug for project
aarizaq-inetmanet-2.0-f7a4a48 ****
make MODE=debug CONFIGNAME=gcc-debug all
cd src && make
make[1]: Entering directory
`/c/omnetpp-4.2.1/my_workspace/aarizaq-inetmanet-2.0-f7a4a48/src'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory
`/c/omnetpp-4.2.1/my_workspace/aarizaq-inetmanet-2.0-f7a4a48/src'
**** Build Finished ****
On 21/02/2012 16:50, Hardy, Andrew wrote:
> I rebuilt.
>
> During the build I got one mingwenv failure. I selected Project | Build
> All again to continue assuming it would see the objects that were
> already made and continue from where it left off.
>
> The dll is exactly the same as before. The last bit of the console
> output which I presume includes the linking is as follows:
>
> ...
> ...
> ...
> debug/src/transport/rtp/profiles/avprofile/RTPMpegPacket_m.o
> ../out/gcc-debug/src/transport/sctp/SCTPMessage_m.o
> ../out/gcc-debug/src/transport/tcp_common/TCPSegment_m.o
> ../out/gcc-debug/src/transport/udp/UDPPacket_m.o
> ../out/gcc-debug/src/underTest/linklayer/Ieee80216/ControlPlane/Ieee80216ManagementMessages_m.o
> ../out/gcc-debug/src/underTest/linklayer/Ieee80216/ControlPlane/Ieee80216Primitives_m.o
> ../out/gcc-debug/src/underTest/linklayer/Ieee80216/Mac/Ieee80216MacHeader_m.o
> ../out/gcc-debug/src/underTest/linklayer/Ieee80216/Mac/WiMAXRadioControl_m.o
> ../out/gcc-debug/src/world/powercontrol/PowerControlMessages_m.o
> ../out/gcc-debug/src/wpan/applications/Ieee802154TestApp/Ieee802154AppPkt_m.o
> ../out/gcc-debug/src/wpan/linklayer/bmac/bmacpkt_m.o
> ../out/gcc-debug/src/wpan/linklayer/ieee802154/contract/Ieee802154MacPhyPrimitives_m.o
> ../out/gcc-debug/src/wpan/linklayer/ieee802154/mac/Ieee802154Frame_m.o
> ../out/gcc-debug/src/wpan/networklayer/contract/Ieee802154NetworkCtrlInfo_m.o
> && ar cr .tmplib$$ @.tmp$$&& g++ -shared -o
> ../out/gcc-debug/src/libinet.dll -Wl,--no-as-needed .tmplib$$
> -L"c:/omnetpp-4.2.1/lib/gcc" -L"c:/omnetpp-4.2.1/lib" -loppenvird
> -loppsimd -lwsock32 -lstdc++ -Wl,--enable-auto-import -shared-libgcc
> -L/usr/bin -L/usr/lib -Wl,-rpath,c:/omnetpp-4.2.1/lib -Wl,-rpath,.&& rm
> .tmp$$&& rm .tmplib$$
> opp_shlib_postprocess ../out/gcc-debug/src/libinet.dll
> ln -sf ../out/gcc-debug/src/libinet.dll .
> make[1]: Leaving directory
> `/c/omnetpp-4.2.1/my_workspace/aarizaq-inetmanet-2.0-f7a4a48/src'
>
> **** Build Finished ****
>
>
> On 21/02/2012 15:21, Hardy, Andrew wrote:
>> Thank you I shall rebuild.
>>
>> Since I have the INETMANET project open in the ws already is the
>> following from the IDE sufficient to rebuild?
>>
>> select Project | Clean
>> select Project | Build all
>>
>>
>>
>>
>> On 21/02/2012 15:15, Rudolf Hornig wrote:
>>> On Tue, Feb 21, 2012 at 4:02 PM, Andrew Hardy<a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk>> wrote:
>>> Thank you so much for taking a look at this.
>>>
>>> Successfully built?:
>>>
>>> Dll file is:
>>> Size: 41.7 KB (42,731 bytes)
>>> Size on Disk: 44.0 KB (45,056 bytes)
>>> The build all from the IDE: Console indicated successful build
>>>
>>> This is definitely wrong. I'm sure the whole INETMANET codebase cannot fir into 42KB.
>>>
>>> Clean the INETMANET project, the rebuild. It should take quite a time. Check the output of the link step (should be somewhere at the end of the log). It must include all object files from INETMANET. There is something definitely wrong with your build configuration...
>>> Rudolf
>>>
>>>
>>>
>>> Present?:
>>> Yes it is present in C:\omnetpp-4.2.1\my_workspace\aarizaq-inetmanet-2.0-f7a4a48\src
>>>
>>> omnet's examples work?:
>>>
>>> I am not sure if I am making this check you suggest correctly but...
>>>
>>> open mingwenv
>>>
>>> run /c/omnetpp-4.2.1/samples/tictoc/tictoc.exe
>>> start simulation - success
>>>
>>> run /c/omnetpp-4.2.1/samples/neddemo/neddemo.exe
>>> start simulation - success, but 'no more events' immediately
>>>
>>> run /c/omnetpp-4.2.1/samples/fifo/fifo.exe
>>> tried all configurations
>>> start simulation - success for all 3
>>>
>>>
>>>
>>>
>>> On 21/02/2012 14:20, Rudolf Hornig wrote:
>>> Are you sure the file libinet.dll is successfully built and is present in the projectroot/src folder?
>>>
>>> Do omnet's examples work correctly?
>>>
>>> Rudolf
>>>
Alfonso Ariza Quintana
without the appropriate patch,
This is the reason because I recommend to use the git protocol, with the
objective of simplify the synchronization between the repository and your
local computer
-----Mensaje original-----
From: Andrew Hardy
Sent: Tuesday, February 21, 2012 7:06 PM
To: omn...@googlegroups.com
Subject: Re: [Omnetpp-l] Cannot run any INETMANET examples after new install
Andrew Hardy
If I go here
https://github.com/aarizaq/inetmanet-2.0
and click on zip I get the very latest version right?
I have just tried aarizaq-inetmanet-2.0-f84480d which looks like it was
made 20/2/12 16:01 and I still get the problem.
Is there a way to get the very latest zip with all the latest fixes in?
If not then where do I go to pick up the latest patches?
Also I shall take a look at the git protocol. I am on Win7 using IDE
and mingwenv for command line. Can I setup git protocol from within
mingwenv? Is there a tutorial any where?
On 21/02/2012 18:41, Alfonso Ariza Quintana wrote:
> The ChannelControl problem was fixed, i suspect that you are using a version
> without the appropriate patch,
> This is the reason because I recommend to use the git protocol, with the
> objective of simplify the synchronization between the repository and your
> local computer
>
>
> -----Mensaje original-----
> From: Andrew Hardy
> Sent: Tuesday, February 21, 2012 7:06 PM
> To: omn...@googlegroups.com
> Subject: Re: [Omnetpp-l] Cannot run any INETMANET examples after new install
>
> I have built this several times and the dll is always exactly the same
> size. A size that it is being suggested indicates it is deficient in
> some way
>
> Any help or advice greatly appreciated.
>
> If I think maybe something is still missing at the end and it hasn't
> really finished I hit Project | Build Project and I straight away get:
>
> **** Build of configuration gcc-debug for project
> aarizaq-inetmanet-2.0-f7a4a48 ****
>
> make MODE=debug CONFIGNAME=gcc-debug all
> cd src&& make
Alfonso Ariza Quintana
wait that the name would be channelControl
how you can see in the file the name must be channelControl
https://github.com/aarizaq/inetmanet-2.0/blob/integration/examples/wpan/csma802154/csma802154net.ned
-----Mensaje original-----
From: Andrew Hardy
Sent: Tuesday, February 21, 2012 8:29 PM
Rudolf Hornig
Andrew Hardy
are saying. I am really confused
The file you reference has...
import inet.world.radio.ChannelControl;
...
channelControl: ChannelControl {
The file I am using from aarizaq-inetmanet-2.0-f84480d has
import inet.world.radio.ChannelControl;
...
channelControl: ChannelControl {
They are the same.
What is the fix that I need that don't have and do you know where I can
get it from?
On 21/02/2012 19:48, Alfonso Ariza Quintana wrote:
> The error that your reported previously was the ChannelControl, the code
> wait that the name would be channelControl
> how you can see in the file the name must be channelControl
> https://github.com/aarizaq/inetmanet-2.0/blob/integration/examples/wpan/csma802154/csma802154net.ned
>
>
> -----Mensaje original-----
> From: Andrew Hardy
> Sent: Tuesday, February 21, 2012 8:29 PM
Andrew Hardy
what others seem to be calling a mingwenv failure, ie
C:\omnetpp-4.2\msys\bin\make.exe: *** couldn't commit memory for cygwin
heap, Win32 error 0
I am told this is the fault of mingwenv and is otherwise benign. I
understand one is just supposed to carry on with the build any way.
I shall try to get a zip of the build output.
It is also suggested that the underlying cause of the simualtion error
message box which is the main subject of this post is really to do with
the 'name'
ChannelControl
not being
channelControl
What you think? In my ned file the name is
channelControl
and the class is
ChannelControl
On 21/02/2012 20:03, Rudolf Hornig wrote:
> What kind of failure you got? In theory it should compile without any failure. It is also strange that resulting .dll file is so small, it should contain all the code on the linker command line.
>
> If you can capture the whole command output into a file, zip it and attach, I may take a look at the build process.
> Rudolf
>
> On Tue, Feb 21, 2012 at 5:50 PM, Andrew Hardy<a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk>> wrote:
> I rebuilt.
>
> During the build I got one mingwenv failure. I selected Project | Build All again to continue assuming it would see the objects that were already made and continue from where it left off.
>
> The dll is exactly the same as before. The last bit of the console output which I presume includes the linking is as follows:
>
> ...
> ...
> ...
> debug/src/transport/rtp/profiles/avprofile/RTPMpegPacket_m.o ../out/gcc-debug/src/transport/sctp/SCTPMessage_m.o ../out/gcc-debug/src/transport/tcp_common/TCPSegment_m.o ../out/gcc-debug/src/transport/udp/UDPPacket_m.o ../out/gcc-debug/src/underTest/linklayer/Ieee80216/ControlPlane/Ieee80216ManagementMessages_m.o ../out/gcc-debug/src/underTest/linklayer/Ieee80216/ControlPlane/Ieee80216Primitives_m.o ../out/gcc-debug/src/underTest/linklayer/Ieee80216/Mac/Ieee80216MacHeader_m.o ../out/gcc-debug/src/underTest/linklayer/Ieee80216/Mac/WiMAXRadioControl_m.o ../out/gcc-debug/src/world/powercontrol/PowerControlMessages_m.o ../out/gcc-debug/src/wpan/applications/Ieee802154TestApp/Ieee802154AppPkt_m.o ../out/gcc-debug/src/wpan/linklayer/bmac/bmacpkt_m.o ../out/gcc-debug/src/wpan/linklayer/ieee802154/contract/Ieee802154MacPhyPrimitives_m.o ../out/gcc-debug/src/wpan/linklayer/ieee802154/mac/Ieee802154Frame_m.o ../out/gcc-debug/src/wpan/networklayer/contract/Ieee802154NetworkCtrlInfo_m.o&& ar cr .tmplib$$ @.tmp$$&& g++ -shared -o ../out/gcc-debug/src/libinet.dll -Wl,--no-as-needed .tmplib$$ -L"c:/omnetpp-4.2.1/lib/gcc" -L"c:/omnetpp-4.2.1/lib" -loppenvird -loppsimd -lwsock32 -lstdc++ -Wl,--enable-auto-import -shared-libgcc -L/usr/bin -L/usr/lib -Wl,-rpath,c:/omnetpp-4.2.1/lib -Wl,-rpath,.&& rm .tmp$$&& rm .tmplib$$
> opp_shlib_postprocess ../out/gcc-debug/src/libinet.dll
> ln -sf ../out/gcc-debug/src/libinet.dll .
> make[1]: Leaving directory `/c/omnetpp-4.2.1/my_workspace/aarizaq-inetmanet-2.0-f7a4a48/src'
>
> **** Build Finished ****
>
>
>
> On 21/02/2012 15:21, Hardy, Andrew wrote:
> Thank you I shall rebuild.
>
> Since I have the INETMANET project open in the ws already is the
> following from the IDE sufficient to rebuild?
>
> select Project | Clean
> select Project | Build all
>
>
>
>
> On 21/02/2012 15:15, Rudolf Hornig wrote:
Rudolf Hornig
If by what kind of failure you mean failure during the build then it is what others seem to be calling a mingwenv failure, ie
C:\omnetpp-4.2\msys\bin\make.exe: *** couldn't commit memory for cygwin
heap, Win32 error 0
I am told this is the fault of mingwenv and is otherwise benign. I understand one is just supposed to carry on with the build any way.
I shall try to get a zip of the build output.
It is also suggested that the underlying cause of the simualtion error message box which is the main subject of this post is really to do with the 'name'
ChannelControl
not being
channelControl
What you think? In my ned file the name is
channelControl
Andrew Hardy
This makes a lot of sense. I shall concentrate on addressing the build
issue. Not sure how to solve the 'couldn't commit memory for cygwin'
problem though.
One question though.
I just want to check if my problem may be an embarrassingly simple one.
Should I be installing
omnet project
followed by inet project
followed by inetmanet project
??
This on the home page:
"INETMANET is based on INET Framework (http://inet.omnetpp.org/) and
continuosly developed. Generally it provides the same functionality as
the INET Framework, but contains additional protocols and components
that are especially useful while modeling wireless communication:"
Make me think the answer to this question is NO.
Neither the readme nor the install files in the root of the inetmanet
project mention the word inetmanet so for "inet" in these files I have
been reading "inetmanet" and so installing inetmanet on top of omnet++
only, not together with an inet project installation.
Is this right?
Many thanks,
Andrew
On 21/02/2012 21:20, Rudolf Hornig wrote:
>
> On Tue, Feb 21, 2012 at 9:37 PM, Andrew Hardy<a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk>> wrote:
> If by what kind of failure you mean failure during the build then it is what others seem to be calling a mingwenv failure, ie
>
> C:\omnetpp-4.2\msys\bin\make.exe: *** couldn't commit memory for cygwin
> heap, Win32 error 0
>
> Ok, I've never seen such an error on windows. It may be harmless, but OMNET was tested on Windows 7 and we have never seen similar errors.
>
>
> I am told this is the fault of mingwenv and is otherwise benign. I understand one is just supposed to carry on with the build any way.
>
> I shall try to get a zip of the build output.
>
> It is also suggested that the underlying cause of the simualtion error message box which is the main subject of this post is really to do with the 'name'
>
> ChannelControl
>
> not being
>
> channelControl
>
> What you think? In my ned file the name is
> channelControl
>
> No, the error you saw indicates that the code related the ChannelControl simple module is NOT available in the .DLL. The size of the .DLL supports this assumption too (it's just some 50KB, so it obviously cannot contain the inet code). The error occurred when OMNeT++ loaded the NED files and after that tried to instantiate the corresponding class.
>
> As long as your build result in a 50K .dll you always will receive the above error, so you must concentrate to fix the build process. Forget about the NED files, they are most likely fine.
>
>
> and the class is
> ChannelControl
>
>
>
>
> On 21/02/2012 20:03, Rudolf Hornig wrote:
> What kind of failure you got? In theory it should compile without any failure. It is also strange that resulting .dll file is so small, it should contain all the code on the linker command line.
>
> If you can capture the whole command output into a file, zip it and attach, I may take a look at the build process.
> Rudolf
>
> On Tue, Feb 21, 2012 at 5:50 PM, Andrew Hardy<a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk>>> wrote:
>
> I rebuilt.
>
> During the build I got one mingwenv failure. I selected Project | Build All again to continue assuming it would see the objects that were already made and continue from where it left off.
>
> The dll is exactly the same as before. The last bit of the console output which I presume includes the linking is as follows:
>
> ...
> ...
> ...
> debug/src/transport/rtp/profiles/avprofile/RTPMpegPacket_m.o ../out/gcc-debug/src/transport/sctp/SCTPMessage_m.o ../out/gcc-debug/src/transport/tcp_common/TCPSegment_m.o ../out/gcc-debug/src/transport/udp/UDPPacket_m.o ../out/gcc-debug/src/underTest/linklayer/Ieee80216/ControlPlane/Ieee80216ManagementMessages_m.o ../out/gcc-debug/src/underTest/linklayer/Ieee80216/ControlPlane/Ieee80216Primitives_m.o ../out/gcc-debug/src/underTest/linklayer/Ieee80216/Mac/Ieee80216MacHeader_m.o ../out/gcc-debug/src/underTest/linklayer/Ieee80216/Mac/WiMAXRadioControl_m.o ../out/gcc-debug/src/world/powercontrol/PowerControlMessages_m.o ../out/gcc-debug/src/wpan/applications/Ieee802154TestApp/Ieee802154AppPkt_m.o ../out/gcc-debug/src/wpan/linklayer/bmac/bmacpkt_m.o ../out/gcc-debug/src/wpan/linklayer/ieee802154/contract/Ieee802154MacPhyPrimitives_m.o ../out/gcc-debug/src/wpan/linklayer/ieee802154/mac/Ieee802154Frame_m.o ../out/gcc-debug/src/wpan/networklayer/contract/Ieee802154NetworkCtrlInfo_m.o&& ar cr .tmplib$$ @.tmp$$&& g++ -shared -o ../out/gcc-debug/src/libinet.dll -Wl,--no-as-needed .tmplib$$ -L"c:/omnetpp-4.2.1/lib/gcc" -L"c:/omnetpp-4.2.1/lib" -loppenvird -loppsimd -lwsock32 -lstdc++ -Wl,--enable-auto-import -shared-libgcc -L/usr/bin -L/usr/lib -Wl,-rpath,c:/omnetpp-4.2.1/lib -Wl,-rpath,.&& rm .tmp$$&& rm .tmplib$$
>
> opp_shlib_postprocess ../out/gcc-debug/src/libinet.dll
> ln -sf ../out/gcc-debug/src/libinet.dll .
> make[1]: Leaving directory `/c/omnetpp-4.2.1/my_workspace/aarizaq-inetmanet-2.0-f7a4a48/src'
>
> **** Build Finished ****
>
>
>
> On 21/02/2012 15:21, Hardy, Andrew wrote:
> Thank you I shall rebuild.
>
> Since I have the INETMANET project open in the ws already is the
> following from the IDE sufficient to rebuild?
>
> select Project | Clean
> select Project | Build all
>
>
>
>
> On 21/02/2012 15:15, Rudolf Hornig wrote:
Rudolf Hornig
Andrew Hardy
I shall try this and get back.
Kind Regards,
Andrew
On 22/02/2012 09:57, Rudolf Hornig wrote:
> INETMANET is a fork of INET meaninhg that you need only INETMANET (but not both). Inetmanet is more or less a superset of the INET framework.
>
> One possible test: just close INETMANET and try to build INET only and then check for libinet.dll there and see if the examples work. If the do, then the issue is INETMANET specific, if NO, then there may be an issue at operating system level (because OMNET's samples seem to work).
>
> Rudolf
>
> On Wed, Feb 22, 2012 at 10:43 AM, Andrew Hardy<a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk>> wrote:
> Thanks Rudolph,
>
> This makes a lot of sense. I shall concentrate on addressing the build issue. Not sure how to solve the 'couldn't commit memory for cygwin' problem though.
>
> One question though.
>
> I just want to check if my problem may be an embarrassingly simple one.
>
> Should I be installing
>
> omnet project
> followed by inet project
> followed by inetmanet project
>
> ??
>
> This on the home page:
>
> "INETMANET is based on INET Framework (http://inet.omnetpp.org/) and continuosly developed. Generally it provides the same functionality as the INET Framework, but contains additional protocols and components that are especially useful while modeling wireless communication:"
>
> Make me think the answer to this question is NO.
>
> Neither the readme nor the install files in the root of the inetmanet project mention the word inetmanet so for "inet" in these files I have been reading "inetmanet" and so installing inetmanet on top of omnet++ only, not together with an inet project installation.
>
> Is this right?
>
> Many thanks,
>
> Andrew
>
>
>
> On 21/02/2012 21:20, Rudolf Hornig wrote:
>
> On Tue, Feb 21, 2012 at 9:37 PM, Andrew Hardy<a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk>>> wrote:
>
> If by what kind of failure you mean failure during the build then it is what others seem to be calling a mingwenv failure, ie
>
> C:\omnetpp-4.2\msys\bin\make.exe: *** couldn't commit memory for cygwin
> heap, Win32 error 0
>
> Ok, I've never seen such an error on windows. It may be harmless, but OMNET was tested on Windows 7 and we have never seen similar errors.
>
>
> I am told this is the fault of mingwenv and is otherwise benign. I understand one is just supposed to carry on with the build any way.
>
> I shall try to get a zip of the build output.
>
> It is also suggested that the underlying cause of the simualtion error message box which is the main subject of this post is really to do with the 'name'
>
> ChannelControl
>
> not being
>
> channelControl
>
> What you think? In my ned file the name is
> channelControl
>
> No, the error you saw indicates that the code related the ChannelControl simple module is NOT available in the .DLL. The size of the .DLL supports this assumption too (it's just some 50KB, so it obviously cannot contain the inet code). The error occurred when OMNeT++ loaded the NED files and after that tried to instantiate the corresponding class.
>
> As long as your build result in a 50K .dll you always will receive the above error, so you must concentrate to fix the build process. Forget about the NED files, they are most likely fine.
>
>
> and the class is
> ChannelControl
>
>
>
>
> On 21/02/2012 20:03, Rudolf Hornig wrote:
> What kind of failure you got? In theory it should compile without any failure. It is also strange that resulting .dll file is so small, it should contain all the code on the linker command line.
>
> If you can capture the whole command output into a file, zip it and attach, I may take a look at the build process.
> Rudolf
>
> On Tue, Feb 21, 2012 at 5:50 PM, Andrew Hardy<a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk>><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk>>>> wrote:
>
> I rebuilt.
>
> During the build I got one mingwenv failure. I selected Project | Build All again to continue assuming it would see the objects that were already made and continue from where it left off.
>
> The dll is exactly the same as before. The last bit of the console output which I presume includes the linking is as follows:
>
> ...
> ...
> ...
> debug/src/transport/rtp/profiles/avprofile/RTPMpegPacket_m.o ../out/gcc-debug/src/transport/sctp/SCTPMessage_m.o ../out/gcc-debug/src/transport/tcp_common/TCPSegment_m.o ../out/gcc-debug/src/transport/udp/UDPPacket_m.o ../out/gcc-debug/src/underTest/linklayer/Ieee80216/ControlPlane/Ieee80216ManagementMessages_m.o ../out/gcc-debug/src/underTest/linklayer/Ieee80216/ControlPlane/Ieee80216Primitives_m.o ../out/gcc-debug/src/underTest/linklayer/Ieee80216/Mac/Ieee80216MacHeader_m.o ../out/gcc-debug/src/underTest/linklayer/Ieee80216/Mac/WiMAXRadioControl_m.o ../out/gcc-debug/src/world/powercontrol/PowerControlMessages_m.o ../out/gcc-debug/src/wpan/applications/Ieee802154TestApp/Ieee802154AppPkt_m.o ../out/gcc-debug/src/wpan/linklayer/bmac/bmacpkt_m.o ../out/gcc-debug/src/wpan/linklayer/ieee802154/contract/Ieee802154MacPhyPrimitives_m.o ../out/gcc-debug/src/wpan/linklayer/ieee802154/mac/Ieee802154Frame_m.o ../out/gcc-debug/src/wpan/networklayer/contract/Ieee802154NetworkCtrlInfo_m.o&& ar cr .tmplib$$ @.tmp$$&& g++ -shared -o ../out/gcc-debug/src/libinet.dll -Wl,--no-as-needed .tmplib$$ -L"c:/omnetpp-4.2.1/lib/gcc" -L"c:/omnetpp-4.2.1/lib" -loppenvird -loppsimd -lwsock32 -lstdc++ -Wl,--enable-auto-import -shared-libgcc -L/usr/bin -L/usr/lib -Wl,-rpath,c:/omnetpp-4.2.1/lib -Wl,-rpath,.&& rm .tmp$$&& rm .tmplib$$
>
> opp_shlib_postprocess ../out/gcc-debug/src/libinet.dll
> ln -sf ../out/gcc-debug/src/libinet.dll .
> make[1]: Leaving directory `/c/omnetpp-4.2.1/my_workspace/aarizaq-inetmanet-2.0-f7a4a48/src'
>
> **** Build Finished ****
>
>
>
> On 21/02/2012 15:21, Hardy, Andrew wrote:
> Thank you I shall rebuild.
>
> Since I have the INETMANET project open in the ws already is the
> following from the IDE sufficient to rebuild?
>
> select Project | Clean
> select Project | Build all
>
>
>
>
> On 21/02/2012 15:15, Rudolf Hornig wrote:
rim negra
Could not read 4 bytes from traCI server ?
Could any one show me where is the matter exactly ?
thanks
On Tue, Feb 21, 2012 at 5:50 PM, Andrew Hardy<a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk>><mailto:a.hardy@2009.ljmu.ac.uk<mailto:a.hardy@2009.ljmu.ac.uk><mailto:a.ha...@2009.ljmu.ac.uk<mailto:a.hardy@2009.ljmu.ac.uk>>>> wrote:
I rebuilt.
During the build I got one mingwenv failure. I selected Project | Build All again to continue assuming it would see the objects that were already made and continue from where it left off.
The dll is exactly the same as before. The last bit of the console output which I presume includes the linking is as follows:
...
...
...
debug/src/transport/rtp/profiles/avprofile/RTPMpegPacket_m.o ../out/gcc-debug/src/transport/sctp/SCTPMessage_m.o ../out/gcc-debug/src/transport/tcp_common/TCPSegment_m.o ../out/gcc-debug/src/transport/udp/UDPPacket_m.o ../out/gcc-debug/src/underTest/linklayer/Ieee80216/ControlPlane/Ieee80216ManagementMessages_m.o ../out/gcc-debug/src/underTest/linklayer/Ieee80216/ControlPlane/Ieee80216Primitives_m.o ../out/gcc-debug/src/underTest/linklayer/Ieee80216/Mac/Ieee80216MacHeader_m.o ../out/gcc-debug/src/underTest/linklayer/Ieee80216/Mac/WiMAXRadioControl_m.o ../out/gcc-debug/src/world/powercontrol/PowerControlMessages_m.o ../out/gcc-debug/src/wpan/applications/Ieee802154TestApp/Ieee802154AppPkt_m.o ../out/gcc-debug/src/wpan/linklayer/bmac/bmacpkt_m.o ../out/gcc-debug/src/wpan/linklayer/ieee802154/contract/Ieee802154MacPhyPrimitives_m.o ../out/gcc-debug/src/wpan/linklayer/ieee802154/mac/Ieee802154Frame_m.o ../out/gcc-debug/src/wpan/networklayer/contract/Ieee802154NetworkCtrlInfo_m.o&& ar cr .tmplib$$ @.tmp$$&& g++ -shared -o ../out/gcc-debug/src/libinet.dll -Wl,--no-as-needed .tmplib$$ -L"c:/omnetpp-4.2.1/lib/gcc" -L"c:/omnetpp-4.2.1/lib" -loppenvird -loppsimd -lwsock32 -lstdc++ -Wl,--enable-auto-import -shared-libgcc -L/usr/bin -L/usr/lib -Wl,-rpath,c:/omnetpp-4.2.1/lib -Wl,-rpath,.&& rm .tmp$$&& rm .tmplib$$
opp_shlib_postprocess ../out/gcc-debug/src/libinet.dll
ln -sf ../out/gcc-debug/src/libinet.dll .
make[1]: Leaving directory `/c/omnetpp-4.2.1/my_workspace/aarizaq-inetmanet-2.0-f7a4a48/src'
**** Build Finished ****
On 21/02/2012 15:21, Hardy, Andrew wrote:
Thank you I shall rebuild.
Since I have the INETMANET project open in the ws already is the
following from the IDE sufficient to rebuild?
select Project | Clean
select Project | Build all
On 21/02/2012 15:15, Rudolf Hornig wrote:
--
HANA Research Group, CRISTAL Laboratory
ENSI, University of Manouba, Tunisia
Andrew Hardy
Thank you again for your help and advice.
Further to our discussion, I built inet on its own from the IDE and go very similar error message boxes to those described previously for inetmanet. The libinet.dll file in \my_workspace\inet\src is 42KB. I tried to run a number of ini files in the manner already discussed and received similar error message boxes on every occasions. Two selected example images of the message boxes are attached.
Following this I cleaned the project from the IDE and opened mingwenv and issued the following commands:
make makefiles >> ../make_makefiles_output.txt
make >> ../make_output.txt
These two files are attached.
Unfortunately I omitted to redirect stderr and so I have included a copy and paste of stderr output (mostly warnings I think) in a separate file.
This occasion of building anything large for omnet was the only occasion when did not see the "couldn't commit memory for cygwin" build error described by others as a benign problem with mingwenv.
Following this build from the terminal window I carried out identical attempts to run omnet.inis with identical results.
I have installed omnet++ 4.2.1 but the same problem existed for 4.2
I am running Windows 7 x64
I really appreciate your advice in this Rudolph, I realise you will be busy. Also I appologise in advance if the cause of this error is something stupid on my part. If there is any other information which may help solve this issue please do not hesitate to request it.
Very Kind Regards,
Andrew
On 22/02/2012 09:57, Rudolf Hornig wrote:
INETMANET is a fork of INET meaninhg that you need only INETMANET (but not both). Inetmanet is more or less a superset of the INET framework. One possible test: just close INETMANET and try to build INET only and then check for libinet.dll there and see if the examples work. If the do, then the issue is INETMANET specific, if NO, then there may be an issue at operating system level (because OMNET's samples seem to work). Rudolf On Wed, Feb 22, 2012 at 10:43 AM, Andrew Hardy <a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk>> wrote: Thanks Rudolph, This makes a lot of sense. I shall concentrate on addressing the build issue. Not sure how to solve the 'couldn't commit memory for cygwin' problem though. One question though. I just want to check if my problem may be an embarrassingly simple one. Should I be installing omnet project followed by inet project followed by inetmanet project ?? This on the home page: "INETMANET is based on INET Framework (http://inet.omnetpp.org/) and continuosly developed. Generally it provides the same functionality as the INET Framework, but contains additional protocols and components that are especially useful while modeling wireless communication:" Make me think the answer to this question is NO. Neither the readme nor the install files in the root of the inetmanet project mention the word inetmanet so for "inet" in these files I have been reading "inetmanet" and so installing inetmanet on top of omnet++ only, not together with an inet project installation. Is this right? Many thanks, Andrew On 21/02/2012 21:20, Rudolf Hornig wrote: On Tue, Feb 21, 2012 at 9:37 PM, Andrew Hardy<a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk>>> wrote: If by what kind of failure you mean failure during the build then it is what others seem to be calling a mingwenv failure, ie C:\omnetpp-4.2\msys\bin\make.exe: *** couldn't commit memory for cygwin heap, Win32 error 0 Ok, I've never seen such an error on windows. It may be harmless, but OMNET was tested on Windows 7 and we have never seen similar errors. I am told this is the fault of mingwenv and is otherwise benign. I understand one is just supposed to carry on with the build any way. I shall try to get a zip of the build output. It is also suggested that the underlying cause of the simualtion error message box which is the main subject of this post is really to do with the 'name' ChannelControl not being channelControl What you think? In my ned file the name is channelControl No, the error you saw indicates that the code related the ChannelControl simple module is NOT available in the .DLL. The size of the .DLL supports this assumption too (it's just some 50KB, so it obviously cannot contain the inet code). The error occurred when OMNeT++ loaded the NED files and after that tried to instantiate the corresponding class. As long as your build result in a 50K .dll you always will receive the above error, so you must concentrate to fix the build process. Forget about the NED files, they are most likely fine. and the class is ChannelControl On 21/02/2012 20:03, Rudolf Hornig wrote: What kind of failure you got? In theory it should compile without any failure. It is also strange that resulting .dll file is so small, it should contain all the code on the linker command line. If you can capture the whole command output into a file, zip it and attach, I may take a look at the build process. Rudolf On Tue, Feb 21, 2012 at 5:50 PM, Andrew Hardy<a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk>><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk>>>> wrote: I rebuilt. During the build I got one mingwenv failure. I selected Project | Build All again to continue assuming it would see the objects that were already made and continue from where it left off. The dll is exactly the same as before. The last bit of the console output which I presume includes the linking is as follows: ... ... ... debug/src/transport/rtp/profiles/avprofile/RTPMpegPacket_m.o ../out/gcc-debug/src/transport/sctp/SCTPMessage_m.o ../out/gcc-debug/src/transport/tcp_common/TCPSegment_m.o ../out/gcc-debug/src/transport/udp/UDPPacket_m.o ../out/gcc-debug/src/underTest/linklayer/Ieee80216/ControlPlane/Ieee80216ManagementMessages_m.o ../out/gcc-debug/src/underTest/linklayer/Ieee80216/ControlPlane/Ieee80216Primitives_m.o ../out/gcc-debug/src/underTest/linklayer/Ieee80216/Mac/Ieee80216MacHeader_m.o ../out/gcc-debug/src/underTest/linklayer/Ieee80216/Mac/WiMAXRadioControl_m.o ../out/gcc-debug/src/world/powercontrol/PowerControlMessages_m.o ../out/gcc-debug/src/wpan/applications/Ieee802154TestApp/Ieee802154AppPkt_m.o ../out/gcc-debug/src/wpan/linklayer/bmac/bmacpkt_m.o ../out/gcc-debug/src/wpan/linklayer/ieee802154/contract/Ieee802154MacPhyPrimitives_m.o ../out/gcc-debug/src/wpan/linklayer/ieee802154/mac/Ieee802154Frame_m.o ../out/gcc-debug/src/wpan/networklayer/contract/Ieee802154NetworkCtrlInfo_m.o&&am p; ar cr .tmplib$$ @.tmp$$&& g++ -shared -o ../out/gcc-debug/src/libinet.dll -Wl,--no-as-needed .tmplib$$ -L"c:/omnetpp-4.2.1/lib/gcc" -L"c:/omnetpp-4.2.1/lib" -loppenvird -loppsimd -lwsock32 -lstdc++ -Wl,--enable-auto-import -shared-libgcc -L/usr/bin -L/usr/lib -Wl,-rpath,c:/omnetpp-4.2.1/lib -Wl,-rpath,.&& rm .tmp$$&& rm .tmplib$$ opp_shlib_postprocess ../out/gcc-debug/src/libinet.dll ln -sf ../out/gcc-debug/src/libinet.dll . make[1]: Leaving directory `/c/omnetpp-4.2.1/my_workspace/aarizaq-inetmanet-2.0-f7a4a48/src' **** Build Finished **** On 21/02/2012 15:21, Hardy, Andrew wrote: Thank you I shall rebuild. Since I have the INETMANET project open in the ws already is the following from the IDE sufficient to rebuild? select Project | Clean select Project | Build all On 21/02/2012 15:15, Rudolf Hornig wrote: On Tue, Feb 21, 2012 at 4:02 PM, Andrew Hardy<a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk>><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk>>><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk>><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk>>>>> wrote: Thank you so much for taking a look at this. Successfully built?: Dll file is: Size: 41.7 KB (42,731 bytes) Size on Disk: 44.0 KB (45,056 bytes) The build all from the IDE: Console indicated successful build This is definitely wrong. I'm sure the whole INETMANET codebase cannot fir into 42KB. Clean the INETMANET project, the rebuild. It should take quite a time. Check the output of the link step (should be somewhere at the end of the log). It must include all object files from INETMANET. There is something definitely wrong with your build configuration... Rudolf Present?: Yes it is present in C:\omnetpp-4.2.1\my_workspace\aarizaq-inetmanet-2.0-f7a4a48\src omnet's examples work?: I am not sure if I am making this check you suggest correctly but... open mingwenv run /c/omnetpp-4.2.1/samples/tictoc/tictoc.exe start simulation - success run /c/omnetpp-4.2.1/samples/neddemo/neddemo.exe start simulation - success, but 'no more events' immediately run /c/omnetpp-4.2.1/samples/fifo/fifo.exe tried all configurations start simulation - success for all 3 On 21/02/2012 14:20, Rudolf Hornig wrote: Are you sure the file libinet.dll is successfully built and is present in the projectroot/src folder? Do omnet's examples work correctly? Rudolf On Tue, Feb 21, 2012 at 3:04 PM, Andrew Hardy<a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk>><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk>>><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk>><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk>>>><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk>><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk>>><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk>><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk><mailto:a.h...@2009.ljmu.ac.uk<mailto:a.h...@2009.ljmu.ac.uk>>>>>> wrote: I cannot seem to find any other posts which help me with this problem When ever I launch an example by opening the example's directory in the Project Explorer view and finding the corresponding omnetpp.ini file, right clicking it and selecting Run As / Simulation, I get the following error message: Error in module during network setup: Class "ChannelControl" not found -- perhaps its code was not linked in, or the class wasn't registered with... Or something similar. After this I have tried Debug As / Simulation but get the same error. I have also tried from mingwenv cd examples/ and "./rundemo", but same error message I have had this problem for a while. One of the posts said the person solved it by installing 4.2.1 and rebuilding everything. I have Win7 x64 and I did the following I started my build again from scratch: Downloaded omnetpp-4.2.1 zip file and unzipped launched mingwenv ran ./configure , make makefiles, then make. Downloaded aarizaq-inetmanet-2.0-f7a4a48 zip file and unzipped created ws folder under omnetpp-4.2.1 put the aarizaq-inetmanet-2.0-f7a4a48 in workspace opened IDE using this workspace Import the project according to install instructions wait until the indexer finishes select Project | Build all The build stopped once with the common mingwenv problem restarted build, build finihsed Again I tried to run the examples but I get the same failure. Am I missing something here? Am I supposed to implement something else before I run these example? Am I following the installation instructions wrongly? Is there any other information about my environment or my installation actions that I could provide which might help highlight where I am going wrong? Any help or advice would be greatly appreciated. ________________________________ Important Notice: the information in this email and any attachments is for the sole use of the intended recipient(s). If you are not an intended recipient, or a person responsible for delivering it to an intended recipient, you should delete it from your system immediately without disclosing its contents elsewhere and advise the sender by returning the email or by telephoning a number contained in the body of the email. No responsibility is accepted for loss or damage arising from viruses or changes made to this message after it was sent. The views contained in this email are those of the author and not necessarily those of Liverpool John Moores University. -- Sent from the OMNeT++ mailing list. To configure your membership, visit http://groups.google.com/group/omnetpp
ANDREA GÓMEZ
Did you find any solution for this problem (channelControl and when
appear an error " " )??
I have the same problem and I could't find a solution...
I have win7 64 bits too.... and I tried some solutions that other
persons recommended to you but for me didn't work :S