By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 1780

Summary:	Build issue: Not a UCOM library.
Product:	TDE	Reporter:	Darrell <darrella>
Component:	qt3	Assignee:	Timothy Pearson <kb9vqf>
Status:	RESOLVED FIXED
Severity:	normal	CC:	bugwatch, darrella, kb9vqf
Priority:	P5
Version:	R14.0.0 [Trinity]
Hardware:	Other
OS:	Linux
Compiler Version:		TDE Version String:
Application Version:		Application Name:

Description Darrell 2013-12-23 13:44:16 CST

When TQt3 is compiled using the -debug option rather than the -release option, many module build logs are filled with the following spew:

/opt/trinity/plugins/designer/libcppeditor.so: Not a UCOM library.
/opt/trinity/plugins/designer/libcppeditor.so: No exported component provided.
/opt/trinity/plugins/designer/libdlgplugin.so: Not a UCOM library.
/opt/trinity/plugins/designer/libdlgplugin.so: No exported component provided.
/opt/trinity/plugins/designer/libgladeplugin.so: Not a UCOM library.
/opt/trinity/plugins/designer/libgladeplugin.so: No exported component provided.
/opt/trinity/plugins/designer/libkdevdlgplugin.so: Not a UCOM library.
/opt/trinity/plugins/designer/libkdevdlgplugin.so: No exported component provided.
/opt/trinity/plugins/designer/librcplugin.so: Not a UCOM library.
/opt/trinity/plugins/designer/librcplugin.so: No exported component provided.
/opt/trinity/plugins/designer/libwizards.so: Not a UCOM library.
/opt/trinity/plugins/designer/libwizards.so: No exported component provided.

The libraries are installed by TQt3.

The sledge hammer approach is to remove the messages from TQt3, from which they originate. All packages are building without failure, but the fact that the -debug option is intended to help discover debugging issues, seems these messages should be investigated. The ideal solution is to resolve why these messages are generated.

Comment 1 Timothy Pearson 2013-12-26 22:44:29 CST

This might be due to the hidden symbols support--ucm_instantiate may be hidden in those libraries when it should not be.

Comment 2 Darrell 2013-12-27 16:15:13 CST

>This might be due to the hidden symbols support--ucm_instantiate may be hidden
>in those libraries when it should not be.
Woooooff. Something just flew over my head.

I hope your answer means the bug is fixable. :)

Comment 3 Timothy Pearson 2013-12-28 04:27:29 CST

(In reply to comment #2)
> >This might be due to the hidden symbols support--ucm_instantiate may be hidden
> >in those libraries when it should not be.
> Woooooff. Something just flew over my head.

The note was primarily for my reference. ;-)

> I hope your answer means the bug is fixable. :)

Yes, the bug is fixable.  It should be fixed in GIT hashes 586f373 (qt3) and cd689d4 (tqt3).  Please verify.

Thanks!

Comment 4 Darrell 2013-12-28 14:46:00 CST

I rebuilt all core packages through tdebase. All build logs are much quieter. Thank you!