why doesn't libc++ on freebsd require a link to libc.so ?
On freebsd libstdc++.so doesn't link to libc.so, but it must call functions like open, close and so on. Why isn't it listed in the output of ldd below like it is say on Linux?

freebsd$ ldd libstdc++.so
libstdc++.so:
 libm.so.2 => /usr/lib/libm.so.2 (0x21113000)

linux$ ldd libstdc++.so.6
 linux-vdso.so.1 =>  (0x00007fff2d316000)
 libm.so.6 => /lib/libm.so.6 (0x00007fdd043e9000)
 libc.so.6 => /lib/libc.so.6 (0x00007fdd04066000)
 /lib64/ld-linux-x86-64.so.2 (0x00007fdd04995000)
 libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00007fdd03e4f000)

why doesn't libc++ on freebsd require a link to libc.so ?
===

On freebsd libstdc++.so doesn't link to libc.so, but it must call functions like open, close and so on. Why isn't it listed in the output of ldd below like it is say on Linux?

freebsd$ ldd libstdc++.so
libstdc++.so:
 libm.so.2 => /usr/lib/libm.so.2 (0x21113000)

linux$ ldd libstdc++.so.6
 linux-vdso.so.1 =>  (0x00007fff2d316000)
 libm.so.6 => /lib/libm.so.6 (0x00007fdd043e9000)
 libc.so.6 => /lib/libc.so.6 (0x00007fdd04066000)
 /lib64/ld-linux-x86-64.so.2 (0x00007fdd04995000)
 libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00007fdd03e4f000)
