Bug 141747 - RPM package conflict
Summary: RPM package conflict
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: unspecified
Hardware: i586 Other
: P5 - None : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-06 11:05 UTC by David Lukacs
Modified: 2006-01-09 12:30 UTC (History)
1 user (show)

See Also:
Found By: Corporate Interoperability Test
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Lukacs 2006-01-06 11:05:28 UTC
I couldn't find more suitable place to send this post... i hope it gets to the right forum.

I use SUSE LINUX Enterprise Server 9 (i586). I have both
/suse/s390/glib-devel-1.2.10-586.1.s390.rpm
/suse/s390/glib2-devel-2.2.3-117.1.s390.rpm
installed.

glib-devel-1.2.10 package creates a symlink in ` /opt/gnome/include`  of `glibconfig.h` file.

It turned out to be impossible to compile a GTK2 application which uses the `glibconfig` header, because in the include path generated by autoconf the ` /opt/gnome/include` directory has precedence over others, thus the header provided by glib gets included instead of the glib2 one.

After removing the link, compilation succeeds.
Comment 1 Stanislav Brabec 2006-01-09 12:30:44 UTC
Link is not from upstream. It was added in install phase:

Thu Nov 30 11:34:23 MET 2000 - egger@suse.de

- Readded missing glibconfig.h link.

I guess it was invalid, because it is platform dependent and must be in platform dependent path. GLib1 based programs should use glib-config to properly include all files.

Fixing for 10.1 (Factory) and supplementary. This change is valid, but it can break some incorrect programs.