Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 53298 - gtk+ 1.2.10-r11 silenlty compiles to faulty library when using -msse2 in CFLAGS
Summary: gtk+ 1.2.10-r11 silenlty compiles to faulty library when using -msse2 in CFLAGS
Status: RESOLVED DUPLICATE of bug 46944
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-08 05:03 UTC by Ákos Maróy
Modified: 2005-07-17 13:06 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ákos Maróy 2004-06-08 05:03:43 UTC 
when having the -msse2 flag in CFLAGS, gtk+ 1.2.10-r11 will compile, but the library will be faulty. for example, it won't display content in tabbed dialogs. see bug #52927 for more details on the error.

Reproducible: Always
Steps to Reproduce:
1. emerge gtk+ 1.2.10-r11 with -msse2 in CFLAGS
2. emerge gtkdiff, or gimp, or vmware, or other gtk programs
3. look at tabbed dialogs, like Settings->Preferences in gtkdiff, and see: nothing! :)

Actual Results:  
the tabbed dialogs all contain nothing when displayed

Expected Results:  
the tabbed dialogs should show their proper content.

see bug #52927 for additional information, as I first found this problem when
trying to run vmware. there are screenshots attached to that bug, displaying the
problem.
Comment 1 foser (RETIRED) gentoo-dev 2004-06-08 07:12:58 UTC 
this is not a gtk fault..



*** This bug has been marked as a duplicate of 46944 ***
Comment 2 Ákos Maróy 2004-06-08 07:18:47 UTC 
well, the GTK ebuild better watch form -msse2 in CFLAGS, and remove it when compiling....
Comment 3 Leonardo Boshell (RETIRED) gentoo-dev 2004-06-08 22:57:12 UTC 
CFLAGS are users responsability. For more info on this same issue, take a look at bug #50616.


*** This bug has been marked as a duplicate of 46944 ***