Case study:

Library not found

The problem:

One of our customers was running a complex build and they got a GCC ‘library not found’ error message.

Library not found - Firefox

The solution:

After a job has been traced in Breeze, double clicking on a program will open up a list of the arguments and environment for that program. You can see which environment variables have changed since the start of the trace.

Breeze also shows you which libraries have been found on your system and if any are missing.

The customer traced their program with Breeze and compared the failed open calls with the program environment settings. They found that an environment variable had been misconfigured and so GCC was looking in the wrong place.

The result:

Using the graph in Breeze they found the script that had set the incorrect variable and fixed it within minutes.