It is too early to send a service request - this isn't even beta software.
... and I have my own bugs to fix..
Just send the link to this thread to the person that released this code to the public. Don't you think Freescale should at least to some basic regression testing before releasing code? Many of your users would not have figured out what was wrong and simply gven up or figured your chips were buggy.
It might also help to have someone working on CW4linux that understands what dependencies are and how they are handled in the Linux world.
I will repeat what I wrote above - it is important that someone at Freescale listens to someone that knows a bit about Linux:
I really urge you guys to think about using the CURRENT and standard eclipse package and just have your parts available as plugins - installable via a standard deb package - (ALL the other distros can install these - the debs are by far the most popular system - the work-time involved in producing a proper package will be paid back several times because the dependencies are automatically handled and you will no longer have those as support issues). The package system can run scripts so you can still annoy your customers with your copy protection schemes.
I hope this comes accross as helpful - This might sound obvious, but we need tools for writing code that we can trust - I've spent more time dealing with CW bugs than my own bugs..