libpthread not found

This is the situation. 
Currently I run FreeBSD 7.1 installed from scratch on a free disk. The first problem started when I tried to install netbeans 6.1; when I realized that a new release (6.5) was available as a package, I uninstalled 6.1 and I "pkg_add -r" netbeans 6.5. Than I "pkg_delete" netbeans 6.5; later:
#portsnap fetch
#portsnap extract
#portsnap fetch update
but now netbeans 6.5 is not available in the port tree.
The strange behaviour of bash ended when I put the 'candidate' in it's original form in /etc/libmap.con.
More, I have to confess that I don't undestand Aryeh's suggestion:

"Then you will need to limit it to diablo only by placing it in the exec path in []'s"

I'm considering the possibility to install again, as this is an "experimental" installation. Maybe somethis went wrong ...
And, more, I'm having problems in upgrading from KDE 3.5 to KDE 4.

Thanks.
Marco
[snip]
>> thanks ... but ... how?
>> now I don't get the first message; but the second tells me that a library
>> is missing, but it is present. anyway I' prepared a very simple
>> /etc/libmap.conf like this:
>> 
>> # /etc/libmap.conf
>> #
>> # candidate             mapping
>> #
>> libc.so.6 		/usr/compat/linux/lib/libc.so.6
> 
> Change to:
> 
> libc.so.6			libc.so.7
>  
>> but clearly this is not enough. should I restart the system or use a
>> program to make the change accepted?
>> 
> 
> No need, it is picked up the next time the libmap.conf file is parsed.
> 
> What is occurring is the java binary was built against libc.so.6, which is
> what you would find on a FreeBSD 6.x box.
> 

>> amm ... when I change the 'candidate' something strange begins to happen:
>> bash doesn't work anymore, saying that it does not find the library. this
>> happens as soon as I do the change, showing what you've explained to me.
 

I am beginning to wonder if the problem isn't a little more involved. Did 
you upgrade the machine from FreeBSD 6.x to 7.x without rebuilding all your 
ports? With bash breaking it sounds like it was built for a 6.x box as well, 
which leads me to wonder how many other ports are the same way.

What you also might look into is installing the misc/compat6x port. However, 
in any event, we need to get down to the bottom of what happened to create 
the situation. The most obvious thing I can think of is an upgrade of the 
system from 6 to 7 without a corresponding rebuild or reinstall of all 
ports. 

-Mike