file system question

I was poking around in /usr/lib and did an ls -l.
It complained that libstdc++.a didn’t exist, i.e., I got:

ls: No such file or directory (libstdc++.a)

So I did an ls and libstdc++.a is listed.
I figured maybe it was a broken symbolic link but I should be able
to do an ls -l on it even if it is broken.

Any idea what is happening?

Carlos

Carlos Clarke <carlos@ptdprolog.net> wrote:

I was poking around in /usr/lib and did an ls -l.
It complained that libstdc++.a didn’t exist, i.e., I got:

ls: No such file or directory (libstdc++.a)

So I did an ls and libstdc++.a is listed.
I figured maybe it was a broken symbolic link but I should be able
to do an ls -l on it even if it is broken.

Any idea what is happening?

Carlos

Yes. This is caused by a bug in the C++ package. The package description
file tells the package manager that file should be included but the
physical file doesn’t exist in the package. ls -l does a stat on the
file so it discovers it doesn’t exist, but ls just lists the contents
of the directory so you see it then.

This has been fixed for the upcoming patch.

\

Keith Russell
QNX Software Systems