$(OS) is CYGWIN but the /target/ OS is HP NonStop. 

A .so library suffix is generated by my cross-toolset for shared libs.  FWIW it registers .so as its suffix for SHARED_LIB.  The original problem was provoked by a prebuilt shared library that had no suffix at all.

Am I stuck with using <search> instead of <file> ? 

If I were to constrain all my "imported" / prebuilt libraries to have the .so suffix, would there be a way to trick bb2 into accepting such <file>s in a cross-development scenario like this?

I'm foggy on why bb2 doesn't just tag such library <file>s as <prebuilt> and be happy if the file exists.

Thanks,
Mark

Vladimir Prus <ghost@cs.msu.su> wrote:

Can you check what's the output of:

$ bjam -f-
ECHO $(OS) ;

is?