Bug 65133 - Unresolved symbols from drivers/video in some configurations
Unresolved symbols from drivers/video in some configurations
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
7.3
All Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-05-17 19:00 EDT by Michal Jaegermann
Modified: 2007-04-18 12:42 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-05-17 19:01:34 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
a patch to prevent unresolved fbgen_ symbols for vide drivers regardless of configuration (1.10 KB, patch)
2002-05-17 19:01 EDT, Michal Jaegermann
no flags Details | Diff

  None (edit)
Description Michal Jaegermann 2002-05-17 19:00:01 EDT
Description of Problem:

There is a compilation issue in 'drivers/video'.  Namely 'fbgen.o' is
used by some other objects ('pm2fb.o', 'pm3fb.o', 'clgenfb.o',
'tridentfb.o', 'tgafb.o', 'stifb.o').  Now if at least one of these
"users" is configured as built-in, implying that fbgen.o will be compiled
as an integral part of a kernel, and some other(s) as modules then you
will see from 'depmod' complaints about unresolved symbols for functions
provided by fbgen.  This actually hits, for example, when one tries to
use a default configuration on Alpha with 'tgafb' built-in.

A fix is obvious.  Add missing EXPORT_SYMBOL(...) to 'fbgen.c' and
'fbgen.o' to a list of export-objs in drivers/video/Makefile.
Attached is a patch for 2.4.18-4 sources.
Comment 1 Michal Jaegermann 2002-05-17 19:01:29 EDT
Created attachment 57804 [details]
a patch to prevent unresolved fbgen_ symbols for vide drivers regardless of configuration
Comment 2 Arjan van de Ven 2002-05-28 07:32:38 EDT
patch added

Note You need to log in before you can comment on or make changes to this bug.