Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 48954 - hsflinmodem fails to config if kernel has been compiled against >=gcc 3
Summary: hsflinmodem fails to config if kernel has been compiled against >=gcc 3
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-25 10:11 UTC by Corvus
Modified: 2004-04-25 10:20 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Corvus 2004-04-25 10:11:41 UTC
when the hsflinmodem ebuild is installed, it runs a script that compiles the kernel-dependant parts of the driver at the time of the first configure or usage.

the script tries to check which compiler the kernel had been compiled against (with some 'grep's in /proc/version), and then use same compiler to compile the source part of the driver module itself.

however with gcc >=3 used for kernel compilation both the check for the compiler  version (doe to changed syntax in the gcc version string (for example uppercase "-V"ersion instead of " v"ersion) and the compilation itself (when 1st had been worked around) (some inline-asm code is in form gcc 3 doesn't like) fails.

tested with gentoo-sources-2.4.20-r14 compiled with gcc 3.3.2

i guess the ebuild creator/maintainer should either
-- restrict the kernel and compiler version in dependencies
-- write a patch to work around the problems (guess it should be possible somehow to compile that stuff with gcc >=3.0, too)
-- write an ebuild for hsflinmodem >=6 which is non beta and maybe doesnt have these problems anymore

Reproducible: Always
Steps to Reproduce:
Comment 1 Corvus 2004-04-25 10:20:25 UTC
installed version of hsflinmodem was hsflinmodem-5.03.27.02122600
 suprisingly the bug was already fixed by Conexant in the slightly newer version
 so sorry for bothering

(note to self, check for newer versions marked instable first before writing bugs)