[Ns-developers] Linking issues between modules in ns-3.11

[Mathieu Lacage]

On Tue, Feb 7, 2012 at 22:39, Kamakshi Sirisha Pathapati
<kamipks at ittc.ku.edu> wrote:
> I did look into the dependencies using ldd on the files within build/debug
> folder. Here is what I found:
>
> [kamipks debug]$ ldd libns3-aeronp.so
>        libns3-internet.so => not found
>        libns3-mesh.so => not found
>        libns3-wifi.so => not found
>        libns3-applications.so => not found
>        libns3-bridge.so => not found
>        libns3-mpi.so => not found
>        libns3-network.so => not found
>        libns3-core.so => not found
>        libns3-propagation.so => not found
>        libns3-config-store.so => not found
>        libns3-tools.so => not found
>        libns3-mobility.so => not found
>        libxml2.so.2 => /usr/lib64/libxml2.so.2 (0x00002b53a6cdd000)
>        libz.so.1 => /usr/lib64/libz.so.1 (0x00002b53a701a000)
>        librt.so.1 => /lib64/librt.so.1 (0x00002b53a722e000)
>        libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00002b53a7438000)
>        libm.so.6 => /lib64/libm.so.6 (0x00002b53a7738000)
>        libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00002b53a79bb000)
>        libpthread.so.0 => /lib64/libpthread.so.0 (0x00002b53a7bca000)
>        libc.so.6 => /lib64/libc.so.6 (0x00002b53a7de5000)
>        libdl.so.2 => /lib64/libdl.so.2 (0x00002b53a813c000)
>        /lib64/ld-linux-x86-64.so.2 (0x0000003ddf800000)

./waf shell

>
> I used the following lines in the wscript file to modify dependencies.
> After including 'aeronp' I see the ./waf does not build or display any
> build output.

Sometimes, build systems need a bit of hand-holding. rm -rf build &&
./waf should help.

Mathieu
-- 
Mathieu Lacage <mathieu.lacage at gmail.com>