Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 45246

Summary: XFree86-4.1.0-0.5.9: unresolved symols in /usr/X11R6/lib/modules/fonts/libbitmap.a
Product: [Retired] Red Hat Raw Hide Reporter: Jonathan Kamens <h1k6zn2m>
Component: XFree86Assignee: Mike A. Harris <mharris>
Status: CLOSED DUPLICATE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0CC: redhat
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-06-21 03:12:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
my XF86Config-4 file
none
Log from failed X server run none

Description Jonathan Kamens 2001-06-21 01:33:08 UTC 
I finally decided to bite the bullet and try once again to upgrade from the
XFree86 3.3.6 Mach64 server to the XFree86 4 server with the ATI driver. 
The last time I tried this, quite a while ago, the results were so
disastrous that I was scared away from using the XFree86 4 server for quite
a while.

This time, Xconfigurator seemed to generate an XF86Config-4 file for me
with no problem.  However, when I tried to use it, to start the server, I
got a whole bunch of errors of the form "Symbol .LC2 from module
/usr/X11R6/lib/modules/fonts/libbitmap.a is unresolved!"  I am at a loss to
explain these.  I will attach my XF86Config-4 file and the log from the
failed server run.

Needless to say, I have reversed to the XFree86 3.3.6 server for the time
being :-).

Any advice?
Comment 1 Jonathan Kamens 2001-06-21 01:33:34 UTC 
Created attachment 21426 [details]
my XF86Config-4 file
Comment 2 Jonathan Kamens 2001-06-21 01:34:08 UTC 
Created attachment 21427 [details]
Log from failed X server run
Comment 3 Stephen Rasku 2001-06-21 03:12:52 UTC 
See bug 44954 as well.
Comment 4 Mike A. Harris 2001-07-03 01:09:37 UTC 
Yes this is a known problem which is due to changes in gcc that do not work
well with the X module loader.  A new package will be available before long,
please read the dupe bugs for details.

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